From: Nick <nick@linicks.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Alexander Fieroch <fieroch@web.de>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.16rc2] compile error
Date: Fri, 3 Feb 2006 19:29:05 +0000 [thread overview]
Message-ID: <7c3341450602031129t1770fa9ao@mail.gmail.com> (raw)
In-Reply-To: <20060203190126.GA28929@mars.ravnborg.org>
> You are hit be an outstanding issue with -rc1 + rc2.
> When you build as root you will alter /dev/null and in your case it
> became a regular file.
>
> Recreate /dev/null and build as normal user for now.
> You can apply patch below to fix it - will be in next -rc.
Although this is fixed, can/should /dev/null be made immutable? I
presume the whole system relies on it...
Nick
next prev parent reply other threads:[~2006-02-03 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 18:55 [2.6.16rc2] compile error Alexander Fieroch
2006-02-03 19:01 ` Alex Romosan
2006-02-03 19:54 ` Alexander Fieroch
2006-02-03 20:56 ` Alex Romosan
2006-02-03 20:59 ` Alexander Fieroch
2006-02-03 19:01 ` Sam Ravnborg
2006-02-03 19:29 ` Nick [this message]
2006-02-03 19:47 ` Gene Heskett
2006-02-03 20:04 ` Sam Ravnborg
2006-02-04 3:30 ` Gene Heskett
2006-02-04 3:32 ` Gene Heskett
2006-02-03 19:35 ` Gene Heskett
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=7c3341450602031129t1770fa9ao@mail.gmail.com \
--to=nick@linicks.net \
--cc=fieroch@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox