From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Alexander Fieroch <fieroch@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.16rc2] compile error
Date: Fri, 03 Feb 2006 12:56:28 -0800 [thread overview]
Message-ID: <87vevw6u0z.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <ds0ce1$dma$1@sea.gmane.org> (message from Alexander Fieroch on Fri, 03 Feb 2006 20:54:41 +0100)
Alexander Fieroch wrote:
> Alex Romosan wrote:
>> look at /dev/null. on my system it keeps getting replaced by a regular
>> file. not really sure where the bug is, but 'cd /dev; ./MAKEDEV null'
>> will recreate the null character device and then the compilation will
>> proceed normally.
>>
>> --alex--
>
> Thanks, that's it. /dev/null was replaced by a regular file.
> Hm, /dev/MAKEDEV null and /dev/MAKEDEV std didn't rebuild the character
> device null... but a reboot did.
you are probably running udev or something like that which generates
the devices automagically...
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
next prev parent reply other threads:[~2006-02-03 20:56 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 [this message]
2006-02-03 20:59 ` Alexander Fieroch
2006-02-03 19:01 ` Sam Ravnborg
2006-02-03 19:29 ` Nick
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=87vevw6u0z.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=fieroch@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox