Dan McGhee wrote these words on 01/22/06 12:15 CST: > Although I will use a script, there is no need to script this. However, > for each section I think that a for-do-done loop will save a lot of > keyboards from freezing as a result of dried blood. :-)
A do loop is much different than a prewritten script. I have no objections to using a loop, in fact lots of places in BLFS use do loops. > The learning is there if someone wants to tear the commands apart. I > could see something like this for each section: > > [snip loop] > which isn't too much different than what's there now. I can see this for sure. And a list of the packages (perhaps even one that could be downloaded) in a file would make it easy. I'm just not sure we should be providing ways to create log files and other such stuff that each person should figure out on there own how they want to do it. > I do, however, think that offering a builder options is important. I'm not sure what you mean here. What options are you talking about? The different packages you may, or may not need for each individual installation? -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 12:13:00 up 119 days, 21:37, 3 users, load average: 1.04, 0.97, 0.64 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
