My apologies - the binary.img generated by live-helper is a variable size depending how stripped the core OS is and which additional programs have been installed - so I shouldn't specify a size for it as you have in your system - additionally it would would make reconfiguration impossible for the linux newbies who will be the ones actually using all of this.
My overall aim is to have a two partition USB drive - the first partition is defined by the binary.img and the second partition is defined by the space left over - to be used as the live-rw partition. Some of the applications I have create (potentially) GBs of logs that need storage, others can work happily with no persistant storage at all so I want to get the partitioning all script based and flexible - which is how I have it configured/working at present. On Mon, 2009-03-09 at 23:37 -0700, Jordan Share wrote: > David Cottrill wrote: > > Thanks - I need to get out of having a "representative" disk because > > I'll be working with many, many applications and disks. > > You still haven't actually specifically said what your goal is. :) > > For example, my goal, in the technique I described, is to take any size > disk, make a standard sized /dev/sda1 and use the rest of the disk for > /dev/sda2. (Which sounded to me like what you might be interested in.) > > Do you have a specific set of partitions and then a "rest-of" partition? > Or an unknown set of partitions and a "rest-of" partition, etc? It is > not clear what your goals/parameters are. > > > I guess I'll > > have to settle for working out how to extract the information I need > > from 'sfdisk -lm ' > > I said "representative disk" to describe the original partitioning > method, but really I suppose I meant "representative partitioning". I > apply that sfdisk file to *any size* disk and it gives me the layout I > want (~512MB /dev/sda1 and rest of the disk for /dev/sda2). > > I was suggesting that you take a disk (any size), and set up your > partitions how you like them, then dump the partitioning, remove the > "size=xxx" from the dump file, etc. > > Also, if you really must parse, you might have more accuracy with > "sfdisk -d", since that gives you the output in integer sectors, rather > than cylinders (which might be fractional). Plus, it is intended for > parsing (by sfdisk, anyway. :) > > Jordan > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
