[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Why no package seems to take care of the new /dev/console device?



Filip Van Raemdonck wrote:
> On Sat, Jan 29, 2000 at 04:14:41PM -0600, Stephen R . Gore wrote:
> > Karl M. Hegbloom wrote:
> > > >>>>> "Shaul" == Shaul Karl <shaulk@israsrv.net.il> writes:
> > > 
> > >     Shaul> Is it simply a matter of rm slink /dev/console and MAKEDEV
> > >     Shaul> the new /dev/console and that is all? What will be the
> > >     Shaul> consequences of doing these rm and MAKEDEDV on a running
> > >     Shaul> system?
> > > 
> > >  That's what I did.  There's code in MAKEDEV that tests the running
> > >  kernel version, and does the right thing based on that.  I don't
> > >  think you have to rm the old one first; just run `MAKEDEV console'.
> > > 
> > >  Actually, on a formerly `slink' system upgraded to kernel 2.2.x, I
> > >  think you should run `MAKEDEV generic' once.  There are probably
> > >  other devices it needs to update.
> >                              ^^^^^^
> > 
> > Indeed, there is a "MAKEDEV update" option.  Just scanning the script
> > seems to indicate it *might* do the right thing.  Can someone with
> > more familiarity with the MAKEDEV script comment on this?
> > 
> Just a question... what are the correct permissions for /dev/console? I found it
> to be 622 on my system... these look rather unusual to me, at least.
> 

Same here. (potato installed from boot-floppies v2.2.4)

Regards,

Steve

Attachment: pgpWPPJwfFw6q.pgp
Description: PGP signature


Reply to: