You wrote:
>I am looking for a list of files that will allow the system to boot
<snip>
>Currently, I can boot to the M-Systems chip as single user . With a
>normal boot, the login prompt shows but does not allow anyone, even
>root, to login (I've copied the passwd, shadow, tons of library files
>and pam.d stuff, but still no luck).
Unlikely your case, but here it goes...
When I moved my diskless from libc to glibc login all of a sudden
stopped to let anyone in. The problem appeared to be missing
/lib/libnss_files.so.1,libnss_files.so.2,libnss_dns.so.2,
libnss_nis.so.2,libresolv.so.2,libnsl.so.1 (not reported by ldd)
and /etc/nsswitch.conf.
Also, perhaps the following extract from my "Diskless-from-NT-mini-howto"
(can be found in www.slug.org.au/etherboot distribution
under name NT-Diskless-Terminal.txt) may be helpful in determining files
required:
"Pruning standard distribution (RedHat, Debian, etc.) to your needs might be
very time
consuming. To ease that painful process I have used remotely booted diskless
client with
NFS-Root (see Etherboot's Readme, NFS-Root and NFS-Root-Client mini-HOWTO's,
Diskless-
HOWTO):
- setup minimal RedHatX.X install (networked workstation, X, no development,
mail, etc.,
~~117MB);
- find . -print|cpio -pmd /usr/NFS/ROOTFS - copy entire fs tree to NFS
exported dir;
- mknod /usr/NFS/ROOTFS/dev/nfsroot b 0 255;
- build vmlinuz-nfs kernel according to NFS-Howto (built-in
bootp,rarp,NFS,NFS root,NIC
driver,RAM disk);
- rdev vmlinuz-nfs /dev/nfsroot - to set NFS root device;
- build image for NFS-Root fs:
#mknbi -d rom -i rom -k vmlinuz-nfs -o nfsImage;
- boot client while monitoring NFS file requests (by Solaris snoop);
- copy files from /usr/NFS/ROOTFS to /usr/BOOT/ROOTFS (MRFS model) according
to snoop's
filelist;
- generate image by mkrootnet script (don't forget to point to the right
kernel vmlinuz-nt).
The above trick not only allows to determine the sought files set but also
debug boot process analyzing NFS messages. I found it convenient to put
"read tmp" statements into
init scripts for debugging. Tracking files up until issuing login gives you
<link to
rootfs.gz> MRFS (~1MB) that can be used to boot Linux from ROM (flash,
eprom, DiskOnChip,
SanDisk, etc.) as well. All the other files requested by client (during
starting X, Java, Java client) were put into (link to remotefs.zip, ~9MB).
Regards,
Pavel Tkatchouk
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
