On Sat, 12 Nov 2005, Matthew Burgess wrote:
Jeremy Huntwork wrote:
Anyway, the results of the farce run are in my homedir:
http://linuxfromscratch.org/~jhuntwork/farce-results
A question for Ken, then. What's the difference between:
2 files differed as expected
and
1 files differed as they normally do
i.e. why can't they be put in the same category?
Cheers,
Matt.
"differed as expected" are files _I_ expect to differ,(fstab, group,
hosts, shadow, bootloader conf, logs (for root - normal user might not
be able to read these, so they will be "ignored"), pids, and a few other
things, all listed in the expected function. Provided people agree with
my rationale, these can safely be ignored.
Bear in mind that my "can it build itself" process is : build system
one, boot it, (get filelist), (perhaps build X and desktop apps), build
system two on a different partition.
"differed as they normally do" have a question mark over them. They
get flagged as "predictable FAIL" in the output. Identified in function
'failure', so far limited to libstdc++, libsupc++ and also lynx, ncftp,
lsof, sshd, traceroute which are blfs but nevertheless things I build
before I reboot. I don't know why these differ. The diffs of these are
in farce-extras, and not at all enlightening. These have usually
differed since I first took an interest in trying to compare builds.
Anything else shows as an "unexpected FAIL:" and really needs to be
investigated. Depending on what you build before running filelist, you
mmight get other things with a date/time/kernel version that slips
through the regexes - that's the real reason for the output in
farce-extras.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
