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: <20090114144937.GA21043@frolo.macqel>
Date:	Wed, 14 Jan 2009 15:49:38 +0100
From:	Philippe De Muyter <phdm@...qel.be>
To:	David Newall <davidn@...idnewall.com>
Cc:	Tomasz Chmielewski <mangoo@...g.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux kernel without file system

On Thu, Jan 15, 2009 at 12:57:55AM +1030, David Newall wrote:
> Philippe De Muyter wrote:
> > 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.
> 
> That's fighting the UNIX design, in "which everything is a file."  You
> can remove all of the disk-based filesystems, but if you try to remove
> open, close, read or write there'll be almost nothing that you can
> usefully do.

Of course, I need read, write and ioctl and socket and friends but I do not
need open, creat, link, rename etc.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ