Hello debian users! my problem description is as follows: I couldn't wait for the beta and the 2.00.34 kernel and the fixed hamm packs that came with it. so I installed the base system and 2.00.33, and started DLding packages. "No", said dselect, you need newer base system to run many of the packs. Ok, I got a newer rescue, drivers, and base2_0.tgz . I've loaded the rescue disk and simply selected the devices, installed the kernel and the base and created a boot disk as was adviced (and created a default boot manager). On reboot, I got a nice "LI".... When I tried to use the boot disk after a reboot, it simply took milenia to load (much longer than it takes usually, and seemed to halt completely), so I had to reset. Now, I did the rescue process all over as before, used the custom boot disk and real problems began. First of all, I was asked to set a root password. I tried all the posible passwords, it agreed and wrote them to disk! but then asked me to write another one. I simply couldn't exit passwd and started another VT, I killed the original VT, and from the new VT started passwd and it worked. After a reboot I discovered that the system logins automatically as root! But that's not all: Programs are missing files, sometimes only minor like readme 's, daemons are not loaded etc. looks like a filesystem failure.
What's my next move? Is it a bug? Is it something I did wrong? By the way, what is the passwords file? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]