Hi, I'm going to re-install a Linux-machine (my home-server). This time I would like to be able to install e.g. a next vesion of Suse but keep the old one available (with maybe a third OS, no Win though). This time I'm going to put in a new disk and keep the old one to be able to switch back until all is OK. But in the future it will be 1 disk. I have a few questions regarding this all. Is there a how-to somewhere I can follow ? What's a good partitioning scheme ? swap (of course) /boot ? size ? / /home others ? Is Suse (10.0 and 10.1) able to modify Grub automatically or will I have to edit the menu manually ? Any other comments ? Thanks for any input. -- Met vriendelijke groeten, Koenraad Lelong A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Mon, 2006-06-19 at 10:39 +0200, Koenraad Lelong wrote:
Hi, I'm going to re-install a Linux-machine (my home-server). This time I would like to be able to install e.g. a next vesion of Suse but keep the old one available (with maybe a third OS, no Win though). This time I'm going to put in a new disk and keep the old one to be able to switch back until all is OK. But in the future it will be 1 disk. I have a few questions regarding this all. Is there a how-to somewhere I can follow ? What's a good partitioning scheme ? swap (of course) /boot ? size ? / /home others ? Is Suse (10.0 and 10.1) able to modify Grub automatically or will I have to edit the menu manually ? Any other comments ? Thanks for any input. -- Met vriendelijke groeten, Koenraad Lelong
Great GRUB and multi-booting resources: * http://www.linuxquestions.org/linux/blog/saikee * A grub menu booting 100+ systems of Dos, Windows, Linux, BSD and Solaris: http://www.justlinux.com/forum/showthread.php?t=143973 * Just booting tips: http://www.justlinux.com/forum/showthread.php?t=144294 * Saikee's grub booting tips: http://www.justlinux.com/forum/showthread.php?p=837905#post837905 Andy Goss -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Andy Goss schreef:
On Mon, 2006-06-19 at 10:39 +0200, Koenraad Lelong wrote:
Great GRUB and multi-booting resources:
* http://www.linuxquestions.org/linux/blog/saikee * A grub menu booting 100+ systems of Dos, Windows, Linux, BSD and Solaris: http://www.justlinux.com/forum/showthread.php?t=143973 * Just booting tips: http://www.justlinux.com/forum/showthread.php?t=144294 * Saikee's grub booting tips: http://www.justlinux.com/forum/showthread.php?p=837905#post837905
Andy Goss
Thanks, I think those are what I need. -- Met vriendelijke groeten, Koenraad Lelong R&D Manager ACE electronics n.v. A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 19 June 2006 11:39, Koenraad Lelong wrote:
Hi, I'm going to re-install a Linux-machine (my home-server). This time I would like to be able to install e.g. a next vesion of Suse but keep the old one available (with maybe a third OS, no Win though). This time I'm going to put in a new disk and keep the old one to be able to switch back until all is OK. But in the future it will be 1 disk. I have a few questions regarding this all. Is there a how-to somewhere I can follow ? What's a good partitioning scheme ? swap (of course) /boot ? size ? /boot is not really necessary
/ /home
others ? No.
Keep It Small and Simple. The default (20 GB for /, rest for /home) is fine. I have only two partitions: swap and /. I could have just one, and swap in a file.
Is Suse (10.0 and 10.1) able to modify Grub automatically or will I have to edit the menu manually ?
The installer should make a working /boot/grub/menu.lst There might be some problems with MBR, PBR, active partition etc in a more complicated setup, but this is easily fixable. No need to worry beforehand, because chances are very good that everything will just work. Ask here if your system doesn't boot (don't get scared by that, nothing is lost). -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Mon, 19 Jun 2006 06:39 pm, Koenraad Lelong wrote:
I'm going to re-install a Linux-machine (my home-server). This time I would like to install a next vesion of Suse but keep the old one available (with maybe a third OS, no Win though).
Is there a how-to somewhere I can follow ? What's a good partitioning scheme ? swap (of course) /boot ? size ? / /home others ?
Riding the SuSE train with new editions every 6 months I have always defined 2 sets of system partitions and used a system of rolling installs. Disks are cheap. First the partitioning: root> fdisk -l /dev/hda Disk /dev/hda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 4 32098+ 83 Linux /dev/hda2 * 5 8 32130 83 Linux /dev/hda3 9 24319 195278107+ f W95 Ext'd (LBA) /dev/hda5 9 1604 12819838+ 83 Linux /dev/hda6 1605 3200 12819838+ 83 Linux /dev/hda7 3201 3328 1028128+ 82 Linux swap /dev/hda8 3329 24319 168610176 83 Linux So hda1 and hda5 are /boot and / and form one OS And hda2 and hda6 are /altOS/boot and /altOS They have 12 Gig and 32 Meg respectively. Allow 2 Gig of swap and give home has all that's left, hopefully lots. They are common to all systems. Here's fstab: /dev/hda5 / reiserfs acl,user_xattr 1 1 /dev/hda1 /boot ext2 acl,user_xattr 1 2 /dev/hda6 /altOS reiserfs defaults 1 2 /dev/hda1 /altOS/boot ext2 defaults 1 2 /dev/hda7 swap swap defaults 0 0 /dev/hda8 /home reiserfs defaults 1 2 When I do the next install (never an upgrade) I will blow away (reformat) altOS hda2 and hda6. They become the new / and /boot leave /home (of course) and the current system. The installer will note the current system and include it in GRUB so I COULD reboot it if I really hated the new system. More important, I have the old /etc/ (now mounted as /altOS/etc/), so I can diff and cat the old configuration files, and re-implement all the cool mods I have build up. I've always had a separate /boot partition ever since the days when BIOSes couldn't cope with files being more than 2 Gig from the start of the disk. ie: Install a system with 4 gig first partition, works fine. Do routine kernel update, it happens to get written past the 2 Gig limit. Unbootable. Damn. This restriction is history, but when I use mirrored meta-disks for /, having /boot as a plain ext2 partition means I can use GRUB. Recently I was amused to hear that some versions of suspend/resume work like a dog UNLESS you have a separate ext2 /boot. So. FWIW, michaelj I agree
A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
-- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 Here's one of my favourite mods (apart from giving IPv6 the boot). Add this to /etc/inputrc ########################################## # START Local additions cribbed from Kim Holburn # # michaelj 2004-10-14 # #-------------------------------------------------------------------------# set bell-style none #set prefer-visible-bell set show-all-if-ambiguous on control-p: history-search-backward control-n: history-search-forward set meta-flag on set convert-meta off set output-meta on #---------------------------------------# # END Local additions # ####################### -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
onsdaginn 21 juni 2006 02:49 skrev Michael James:
swap (of course) /boot ? size ? / /home others ?
Riding the SuSE train with new editions every 6 months I have always defined 2 sets of system partitions and used a system of rolling installs. Disks are cheap.
Places on the hard disk, that may grow such as /tmp and /var are sometimes well kept on separate disks to limit their growth. Same applies to /usr/local, which ensures local data separate from the main OS. You'd want /home on a separate disks, merely to ensure portability and simplify security such as with RAID. Beyond that, I usually keep the OS on one disk apart from /boot. I dual boot, by keeping Windows on a separate disk. My 2€¢ worth. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Places on the hard disk, that may grow such as /tmp and /var are sometimes well kept on separate disks to limit their growth. Same applies to /usr/local, which ensures local data separate from the main OS. Each installation had different reasons for doing things like this. In classic Unix, one of the strategies that governed how to partition was
On Wednesday 21 June 2006 4:47 pm, Orn E. Hansen wrote:
based on backup. The root and /usr file systems are very stable and change
infrequently. The /var directory tree contains log files and spool files,
so the backup strategy here is different from root and /usr. Likewise
the /home tree contains the users' directories, and is a candidate for yet
another backup strategy.
/tmp and /var/tmp different in that they (should) short term data, and
generally do not need to be backed up. Because of their nature, by making
these a separate partition, you limit their growth, but you also need to
allocate sufficient space. Additionally, you don't want to include these in
backup. /usr/local is just what it says. It is a repository for locally
installed programs and libraries. It may be unique to each system where
much of the root and /usr trees might be cloned.
For a home desktop or laptop, you might want to keep /home in a separate
partition so that you can upgrade your OS without having to backup and
restore /home.
--
Jerry Feldman
On Thu, 2006-06-22 at 08:53 -0400, Jerry Feldman wrote:
The /var directory tree contains log files and spool files,
One thing to remember about /var is that it _can_ contain persistent data. E.g., databases, web pages, etc... Most of these persistent data is being moved out of various locations like /var/lib, /var/www, etc... and into /srv as of the Linux Filesystem Hierarchy Standard (FHS) version 2.3, which is also Linux Standards Base (LBS) 2.0 (or was it 1.3?). The idea is that persistent service data should be in /srv. About 6 years ago, the Linux FHS decided to move it out of /home, away from persistent user data. As much as I professional barked originally about adding a new, top level directory (TLD) in /srv, I do have to agree with the fact that it shouldn't be home, but /var was a poor choice. Today I always build persistent service data to go in /srv, and not under /var, /var/lib, /var/share, etc... I try to avoid using symlinks if I can, but have. Some common directories I put under /srv: /srv/ftp (/var/ftp) /srv/mysql (/var/lib/mysql) /srv/pgsql (/var/lib/pgsql) /srv/svn (/var[/lib]/srv and various) /srv/trac (/var/lib/trac) /srv/www (/var/www) And others A few I leave in /var: /var/named /var/yp (basically anything very UNIX-legacy) -- Bryan J. Smith Professional, technical annoyance mailto:b.j.smith@ieee.org http://thebs413.blogspot.com ---------------------------------------------------------- The existence of Linux has far more to do with the breakup of AT&T's monopoly than anything Microsoft has ever done. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (7)
-
Andy Goss -
Bryan J. Smith -
Jerry Feldman -
Koenraad Lelong -
Michael James -
Orn E. Hansen -
Silviu Marin-Caea