No actually I'm not building for a different architecture but just thought it would be easy and cleaner to boot rather than chroot (or now I realize it is the other way around).
Yes what you said makes sense, the steps for different architectures looks a little different, I'll try to see if there is some extra step there I might have missed for x86-64. Thanks. -Ash On Sun, Jul 3, 2011 at 7:04 PM, Grail Dane <[email protected]> wrote: > Hi Ash > > Sorry I forgot to look at the part where you said 'multilib' :( > > I have noticed though that there is a difference in the Boot sections of > different builds (but not sure why). > > In GIT-20110703-x86 version they have: > > ln -sv /tools/sbin/{agetty,blkid} ${CLFS}/sbin > > Which yours does not ?? > > So only thing I can think of is to have a look and see if there are any > other steps that might be missing. > > Also, just out of curiosity, are you building for a different architecture > and so are choosing to boot? > Cheers > grail > ------------------------------ > From: [email protected] > Date: Sun, 3 Jul 2011 18:37:46 -0700 > > To: [email protected] > Subject: Re: [Clfs-support] CLFS - Unable to login on the first bootup > > > HI Grail > > I didn't quite get you there. Among the two routes to initially set up the > system - "7 - If you're going to boot" and "8 - If you're going to chroot", > I chose 7. So at the end of it I was on the assumption that I should boot up > the initial/temporary system using the basic kernel I've built in step 7.10. > > Or do you happen to say I could happen to proceed with steps in chapters 9, > 10 and above where I get to build the actual packages and tools for my > system right from my host machine (without a chroot) ? > > Sorry if this question sounds silly, but I happen to be lost here. > > Thanks. > > -Ash > > On Sun, Jul 3, 2011 at 4:39 PM, Grail Dane <[email protected]> wrote: > > Hi Ash > > As you have only completed part of the solution I am not sure why you > thought you would be able to boot the system?? > > Regards > grail > ------------------------------ > From: [email protected] > Date: Fri, 1 Jul 2011 11:15:54 -0700 > To: [email protected] > Subject: [Clfs-support] CLFS - Unable to login on the first bootup > > > Hi > > I'm following CLFS: Version GIT-20110622-x86_64-Multilib > > I'm using openSUSE 11.4 as the host machine to build the cross-to and other > basic tools for the minimal CLFS system booting. > > This is the minimalistic system refered in Chapter 7 "If You Are Going to > Boot" and not the final CLFS system. > > I got through with the steps mentioned in chapters 1-7 without any errors. > > When I finally went to boot the system I initially got an unable to mount > root fs error. It said tried ext2, ext3, ntfs and stuff (but didn't mention > ext4). Then I realized I had not compiled ext4 into the kernel but just as a > module. I rebuild the kernel separately once again and I had success in > getting past this error. > > But it was complaining about spawning /sbin/agetty and so did not get any > login prompt. I booted into my host machine and noticed that /sbin didn't > contain agetty, instead it was present in /tools/sbin but according to the > steps in chapter 7.6, it the lines look as below: > 1:2345:respawn:/sbin/agetty -I '\033(K' tty1 9600 > > So either util-linux didn't install them to the proper location (should it > have been ${CLFS} instead of /tools ?) or I missed some detail/step. > > I tried modifying the /etc/inittab to use /tools/sbin/agetty instead of > /sbin/agetty, and now I get a login prompt but entering username as root > does not login into the system. :( It doesn't print any error messages but > waits for roughly 30 seconds and again displays the login prompt. > > I also copied the line from /etc/shadow on my host machine for the user > root into ${CLFS}/etc/shadow. I even created an empty ${CLFS}/etc/gshadow. > But still the same behaviour. > > Any help here would be appreciated. Let me know if I need to post any > additional logs or even my kernel's .config file. Thanks. > > -Ash > > _______________________________________________ Clfs-support mailing list > [email protected] > http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org > > _______________________________________________ > Clfs-support mailing list > [email protected] > http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org > > > > _______________________________________________ Clfs-support mailing list > [email protected] > http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org > > _______________________________________________ > Clfs-support mailing list > [email protected] > http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org > >
_______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
