Originally Posted by lloydsmart
Wayhay! My system is alive! I didn't get the gentoo disk working, just used the lfs livecd with the clfs book and sources. That seemed to be easiest as I knew I already had x working on there.
The config you made me worked great! Thanks so much for that. I'm now looking forward to your hints, let me know when they're done!
I shiuld be able to work on the system for a couple of hours tonight, then spend some proper time on it (blfs stuff) on saturday.
The only problem i've encountered so far is that it won't bring up eth0, so no network access. This is my no. 1 priority at the moment as I need to get wget-ing! I don't know where to start though, weather it's a kernel thing or what.
EDIT: Got eth0 up and running with a kernel recompile. Had to enable the forcedeth drivers. Now I'm gonna quickly try and get wget installed and running before I head off to work again.
Thanks ... As I posted previously, I wasn't sure about your NIC. You got it though.... good to hear it. BTW, that kernel is a total hack, meaning you can look closer into the BFS feature (a.k.a.
BRAIN FUCK SCHEDULER ... google it.) under the general settings. It was written by a guy who was on Linus's kernel development team, its experimental, but it adds true threading to your desktop. This feature is under " General Settings --->
". You can swith from CFS to BFS...
I take no credit in any way for this kernel, just helping with your .config (This credit goes to the maintainers of the zen-overlay at Gentoo & the developers @ zen-sources.org
Also, I am sure you are using the standard LFS bootscripts right...? You should take a look @ Roy Marples OpenRC 0.5.0
, I implemented it into my init startup ... and man... so much better... a way clean startup (boot), that I also can run in parallel, and with using Gentoo's dhcpcd init daemon for dhcp. Also, it has a boot logging feature that writes to a log file in /var/log/rc.log for any troubleshooting of any startup issue's (very handy). Much better than any BSD, or LFS setup I could find.
I have been documenting this implementation, and have been working on some patches for the CLFS pure64 svn
setup. I am having trouble with installing the CLFS multilib-svn at the moment ... Going to try it with a liveDVD instead, to see if that will work. Once I have setup the Multilib, and have tested and added ARCH's ABS support, I'll post on my up and coming blog (still a work in progess)
Did you use any of my hints with the .bashrc and the DIR_COLOR..? It makes a great colored console, and sets your global gcc flags.
Things I have implemented into my CLFS pure64 & issue's I had:
Custom .bashrc with/ colors (some borrowed from Gentoo)
Implementation of Roy Marples OpenRC 0.5.0 inits and tool sets
, awesome stuff IMHO. (I had to patch the source to get it to compile correctly and have confirmed it with Roy & he has said there will be new release soon to resolve this issue.)
A big problem was with my locale's ... arrgh ... all my console characters where way out of wack... even with exporting the locale in my /etc/profile
I decided on using Debians tool called "locale-gen
" which reads a config file in /etc
. This tool sources my init's function.sh; to set the right terminal & then uses the config file to set my global locale's (awesome fix...!) Now all of my dialog boxes (e.g. menuconfig, pkgtools), and any console commands are set correctly. No more garbled console output..Woo Hoo..! If you have a similiar problem let me know, so I can upload the scripts and config files for this fix.
OVERVIEW & CONCLUSION:
You inspired me to give CLFS pure64 a try ... thanks & in no way did I intend on hijacking your thread .. just wanted to contribute...
Now I am at a base install w/ all proper inits, udevd rules, and with proper shutdown scripts. So now I am at the level of adding any additional packages and programs. I have added nano, rsync & wget ... that's about it. The reason for this is I am looking into & researching a "TRUE" solution to managing packages properly, once you enter the realm of BCLFS
. This is all dandy, being able to add packages from their source, and using InstallWatch to monitor where each file is installed .. etc.. What a pain when it comes to removing any packages or upgrading...
I have been asking around in the ARCH's forums addressing this issue
... I gave a brief synopsis and have had some great responses to my challenge, and some contribution to implementing ARCH's ABS system into CLFS, their are MAJOR
advantages to this IMHO, like making and editing the PKGBUILDS, and using ARCH's AUR... some might disagree with this, because it takes away from the LFS philosophy of a true LFS Linux environment... I say config at one's hearts content... & borrow any tools and source code along the way, no limitations.
I have briefly tried a Slackware solution, and with my lack of knowledge of Slackware's pkgtool's & issues with tar, and the lack of any documentation on this, I've abandoned using pkgtool... Would be great to see it I could get working ...
So if you have any idea's on managing your package source... please share. It would be nice to implement a true fakeroot environment to build a package from source, and then install the package into the correct FHS layout of CLFS. A good example of this is Gentoo's ebuilds & sandbox, or ARCH's pacman, makepkg & PKGBUILDS.