yes, it sounds like a minor victory but i got the pre-built
2.6.21-ts kernel running on my ts-7250 and mounting one of the debian
root filesystems, and i have a few questions regarding some tweaking i
had to do so i'm hoping someone can clear up those points.
from the "ARM for Linux" page here:
http://www.embeddedarm.com/software/software-arm-linux.php
it seemed clear that the root fs i wanted was "Debian Linux for
TS-7200 series and Linux2.6 - version 3.1 Sarge", and i followed the
instructions in ch 5 here:
http://www.embeddedarm.com/documentation/software/arm-linux-ts72xx.pdf
the first minor glitch is that the instructions for un'tarring the
rootfs tarball aren't quite right for the tarball above since
everything is created with respect to being under "tmp/mnt/" in that
tarball (unlike the other tarballs there). not a big deal, just
something a person needs to notice to make sure they do the mount
properly.
the second curiosity i noticed was the instruction to add the
following to the rootfs /etc/fstab file:
192.168.0.1:/path/to/nfsroot / nfs exec,dev,suid 1 1
that puzzles me -- in all the time i've NFS mounted root filesystems,
i've never had to add a line like that to the fstab file of the root
filesystem itself. and the mount *seems* to work just fine without
it. can someone explain the purpose of that line? it seems redundant
since the NFS mount is given as part of the kernel command line
itself.
the next thing i appeared to need to fix was that, in the root
filesystem, the file /etc/network/interfaces contained:
...
auto eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 192.168.0.50
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
...
as far as i can tell, this would pretty clearly clash with
specifiying "ip=dhcp" at boot time. in fact, if i left that as static
eth0 configuration, the boot sequence would simply lock up when it got
to configuring the network interfaces (not surprisingly). since i was
using dhcp, i simply commented out all the static info and uncommented
the dhcp line and things seemed to work fine. can someone verify that
that was a necessary thing to do? it definitely seemed to solve the
net config hanging.
finally, i'm curious that, even after the system is up and *clearly*
NFS mounted, if i run "mount", i see:
:root# mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw,default)
devpts on /dev/pts type devpts (rw,gid=5,mode=620,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
:root# mount -t nfs
:root#
in other words, there is no output representing the NFS mount point.
it's in /proc/mounts, though:
:root# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / nfs
rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=sys,addr=192.168.1.241
0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/root /dev/.static/dev nfs
rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=sys,addr=192.168.1.241
0 0
tmpfs /dev tmpfs rw 0 0
:root#
i guess i'm just confused as to why the "mount" command doesn't seem
to list NFS mounts, even with the "-t nfs" option.
anyway, if anyone can expand on any of the above, i'd be grateful.
thanks.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|