Re: Bug with fixit live 8.0 memstick.img running on F1 after MBR

[Julian H. Stacey]

Hi Ken,
cc hackers@, re@

 On Wed, 2010-04-21 at 21:09 +0200, Julian H. Stacey wrote:
  Hi hackers@,
  No replies in over 4 days to this, so this is a repost,=20
  I've also added re@ as newish memstick.img might interest them ?
 
(The live command prompt on F4 wasn't much use, no ls yet.)
 
 echo *

Ah Yes !
Sorry I'm so dyed in the wool I forgot, 
( I tend to assume sh, even though FreeBSD went csh with
internal echo maybe a decade back. )
(PS 'cat .' is another arcane trick in some other contexts :-)



 trying to do.  There is a script named make-memstick.sh in
 /usr/src/release/scripts on head and stable/8 (it got added after
 8.0-RELEASE was out) that I use to make the memstick images.

... 

OK, Thanks I'll take a look at your script, 
 if I have something useful to contribute, will send-pr  cc you.

Cheers,
Julian
-- 
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text,  Not HTML quoted-printable Base64 http://www.asciiribbon.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: Bug with fixit live 8.0 memstick.img running on F1 after MBR

[Ken Smith]

On Wed, 2010-04-21 at 21:09 +0200, Julian H. Stacey wrote:
 Hi hackers@,
 No replies in over 4 days to this, so this is a repost, 
 I've also added re@ as newish memstick.img might interest them ?

   (The live command prompt on F4 wasn't much use, no ls yet.)

echo *

That said you usually run into a different thing you can't do
shortly after finding out what files/directories are there...

  Conclusion:
Would be nice if others tried too, to tell if it's my mistake or a bug.
WOrth doing as it also sets you up ready with a stick that can rescue/
fixit + has enough space for other file systemes with your own
personal /usr/local inc. X, ready for eg testing laptops in shops.

I won't have much time to fiddle with this in the next few days but
just a few misc. comments.  I never pictured someone wanting to do
what you're trying to do with the memstick images so this sort of
thing was never tested (at least by me).  I pictured people taking
a totally different approach to doing the general thing you are
trying to do.  There is a script named make-memstick.sh in
/usr/src/release/scripts on head and stable/8 (it got added after
8.0-RELEASE was out) that I use to make the memstick images.

If you don't like what's on the memstick images we provide you
can basically roll your own using that script, possibly by
starting off with what's on our memstick image (just mount
it and copy everything off it to a directory that you then
add/remove stuff to produce what you want).  Just as a quick
example if you wanted the full DVD (packages and all) on
a memstick you could stick the DVD in a drive (or mount
the DVD .iso file as a vnode md or whatever) and do:

  make-memstick.sh /cdrom dvd.img

Then copy dvd.img to a drive.  Or, more to your point,
copy /cdrom to normal disk space and then add/remove stuff
before running the script.

The make-memstick.sh script is, on purpose, very basic.  It
just barely does what I need it to and can be used as a base
to come up with your own script that does more if you find
that doing this sort of thing happens often (testing laptops
in shops, etc).
-- 
Ken Smith
- From there to here, from here to  |   kensm...@buffalo.edu
  there, funny things are everywhere.   |
  - Theodore Geisel |



signature.asc
Description: This is a digitally signed message part

Re: Bug with fixit live 8.0 memstick.img running on F1 after MBR

[Julian H. Stacey]

Hi hackers@,
No replies in over 4 days to this, so this is a repost, 
I've also added re@ as newish memstick.img might interest them ?

Reference:
 From: Julian H. Stacey j...@berklix.com 
 Date: Sat, 17 Apr 2010 12:05:46 +0200 

Julian H. Stacey wrote:
 Hi Hackers,
 Bug found with fixit live 8.0 memstick.img running on F1 after MBR :
 
 First I checked my PC BIOS boots OK:
   I copied 8.0-RELEASE-i386-memstick.img to a raw 2G USB stick, it boots
   fine,  one can go into fixit menu, using image on stick
 
 Next
   I fdisk partitioned an 8G stick  copied 8.0-RELEASE-i386-memstick.img
   to F1 (da0s1), set F1 active, booted OK, went into fixit, selected
   USB stick for the live media,  it failed to find a USB media.
 
   (The live command prompt on F4 wasn't much use, no ls yet.)
 
   I tried telling it to install to F2 (6.5 G ufs), using files from
   local FS on stick, (I told it path 8.0-RELEASE ) but on 2 attempts,
   it couldnt find where to install to get bins from.
 
   I since confirmed those files are there on F1 8.0-RELEASE/ , see below.
 
 Conclusion:
   Would be nice if others tried too, to tell if it's my mistake or a bug.
   WOrth doing as it also sets you up ready with a stick that can rescue/
   fixit + has enough space for other file systemes with your own
   personal /usr/local inc. X, ready for eg testing laptops in shops.
 
   I since mounted my 8G stick on a normal 8.0 PC  installed F2
   from /usr/src  /usr/local from hard disc. I have another 4G I
   could test with MBR, but testing here is disruptive as only my
   main machine has boot- off- USB functionality).
 
 I mounted both sticks later to document what I was using:
 
 2G stick with no MBR, (`dangerously dedicated', that worked OK:
   ls -l /devusb/red - /dev/da0a
 
   df | grep usb
   Filesystem  SizeUsed   Avail Capacity  Mounted on
   /devusb/red 921M858M-11M   101%/usb/red
 
   disklabel da0
   # /dev/da0:
   8 partitions:
   #size   offsetfstype   [fsize bsize bps/cpg]
 a:  1803124   16unused0 0   
 c:  18031400unused0 0 # raw part, don't 
 edit
   disklabel: partition c doesn't cover the whole unit!
   disklabel: An incorrect partition c may cause problems for standard system 
 utilities
 
 8G stick with MBR:
   fdisk da0
 *** Working on device /dev/da0 ***
 parameters extracted from in-core disklabel are:
 cylinders=977 heads=255 sectors/track=63 (16065 blks/cyl)
 
 parameters to be used for BIOS calculations are:
 cylinders=977 heads=255 sectors/track=63 (16065 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 63, size 2988027 (1458 Meg), flag 0
 beg: cyl 0/ head 1/ sector 1;
 end: cyl 185/ head 254/ sector 63
 The data for partition 2 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 2988090, size 12707415 (6204 Meg), flag 80 (active)
 beg: cyl 186/ head 0/ sector 1;
 end: cyl 976/ head 254/ sector 63
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED
 
   mount 
 /dev/da0s1a  on /usb/sanblack.img (ufs, local)
 /dev/da0s2a  on /usb/sanblack.ufs (ufs, local, soft-updates)
 
   df 
 Filesystem  SizeUsed   Avail Capacity  Mounted on
 /dev/da0s1a 921M858M-11M   101%/usb/sanblack.img
 /dev/da0s2a 6.3G2.7M5.8G 0%/usb/sanblack.ufs
 
   cd /usb/sanblack.img/8.0-RELEASE
 du -s kernels # 60M
 ls base   # base.aa - base.bl, base.inf base.mtree install.sh*
 
   disklabel da0s1
 #size   offsetfstype   [fsize bsize bps/cpg]
   a:  1803124   16unused0 0   
   c:  29880270unused0 0 
 
   disklabel da0s2
   a: 12707399   164.2BSD0 0 0 
   c: 127074150unused0 0 

Cheers,
Julian
-- 
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text,  Not HTML quoted-printable Base64 http://www.asciiribbon.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org