**Slackware question ?? Update. (Network question)**
- Thread starter AFB
- Start date
I can boot from the first disk (iso) and get a live type system. Do I just run fdisk and make root and swap partions then install ?
Thank you so much, I have leaned more about linux in the past month than in the past 8 years. I still have a long way to go, but I am getting there. It is very nice of the Linux gurus to help out people that are Linux newbies, I greatly appreciate you reading this.
Thank you so much, I have leaned more about linux in the past month than in the past 8 years. I still have a long way to go, but I am getting there. It is very nice of the Linux gurus to help out people that are Linux newbies, I greatly appreciate you reading this.
You can.
I like to use cfdisk actually, but fdisk is fine.
Do like fdisk /dev/hda or cfdisk /dev/hdc or whatever. Remember there is no "c" drive in *nix, and the hardware resources corrispond to special /dev/ files. Hd* files represent IDE devices (cdroms, zip drives, harddrives, whatever).
hda=primary master
hdb=pimary slave
hdc=secondary master
hdd=secondary slave.
Then each partition for each harddrive is represented by a file with the hd* with the partition number added on the end. Like /dev/hda1 would be the first partition on the primary master harddrive and /dev/hdc3 would be the 3rd partition on the secondary master, etc etc.
I make one big / (root) partition for all my files, a /home partition so that I can format and reinstall the OS without messing up any user settings or files and a swap partition. You won't need a swap partition any larger then 512 (you can have it bigger if you want, though) megs or so, irregardless of how much real ram your running.
I like to write down the drive/partition names and what I want to use them for so that I don't get mixed up and forget which was which.
Once you get everything partitioned out, reboot if you want to make the changes perminate (not neccisary, but its a nice thing to do).
Once you boot up with the slackware install disk you would just type it "setup" if I remember correctly. It should have a couple pages of explaination you can look thru at boot up.
It will have a bunch of steps to go thru, you can skip some of them, but generally just go thru one by one
Once you get to the "target" stuff, format the partitions partitions as ext3 partitions, except for the swap of course. You can skip the sector scans or whatever if you don't want to wait and trust your harddrive to be healthy.
Once it becomes time to select what packages to install, just tell it to install everything and you will be fine. (uses up to 4 gigs or so, maybe more, I forget how exactly big it gets with "everything")
I like to use cfdisk actually, but fdisk is fine.
Do like fdisk /dev/hda or cfdisk /dev/hdc or whatever. Remember there is no "c" drive in *nix, and the hardware resources corrispond to special /dev/ files. Hd* files represent IDE devices (cdroms, zip drives, harddrives, whatever).
hda=primary master
hdb=pimary slave
hdc=secondary master
hdd=secondary slave.
Then each partition for each harddrive is represented by a file with the hd* with the partition number added on the end. Like /dev/hda1 would be the first partition on the primary master harddrive and /dev/hdc3 would be the 3rd partition on the secondary master, etc etc.
I make one big / (root) partition for all my files, a /home partition so that I can format and reinstall the OS without messing up any user settings or files and a swap partition. You won't need a swap partition any larger then 512 (you can have it bigger if you want, though) megs or so, irregardless of how much real ram your running.
I like to write down the drive/partition names and what I want to use them for so that I don't get mixed up and forget which was which.
Once you get everything partitioned out, reboot if you want to make the changes perminate (not neccisary, but its a nice thing to do).
Once you boot up with the slackware install disk you would just type it "setup" if I remember correctly. It should have a couple pages of explaination you can look thru at boot up.
It will have a bunch of steps to go thru, you can skip some of them, but generally just go thru one by one
Once you get to the "target" stuff, format the partitions partitions as ext3 partitions, except for the swap of course. You can skip the sector scans or whatever if you don't want to wait and trust your harddrive to be healthy.
Once it becomes time to select what packages to install, just tell it to install everything and you will be fine. (uses up to 4 gigs or so, maybe more, I forget how exactly big it gets with "everything")
Update, It doesn't boot. It says "Searching for boot record from IDE-0..OK" an then freezes. I bet lilo config, is FUBAR.
You can rerun lilo by using a chroot command.
Boot up with the install disk. Once you get to the command line mount the root partition from the harddrive to something like /mnt
mount /dev/hda1 /mnt
Then maybe mount proc, it's not nessicary though for lilo.
mount proc -t proc /mnt/proc
Then cd into the mounted partition, then use the chroot command to "change root" That will make you it so that that shell will operate as if it is running off of the harddrive, You can run most any command or do anything as if you rebooted into your harddrive.(within limits)
cd /mnt
chroot ./
Then edit the /etc/lilo.conf and make sure that it is ok. If you want to make sure that it is going into the mbr check the boot option. boot=/dev/hda goes to the MBR boot=/dev/hda1 means that it's going to the beginning of that partition.
After you make sure that lilo.conf is correct then rerun lilo. Then exit and umount everything and reboot.
lilo
exit
cd ../
umount mnt/proc
umount mnt
reboot
And that should fix lilo.
Boot up with the install disk. Once you get to the command line mount the root partition from the harddrive to something like /mnt
mount /dev/hda1 /mnt
Then maybe mount proc, it's not nessicary though for lilo.
mount proc -t proc /mnt/proc
Then cd into the mounted partition, then use the chroot command to "change root" That will make you it so that that shell will operate as if it is running off of the harddrive, You can run most any command or do anything as if you rebooted into your harddrive.(within limits)
cd /mnt
chroot ./
Then edit the /etc/lilo.conf and make sure that it is ok. If you want to make sure that it is going into the mbr check the boot option. boot=/dev/hda goes to the MBR boot=/dev/hda1 means that it's going to the beginning of that partition.
After you make sure that lilo.conf is correct then rerun lilo. Then exit and umount everything and reboot.
lilo
exit
cd ../
umount mnt/proc
umount mnt
reboot
And that should fix lilo.
It says "boot=/dev/hda1" instead of "boot=/dev/hda" is that ok ? That is the only error I could find.
That just means that it's going to install the boot loader at the beginning of the partition, not the harddrive.
The MBR is just the first sector of the harddrive. The first 512k or so if I am correct.
Just delete that 1 off of it and run lilo to install it in your MBR and then your BIOS should be able to find the bootloader with no problem
The MBR is just the first sector of the harddrive. The first 512k or so if I am correct.
Just delete that 1 off of it and run lilo to install it in your MBR and then your BIOS should be able to find the bootloader with no problem
Thanks, just reinstalled it. Lilo wasn't getting installed in the MBR. Thanks It works great except one thing, How do I configure an the network card ? I know the networking stuff, I just don't know set it up in Linux.
Thanks :heart:
Thanks :heart:
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 23K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 19K
-
-
-
Intel processors crashing Unreal engine games (and others)- Started by BFG10K
- Replies: 2K
Facebook
Twitter