Multiple Targets for PeeWee Linux

[David Wood]

On Thu, 7 Sep 2000, Ralph Stickley wrote:

> We are beginning to integrate the ramdisk configuration utilities into the
> latest version of pwlconfig.  I plan on working on this over the next few
> days...Anybody have any suggestions please let me know...

Great! :)

> ======
> Requirement: To build a project on several different targets. Users should
> configure each target as required, then choose the proper target
> configuration before doing the Erase/load operations on the target device.
> 
>                   Main menu changes:
>                   ==================
>                   ...
>                   ---
>                   Configure Target Device "CF 32Mb"-->

How about:          Manage Target Devices -->
                    Select Target Device -->

>                   Erase "Flash" -->
               of course, erase "flash" would be in the management,
>                   Load Filesystem to Flash -->
               as well as the loading of the filesystem,
>                   Lilo...
               and lilo ;)
>                   ---
>                   ...
> 
> 
> Selecting "Configure Target Device -->" gives the following menu from
> "pwl_targets" script file:
> 
>                   PWL Target Menu
>                   ===============
>                   Select Target Type -->
>                   Save Target Configuration for "my floppy" 
>                   Create New Target
>                   ---
>                   Configure "CF 32Mb" Parameters
>                   [*] CF 32Mb
>                   [ ] CF 16Mb
>                   [ ] RAM 256Mb
>                   [ ] My test Floppy
>                   [ ] My CDROM release
                    [ ] TFTPboot directory
> 
> Now each target file would contain all the default parameters as
> configured for that target.  The "Configure "CF 32Mb" menu item would then
> display the parameters (basically just like the current "project defaults"
> menu )
> 
>                   Configure Target parameters
>                   =================
>                   ---- Boot defaults ---
>                   boot image file: /boot/bzImage
>                   boot location: /dev/hda1
>                   ---- Lilo defaults ---
>                   Lilo boot label: pwlinuz
>                   Lilo timeout: 2
>                   Lilo custom command: linear
>                   Lilo image command: vga=0x317
>                   ---- Device defaults ---
>                   Mount point: ./mnt
>                   Device name: FLASH
>                   Device node: /dev/hda
>                   ---- Partition defaults ---
>                   Boot partition: 1  size: 1Mb
>                   system partition: 2 size: 28Mb
>                   Other partition: 3 size 2Mb
>                   ---- Ram Disk Defaults ---
>                   initrd name: rd_image
>                   verbose operation: On
>                   ???
> 
> And Where the Select Target Type menu is as Adi proposed:
> 
>                   Select Target Type
>                   ==================
>                   1)  Compressed ramdisk on FAT 16 partition"
>                   2)  Compressed ramdisk on ext2 partition"
>                   3)  Uncompressed ramdisk, boot from FAT 16 partition"
>                   4)  Uncompressed ramdisk, boot from ext2 partition"
>                   5)  Read-only root fs with multiple ramdisks"
>                     ----- Non-flash target devices -----"
>                   6)  Compressed ramdisk on floppy disk w/o bootloader"
>                   7)  Compressed ramdisk on FAT12 floppy disk w/syslinux"
>                   8)  Bootable iso image w/ramdisk"
>                   9)  Bootable iso image w/read-only root"
>                   "  -----    For testing only!     -----"
>                   10) Read-write root on a single partition"  > 
> 
> 
> Ok, I can integrate this and get any/all parameters stored and loaded
> fairly easily.  I'll try to get the parameters from your rd_dialog
> functions...any list you have would be appreciated...
> 
> The next step is to activate the Erase/Foramt command to handle all the
> various partitions; and the Load command must build the ramdisk images
> etc..
> 
> Does this look like something that would work for all different targets ? 
> Suggestions ??
> Thanks,
> Ralph

While I have the author's attention,

The current version builds the filesystem into projects/<projectname>/mnt/. 
There's no note about where the filesystem is built (I discovered with
find).  Also, if I mount a ramdisk/drive/device to the mountpoint, the
filesystem build fails on a failure to make the directory.  Could you
possibly make that specific mkdir check to see if its a mountpoint first?

-David

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