Re: [expert] Disk partitioning
Rusty Carruth wrote: You may want to add another partition for a test '/', for upgrading or trying things that you have an idea may break you badly... lets see. /boot - 20 M (way more than you'll ever need, but hey, its a tiny percentage! ;-) /home - 5Gig (you DON'T want to see my home dir!) /var - 1G (just a guess) /tmp - 3G (you want to have an ISO image, why not also have the original tree also?) /vmwin98 - 2G (can you REALLY install all that crud in 2G?) /root - 3 to 5G (yeah, you can easily make that in 1-2 gig, but why squeeze?) I assume you mean root (ie /) here. It's normally suggested to make / smaller (about 256 MB should be more than enough), and have a /usr partition of the rest. Thus installing software into /usr or /opt doesn't mean you run out of space in your /. Then you might also want to have a /root partition (root's home) so that root can log in and fix things (have space to work) if your /home is unavailable or full. Again 256 MB should be enough for anything. /root2 - 3 to 5G (your test root partition) total: up to 21Gig. Adjust the sizes up from there to fit your own preferences. (I'd much rather have EXTRA space than have to move things around because I ran OUT! (been there, done that, real pain)) Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 808 2497 Stellenbosch Automotive Engineering http://www.cae.co.za
Re: [expert] Disk partitioning
Courtesy bcc to Neal also "Neal Lippman" [EMAIL PROTECTED] wrote: I am wondering what advice and/or thoughts people might have regarding disk partitioning for a brand new install. I have just finished assembling the hardware, and have a fully blank and unformatted 45GB disk, and I'd like to plan out my partitions before starting on the install. I was figuring - a small boot partition to contain /boot - a /home partition for /home - a /var partition so that log files, etc, are limited and the disk cannot get flooded by logs if there are mail spam attacks or something like that - a /tmp partition for temp files - large enough that i can create the images for cd's prior to burning, so it will need to be at least a few GB - a /vmwin98 partition for a vmware parition to contain a win98 virtual machine install (for Quicken and Word, which I still need to use) - a root partition to contain /, of course, and all of its usually stuff including /usr, with mount points for /home, /var, /tmp, /boot, /vmwin98 I cannot make up my mind regarding another partition that is either FAT16 or FAT32 for a bootable windows install. I've been planning to run windows only under vmware, but then I got to thinking that maybe I might need a way to boot into windows for some reason or another... Its a bit tricky (and I forget how I did it!), but you can get vmware to use a pre-existing (bootable) w98 partition. Any one with pointers or advice on this scheme, how large to make each partition, etc? You may want to add another partition for a test '/', for upgrading or trying things that you have an idea may break you badly... lets see. /boot - 20 M (way more than you'll ever need, but hey, its a tiny percentage! ;-) /home - 5Gig (you DON'T want to see my home dir!) /var - 1G (just a guess) /tmp - 3G (you want to have an ISO image, why not also have the original tree also?) /vmwin98 - 2G (can you REALLY install all that crud in 2G?) /root - 3 to 5G (yeah, you can easily make that in 1-2 gig, but why squeeze?) /root2 - 3 to 5G (your test root partition) total: up to 21Gig. Adjust the sizes up from there to fit your own preferences. (I'd much rather have EXTRA space than have to move things around because I ran OUT! (been there, done that, real pain)) I also have a /usr/src partition on some of my machines, but that's only for those with limited disk... rc Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] Voice: (480) 345-3621 SnailMail: Schlumberger ATE FAX: (480) 345-8793 7855 S. River Parkway, Suite 116 Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825
[expert] Disk partitioning
I am wondering what advice and/or thoughts people might have regarding disk partitioning for a brand new install. I have just finished assembling the hardware, and have a fully blank and unformatted 45GB disk, and I'd like to plan out my partitions before starting on the install. I was figuring - a small boot partition to contain /boot - a /home partition for /home - a /var partition so that log files, etc, are limited and the disk cannot get flooded by logs if there are mail spam attacks or something like that - a /tmp partition for temp files - large enough that i can create the images for cd's prior to burning, so it will need to be at least a few GB - a /vmwin98 partition for a vmware parition to contain a win98 virtual machine install (for Quicken and Word, which I still need to use) - a root partition to contain /, of course, and all of its usually stuff including /usr, with mount points for /home, /var, /tmp, /boot, /vmwin98 I cannot make up my mind regarding another partition that is either FAT16 or FAT32 for a bootable windows install. I've been planning to run windows only under vmware, but then I got to thinking that maybe I might need a way to boot into windows for some reason or another... Any one with pointers or advice on this scheme, how large to make each partition, etc? NB: I would prefer NOT to allocate the whole 45GB just yet - with such a large HD, I wouldn't mind leaving a good bit of it (maybe even half) open so that later on when I think of something I need a partition for, I have plenty of room to add it.
Re: [expert] Disk partitioning and Disk Drake
Just wanted to note something Windows NT and Windows 2000 will allow you to create up to 4 primary partitions on a single drive. This isn't supported by DOS fdisk either, yet no one claims that it needs work. Personally, I think thatdiskdrake is functioning properly. Thanks If you are installing linux on a clean hard drive, Disk Drake may be okay. If you are installing linux on a system with windows on it, like a lot of people will be, and are trying to create a linux partition out of unused space on the drive, sorry, Mandrake, but someone needs to work on this. I have found that various versions of Disk Drake will create partition errors, anything from minor errors that don't seem to affect the drive to real goofball errors on some cooker versions. Whatever you do, don't create a linux "primary" partition using Disk Drake. Disk Drake doesn't resize the extended Dos partition that the dos fdisk originally set up. Instead, it creates linux partitions in the extended Dos partition. This kind of bothers me. Shouldn't the linux partition be created as totally separate from the Dos partition? "Extended" seems to be the default choice in Disk Drake. If you try to create a "primary" linux partition in the extended Dos partition, you'll end up with a truly goofed-up partition table. I fixed this with a third party program called Partition Commander but was freaked for a short while, thinking I'd lost everything. It is safer to use something like Partition Commander to set up the linux partitions, and then install linux. You can change the default file system in the linux partition to reiserfs when you install linux. If you install linux as a secondary os on a laptop, careful, because you might not even be able to boot from a floppy if things go wrong. There is no bios setup in the Sony VAIO laptop I have, it seems to be a stupid windows program! Grub got stuck and wouldn't boot anything, just displayed a "grub" on the screen, even though I'd set the stupid windows Bios configuration to boot CD-floppy-hard disk in that order. The only way to fix this was to stick in the linux installation cd and reinstall or upgrade without selecting files so you can redo grub or whatever. I really think the Mandrake versions of linux are great -- the only ones that were ever easy to install and use -- and I hate to have to rely on third party software to fix things, but that's just the way it is. Partition Commander is pretty cheap (I picked one up for about $30). There's plenty of semicolons to go around
Re: [expert] Disk partitioning and Disk Drake
Are you sure, I installed Mandrake 7.1 on a Toshiba Satellite 1605 running windows98.. just popped the CD in while already in windows, installation took care of auto-partitioning and setting up LILO for a dual-boot system, worked like a charm. What I found really screws things up is *BSD-Linux, had a bad master boot record experience. --- pablito [EMAIL PROTECTED] wrote: If you are installing linux on a clean hard drive, Disk Drake may be okay. If you are installing linux on a system with windows on it, like a lot of people will be, and are trying to create a linux partition out of unused space on the drive, sorry, Mandrake, but someone needs to work on this. I have found that various versions of Disk Drake will create partition errors, anything from minor errors that don't seem to affect the drive to real goofball errors on some cooker versions. Whatever you do, don't create a linux "primary" partition using Disk Drake. Disk Drake doesn't resize the extended Dos partition that the dos fdisk originally set up. Instead, it creates linux partitions in the extended Dos partition. This kind of bothers me. Shouldn't the linux partition be created as totally separate from the Dos partition? "Extended" seems to be the default choice in Disk Drake. If you try to create a "primary" linux partition in the extended Dos partition, you'll end up with a truly goofed-up partition table. I fixed this with a third party program called Partition Commander but was freaked for a short while, thinking I'd lost everything. It is safer to use something like Partition Commander to set up the linux partitions, and then install linux. You can change the default file system in the linux partition to reiserfs when you install linux. If you install linux as a secondary os on a laptop, careful, because you might not even be able to boot from a floppy if things go wrong. There is no bios setup in the Sony VAIO laptop I have, it seems to be a stupid windows program! Grub got stuck and wouldn't boot anything, just displayed a "grub" on the screen, even though I'd set the stupid windows Bios configuration to boot CD-floppy-hard disk in that order. The only way to fix this was to stick in the linux installation cd and reinstall or upgrade without selecting files so you can redo grub or whatever. I really think the Mandrake versions of linux are great -- the only ones that were ever easy to install and use -- and I hate to have to rely on third party software to fix things, but that's just the way it is. Partition Commander is pretty cheap (I picked one up for about $30). __ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/
Re: [expert] Disk partitioning and Disk Drake
Thank's for your interesting words on partitioning and formating, I myself use Partition Magic, one of my absolute favorites and one of a few that I'm ready to pay for, it's worth it. ei On Friday 29 December 2000 18:24, pablito wrote: [snip] -- @~~ EagleIce ~ [EMAIL PROTECTED] ~~@ @~~ Running GNU/Linux KDE ~~@
Re: [expert] Disk partitioning and Disk Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Only slightly on topic, but perhaps I'll save someone some headaches... I ran into "issues" installing on a system with a Mylex AccelaRAID 250 (DAC960) controller. The Mylex card only recognizes 7 partitions and DiskDrake insisted in creating something like this (it was a month or so ago so I may be a bit off...) /boot rd/c0d0p1 / rd/c0d0p5 /swap rd/c0d0p6 /home rd/c0d0p7 /varrd/c0d0p8 /usrrd/c0d0p9 Of course rd/c0d0p8 rd/c0d0p9 aren't valid so the mke2fs failed. I ended up switching out to a console and using fdisk to create valid partitions and only then was I able to install LM7.2 Let's just say it was a minor pain in the @$$. On Friday 29 December 2000 09:24, pablito wrote: I have found that various versions of Disk Drake will create partition errors... -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpNOv4ACgkQCIwrOqxGmNvPrwCgm5YIQuHrxCTjjATmnvEfwYZo +jUAn2X+IwmiUG8OnuWG1aKZePjVgDdi =fbM9 -END PGP SIGNATURE-
[expert] Disk partitioning and Disk Drake
If you are installing linux on a clean hard drive, Disk Drake may be okay. If you are installing linux on a system with windows on it, like a lot of people will be, and are trying to create a linux partition out of unused space on the drive, sorry, Mandrake, but someone needs to work on this. I have found that various versions of Disk Drake will create partition errors, anything from minor errors that don't seem to affect the drive to real goofball errors on some cooker versions. Whatever you do, don't create a linux "primary" partition using Disk Drake. Disk Drake doesn't resize the extended Dos partition that the dos fdisk originally set up. Instead, it creates linux partitions in the extended Dos partition. This kind of bothers me. Shouldn't the linux partition be created as totally separate from the Dos partition? "Extended" seems to be the default choice in Disk Drake. If you try to create a "primary" linux partition in the extended Dos partition, you'll end up with a truly goofed-up partition table. I fixed this with a third party program called Partition Commander but was freaked for a short while, thinking I'd lost everything. It is safer to use something like Partition Commander to set up the linux partitions, and then install linux. You can change the default file system in the linux partition to reiserfs when you install linux. If you install linux as a secondary os on a laptop, careful, because you might not even be able to boot from a floppy if things go wrong. There is no bios setup in the Sony VAIO laptop I have, it seems to be a stupid windows program! Grub got stuck and wouldn't boot anything, just displayed a "grub" on the screen, even though I'd set the stupid windows Bios configuration to boot CD-floppy-hard disk in that order. The only way to fix this was to stick in the linux installation cd and reinstall or upgrade without selecting files so you can redo grub or whatever. I really think the Mandrake versions of linux are great -- the only ones that were ever easy to install and use -- and I hate to have to rely on third party software to fix things, but that's just the way it is. Partition Commander is pretty cheap (I picked one up for about $30).
[expert] disk partitioning help for new server
Hi, I'm setting up a box to be a webserver with mysql as the backend database and I need a little advise about hot I should partition things. I have 3 drives: 2 - 18 gig SCSIs set up as a level 1 raid 1 - 20 gig ide What are good sizes for the partitions? I want to put everything on the raid array: /, /home, /usr, /var, etc. and use the ide drive as internal backup. Are there any problems with mounting / from a raid array? How about /boot ? Should I mount the raid as /home and put the rest of the system on the ide drive? the RPMs install MySQL in /var/lib/mysql /var seems like a dumb place for it, with the recommended size for the /var partition it would run out of space when the DB gets large. Where do other people put it? I was thinking of /home/mysql thanks for any thoughts, Gavin
RE: [expert] disk partitioning help for new server
I just moved my / and /boot over to raid1 partitions. It works. There is a trick to setting up lilo for /boot on raid1. I uninstalled lilo and installed lilo-21.4.1 from a ftp site before I got it working. However, I think it may work with the stock Mandrake lilo. I started off with Mandrake / on /dev/hda1 and setup the raid on /dev/hdb1 and /dev/hdc1. I created the raid array and mounted it as /mnt/newroot. Then I did a cp -ax / /mnt/newroot. Then I swapped jumpers on the hard drives so now /dev/hdb1 is /hda1. After booting be sure to correct your /etc/raidtab!! My /etc/lilo.conf is: boot = /dev/md1 === the trick that makes it work timeout = 50 prompt message = /boot/message default = linux vga = 0x0f05 read-only map=/boot/map install=/boot/boot.b keytable=/boot/us.klt image = /boot/vmlinuz label = linux append = "max_scsi_luns=5" root = /dev/md0 image = /boot/vmlinuz.old label = oldlinux append = "max_scsi_luns=5" root = /dev/md0 other = /dev/fd0 label = floppy unsafe My /etc/fstab is: #/dev/hda1 / ext2defaults1 1 /dev/md0/ ext2defaults1 1 /dev/md1/boot ext2defaults1 1 #/dev/hda2 swapswapdefaults0 0 /dev/hda2 noneswappri=100,exec,dev,suid,rw 1 1 /dev/hdc2 noneswappri=100,exec,dev,suid,rw 1 1 none/proc procdefaults0 0 none/dev/ptsdevpts mode=0620 0 0 /dev/fd0/mnt/floppy auto sync,user,noauto,nosuid,nodev,unhide 0 0 /dev/cdrom /mnt/cdrom auto user,noauto,nosuid,exec,nodev,ro 0 0 elmo:/home/Mandrake /mnt/nfs nfs noauto,ro,nosuid,rsize=8192,wsize=8192 0 0 My /etc/raidtab is: # Sample raid-1 configuration raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/hda1 raid-disk 0 device /dev/hdc1 raid-disk 1 raiddev /dev/md1 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/hda3 raid-disk 0 device /dev/hdc3 raid-disk 1 Basically, just follow the instructions in /usr/doc/raidtools-0.90/Software-RAID.HOWTO.txt Hope this helps, Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Gavin Clark Sent: Tuesday, April 25, 2000 3:28 AM To: [EMAIL PROTECTED] Subject: [expert] disk partitioning help for new server Hi, I'm setting up a box to be a webserver with mysql as the backend database and I need a little advise about hot I should partition things. I have 3 drives: 2 - 18 gig SCSIs set up as a level 1 raid 1 - 20 gig ide What are good sizes for the partitions? I want to put everything on the raid array: /, /home, /usr, /var, etc. and use the ide drive as internal backup. Are there any problems with mounting / from a raid array? How about /boot ? Should I mount the raid as /home and put the rest of the system on the ide drive? the RPMs install MySQL in /var/lib/mysql /var seems like a dumb place for it, with the recommended size for the /var partition it would run out of space when the DB gets large. Where do other people put it? I was thinking of /home/mysql thanks for any thoughts, Gavin
Re: [expert] disk partitioning help for new server
thanks! I was expecting responses like "yes" ;-) Gavin -- From: "Bill Shirley" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [expert] disk partitioning help for new server Date: Tue, Apr 25, 2000, 4:23 AM I just moved my / and /boot over to raid1 partitions. It works. There is a trick to setting up lilo for /boot on raid1. I uninstalled lilo and installed lilo-21.4.1 from a ftp site before I got it working. However, I think it may work with the stock Mandrake lilo.
