public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@speakeasy.net>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cerberus errors on 2.4.19 (ide dma related)
Date: 18 Aug 2002 14:10:34 -0400	[thread overview]
Message-ID: <1029694235.520.9.camel@psuedomode> (raw)
In-Reply-To: <1029662182.2970.23.camel@psuedomode>

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?




On Sun, 2002-08-18 at 05:16, Ed Sweetman wrote:
> On Sun, 2002-08-18 at 05:10, Alexander Viro wrote:
> > 
> > 
> > On 18 Aug 2002, Ed Sweetman wrote:
> > 
> > > (overview written in hindsight of writing email)  
> > > I ran all these tests on ide/host2/bus0/target0/lun0/part1 
> > 
> > Don't be silly - if you want to test anything, devfs is the last thing
> > you want on the system.
> > 
> > 
> 
> 
> OK, i can remove devfs, but I dont really see how that would make dma
> transfers (memory) become corrupted and pio mode transfers (memory) to
> not.  
> 
> I'm going to remove it, but i dont see how it's going to affect what's
> going on. 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



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

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  6:44 cerberus errors on 2.4.19 (ide dma related) 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 [this message]
2002-08-18 18:20       ` Sean Neakums
2002-08-18 18:29         ` Ed Sweetman
2002-08-18 18:36           ` Sean Neakums
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=1029694235.520.9.camel@psuedomode \
    --to=safemode@speakeasy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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