Jordan Share <[EMAIL PROTECTED]> writes: > I don't mind using shorter names, but maybe the master script should > give a warning if it finds directories with long filenames?
Good idea; I will implement this sometime. > Also, you may want to change the docs that say (paraphrased) "it > doesn't matter what the directories are named, since install.pl > scans the actual content of the directories". Done. > I tarred and bzipped up the entire $oem$ tree, and put it at: > http://waken.krotus.com/~jshare/oemtree.tbz Got it; thanks. I may not have time to play with it before this weekend, though. > Yes, I can use the "production" (3.5) unattended install with no > problem. Starting with version 4.0, we are using FreeDOS instead of MS-DOS on the boot disk. So experimenting with the current DOS-based boot disk might also be interesting. > Here's what I've done after the previous mail: > * Started a reinstall from "production" 3.5 unattended. > * Let it run partway, just to verify that it was working (it ran > past the point where it expands the partition and converts to NTFS) > * Then rebooted and tried to install from the "unbeta" 4.2pre2. Allowing it to repartition, or not? > * Now I get wacky errors when I try to use the unbeta: > > Proceed with Format (YES/NO)? yes > # *** Formatting 2000 Mbytes as FAT16. ***Safe QuickFormatting (trying > to save UnFormat data) > Drive_IO( command=READ sector=0 count=1 ) [FAT12/16] [drive > C*]Critical error encountered while using DOS disk driverDOS driver > error (hex): 01Description: unknown unit for driverProgram terminated. Wait, is this the DOS or the Linux boot disk? Note that this will not work once the partition is converted to NTFS. You have to let Unattended re-create the partition as FAT or else the whole DOS-mode sequence is going to have problems. Possibly these problems; I have never tried it... > I'm starting to wonder if the drive is being partitioned at all by > the unbeta. That would certainly explain some things. But I do not know why that would be. > Next, I reboot and partition under dos. Hmm, that's weird, I get: > fdisk_cmds = fdisk /clear 1;fdisk /prio:2000;fdisk /activate:1 > > ABOUT TO PARTITION THE FIRST HARD DRIVE! > WARNING: This operation erases the disk! > Are you sure[Y,N]?Y > > Re-checking partition table...no change. Continuing. > > So, the dos fdisk thinks that after it issued the command shown above > (we tweaked the install script to show fdisk commands when we were > setting up "multiboot" machines), there was no change to the partition > table. On the same drive which gave the errors above? That is weird... > Previously, when I've repartitioned under linux, it "calls IOCTL" to > reread the partition table (or something). Is that happening with the > unbeta? Yes. Parted does that call after changing the partition table; it just isn't noisy about it. You can see the results in dmesg (you can use Alt-F2 or -F3 to switch to another virtual console while the install.pl script is running). - Pat ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ unattended-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-devel
