Let's get to the core problem

jan at helga.lk.etc.tu-bs.de jan at helga.lk.etc.tu-bs.de
Sun Jun 25 05:33:31 PDT 2000


Hi All,


On Sat, Jun 24, 2000 at 03:12:34PM -0700, Eric A. Ayer wrote:
[...]
> Some thoughts on the bootable CD:  First, the files included on the CD should,
> in my humble opinion, be limited to those that are necessary for booting and
> compiling the sources (plus the sources themselves).  Unneeded programs would

& (c)fdisk & e2fsprogs
& the network stuff comes lateron...
just to remember this

> be un-included.  That means going through each package and picking out what is
> needed and what is not.  More on this later.  Second, keep in mind that ISO
> images are not capable of supporting links, hard or soft, and we're going to
> need those, so a purely ISO boot system may not work.
[...]
> Should we implement LSB in this?  I really like the idea of a standard base,
> and I see why it is needed (badly).  However, I don't want to create a
> standard base that is designed purely for one set of vendors, namely, the
> database vendors.  If the standard base is created, it should provide a common
> system that can be used for many applications, providing a stable environment
> for all of them.  Now the DB guys aren't going to like that statement, but just
> keep in mind that, if LSB promotes a system that runs DB and nothing else,
> nobody's going to use it.

:)

> I would think that DB only needs a basic system to run on, pretty much where
> the LFS project (officially) stops.  The kernel, init, and basic utilities may
> be all that is needed for LSB, and if basic networking and some form of X are
> needed, that's ok too.  Specifying an entire filesystem layout that is not
> compatible with other apps would be way too much, but requiring a few things
> may be ok.

what about an LSB- mode ?

In the hope that it's worth it...

[...]
> Related to this last item, I have a shell programming question.  I wanted to
> write a shell function to copy directories from one place to another recurs-
> ively, creating sub-dirs as needed and checking for overwrites.  This is one
> of those functions in vars.  I found that shell functions can't be recursive,
> so I need to get a directory listing into a shell variable and step through
> each item.  Easy enough to create the variable - dirvar=`ls`.  But how do you
> get one item out of that variable?  I remember doing this before, sucking out
> one word from the variable, but I can't remember how.  Any ideas?

with
'find $PATH -type d|tac'
you will get the directories in a 'recursive' order.

-- 
regards,
Jan Niemann
--
Mail archive: http://www.pcrdallas.com/mail-archives/alfs-discuss
IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
Unsubscribe: email alfs-discuss-request at linuxfromscratch.org and put
"unsubscribe" (without the quotation marks) in the body of the message
(no subject is required)



More information about the alfs-discuss mailing list