All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <fsdeveloper@yahoo.de>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: warning: process 'update' used the obsolete bdflush...
Date: Sun, 1 Jun 2003 22:09:05 +0200	[thread overview]
Message-ID: <200306012209.05634.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <1054495899.943.2.camel@teapot.felipe-alfaro.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 01 June 2003 21:31, Felipe Alfaro Solana wrote:
> "update" is not a program, but a kernel daemon that was superseded by
> pdflush in 2.5 kernels. I just can't remember right know what caused
> that warning, but it's similar to the SO_BSDCOMPAT warning that is
> triggered when running bind.

calling syscall bdflush() triggers this warning.
this syscall is obsolete.
Things can now be done through /proc/sys/vm

- -- 
Regards Michael Büsch
http://www.8ung.at/tuxsoft
 22:07:21 up  2:53,  3 users,  load average: 1.00, 1.07, 1.06

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+2l1hoxoigfggmSgRApnXAJkBfQw8CBVaUmJRuCNGA/8oZOAPygCfYREJ
sHauLAtZZfbcbAC+P9OL3BE=
=zBAB
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-06-01 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31  9:04 warning: process 'update' used the obsolete bdflush Paul Rolland
2003-05-31  9:34 ` Stewart Smith
2003-06-01 19:31   ` Felipe Alfaro Solana
2003-06-01 20:09     ` Michael Buesch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-31 10:53 mikpe
2003-05-31 11:51 ` Paul Rolland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200306012209.05634.fsdeveloper@yahoo.de \
    --to=fsdeveloper@yahoo.de \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.