Thanks so much when i do echo $PWD i get /root also when i do ls / it shows all my directories i even did a cd / and did lsagain to make sure Its all there ! thank god and thank you. it was so silly of me not to check there.Well why is it when i log into root it doesnt automatically take me to / like in ubuntu and other linux systems. even on ubuntu when I do a sudo su it takes me to root@pcname:/#. Can i do something on lfs to make it show up this way or is it intentional that lfs doesnt goto / automatically after login to root.
So that means my lfs system is working fine? Is this how its supposed to be setup into root and not root@pcname:/# ? Regards On Fri, Jul 13, 2012 at 8:48 AM, Ken Moffat <[email protected]> wrote: > On Fri, Jul 13, 2012 at 07:44:19AM +0530, James Pinto wrote: > > Hi > > > > I have completed building LFS and am able to boot and login into root > user > > but Im unable to view any of the folders such as home etc, var, etc... > > The ls command doesnt show any files or folders.On the other hand when I > > chroot into lfs using my host system I can access everything. > > Are you sure this is indeed lfs ? [ cat /etc/lfs-release or look at > the output from 'mount'and compare it to where you were building ]. > > For the moment, your question doesn't make a lot of sense : root can > access everything (unless you have security policies such as > selinux, which would mean you were on the host system). Or are you > running 'ls' in ~/ (i.e. /root) ? > echo $PWD > > If so, the command you want is probably 'ls /' ? > > Failing that, 'type -pa ls' (that's a variant of 'which lfs' as you > will see when you eventually get in to BLFS - if 'ls' exists then it > seems likely that /usr/bin/ exists :) > > Also fr your > > information I have used my existing grub, Grub 2 and used grub customiser > > to automatically searchh and add the entry into the grub. I have also > tried > > adding the entry in the below format to the 40_custom file to see if it > > works, it does get added and when i select it it says file not found and > > then press any key to continue and when I press it starts up into login > > alright. The first option (using grub customiser) doesnt even give me an > > error. > [ snip ] > > For this part, I've few ideas - all bootloaders are nasty, grub no > more so than any others - just differently. > > Using chmod on /boot/grub/grub.cfg so that I can write to it works > for me (ditto the old menu.lst when I last used it). > > menuentry "GNU/Linux, Linux 3.4.3-lfs-SVN-20120623" { > > set default=0 > > set timeout=5 > > insmod ext3 > as somebody said the other day (I think) - doesn't ext2 (in grub > nomenclature) work for you ? > > set root=(hd0,2) > > As far as I can remember, 'set root=' is something I've always put > at the start of grub.cfg or menu.lst because it applies to *all* the > entries. Actually, default and timeout also belong to the menu as a > whole, NOT to individual entries - maybe your real problem is that > you've got syntax errors here ? > > Whatever, either you are able to boot the new system, or you are > not. It seems you are not - I'm unsure *which* of your systems you > are booting (host, lfs), and I don't know what that 'grub > customiser' is - and for the latter, I don't care, I assume it is > something specific to your host distro. > > If you created /etc/lfs-release and you can cat it, then you are in > the new LFS system. Otherwise, you are probably in the host system. > > > linux /boot/vmlinuz-3.4.3-lfs-SVN- > > 20120623 root=/dev/sda7 ro > > } > > > > The problem is the same in both cases > > ls shows nothing is there > > If you get "file not found" then you have an error in that grub > stanza, so you are apparently *not* managing to boot your new LFS > system. > > One erroneous variation, which I often make myself (last time only > a few hours ago :-( ) is to copy a grub entry, change the kernel > name, but forget to change the root= : when that happens, you can > boot the intended kernel, but on the host system. > > Whenever we get problems (and we all do, me included), it helps if > we can understand what is happening, instead of what we think is > happening. In your case, you seem to have two problems: > > 1. failure to load the LFS kernel > > 2. possibly, something weird in the new LFS system (I'm not > convinced about this at the moment). > > I suggest that you put the LFS kernel (vmlinuz3.4.3-lfs-SVN) > wherever your host system has put its kernels - probably in its > /boot - i.e. *copy* it into /boot from the host system, and then > remove any variations in the host's grub menu.lst (I *hope* that > your host system doesn't specify default, timeout, insmod, root for > each kernel - if it does, it appears to lack sanity.) > > > and I cant see any of my files or dirctories, whereas I see them using > > chroot on my host system. > > > > Please help! > > > > Regards > > -- > > James Earnest Pinto > > Director/CEO > > *Phoenix Fusion* > > www.phoenixfusion.in > > > > Mobile: +91 8595053531 > > > People here are usually sensible, but you might want to stop > broadcasting your phone number, unless you enjoy calls at weird times > :) > > ĸen > -- > das eine Mal als Tragödie, das andere Mal als Farce > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > -- James Earnest Pinto Director/CEO *Phoenix Fusion* www.phoenixfusion.in D-4, Krist Jyoti, Pushpanjali Enclave, Pitampura, Delhi - 110034 Mobile: +91 8595053531 Facebook: http://www.facebook.com/pages/Phoenix-Fusion/286108164758740
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
