Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just found out that RH comes with parted, so that's probably already installed on your machine as well, and yes masterc is right, it looks easy enough.
An other question:
Is it possible to share boot partition?
I will install debian far beyond the 1024 cilinder and quite frankly I'm not sure wether my machine is able to boot from beyond the 1024th, so I want to play it save.
btw: is there a way to check wether I can boot debian from beyond the 1024th? I use the Grub bootloader.
is there a way to check wether I can boot debian from beyond the 1024th? I use the Grub bootloader.
It has more to do with your BIOS than your bootloader. If your box is only a couple yrs old, that shouldn't be a problem.
Is it possible to share boot partition?
Totally, and to give you an example off how it works, you could have only one kernel in a boot partition and use it on different installs on different partitions.
I've never done it [...so you might wanna get a second opinion] but I probably would feel more comfy to do it manually by copying the 2nd install's kernel into the boot partition and editing fstab after the fact as opposed to letting a 2nd install write to /boot during install...but it's probably safe anyhow.
So I could just try installing everything on the root partition and then if it turns out that I can't boot from there copy the kernel to my exisisting boot partition.
Originally posted by annehoog So I could just try installing everything on the root partition and then if it turns out that I can't boot from there copy the kernel to my exisisting boot partition.
Right?
Anne
You got it.
If worst comes to worst, you could always use the booting kernel [...existing install] to boot the FS that's past the 1024th cyl.
It's just a matter of writing the right menu.lts [...or grub.conf for R-H???] entry.
That way you could salvage your install, let alone the fact that you can always use your install CD's rescue or the existing install in "chroot" mode.
btw, the same principle can be applied to /home if your distros are close, app-version-wise, but /boot is a sure bet.
Thanxx guys. I think that now my pre-installing questions are answered.
I've dedicated coming sunday to installing debian on my to be created new partition.
I'll keep you informed on the progress.
I succesfully resized my existing partitions and added a root partition for debian and a /docs partition for them to share. (thanks to RH for putting parted on their rescue disk)
Then I installed Debian......which is where problems began
-install went ok except: I selected es1370 as my audio driver only to find out afterwards that I should have selected es1371 (ooops!!!) Can I just add a module to fix this?
-I got confused at the interface of taksel resulting in me breaking of the config programm early by accident. (no idea what is installed and what isn't)
-It kept asking me questions I knew nothing about (networking dial-up configs and such) I hope I didn't do anything irreversible and that (after I install the modem drivers-I have a Intel ham modem) I can get my connection up)
-I can't get in to X (trying to fix that by comparing the XFree86 files of RH and Debian)
I know I could, but then I would get a bloated config file (due to some major experimenting I did in RH)
I'll do it for now though and I'll save the old file so I can always clean up the mess later.
Anne did you manage to get Slackware up?.. I know I did .. I had a little trouble getting up my DSL connection.. But its working fine now... And let me know hows debian.. As I left about 9GB free for new distros.. Right now I have RH8 and SLack.. ANd maybe I'll try freeBSD
I put installing Slackware on hold for a while b/c I caved in to the pressure of some seriously debian addicted coleagues of mine.
But how knows, maybe that'll be my next project.
First experiences with Debian are good.
Install went easier than expected and I only ran in to problems after the base-system already had been installed. Trouble began running taksel (to select which packages to install and which not) b/c I didn't understand the interface gave enter and it went right in to installing packages I didn't want (like KDE) leaving me with a somewhat bloated system which I'll have to clean up.
Also the post-install confronted me with some network and serverrelated questions I knew nothing about. So I'm so hoping that I'll be getting my internet up.
Which leads me to the last problem I encountered, which is related to the fact that Debian assumes you have a hardware modem which it can set up itself, but I have a linmodem which I have to install manually, so much of the post-install config I had to skip and i'm hoping I'll get it right manualy after I install the modem.
Also setting up X was kind of tricky for a while but copying my RH XF86-config file to Debian solved the issue
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.