Re: Debian conflicts with FHS on /usr/include/{linux,asm}
- To: Raul Miller <moth@magenta.com>
- Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>, joey@kitenet.net, shaleh@varesearch.com, fhs-discuss@ucsd.edu, debian-policy@lists.debian.org, quinlan@transmeta.com, t.sippel-dau@ic.ac.uk, moth@magenta.com
- Subject: Re: Debian conflicts with FHS on /usr/include/{linux,asm}
- From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
- Date: Wed, 14 Jul 1999 10:57:29 -0400
- Message-id: <[🔎] 199907141457.KAA01763@tsx-prime.MIT.EDU>
- In-reply-to: Raul Miller's message of Wed, 14 Jul 1999 09:17:37 -0400, <[🔎] 19990714091737.T21210@rdm.legislate.com>
Date: Wed, 14 Jul 1999 09:17:37 -0400
From: Raul Miller <moth@magenta.com>
Ok, but let's take this back into the arena of FHS. I hope that FHS
isn't only for naive users. [If FHS intends that distributions cannot
support users with multiple kernels I'm going to be very disappointed.]
According to the current FHS, as soon as you have a system which can
boot two distinct kernels, the system is not FHS compliant. This is a
bad thing, in my opinion.
But only one kernel can be the one which boots by default --- for
example, if you just type "return" at the LILO prompt.
It is also not naive-user-friendly to require the user to type a kernel
name each time the computer boots!
So which ever kernel boots by default when you power-on the machine and
don't type anything special to select a specific kernel should be the
one which /usr/src/linux points at. Is that really unreasonable?
- Ted
Reply to: