mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: Re: cerberus errors on 2.4.19 (ide dma related)
Date: Sun, 18 Aug 2002 19:36:47 +0100	[thread overview]
Message-ID: <6uhehsui80.fsf@zork.zork.net> (raw)
In-Reply-To: <1029695363.1357.5.camel@psuedomode> (Ed Sweetman's message of "18 Aug 2002 14:29:23 -0400")

commence  Ed Sweetman quotation:

> On Sun, 2002-08-18 at 14:20, Sean Neakums wrote:
>> commence  Ed Sweetman quotation:
>> 
>> > It appears i'm completely unable to not use devfs.  Attempting to
>> > run the kernel without mounting devfs results in it still being
>> > mounted or if not compiled in, locks up during boot.  Attempts to
>> > run the kernel and mv /dev does not work, umounting /dev does not
>> > work and rm'ing /dev does not work.  I cant create the non-devfs
>> > nodes while devfs is mounted and i cant boot the kernel without
>> > devfs.  It seems that no uninstall procedure has been made and i've
>> > read the documentation that comes with the kernel about devfs and it
>> > says nothing about how to move back to the old device nodes from
>> > devfs.
>> >
>> > anyone have any suggestions?
>> 
>> Where does the boot hang?  If it comaplains about not being able to
>> open /dev/console or some other device node, it may be that your /dev
>> has no nodes in it.  This happened to me when I eradicated devfs (I
>> got fed up of fighting with devfsd to get my permission changes to
>> stick, and had reshuffled FSes in the meantime) and so I booted from a
>> rescue disk, mounted my root FS and recreated the device nodes in
>> /mnt/dev.
>> 
>
> I know i have no device nodes.  I removed them all before installing
> devfs.

You must have been really keen on devfs.

> the devfs documentation says it doesn't need to have devfs mounted
> to work, but this doesn't seem to be true at all.

If it does say exactly that, then it is outrageously wrong.

> Hence my confusion. I know i can go download a bootable iso and get
> that burned and working but I shouldn't have to do that.

Uh, you deleted your devices nodes, and now you want to boot the
system without devfs.  You have to do precisely that, or something
equivalent.

-- 
 /                          |
[|] Sean Neakums            |  Questions are a burden to others;
[|] <sneakums@zork.net>     |      answers a prison for oneself.
 \                          |

  reply	other threads:[~2002-08-18 18:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  6:44 Ed Sweetman
2002-08-18  7:15 ` Ed Sweetman
2002-08-18  9:19   ` Andre Hedrick
2002-08-18 18:11     ` Ed Sweetman
2002-08-18 18:31     ` Ed Sweetman
2002-08-18  7:26 ` Ed Sweetman
2002-08-18  9:00   ` Barry K. Nathan
2002-08-18  9:13     ` Ed Sweetman
2002-08-18 17:50   ` Jonathan Lundell
2002-08-18 18:04     ` Ed Sweetman
2002-08-18  9:10 ` Alexander Viro
2002-08-18  9:16   ` Ed Sweetman
2002-08-18 18:10     ` Ed Sweetman
2002-08-18 18:20       ` Sean Neakums
2002-08-18 18:29         ` Ed Sweetman
2002-08-18 18:36           ` Sean Neakums [this message]
2002-08-18 21:53             ` Barry K. Nathan
2002-08-18 22:26               ` devfs Ed Sweetman
2002-08-18 22:47                 ` devfs Sean Neakums
2002-08-18 23:03                 ` devfs Alexander Viro
2002-08-18 23:15                   ` devfs Ed Sweetman
2002-08-21  4:49                     ` devfs Richard Gooch
2002-08-21  5:03                       ` devfs Ed Sweetman
2002-08-19  1:06                   ` devfs Olivier Galibert
2002-08-19  2:01                     ` devfs Greg KH
2002-08-18 23:18                 ` devfs Barry K. Nathan
2002-08-18 22:41           ` cerberus errors on 2.4.19 (ide dma related) Andrew Rodland
2002-08-18 22:55             ` Ed Sweetman
2002-08-19 21:46               ` Ed Sweetman
2002-08-18 19:53       ` Ed Sweetman
2002-08-18 20:07         ` Andre Hedrick
2002-08-18 20:29           ` Ed Sweetman
2002-08-23  0:03             ` Samuel Flory
2002-08-19  0:06       ` Denis Vlasenko

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=6uhehsui80.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --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

all inboxes | Powered by JetHome®