making floppy systems

[fred anger]

So, assuming I have a bootable floppy and some means of transferring a
tarred-up filesystem image to the embedded system's harddrive, how do I go
about getting that image out of PWL?  Simply tar up the
./Embedded_Build/projects/blah/mnt directory?  Then once I partition and
format the embedded system's hard drive, I untar the file system on to it,
but how do I get a boot loader installed (lilo)?  Would I make the
appropriate changes to the ramdisked /etc/lilo.conf and run lilo, or would
I have to make a lilo boot disk to boot from the newly-created hard-drive
filesystem first?

-fa

On Fri, 1 Sep 2000, Ralph Stickley wrote:

> Fred,
> 
> --- fred anger <anger@rightarm.org> wrote:
> > On Fri, 1 Sep 2000, Ralph Stickley wrote:
> > > Yes...So far, all my development has been on DOC flash (M-Systems
> > Disk-On-Chip
> > > which was quickly abanonded for cost reasons) and Compact Flash (PCMCIA
> > Adaptor
> > > and USB/CF adaptor).  These are all "integrated" hard drives available
> > directly
> > > to pwlconfig.  
> > 
> > Those devices still require you to detach them from the "embedded" system,
> > and to the machine running pwlconfig though.  That's what I was hoping to
> > get around.  I don't think it's possible with PWL.
> > 
> Hmmmm...I see your point. I my systems, the actual device that is embedded is
> physically mounted on my development box then transfered to the embedded
> system.
> 
> If you exract the file system then compress that to one file. Put that one file
> on your boot floppy and then extract it to the embedded hard drive. (you may
> have to boot off a floppy that loads the "boot" filesystem into ramdisk - then
> insert the new file system from a floppy created by pwlconfig.  
> 1. build a boot floppy include tar/gzip/cp/lilo/mkfs/..etc.. utilities
> 2. create a working file system using pwlconfig
> 3. Boot the embedded target with the boot floppy - run system out of a ramdisk
> 4. Isert the pwlconfig filesystem and copy the files to the embedded hard disk.
> 
> Is there a way to automate this ? If your only interface to the embedded system
> is a floppies I don't know what else could be done.
> 
> However,
> 
> Is there any way you can have the Embedded system boot and access a network ?
> Then you could ftp files from your pwl development system. (Or better yet,
> mount the embedded system as a disk - NFS or something like that).  
> I'm guessing here, but something like this:
> 
> Embedded box 
> - partition 1 - boot and allow access via network
> - partition 2 - system application - erased/replaced as requested remotely
>  
> > > Hope this help. Also, Adi is approaching the boot/ramdisk file system
> > support.
> > 
> > That would be incredibly useful :)
> >
> I think this is mostly working but not integrated into pwlconfig.  Maybe next
> week will see a flurry of activity on this...let me know if anything else would
> be helpful here...
> 
> Enjoy the weekend,
> Ralph
> 
>  
> > Thanks for your help.
> > 
> > -fa
> > 
> > 
> > ---------------------------------------------------
> > See the list archives at http://adis.on.ca/archives/
> > See the PWL homepage at  http://peeweelinux.com
> > ---------------------------------------------------
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail - Free email you can access from anywhere!
> http://mail.yahoo.com/
> ---------------------------------------------------
> See the list archives at http://adis.on.ca/archives/
> See the PWL homepage at  http://peeweelinux.com
> ---------------------------------------------------
> 

---------------------------------------------------
See the list archives at http://adis.on.ca/archives/
See the PWL homepage at  http://peeweelinux.com
---------------------------------------------------