Thread: questions
Status: Planning
Brought to you by:
lukisi71
From: kriss <chr...@al...> - 2006-11-21 04:47:58
|
hi does it make more sense to make bash & glibc local ? while i'm building a MASSIX i choosed to add some packages (nfs-utils,bind, gmp ...) so we can use MASSIX on the net don't you have more ? (and local or not ?) also i'm facing a problem now : http://cross-lfs.org/view/svn/x86_64-64/chroot/pwdgroup.html i'm not sure what to do so to have a proper use of MASSIX can you post a list of users & groups -- REGARDS && THANKS CIAO KRISS |
From: Luca D. <luc...@gm...> - 2006-11-21 16:21:21
|
You are working hard, Kriss! I am trying to write some scripts to automate the build process. Have you kept track of what you've done to build the system? About users and groups, I have no idea. Let's go with the usual settings recommended by the book (LFS or Cross-LFS) --Luca |
From: Luca D. <luc...@gm...> - 2006-11-21 16:44:21
|
Kriss, I already said local for bash and glibc. Are you suggesting to make them remote? --Luca |
From: kriss <chr...@al...> - 2006-11-21 17:06:54
|
Le mardi 21 novembre 2006 =C3=A0 17:44 +0100, Luca Dionisi a =C3=A9crit : > Kriss, I already said local for bash and glibc. > Are you suggesting to make them remote? >=20 > --Luca >=20 > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share= your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Massix-devel mailing list > Mas...@li... > https://lists.sourceforge.net/lists/listinfo/massix-devel yes remote sorry ps i didn't work hard : migraines --=20 http://sourceforge.net/projects/massix/ |
From: Luca D. <luc...@gm...> - 2006-11-21 20:20:05
|
I think it is better to have bash and the toolchain locally installed. We will have more troubles than advantages trying to use these 2 pieces remotely. As I said, I worked much less hard than Kriss did. I had very little time to devote to it. At the moment I have written some scripts to try and automate the process of building the system. I didn't even reach the beginning of chapter 5 (building temporary system) By the way, Kriss, have you scripted your build? Or have you written down the steps you did? I think this should be our real work now, so that when we want to test some new flag in configuring a package we can redo the whole build easily and without errors. When the scripts I'm working on will be reasonably robust I will put them in the SVN server of sourceforge. --Luca PS Kriss, I hope you are fine now. |
From: kriss <chr...@al...> - 2006-11-21 21:15:33
|
i'm ~fine thanks i didn't use package user management sorry i use jhalfs to download packages & to extract commandes and i run commandes manually changed CLFS in MASSIX that's all for now after making users i'll change to remote all packages that you want i didn't script cause i prefer see what's happen but using jhalfs for MASSIX look easy i 'll not build lilo and bin86 i already have grub and no floppy for daemons that are not remote : ok (bind, dhcp ...) for the rest remote so i'll take note of all i do when you tell about flags else than dirs ?!? it's easy to have all commandes in 1 file so assumming the partition is ok and sources are here it will run in one shot i'll post it here when ok if you put your fingers in jhalfs it's more long than changing final commandes so i didn't try -- http://sourceforge.net/projects/massix/ |