mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "gmu 2k6" <gmu2006@gmail.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>
Cc: "Andreas Mohr" <andi@rhlx01.fht-esslingen.de>,
	"Andrew Morton" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [WARNING -mm] 2.6.18-rc2-mm1 build kills /dev/null!?
Date: Thu, 27 Jul 2006 14:24:51 +0000	[thread overview]
Message-ID: <f96157c40607270724v40f1db96q19d1c206b12bb7e0@mail.gmail.com> (raw)
In-Reply-To: <f96157c40607270724n72234492n9a34accca6512e91@mail.gmail.com>

On 7/27/06, gmu 2k6 <gmu2006@gmail.com> wrote:
> On 7/27/06, Michael Tokarev <mjt@tls.msk.ru> wrote:
> > Andreas Mohr wrote:
> > > Hello all,
> > >
> > > for some reason a 2.6.18-rc2-mm1 build seems to kill my /dev/null device!
> > >
> > > A simple
> > > # make bzImage modules modules_install
> > > managed to reduce my
> > >
> > > crw-rw-rw-    1 root     root       1,   3 27. Jul 12:04 null
> > >
> > > into the charred remains equivalent of
> > >
> > > -rw-r--r--    1 root     root            0 27. Jul 12:02 null
> >
> > Don't build as root.
> >
> > While something's broke in kernel build scripts and probably
> > should be fixed, it's not a reason for anyone to get their
> > whole filesystem rm -rf'ed.
>
> and it does not matter if you're using udev:
> $ ls -l /dev/null
> crw-rw-rw- 1 root root 1, 3 2006-07-27 11:42 /dev/null

actually this is so obvious I should not have posted that reply. sorry guys.

      reply	other threads:[~2006-07-27 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 10:11 Andreas Mohr
2006-07-27 10:17 ` Andreas Mohr
2006-07-27 11:22   ` Andreas Mohr
2006-07-27 14:19 ` Michael Tokarev
2006-07-27 14:24   ` gmu 2k6
2006-07-27 14:24     ` gmu 2k6 [this message]

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=f96157c40607270724v40f1db96q19d1c206b12bb7e0@mail.gmail.com \
    --to=gmu2006@gmail.com \
    --cc=akpm@osdl.org \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®