[SoaS] [Sugar-devel] SOAS 2 problems
Thomas C Gilliard
satellit at bendbroadband.com
Wed Jan 27 07:59:27 EST 2010
I have done it. and it works. NO Persistence though
opensuse-edu does this also with an added twist. you can use fdisk (or a
script) to build a persistence partition after creating th usb with dd:
-----------------------------------------
# dd if=openSUSE-Sugar-live-unstable.i686-0.3.0-Build22.2.iso
of=/dev/sdg bs=4M
152+1 records in
152+1 records out
639631360 bytes (640 MB) copied, 118.261 s, 5.4 MB/s
root at 520n-robert:/home/robert/Desktop# fdisk /dev/sdg
The number of cylinders for this disk is set to 3824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdg: 4009 MB, 4009754624 bytes
64 heads, 32 sectors/track, 3824 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x86803d76
Device Boot Start End Blocks Id System
/dev/sdg1 * 1 610 624640 83 Linux
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (611-3824, default 611):
Using default value 611
Last cylinder, +cylinders or +size{K,M,G} (611-3824, default 3824):
Using default value 3824
Command (m for help): p
Disk /dev/sdg: 4009 MB, 4009754624 bytes
64 heads, 32 sectors/track, 3824 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x86803d76
Device Boot Start End Blocks Id System
/dev/sdg1 * 1 610 624640 83 Linux
/dev/sdg2 611 3824 3291136 83 Linux
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
#
--------------------------------------------------------
Links:
http://wiki.sugarlabs.org/go/Category:Liveusb
http://en.opensuse.org/Live_USB_stick
http://lizards.opensuse.org/2009/08/13/cliced-hybrids/
Xander Pirdy wrote:
>> Yes, this could indeed be the simplest solution: tell users to create a
>> read-only installation media by burning the ISO. Since Fedora 12, the
>> live ISO image also contains a bootable MBR, so users can just dd it to
>> a master USB stick:
>>
>> http://fedoraproject.org/wiki/FedoraLiveCD/USBHowTo#Using_dd
>>
>
>
> Correct me if I am wrong, this tutorial seems to be a bit ambiguous on the
> point,
> but would you loose persistence if you simply dd the iso? If not where is
> the
> storage for this located, or is it just a full-type of installation? If it
> is a full installation
> then this would mean that either you loose a journaling ext3/4 fs on the
> usb, or it
> will become inaccessible via windows (on a typical installation, and where
> the
> user doesn't have admin rights)...correct? If it is ever a goal to be able
> to boot via
> a virtual machine on windows wouldn't this make that impossible?
>
> I may just not be understanding you correctly, in which case my apologies. I
> do
> think that a full installation has more drawbacks than it seems initially.
> For
> example wouldn't it be very easy to upgrade the current overlay method, by
> just
> replacing the iso? This could also make it very easy for teachers to
> customize the
> activities of the students.
>
> -Alexander Pirdy
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> SoaS mailing list
> SoaS at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/soas/attachments/20100127/92b9545c/attachment.htm
More information about the SoaS
mailing list