On 05 Jun 2005, you wrote in lfs.support:
> On Sat, 4 Jun 2005, Matthew Burgess wrote:
>
>>
>> Ken, FWIW my scripts do the following to avoid scanning paths that won't
>> (or shouldn't!) see any changes during a build:
>>
>> find . -xdev ! -path "./logs/*" ! -path "./home/*" ! -path "./proc/*" \
On Sat, 4 Jun 2005, Matthew Burgess wrote:
>
> Ken, FWIW my scripts do the following to avoid scanning paths that won't
> (or shouldn't!) see any changes during a build:
>
> find . -xdev ! -path "./logs/*" ! -path "./home/*" ! -path "./proc/*" \
>! -path "./sources/*" ! -path "./tmp/*" ! -path
Ken Moffat wrote:
The repeated grep -v invocations sure burn up CPU cycles, but for me
its worth it to remove _most_ of the irrelevant changes. When I do this
for blfs on a running system there are still occasional irrelevant
changes, e.g. to /etc/ntp.drift, so use with care.
Ken, FWIW my sc
On Sat, 4 Jun 2005, Ag Hatzim wrote:
>
> To create the log file you can use the log-install or paco or just use
> this simplier but a little more dangerous way. Use the find command to
> make a log of your system *before* you built the package and one more
> *after* the build,then create the diff
Chakkaradeep C C([EMAIL PROTECTED])@Sat, Jun 04, 2005 at 10:47:59AM +0530:
>
> > Its a good idea to log every single package and a better idea to create
> > binaries for every package,just in case something goes wrong.
>
> hey, how do create log of binaries, is that i have to collect manually
> t
hi,
thanks a lot Hatzim, your reply has given me several ideas.
> Its a good idea to log every single package and a better idea to create
> binaries for every package,just in case something goes wrong.
hey, how do create log of binaries, is that i have to collect manually
the names of the binar
Chakkaradeep C C([EMAIL PROTECTED])@Sat, Jun 04, 2005 at 01:27:39AM +0530:
>
> well, this is not a bad idea, i will try writing my own scripts and
> see how far can this take me in automating my job now! :-)
>
Its a good idea to log every single package and a better idea to create
binaries for ev
Andrew Benton wrote these words on 06/03/05 14:48 CST:
> tar xjf foo-bar.tar.bz2 &&
> cd foo-bar &&
> ./configure --prefix=/usr &&
> make &&
> make install &&
> cd .. &&
> rm -rf foo-bar &&
> ldconfig &&
What? No 'make check'? :-)
I too have custom scripts that I've written that do my LFS build
hi,
> I run certain key bit by hand but then the scripts run unattended in between.
> >Writing the scripts and debugging them the first time was time consuming but
> >once it's done it's dead easy to update a new package in the script. Run the
> >scripts again and you have a clean new system. I
Chakkaradeep C C wrote:
hey i think YOPER got installed on top of LFS and now both are not
working.so planning to build LFS again.i think there is no other
choice left!...
is there any automated script which installs LFS?
There is Automated Linux From Scratch http://www.linuxfromscratch.org/alf
On 6/3/2005 14:49, Chakkaradeep C C wrote:
> is there any automated script which installs LFS?
There are many. There is nalfs and there is a ton of various other
scripts and systems other people have come up with. I suggest you give
the archives a good searching and you will find all this stuff
hi,
> Sounds like probably your PATH is messed up. I doubt Yoper was the cause,
> unless it was working before you installed Yoper, in which case it would be
> something screwed up after you partitioned. More than likely it was putting
> Portage on there that messed something up.
hey i think YO
hi everybody,
i completed LFS and was happy with the system. Then came the idea of
Package Management System and i was trying with Portage. So my LFS was
with a Package Manager. I had built LFS in a separate extended
partition,
/dev/hdb5 - root
/dev/hdb6 - swap
so i had my
13 matches
Mail list logo
