Re: /dev/console wrong on upgraded systems (2.0 -> 2.1)
On %M 0, Ralf G. R. Bergs wrote
> On Mon, 26 Apr 1999 16:30:51 +0000, Lazarus Long wrote:
>
> [...]
> >If I add 2.2.x to lilo at some point, choosing between 2.0.36 and 2.2.x
> >at boot will not be adequate? (This is what I've suspected, but been
> >told otherwise.)
>
> I *think* 2.0.36 is a kernel version that also/already understands the new
> device nodes. When I upgraded my Debian 2.0 system (running kernel 2.0.36 if
> I'm not mistaken) to kernel 2.2.x I did NOT have to update the device nodes
> (except from /dev/console as I learnt these days.) However my ancient
> Slackware 2.1(?) system needed to be upgraded.
>
Another issue is that printer device names change with 2.2 kernels; what
was lp1 becomes lp0, so if you have a printer and want to choose between
2.0.x and 2.2.x at boot time, you will have to select a suitable printcap
using symlinks or somesuch in your startup scripts.
John P.
--
huiac@camtech.net.au
john@huiac.apana.org.au
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
Reply to: