linux-kernel - Re: linux kernel without file system

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]

Message-ID: <20090114093422.GA9771@frolo.macqel>
Date:	Wed, 14 Jan 2009 10:34:22 +0100
From:	Philippe De Muyter <phdm@...qel.be>
To:	Tomasz Chmielewski <mangoo@...g.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux kernel without file system

On Wed, Jan 14, 2009 at 09:46:48AM +0100, Tomasz Chmielewski wrote:
>> I need to design a very small embedded system that must only control
>> one ethernet port and two serial lines and must fit in a very small flash
>> memory.  So I thought about replacing the call to /etc/init by my 
>> application
>> program and removing all the file-system part of linux.
>> Is that doable ?
>> Is there a 'standard' way of doing that ?
>> The first problem I see is accessing my serial lines.  How could I do that
>> without using open("/dev/ttySx"), which requires a file system ?
>> Is there a way to access devices that does not require a file-system ?
>
> You could put everything in initramfs (and embed it in the kernel).

Actually, I was thinking about reducing the footprint of my kernel by
removing all the fs-related system calls, so the problem is not where
the file-system is, but how to access (serial) devices without giving their
"/dev/..." name.

Thanks anyway

Philippe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/