Journal zukinux's Journal: Slackware 12.0 here I come!
So... a while ago I've started to download Slackware 12.0 DVD Iso, which became my worst downloading nightmare, ever.
I've downloaded the Slackware 12.0 torrent and waited for it to finish, after 2 weeks or so, it was something like 98% done! but then, someone hard-shutdown my computer, and most of the pieces were wrong and it tried to download 95% of the 98% pieces. It took me another 2 weeks, but I'm done! md5sum for the ISO showed a good ISO and I was actually quite happy :)
So... I wanted to format my dual boot winxp-slackware11.0 computer, but I havn't used the XP for like 1 year, so I thought I might drop by to check how's the XP going.
When I've entered the windows XP I've found out I had a password to enter XP, so I've tried all the password I use in many variation un-till the user got locked.
I've restarted to Slackware 11.0 and searched for solutions on the internet, and found out there's a linux-based live-cd that re-write the SAM (Security Accounts Manager) but it was too late, cause it doesn't know how to handle a locked users.
I had in-fact to reinsert win-xp installation CD to repair the locking and so that's what I've done, after that I re-used the linux-based live-cd to override the SAM's current password, and WALLA, I got in.
But then I've found out there's nothing important like I thought while I was looking at the computer from the linux Terminal, but had to make sure, and I've restarted again to re-install the Windows XP (this time with only 35 GB unlike 60 the other time).
Done that... was a charm (NOT!) and then I've had time to the real installation, SLACKWARE 12.0!! , I was excited, at first I used the 2.6.21.5-SMP Kernel for the Installation, and it worked like a charm, finished the Installation and I was like... I got a strong feeling I will get a kernel panic on this one. So I was right, and I got a kernel-panic, for no-reason (Well... It said that VFS was not mounted, but actually there was not reason for it to happened [ I've also tried to log with appending some lines in lilo like : root=/dev/sda2 noinitrd... etc, nothing helped] ).
So I've re-installed using the normal 2.6.21.5 Kernel, and found out there's something even weirder in that installation : /sbin/ wasn't really mount, which means that the step from VFS to Real FS wasn't really made, and I'm not sure why I didn't get any kernel panic!
I've reinstalled using the 2.6.21.5-smp kernel, and done the same stuff I did in the first installation, thought this time I gave /opt more 5 gb, that's the only difference from the first installation, it worked!, why? I don't know.
Giving more 5 GB to /opt shouldn't have had any affect on the computer!!
That was totally weird, but I didn't stay their to ask my computer why it didn't work.. I've installed some necessary programs such as checkinstall, aMule, Azerus , configured my own box such as things on start-up scripts, ssh, customization of my DHCPCD script, and such and such stuff, compiled a newer kernel
I was done, and now I can be happy with my-self, I'm on my new Slackware 12.0.
Good bye, and enjoy the week :)
I've downloaded the Slackware 12.0 torrent and waited for it to finish, after 2 weeks or so, it was something like 98% done! but then, someone hard-shutdown my computer, and most of the pieces were wrong and it tried to download 95% of the 98% pieces. It took me another 2 weeks, but I'm done! md5sum for the ISO showed a good ISO and I was actually quite happy
So... I wanted to format my dual boot winxp-slackware11.0 computer, but I havn't used the XP for like 1 year, so I thought I might drop by to check how's the XP going.
When I've entered the windows XP I've found out I had a password to enter XP, so I've tried all the password I use in many variation un-till the user got locked.
I've restarted to Slackware 11.0 and searched for solutions on the internet, and found out there's a linux-based live-cd that re-write the SAM (Security Accounts Manager) but it was too late, cause it doesn't know how to handle a locked users.
I had in-fact to reinsert win-xp installation CD to repair the locking and so that's what I've done, after that I re-used the linux-based live-cd to override the SAM's current password, and WALLA, I got in.
But then I've found out there's nothing important like I thought while I was looking at the computer from the linux Terminal, but had to make sure, and I've restarted again to re-install the Windows XP (this time with only 35 GB unlike 60 the other time).
Done that... was a charm (NOT!) and then I've had time to the real installation, SLACKWARE 12.0!! , I was excited, at first I used the 2.6.21.5-SMP Kernel for the Installation, and it worked like a charm, finished the Installation and I was like... I got a strong feeling I will get a kernel panic on this one. So I was right, and I got a kernel-panic, for no-reason (Well... It said that VFS was not mounted, but actually there was not reason for it to happened [ I've also tried to log with appending some lines in lilo like : root=/dev/sda2 noinitrd... etc, nothing helped] ).
So I've re-installed using the normal 2.6.21.5 Kernel, and found out there's something even weirder in that installation :
I've reinstalled using the 2.6.21.5-smp kernel, and done the same stuff I did in the first installation, thought this time I gave
Giving more 5 GB to
That was totally weird, but I didn't stay their to ask my computer why it didn't work.. I've installed some necessary programs such as checkinstall, aMule, Azerus , configured my own box such as things on start-up scripts, ssh, customization of my DHCPCD script, and such and such stuff, compiled a newer kernel
I was done, and now I can be happy with my-self, I'm on my new Slackware 12.0.
Good bye, and enjoy the week
Slackware 12.0 here I come! More Login
Slackware 12.0 here I come!
Slashdot Top Deals