• Please review our updated Terms and Rules here

Installing an older version of Slackware Linux

Status
Not open for further replies.
The PC is an AMD CPU Ryzen 3? I think. 64GB of RAM. Debian is installed and working fine. Had a bit of a SNAFU with the Adaptec card. Looked like it was plugged in for power but wasn't getting it. I changed over to a different plug and felt it seat. It now shows the Adaptec BIOS msg. I had run LSCSCI but did not
see my SCSI drive. I should now after it reboots.
 
If the system isn't completely locked up you can just go to another tty with ctl-alt-F whatever, log in as root and run top to veiw the processes taking too much ram and kill those processes. Then change back to where you were and the system should be fine. At the very worst you will be dumped to the cli prompt or login prompt, graphical or cli. depending on how the Lnux installation is set up.
 
Last edited:
It appeared to have dropped out of the GUI set up screen to display those messages. Yes, I suppose I could have switched to another TTY and checked. I did not do so, and it really doesn't matter now as that system will just stay a DOS system forever now. I have no idea how long it would have taken to fully installed Linux. Painfully slow coming from the CDR.
 
Just to be clear: P1 = 586 Ppro+ = 686. So there's an abrupt change in Linux not running on a p1.

I should dig my old P1 box out from the pile--I use it for NT4 and a Linux distro; just can't remember which one offhand. I think less than 64MB memory on it. I do recall that NetBSD will run on most x86 boxes 386-and-later (non GUI). I recall having to use it to grab some tapes using a QIC36 interface drive. Old Linux drivers for ftape were really buggy and unstable.
 
Last edited:
It appeared to have dropped out of the GUI set up screen to display those messages. Yes, I suppose I could have switched to another TTY and checked. I did not do so, and it really doesn't matter now as that system will just stay a DOS system forever now. I have no idea how long it would have taken to fully installed Linux. Painfully slow coming from the CDR.
Depends on the Distro and what you choose to install. Installation on my AMD system of TinyCore Linux took less than 15mins and that included X windows and TCs "desktop". Once installed you can install other applications, including window managers, such as KDE/XFCE4, browsers such as Chromium and tons more. Some application are older versions but all have been tested and proven to run with TC. TCs GUI nterface took about a hour to get the hang of. As usual RTFM...... http://www.tinycorelinux.net/corebook.pdf

First thing I do once any variant of Linux is installed is install mc if it wasn't installed by default.
 
Last edited:
If someone is new to Linux and in cli mode mc gives that person a damn good idea how the file structure is in "modern Linux" and the various BSDs. with mouse support. Do the same in something like, say Xandros 3 and you'll see note that not much has really changed....Due to the formation of the Linux Foundation the file structure is better standardised from Distro to Distro.
 
Last edited:
Actually, not a lot of the fundamentals have changed since I was using System III back in the early 80s. Very familiar territory, if you're used to the cli.
 
He did say this was more for someone new to Linux. You and I are not new to it. I've been using it for decades.
 
That's what I found Chuck when first investigate this Linux thing in the the late 90s early 2000s.

If you haven't heard of mc you haven't been taking much notice *nixs. A lot of earlier ones installed it by default.
 
You didn't know the install routine locks the opticle media during the setup/install routine either. All Linux distros I've installed since the late 90s did as well....
 
I had forgotten. I rarely use CD these days. I haven't for years. Had a pile in my closet but have not used them in some time. Give me a break. So not remember that is cause where I should use this tool. It just seemed the CD had lost power. No blinking from it. As it had been blinking during the partial install. And why did it lose it after booting off it? That seems most odd of all.
 
The kernel was being decompresed and loading into a ram disk....The cd in the drive didn't need to be accessed at that point in time.
 
Ah, but during the install of all my selected packages it needs to access the CD. Otherwise there would be no point in asking me for what I wanted to install? Right? Can we put this part of the thread to rest? Please. I made a mistake on the CD and asked a question. Then you jump on my back.
 
Try and be a bit more patient next time installing it on old hardware with a meager amount of ram....

Red Hat 6.2 would've installed just fine on it. Just like it did on my AIO Compaq Presario CDS524 with a 486DX2/66 cpu......AND picked up EVERY bit of hardware on it no worries at all.

Mandrake 6.1 did as well even though it was ment to be a i586 distro:486linux.jpg486linux2.jpg
 
Last edited:
Normally I would not have even tried to install that there. But it was available and working. I still believe the 32MB of ram was my primary issue. Nothing I read even suggested this minimal amount would work even for Slackware. But I did it anyways as I am lazy sometimes. It was much easier to install on the new PC with a newer version of Linux. It might have helped if the error message were better than just "killed". I did not want to run Red Hat. I always liked Slackware back in the days so went with that. Can we give this topic a break now? You have no idea if it would have installed on my system as you don't know how it's configured. Saying it works for me so it should work for you too has always bugged me when people say that. I will not be replying to any more comments posted in this thread.
 
Slackware 15 will install on a Pentium 133 with 32megs of ram as well with the generic kernel.
The same goes for Slackware 14.2.
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top