p0tp
Group: Members
Posts: 3
Joined: Aug. 2005 |
|
Posted: Aug. 31 2005,02:14 |
|
Ok, as briefly as possible: I have a 512MB USB drive that I've been massaging DSL-embedded (or 5way) on for about 4 months, and it is now completely and officially kicking @$$ up and down the block!!! Boots up perfectly on my home machine, and runs all day on top of W2K pro on my work machine in qemu without a hitch.
I recently used qemu-img to create a new 128MB image file on the USB drive, which I then mounted under my qemu environment as a new hard disk (hdc). I modified everything to use the new 'hdc' for all backup/restore and myDSL files, thereby eliminating the risk of running out of room on the stock 'hdb' disk image file, which would have made me very very sad and probably caused me to break nearly everything within reach. And voila, it worked!
But then I got home and booted the USB drive directly, and quickly realized that all my configuration info and myDSL files under my new qemu environment don't show up to the direct-bootable DSL environment.
So, long story, but stupid simple question: how/what do I modify so that the direct-boot DSL will recognize the new 'hdc' image file on my USB drive? An mtab entry? fstab? The primary trick to getting it working on the qemu side was modifying "dsl-windows.bat" to assign the image file to a drive, but now I'm at a loss for what the analog would be on the direct-boot side.
Any suggestions? I feel like it should be something extremely obvious, but so far not much about this project has been obvious, so I'll go ahead and publicly confess my ignorance/stupidity.
Thanks!
|