Truth of matter is, the directories used on both systems were copied from elsewhere, so both were in a more sequential state than the source archive that was accumulated over time and is scattered all over the partition.
Either way, this might become a popular piece of software, especially if the capabilities and features are somewhat similar to that of the VTune program. Would probably make a good comparison article for DevChannel.org
--
Gerard Beekmans
Re:Automated Linux from Scratch
on
LFS 4.0 Released
·
· Score: 1
In my opinion the useful knowledge is knowing how the various software on your system interact with eachother. Just an example that comes to mind:
Not everybody figures out that the groff and man packages are closely tied in to eachother. Often people think that 'man' is a program by itself that shows you manual pages. Little is known about programs like gtbl and nroff who do the formatting, then feeding it to a pager like 'less' or 'more'. All man basically does is invoking the right programs with the right parameters (note: this depends on your man package version and vendor of course).
It boils down to something like:
cat/usr/share/man/man1/ls.1 | gtbl | \
nroff -mandoc | less -is
People who don't just install LFS but actually take the time to learn what they are installing by reading the docs that come with packages, example files and what not would learn this.
Some people may not find the above tidbit useful. I myself do find it useful. It gives me a clearer understanding how a man page is displayed and how big a part "groff" plays in all this (and that I need groff installed to be able to display man pages in a convenient matter, so keeping groff around would be a good idea).
Well, no the LFS-BOOK doesn't come with a package manager. The idea behind LFS is that you are in the driver's seat, not us. So it's up to you to decide on a package manager. If you want to use RPM, feel free to do so. Want to use deb? Fine too. Or use a simple method of using the 'find' program to gather a list of files that were installed during a package installation (which I do). If I need to figure out where a file comes from, I run a command like this:
grep/usr/bin/gcc/var/install-logs/*
And I'll get back a list with all the packages that have something to do with/usr/bin/gcc. Now,/usr/bin/gcc will only return one match but since I'm using grep I can look for other patterns (all packages that install something in/usr/share/locale for example)
Anyways, because LFS is so basic you get to decide yourself what to use and aren't stuck with whatever somebody else decided for you to use.
sure, this isn't really suitable for Linux newbies, but then again LFS was never meant for newbies but rather for people who are knowledgable in Linux already and want more flexibility than most distributions can offer (not all distro's, I said _most_. Big diff. there).
It's usable. There are various implementations that a lot of people have been using over the last year or so with a lot of success, if you're ok with not having a fancy-schmancy GUI interface. The official ALFS implementation is still under development. An initial release shouldn't be too far away anymore.
Not yet. The initial release of ALFS won't have package management support, or any other 'extra' features. That's all planned for afterwards. If we wait to implement every single feature at once and release it, it'll take forever and a day to get the first version out, it will take twice that long to properly debug all that code.
Slashdot Mirror
New one SCSI is physically 40% faster. That wasn't really the comparison. Look again, the first drive is a lot closer to the IDE one.
I didn't specify no.
Truth of matter is, the directories used on both systems were copied from elsewhere, so both were in a more sequential state than the source archive that was accumulated over time and is scattered all over the partition.
Interesting piece of software. I wonder if "Performance Inspector" was inspired by Intel's VTune Performance Analyzer software ( http://www.intel.com/software/products/vtune/).
Either way, this might become a popular piece of software, especially if the capabilities and features are somewhat similar to that of the VTune program. Would probably make a good comparison article for DevChannel.org
--
Gerard Beekmans
In my opinion the useful knowledge is knowing how the various software on your system interact with eachother. Just an example that comes to mind:
/usr/share/man/man1/ls.1 | gtbl | \
Not everybody figures out that the groff and man packages are closely tied in to eachother. Often people think that 'man' is a program by itself that shows you manual pages. Little is known about programs like gtbl and nroff who do the formatting, then feeding it to a pager like 'less' or 'more'. All man basically does is invoking the right programs with the right parameters (note: this depends on your man package version and vendor of course).
It boils down to something like:
cat
nroff -mandoc | less -is
People who don't just install LFS but actually take the time to learn what they are installing by reading the docs that come with packages, example files and what not would learn this.
Some people may not find the above tidbit useful. I myself do find it useful. It gives me a clearer understanding how a man page is displayed and how big a part "groff" plays in all this (and that I need groff installed to be able to display man pages in a convenient matter, so keeping groff around would be a good idea).
Well, no the LFS-BOOK doesn't come with a package manager. The idea behind LFS is that you are in the driver's seat, not us. So it's up to you to decide on a package manager. If you want to use RPM, feel free to do so. Want to use deb? Fine too. Or use a simple method of using the 'find' program to gather a list of files that were installed during a package installation (which I do). If I need to figure out where a file comes from, I run a command like this: /usr/bin/gcc /var/install-logs/*
/usr/bin/gcc. Now, /usr/bin/gcc will only return one match but since I'm using grep I can look for other patterns (all packages that install something in /usr/share/locale for example)
grep
And I'll get back a list with all the packages that have something to do with
Anyways, because LFS is so basic you get to decide yourself what to use and aren't stuck with whatever somebody else decided for you to use.
sure, this isn't really suitable for Linux newbies, but then again LFS was never meant for newbies but rather for people who are knowledgable in Linux already and want more flexibility than most distributions can offer (not all distro's, I said _most_. Big diff. there).
It's usable. There are various implementations that a lot of people have been using over the last year or so with a lot of success, if you're ok with not having a fancy-schmancy GUI interface. The official ALFS implementation is still under development. An initial release shouldn't be too far away anymore.
Not yet. The initial release of ALFS won't have package management support, or any other 'extra' features. That's all planned for afterwards. If we wait to implement every single feature at once and release it, it'll take forever and a day to get the first version out, it will take twice that long to properly debug all that code.
Should be fixed now. Even though linuxfromscratch wasn't the main theme of this thread, the server got hit with the, now famous, slashdot effect.
It seems these days one shouldn't have a server online that isn't able to hold up against slashdot else the server's admin will pay for it ;)
(also; thank God for mirrors)