Hmm ! Itz a mixed reaction eh ?
Quote:
In all my years as a Slacker I've never heard of this happening. What you're saying is that you successfully installed to an external drive, booted, then compiled 2.6 and suddenly all your main binaries disappeared?
Did you happen to uninstall any packages?
|
Nope ! I INSTALLED packages after compiling them to suit the architecture of my hardware.
More than the binaries, it were the libraries that were hit worst.
Quote:
compile your own kernel with USB support built-in.
|
In my experience of 5 years with linux on an external drive, I've never had success with usb/firewire support built in kernel. Seeminlgy, the kernel doesn't wait long enough for the device to initialize (this is especially true for ext. HD as it takes time for the ext HD to respond) and before it does tries to mount the real root and bang ! Kernel Panic !!
Quote:
you broke the system down, it's not its fault
|
&*&*#$^* ???? I don't think I understand that ! Seems like you know what exactly I did wrong or went wrong. May be you can shed some light on this !
Quote:
It almost looks like to celebrate your 100th post you decided to troll the Slackware forum.
|
;-D
Quote:
1) Imagine yourself driving towards a brick wall with a bomb in the front seat. What would be the first thing you would do? (Stop, or at least slow down and give yourself a fighting chance.)
|
Ha ha ! Ho ho ho ! Whatz the bomb here ? The compiler ? slackware ? libs ? or myself ?
Quote:
2) There's no good reason to recompile the packages. If you just use it for a day or two, you'll notice that Slackware is already faster than SuSE10.
|
Why can't I compile pkgs for the architecture that I wanna. Slackware is faster than SuSE or that the difference in performance/speed between i386 and pentium4 bins on a P4 may not be noticeable is a different issue altogether. Technically it should be possible to compile the package to any arch that it supports. I wanted to do this just for the fun of this. :-))
Quote:
3) Installpkg didn't delete your lib files... you're asking the wrong question. You're complaining about Slackware, .....
|
Oh ! Hold your horses buddy ! before you jump to conclusions about me complaining about slackware. Complaining about slackware ??&^&*^&*^& Never mind !
Quote:
but I'm not sure that what you have on your hard drive can still be called "Slackware".
|
Excuse me ! If slackware from your point of view is the distro that comes with the precompiled binaries which you'd accept and live with it without recompiling/modifying, then YES, what I've got on my HD cannot be called slackware !
Quote:
Was your external drive usb drive?
|
Plz. read the first posting.
OK guys ! I expected someone to hint me at what could have gone wrong and thus not to seethe (knuckles) nor curse nor to thwart back at me like this ! I don't know what exactly went wrong ! But, I know, all I did was to install slackware and then try and compile the packages with i686/P4 arch and installing these packages simply resulted in lost bins and libs. ls didn't work, mount didn't work, logout/exit/reboot didn't work either. Holding the power button for few seconds worked just great !! ;^)
Now, I have reinstalled slackware for the 5th time with kernel 2.4 and it seems to be working OK. I have not tried to compile my own pkgs and I have no intentions to do so. I'd use SuSE for that. :-))
I mentioned in my thread starter that, kerne; 2.4 is complaining about module not being in ELF format. Yep, strange as it is, the precompiled kernel that comes with slackware is having ELF support built in as the default binary format yet, the modules that came with the kernel are a.out format ! I'd to compile my own kernel which compiled the modules in ELF format and the initrd problem has been resolved.
I think, the reason why I couldn't do what I wanted to do would remain a mystery unless I do it again and get to the root of it. ;-) I've got no intention of doing that at least for now. I've already spent 3 days into this and I think this thread should be closed now. At least from my end. ;-D