linux-kernel - Re: how to have the kernel do udev's job and autoload the right modules ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 07 May 2015 08:04:40 -0400
From:	Austin S Hemmelgarn <ahferroin7@...il.com>
To:	David Lang <david@...g.hm>,
	linuxcbon linuxcbon <linuxcbon@...il.com>
CC:	Ken Moffat <zarniwhoop@...world.com>,
	Richard Weinberger <richard@....at>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: how to have the kernel do udev's job and autoload the right modules
 ?

On 2015-05-06 16:49, David Lang wrote:
> On Wed, 6 May 2015, linuxcbon linuxcbon wrote:
>
>> On Wed, May 6, 2015 at 7:53 PM, David Lang <david@...g.hm> wrote:
>>> It's perfectly legitimate to not want to use udev, but that doesn't mean
>>> that the kernel will (or should) do it for you.
>>> David Lang
>>
>> When I boot the kernel without modules, I don't have anything working
>> except "minimal video".
>> I think the kernel should give a minimal support for network, sound and
>> video, even if 0 modules are loaded. I am just dreaming,
>
> You can do that, you just need to build in all the network and sound
> drivers (and pick which driver in the case of conflicts)
>
> There isn't such a thing as a 'generic' network or sound card. For video
> there is 'VGA video' which is used by default on x86 systems, but even
> that's a driver that could be disabled.
>
To explain further, video has a standardized hardware level API (VGA and 
VBE) because it is considered critical system functionality (which is BS 
in my opinion, you can get by just fine with a serial console, but 
that's irrelevant to this discussion).  Sound is traditionally not 
considered critical, and therefore doesn't have a standardized hardware 
API.  Networking is (traditionally) only considered critical if the 
system is booting off the network, and therefore only has a standardized 
API (part of the PXE spec, known as UNDI) on some systems, and even then 
only when they are configured to netboot (and IIRC, also only when the 
processor is in real mode, just like for all other BIOS calls).


Download attachment "smime.p7s" of type "application/pkcs7-signature" (2967 bytes)