![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Linux Support Linux - Operating Systems and Applications Support |
![]() |
|
|
Thread Tools |
|
|
#22 (permalink) |
|
Moderator/Gearhead
|
Certainly. And I just about guarantee you'll love it. You just need another partition to install PCLOS on. Once you install PCLinuxOS, you'll need to manually add Ubuntu back onto your menu.lst (For GRUB)
__________________
![]() Registered Linux User #435503 Don't let socialists take over this country. Vote Nobama 2008! Last edited by K-B : 03-06-2007 at 06:33 AM. |
|
|
|
|
|
#23 (permalink) |
|
Mentally divergent
Join Date: Jun 2005
Location: Chehalis, WA, USA
Posts: 1,178
OS: W2K, Ubuntu 8.04
|
Kyle -
How would you suggest yustr set things up so that he can load more than one Linux distro? The only method I'm at all familiar with is chainloading. Here's a link back to that thread where I built a couple of guides. Dual LINUX OS yustr, the GPLCD guide might or might not be helpful, but I'm thinking the PCLOS guide should help you to get an idea how GRUB identifies partitions, and how to chainload OS'es. I've built a couple of multi-boot HDD's. They were all-Linux, but the principles are the same for a Windows/Linux setup. Chainloading works very well once you figure out the exact commands that need to be added to GRUB. I have two comments regarding those guides. Both comments refer to possible problems that might crop up down the road that I was unaware of at the time I wrote them. In both cases, the multi-boot will work at first but updates may make a mess of things. #1 If you enter your Linux partitions in menu.lst above the Debian Auto-Magic divider, the next time you download a kernel update GRUB will lose track of your Linux partition. I am not sure of the best way around this. I've manually re-entered the GRUB data, but can't remember right now how I did it (found directions on Ubuntu forums). I've read that a way to eliminate this problem all together is to place your Linux partitions in menu.lst underneath the Debian Auto-Magic divider. Again, read this on Forums. But haven't tried that. #2 The other complication also crops up whenever you do updates, but I believe this comes up every time you update. The problem wasn't there in Dapper but is in Edgy and will continue in newer releases. If you compare fstab in Dapper and fstab in Edgy, you'll see that Edgy added a UUID identifier to the list of automatically mounted devices. My understanding is that the UUID identifier was added to make it more convenient for system administrators. Even if you moved the HDD to a different physical location the OS will pick up the UUID. Or something like that This may be great for its intended purpose, but it makes things harder for the rest of us. The fix (I'm told) is to carefully delete the UUID from fstab and leave everything else on the line. I haven't explained how this UUID thing gets you yet, so I'll do that now. If you have only one Linux OS UUID doesn't cause problems because fstab is updated also and you simply keep on trucking without even knowing what happened in the background. However. Let's say you have multiple Linux OS'es. You update one of them. That UUID identifier has now changed. Your other Linux OS'es doesn't know that, and when you start another one you get a weird "fsck" error message, then you're dumped to a text recovery screen. Being a terminal newb, I decided that multi-booting was just not worth the hassle and now intend to settle on one distro. I'm kinda tired of thinking I figured something out well enuf to get by, then getting slapped upside the head again. You can get past these hurdles. I just wanted to let you know they're out there. |
|
|
|
|
|
#24 (permalink) |
|
Moderator/Gearhead
|
Actually, I've never done/tryed chainloading. The way I would've done it is to manually add the lines to GRUB like they say here:
http://www.newlinuxuser.com/adding-o...stems-to-grub/ But it seems to me that this PCLOS guide would be good to follow. http://pclinuxonline.com/wiki/GrubMenu I'd forgotten about that one.
__________________
![]() Registered Linux User #435503 Don't let socialists take over this country. Vote Nobama 2008! |
|
|
|
|
|
#26 (permalink) | |
|
Moderator/Gearhead
|
Quote:
![]()
__________________
![]() Registered Linux User #435503 Don't let socialists take over this country. Vote Nobama 2008! |
|
|
|
|
|
|
#27 (permalink) |
|
Mentally divergent
Join Date: Jun 2005
Location: Chehalis, WA, USA
Posts: 1,178
OS: W2K, Ubuntu 8.04
|
Sorry, carsey, I saw yustr's post on the top of a new page and just started responding without thinking about whose thread it was...
Kyle, is that your blog? I like it! "Chainloading" is a common description for the process of manually entering those lines in the GRUB menu.lst, just like your two links. |
|
|
|
|
|
#29 (permalink) |
|
Asst Manager, TSF Articles
|
Hi Chris,
In terms of what size HD to go for, get the largest you can afford. There's not a lot of difference in price between a 60 G and a 320 G. Think about future proofing. I can still remember when my colleagues wondered what on earth I needed a 10 MB HD for. Regards, John.
__________________
If you feel that TSF has helped you please make a donationand help to keep the forum free Cenedl heb iaith, cenedl heb galon |
|
|
|
|
|
#30 (permalink) | |
|
Moderator/Gearhead
|
Quote:
![]() No, that's not my blog, but I wish it was:D
__________________
![]() Registered Linux User #435503 Don't let socialists take over this country. Vote Nobama 2008! |
|
|
|
|
![]() |
| Thread Tools | |
|
|