SM Linux Folding Drive Image Pt2
Enverex
Worcester, UK Icrontian
Started a new thread because I don't seem to have access to view my old one anymore...
Anyway, I've been working on it all day and I managed to get the disk usage of the OS down to 470MB, even better is that the image of the disk compresses down to 174MB which makes the download considerably less painful. I'm just sorting out a few more things at the moment to make sure it works happily and then I should be able to put it up for testing.
Anyway, I've been working on it all day and I managed to get the disk usage of the OS down to 470MB, even better is that the image of the disk compresses down to 174MB which makes the download considerably less painful. I'm just sorting out a few more things at the moment to make sure it works happily and then I should be able to put it up for testing.
0
Comments
Assuming it has a net connection and there is a DHCP server on the network (would kinda be pointless without, heh) yeah, it'll run headless fine.
Just trying to find the best way to image it still.
One question: Does anyone think this is going to be imaged on to any drives SMALLER than 4GB?
SM4's drive is 1.6GB.
Don't worry too much about it, I've got a spare 10GB drive I can use. If it's easier to image it as a 4GB drive, go ahead.
I hate having it force a 4GB drive for 1GB of data anyway.
Anyways, here's a screenshot of the customised bootloader. I managed to get around the "what if it's SCSI? What if it's on the secondary controller!?" problem by putting them all as options. After the first boot (or after unimaging even) you can set the default via the grub file which I'll put in the documentation. But this lets you boot it without being able to modify it first regardless of where it is.
no backups because of no-where to back them up to .
That sucks, Env. I know that feeling. Hope you're back up and running soon.
Hopefully will be up tonight.
The contents of the drive when compressed with a basic bzip2 come to a huge 129.2MB, so the download isn't very painful.
No idea what the login details were (or address, etc).
Give me a shout if anyone wants to try it. I tested it on one of my SATA drives and it worked fine using my instructions above (took about 3 minutes, heh).
Prof should be interested that I've patched the kernel to use the BAD-RAM ability which means you can now use this on machines with defective RAM modules. I'll document this later if anyone is interested. The compressed archive is now down to 112MB with the entire extracted OS footprint being only 356MB.
No bites though, has everyone lost interest entirely?
I could swear I sent you a PM with the link... ok.. where the hell did I send it? lol