.EDU] On Behalf Of
> Rick Troth
> Sent: Friday, November 08, 2002 4:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] More NSS Info
>
> > If you create a CMS file called PROGRA~1 DIR I'll have to murder
you.
>
> ;-)
>
> > Just so you know. Other than
Rick Troth <[EMAIL PROTECTED]> wrote:
>
> > 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 particula
> 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
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 ve
> 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
> dire
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 dynam
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
> 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 i
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
> mu
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 sh
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 /sb
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 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 an
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 C
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 t
> 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?
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, and
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
for this. We should use that as a model 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, N
Not really. If you use the cmsfs stuff, that information can all be on the
191 disk and read by the startup scripts.
Mark Post
-Original Message-
From: David Boyes [mailto:dboyes@;sinenomine.net]
Sent: Friday, November 08, 2002 11:23 AM
To: [EMAIL PROTECTED]
Subject: Re: More NSS Info
RIST.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 to create the NSS with just the
> boot disk and maybe
> swap configured in on the kernel parameter line, a
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 ri
I don't have the faintest idea why IBM claims that you have to have an
identical DASD layout on all machines that share an NSS.
Admittedly cursory testing seems to show that your NSS will have
whatever parameter line you burned into it, which does specify a range
of devices. But not only can thos
23 matches
Mail list logo
