Hi,
I'm considering building a system based on BLFS-svn-20110728 and LFS-6.7 .
Are Wayne/Guy/Randy/etal interested in receiving any
patches/confirmations/feedback/&c from that process, towards a release
of BLFS-6.7.x by end March 2012 at latest?
If yes, then is it ok to mail the info mainly as patch-format attachments,
to the 'blfs-book@...' list; with the patches being generated from diffs
of the xml tree of the svn book? And those with commit &c rights, can
pick 'em up from there?
The areas covered here, in the first instance at least, would be - in
approximate order of 'requirements' and their 'dependencies':
----
* X/Print software: SeaMonkey, Xpdf/ePDFView/GSview, CUPS/LPRng.
* X Windows, running twm. (Besides, KDE/GNOME seem handled just fine by
Randy/Thomas/&c).
* some userland stuff from chapters 6, 10, 11, 15, 16, & 18 : mostly
'classical'.
* some sysadmin stuff from chapters 4, 11, 16, & 17 : mostly 'classical'.
* servers - much of chapter 19, plus ntp/sendmail/procmail/bdb/rsync.
(The machine is partly a general test-area.)
* a few non-BLFS items, such as Git, Dovecot, SqWebMail, Lilo, some
Milters (e.g. j-chkmail, clamav), etc.
----
Much of post- chapter '24. X Libraries' would not be covered here, at
least in this first instance. Looking through the tree of dependencies,
and focussing mainly on only required/recommended deps, I think that
the above is quite-readily do-able with current BLFS-svn. (In particular,
I hadn't quite realised just how contained and 'clean' is the dep-tree
for getting the above X-/Print-software + X-windows.)
Some more detail on the rationale at this end:
----
* I want to get a reasonably functional system up-and-running fairly
promptly.
* Given some time &c constraints, I don't _really_ want to run the risk
here, right now, of getting bogged down in 'unknown territory' - e.g.
trying to plough ('plow') through a BLFS based on LFS-6.8 or later.
* Therefore BLFS-6.3 or BLFS-svn look to be the main BLFS choices here.
* The hardware to be used is based on an AMD E-350 processor
('Asus E35M1-M PRO' motherboard), with no other 'new' 'exotic' hardware
- e.g. will use standard Intel PCI/PCIe NICs, and laptop hard drives
(i.e. 2.5" 5400rpm - the new 1tb samsung/wd); and no usb3/ssd on that
system yet. (Am aware that compilation times will be slowed 'a bit'
compared to more powerful processors).
* Both BLFS 6.3 & svn are a bit too old to make _full_ use of the E-350
capabilities: but AIUI, should still be OK for most functionality -
just things like 3D might be omitted; which is ok, for now at least.
* So, the choice is then BLFS 6.3 or svn.
Looking through svn, most of the 'builds/works with' data covers LFS
6.5 thru 6.7; and IIRC leans more towards the 6.7 end of things.
So, it looks like BLFS-svn has quite a lot of compatability with
LFS-6.7 .
* Therefore, it seems that the 'BLFS-svn-20110728 and LFS-6.7' combination
is the way to go here.
----
Is the above reasonably sensible? I'm aware that that's perhaps straying
towards more of a blfs-support type of question. However, the central
point here, for now, is whether or not the above can be useful towards
getting a concrete BLFS release out of the door.
rgds,
akh
--
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
