Ken Moffat wrote: > On Sun, Aug 20, 2006 at 09:48:23PM +0100, Reece Dunn wrote: > > > > LFS is an ideal distribution for be, because: > > * I already know how to use bash, rm, tar and the like from cygwin; > > * it gives me the opportunity to discover Linux things gradually (like > > using > > chmod to make scripts executable); > Au contraire, any variant of LFS will drop you in at the deep end.
:). I am very much aware that any LFS distribution is not for the feint of heart. I don't see the casual PC user running LFS! > It's great for learning how things fit together, but my opinion is > still that most people shouldn't come here until they know what they > dislike about the distro they are using - if all you want is a > spartan system, fine, but for most of us it helps to know which > packages we want to use, and trying out the alternatives from a > distro is a lot simpler. I am using two distros on LiveCD at the moment (which I am writing this e-mail on), having ditched Windows. I am learning from the LFS end and from the LiveCD distro end. > If you are ready, great, enjoy the build. I will :). > > * the major distributions I have tried either don't support what I want out > > of the box (e.g. mp3 support), don't allow the configuration I need > > (e.g. > > have problems with loadkeys gb or loadkeys uk), have problems with my > > hardware (e.g. problems with getting the soundcard on my laptop > > working), > > or come with software I'll never use (how many variants of bash do you > > need anyway?); > > At any given time, one version of bash is enough, but preferably a > fully working version [ in-joke for readers of clfs-dev :) ]. So > far, I haven't seen out-of-the-box mp3 support in any version of LFS > - personally, I use mpg321 for mp3 (GPL'd and nominally maintained), > but even mpg123 is a matter for BLFS. In that sense, we aren't a > distro, you build exactly the (blfs) applications you want and > nothing else. I understand this. And there are other projects (like cairo) that aren't part of BLFS. One step at a time. > Just about everybody on -dev uses some form of automation, but that > doesn't mean you should automate before you can build it by > following the book. I generally work through the sub-chapter and get that working, *then* I automate that section so it is easy to get back to that point. > Building a c++ program to build and install > sounds like severe overkill - the reason shell scripts are so > popular is that they are easy to modify and they have enough power > for this sort of use. My automation tool started life as a shell script and evolved into the C++ version it is now. All my C++ program is doing at the moment is spitting out a batch file. However, that's a topic for a different list :). > > My aim is to build all of the boostrap stage and minilfs using my package > > manager tool. The aim then is to use this to manage what packages (and > > their versions) are installed on my system. The next phase is then to use > > my tool to build the LFS system and then go beyond.. :)! > > You will also have seen the thread Chris started about people who > use package management tools before they're ready for them. Oh > well, at worst you get to keep both pieces when it breaks. I am not saying that I am going to write and use the package management (as opposed to package building) tools right this minute. That will evolve and develop as I learn what is involved in managing different packages. > The point is to get a working system. Once you know how to do that, > by all means explore your own ideas on package management - apart > from anything else, doing it in your preferred graphical desktop is usually > a lot easier than keeping multiple ttys open while you hack your source code. Indeed. Hence me writing this e-mail from a LiveCD distro. The package management stuff will come later, once I start to understand what is involved. > If you automate, you have to know what to change. Looks as if > you've started the learning process. For the chroot part, clearly a > separate script/program is appropriate. That was the solution I came up with. > > At the moment, I am building LFS on my laptop. Once I get it working, > > I'll build it on my desktop. Then, I would like to get (C)LFS working on > > a PDA - for that, I'll want to create a 'lean' version of CLFS. > > When you look at clfs, look at clfs2 - it's about cross-compiling > the whole system, but I'm not up to speed with it (too busy looking > at testsuites in clfs1) Thanks for the advice. > again this isn't the right list to discuss it. I am aware of that. I was giving an overview of why I chose LFS, where I am in the LFS build process and where I intend to go with it. This wasn't a call for help (for now), but was to say that there are new people interested in the LFS project. Thanks, - Reece _________________________________________________________________ Be one of the first to try Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
