You want a work-around for the keytables? Just copy /usr/lib/kbd to
/lib/kbd, unmount /usr then create /usr/lib and link/copy /lib/kbd to
it. When you boot, the /usr directory on the root partition will only
contain lib/kbd et al - not too much space taken but enough to get
loadkeys working; when you get to mounting all partitions, the
/usr partition will still successfully mount and hide your 'hack'. Works
for me with no changes to the init scripts.
Martin
On 16 Jan 2001, Trond Eivind Glomsrød wrote:
> Jean Francois Martinez <[EMAIL PROTECTED]> writes:
>
> > Windows was designed with crashes in mind so AFAIK it does not cache as much as
> > Linux do and repairs are faster. I still have to see the Windows repair
> > utilities prompt the user for what to do with inode number 152568. This
> > happens in Linux (it is not designed for crashing) and to add insult to injury
> > the keytables are not loaded when fsck happens because RedHat does not put a
> > copy of the keytable in / like Mandrake does so you have no national keyboard
> > unttil /usr is mounted. At times I wonder if there is a single RedHat employee
> > who knows there is people east of Rhode Island in the fabled countries of
> > France, United Kingdom and Germany. :-)
>
> Have you filed that in bugzilla?
>
>
--
===========================================================
_/ _/_/_/_/
_/_/ _/_/ _/
_/ _/_/ _/_/_/_/ Martin John Bartlett
_/ _/ _/ _/ Senior Technical Consultant
_/ _/_/_/_/ CSC Financial Services Group
_/ ([EMAIL PROTECTED])
_/ _/
_/_/
===========================================================
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
