RE: [Ltib] Old uImage Won't Boot

[Daniel Widyanto]

Hi Carolyn,

 

IMHO it matters when you put symbolic-link to the real NFS directory.

 

-----------

My host /etc/exports file is:

/tftpboot/ltib 192.168.1.100(rw,no_root_squash,sync)

 

/tftpboot/ltib is a link to the root file system

/tftpboot/ltib -> /home/vrams/mpc8536ds/ltib/rootfs

-----------

 

See http://uw714doc.sco.com/en/SDK_sysprog/_Using_Symbolic_Links_with_NFS.html example #2

 

Regards,

-daniel

 

From: address@hidden [mailto:address@hidden On Behalf Of Reer, Carolyn (SA-1)
Sent: Monday, November 08, 2010 10:08 PM
To: Peter Barada; address@hidden
Subject: RE: [Ltib] Old uImage Won't Boot

 

That strange command line is because the line wrap is off during boot time.

This line

Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.1:/tftpboot/ltib ip=192.168.1.100:192.168.1.1:192.168.1.1:255.255.25f

Is actually this line:

Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.1:/tftpboot/ltib ip=192.168.1.100:192.168.1.1:192.168.1.1:255.255.255.0:mpc8536ds:eth0:off

 

It must be something else. The NFS mounts. But after that all subsequent mounts fail.

 

This is posted just before the NFS is mounted:

IP-Config: Complete:

     device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=192.168.1.1,

     host=mpc8536ds, domain=, nis-domain=(none),

     bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=

 

Is ‘rootpath=’ correct? Should it be blank? All other parameters seem correct.

This configuration booted in the past. But I don’t have the ‘good’ boot log. I’m afraid I screwed up the permissions when I coped the directory for backup.

Thanks Again

 

Carolyn Reer

201-405-2992

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This communication is intended only for use by the addressees named herein and may contain business confidential and/or legally privileged information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, disclosure or copying of this e-mail and its contents is strictly prohibited. If you have received this e-mail in error, kindly notify the sender by replying to this message. In addition, please permanently delete the message and any attachments without copying or disclosing the contents. Thank you for your cooperation.