Re: umass: should the device specific information be moved from C code to the text file?
- From: Ivan Voras <ivoras@xxxxxxxxxxx>
- Date: Fri, 29 Feb 2008 12:44:44 +0100
Peter Jeremy wrote:
This sounds like a nice idea - it's also a nuisance having to recompile
the kernel just to support a weird new USB device you've acquired.
You can probably keep USB support as a module if you need to recompile
it often :)
On the original topic: please don't do that. Recent ultra-modern Linux
systems have started offloading such critical kernel functionalities to
the userland, making it almost impossible to deal with when things go
bad (e.g. in single user mode). See also trouble ZFS has in single user
mode because it relies on files in the file system and a userland rc.d
script (hostid).
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- References:
- Prev by Date: Re: umass: should the device specific information be moved from C code to the text file?
- Next by Date: Re: problem with ldconfig
- Previous by thread: Re: umass: should the device specific information be moved from C code to the text file?
- Next by thread: Re: umass: should the device specific information be moved from C code to the text file?
- Index(es):
Relevant Pages
|