initscripts: font fix && modules

[Jasper Huijsmans]

Op 2003-11-06 14:05:55 schreef nestu:
> Hi ;)
> a ) fonts: rc.sysinit has erroneously /bin/loadkeys and not /usr/bin/
> loadkeys as Lunar has, so:
> 
> 	if [ "$CONSOLETYPE" = "vt" -a -x /bin/loadkeys ]; then
> 
> 
> has to be changed to		
> 
> 	if [ "$CONSOLETYPE" = "vt" -a -x /usr/bin/loadkeys ]; then
> 	

No, loadkeys has to be moved ot /bin. /usr may not have been mounted  
yet.

> As a side note, to get stuff working as before the new initscripts,  
> and
> after changing the loadkeys path in rc.sysinit, I set (in my case  
> spanish
> environment):
> 
> 	* /etc/sysconfig/keyboard: export KEYMAP=es
> 	that will (in my case) do "loadkeys es" when I see "Loading  
> default
> keymap" on boot.
> 	
> 	* /etc/sysconfig/i18n: export SYSFONT=lat0-16
> 	that will run (in my case) "consolechars -f lat0-16", echoing  
> "Setting
> default font" boot msg.
>

Are the 'export's required? I would think just setting the variable  
should
work.

> b ) Why is /etc/modules left out of new installs? In modutils'  
> POST_INSTALL
> we still get a message to use this file (for non new initscripts  
> users, I
> suppose). It has been now disabled by the not install of a init.d/ 
> modutils
> file from module-init-tools or modutils. That init.d/modutil file  
> cycled
> through /etc/modules modprobing all listed modules. This file used to  
> be
> installed, and linked from /etc/rcS.d/S20modutils, so it was executed  
> on
> boot. Should we now only use an alias from /etc/modules.conf, like  
> for
> example as done in /etc/rc.sysinit for sound? What if we want to load  
> a
> module that is not loaded specifically in rc.sysinit ?
>

You are right, this functionality is still missing. I wonder how redhat
handles this, through kudzu perhaps?. csm said he preferred a separate
initscript for this, so we could adapt the current script to run early  
in the
startup for all runlevels, but that may be a bit late.

The rc.sysinit script does have a line about running /etc/rc.modules  
for
backward compatibility. I could add the module loading there.

In fact, that may make all the other module probing in rc.sysinit  
redundant.
It does put the responsibility for loading the correct modules in the  
hands of
the user/admin, but that sounds like a good thing anyway.

Anyone else have an opinion on this?

	Jasper