Would it not be sufficient to create the NSS with just the boot disk and maybe
swap configured in on the kernel parameter line, and then using something very
early on in the boot process to add the other disks using /proc/dasd/devices?
It might take some work to get the NSS and RO boot disk just
]On Behalf Of
Kris Van Hees
Sent: Friday, November 08, 2002 11:00 AM
To: [EMAIL PROTECTED]
Subject: Re: More NSS Info
Would it not be sufficient to create the NSS with just the
boot disk and maybe
swap configured in on the kernel parameter line, and then
using something very
early on in the boot
for
ideas.
-- db
David Boyes
Sine Nomine Associates
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390;VM.MARIST.EDU]On Behalf Of
Kris Van Hees
Sent: Friday, November 08, 2002 11:00 AM
To: [EMAIL PROTECTED]
Subject: Re: More NSS Info
Would it not be sufficient
On Fri, 8 Nov 2002, David Boyes wrote:
Much as I dislike Solaris, their diskless workstation filesystem layout
is a pretty good model for this. We should use that as a model for
ideas.
They also demonstrated the first shared /usr implementation.
They also do something I call folding (for
PROTECTED]
[mailto:owner-linux-390;VM.MARIST.EDU]On Behalf Of Kris Van Hees
Sent: Friday, November 08, 2002 10:00 AM
To: Linux on 390 Port
Subject: Re: More NSS Info
Would it not be sufficient to create the NSS with just the boot disk and
maybe
swap configured in on the kernel parameter line
If you use the cmsfs stuff, that information can all be on the
191 disk and read by the startup scripts.
What about a CMSFS that can do directories and specials (device files)
akin to the UMSDOS hack?
On Fri, 8 Nov 2002, Kris Van Hees wrote:
Despite what Sun Microsystems did with linking /usr/bin and /usr/sbin
into the root filesystem as /bin and /sbin, a more sensible setup is
still to have the core utilities that are required to boot a system
(and to do basic maintenance) as part of the
On Fri, Nov 08, 2002 at 10:58:30AM -0600, Rick Troth wrote:
If you use the cmsfs stuff, that information can all be on the
191 disk and read by the startup scripts.
What about a CMSFS that can do directories and specials (device files)
akin to the UMSDOS hack?
If you create a CMS
On Fri, Nov 08, 2002 at 01:15:01PM -0500, Adam Thornton wrote:
On Fri, Nov 08, 2002 at 10:58:30AM -0600, Rick Troth wrote:
If you use the cmsfs stuff, that information can all be on the
191 disk and read by the startup scripts.
What about a CMSFS that can do directories and
David Boyes writes:
You would need at least one non-root/swap address mounted as /config or
something for storing the configuration of what goes where, and you'd
have to move at least a few of the utilities (eg mount, ifconfig, etc)
from /usr to /sbin (generating statically linked versions)
On Fri, Nov 08, 2002 at 11:23:25AM -0500, David Boyes wrote:
You would need at least one non-root/swap address mounted as /config or
something for storing the configuration of what goes where, and you'd
have to move at least a few of the utilities (eg mount, ifconfig, etc)
from /usr to /sbin
On Fri, Nov 08, 2002 at 10:52:52AM -0600, Rick Troth wrote:
On Fri, 8 Nov 2002, David Boyes wrote:
Much as I dislike Solaris, their diskless workstation filesystem layout
is a pretty good model for this. We should use that as a model for
ideas.
They also demonstrated the first shared
On Fri, Nov 08, 2002 at 12:24:13PM -0500, Kris Van Hees wrote:
I would *love* to see a CMSFS that can support things like device files so
we can finally put /dev somewhere other than the root filesystem, so / can
truly be made RO. I worked on that using initrd, but cmsfs would be so
much
You would need at least one non-root/swap address mounted
as /config or
something for storing the configuration of what goes where,
and you'd
have to move at least a few of the utilities (eg mount,
ifconfig, etc)
from /usr to /sbin (generating statically linked versions)
and include
On Fri, Nov 08, 2002 at 02:16:47PM -0500, Matt Zimmerman wrote:
On Fri, Nov 08, 2002 at 12:24:13PM -0500, Kris Van Hees wrote:
I would *love* to see a CMSFS that can support things like device files so
we can finally put /dev somewhere other than the root filesystem, so / can
truly be made
On Fri, Nov 08, 2002 at 03:09:54PM -0500, Kris Van Hees wrote:
I worked on a RO / before (presented briefly at SHARE in TN), and
unfortunately Linux has (or had - they may have fixed it) a C library that
usesthe Unix domain socket /dev/log for syslog handling, and that one is
created
If you create a CMS file called PROGRA~1 DIR I'll have to murder you.
;-)
Just so you know. Other than that, sure, sounds like a plan--I assume
you mean that you use some filesystem convention like a file which
always has some particular name, which contains a CMS filename to Unix
On Fri, Nov 08, 2002 at 02:44:19PM -0500, David Boyes wrote:
What distribution are you using which places these utilities in /usr?
Sorry, finger check. I date back far enough that everything was in or near
/usr... thanks. Meant to say from their default location.
I do not date back very far
This folding, as far as I know, is just a couple of symlinks, from /bin to
/usr/bin and from /lib to /usr/lib. Doing the same thing on a typical Linux
Specifically, running 'ls -l' in root, you see
bin - usr/bin
lib - usr/lib
If memory serves, you do NOT
Hello from Gregg C Levine
And if you murder him, I'll be forced to use my Jedi Knight functions to
send you to Kessel. Just going along with it, Rick.
---
Gregg C Levine [EMAIL PROTECTED]
The Force will be with
20 matches
Mail list logo
