Re: Local Multi-User X (?) problems

[Helge H. <hel...@ai...>]

On Thu, Oct 30, 2003 at 12:48:02PM +0100, Svetoslav Slavtchev wrote:
> 
> > Yes. I think I once read that if you build a kernel for a specific 
> > system, and there is something you use all the time, compile it into 
> > the kernel, if you use it just occasionally, compile it as a module. 
> 
> that's probably OK,
> but the question is whether the init scripts 
> can live with it
> 
Debian seems to cope.  I run a kernel with no module support at all.
(The module interface changed late in 2.5.xx, modules were unavailable
for a while anyway.)

> althougt what happens if you decide to change some hardware,
> filesystem ?
> 
Compile a new kernel.  You have to turn the machine off anyway
to install non-hotplug hardware.  You can precompile filesystems
that you think you might need in the future.  (Drivers too, but they
tend to have boring probe timeouts when the hw isn't there.)

> it's more flexible to have most hardware compiled as module's
> 
Sure - and a lot more hassle if you're running experimental kernels,
devfs, or drivers not yet supported by the distribution.

> > > > BTW, /proc/bus/usb/devices does not exist on my system,
> > >
> > > this is somewhat strange
> > > you must have it
> > 
> > OK... 
> > 
> probably your init script doesn't like
> built in support for usb,
> this is the case for mandrake as well
> if usb is built in the kernel, not as modules,
> service usb doesn't start -- it doesn't mount
> usbfs and there might be some issues with 
> certain usb drivers
> you probably have to mount it yourself then
> 
Put this in /etc/fstab:
none                  /proc/bus/usb usbfs   defaults                    0 0


Helge Hafting