Ardenfort,

   Without going in to detail, I would:
     1) copy the NFS file system to your CF.
     2) Update /etc/fstab to reflect the new disk layout.
     3) Install Grub on the CF.
     4) Update /boot/grub/grub.conf or /boot/grub/menu.lst, grub will
        use which ever it finds.
     5) Try booting on your laptop as a test. You may need to get into
        Grub command mode to adjust the kernel options.
     6) Install it on you Soekris and boot it.

   I would use the LABEL options for fstab and grub.conf. It is more flexible
that /dev/hda1 or /dev/sdax. If you do this you will need to change the label
on you CF using e2label.

   Hope that helps? Good luck.

-- 
William Estrada
[EMAIL PROTECTED]
Mt-Umunhum-Wireless.net ( http://Mt-Umunhum-Wireless.net )
Ymessenger: MrUmunhum

> Message: 6
> Date: Tue, 25 Dec 2007 18:51:11 -0800
> From: "Floating Integer" <[EMAIL PROTECTED]>
> Subject: [Soekris] very basic questions on booting from compactflash
> To: [email protected]
> Message-ID:
>       <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> I now have a Soekris 4521 board running Linux and some utilities on it. I
> did all of my initial application development using NFS as it was a simple
> thing to do.  On my laptop, /nfs directory now contains all the files and
> directories that the board needs.
> 
> I used buildroot. It created a file system in tar.  I untar it into /nfs. I
> customize the files under /nfs. The board performs a PXE boot, downloads
> kernel from /tftpboot of the laptop. The pxelinux.cfg/default directory
> tells the board to look for the root file system under /nfs.
> 
> The total size of all files and directories in /nfs  is ("du -s /nfs") about
> 128MB. The compactflash has 1GB. The board has 64MB of RAM.  When the kernel
> has loaded and other modules have loaded, about 9MB of the main memory is in
> use.  So far so good.
> 
> I have one issue that is still not resolved. How do create a bootable
> compact-flash with what is available on /nfs? What are the steps?  I am
> missing some fundamentals of the boot process here. It seems like I should
> create a ramdisk image of a subnet of files from /nfs and place the ramdisk
> image in /nfs/boot directory.  Should the ramdisk-image be created for 64MB
> of RAM that the board has?
> 
>  On my laptop, /nfs/boot/   - this contains the kernel  "bzImage" and also
> "grub" the kernel-loader.  Buildroot didn't create menu.lst by default.
> /dev/ram exists.  What would be a common menu.lst file if the system boots
> from flash?
> 
> Any pointers (books, website anything) will be greatly appreciated.
> 
> thanks,
> ardenfort


_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech

Reply via email to