Re: Why no package seems to take care of the new /dev/console device?
On Sat, Jan 29, 2000 at 11:10:31AM -0500, Daniel Burrows wrote:
> I have no idea what should be done, but if it's decided that
> replacing the console device is correct..
>
> On Sat, Jan 29, 2000 at 05:53:30PM +0200, Shaul Karl was heard to say:
> > 2) Decide what current users (slink users) should do. Is it simply a
> > matter of rm slink /dev/console and MAKEDEV the new /dev/console and
> > that is all? What will be the consequences of doing these rm and
> > MAKEDEDV on a running system?
>
> I'd assume that the only problem is that programs might try to open
> /dev/console in the brief timespan that it's gone..would it be
> sufficient to just MAKEDEV the new console in another directory on
> the same filesystem, then mv it to /dev/console? (mv should use
> rename, which is atomic)
>
> Daniel
>
FYI, I just updated my /dev/console as discussed here, then ran
$ xconsole -file /dev/xconsole &
and it works like a charm.
$ xconsole -file /dev/console &
returns the same "Couldn't open console", as just running "xconsole &"
Also, anyone know if the perms on /dev/console should be:
crw------- root tty /dev/console ?? (Seems okay)
--
+----------------------------------------------------+
| Eric G. Miller egm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc |
+----------------------------------------------------+
Reply to: