DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Installation and Upgrading

OpenBSD Installation and Upgrading Installing and upgrading OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 22nd November 2008
MetalHead MetalHead is offline
Port Guard
 
Join Date: Sep 2008
Posts: 24
Default Recommended Partition Layout

Hi..

What would you guys recommend for the best partition layout for a desktop system?

I'm using:

/
/swap
/tmp
/var
/usr
/home

What about /usr/local instead of /usr ? Any disadvantages or advantages ?

I'm getting ready to install OPBSD on a new computer and I'm wondering what the best partition layout is.

Thanks in advance..
Reply With Quote
  #2   (View Single Post)  
Old 22nd November 2008
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,125
Default

If you create an /usr/local instead of an /usr, then the installer will create an /usr in the root partition '/'.

If you plan to use the OBSD ports system a lot, then you could create an "/usr" as well as an "/usr/ports".
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #3   (View Single Post)  
Old 22nd November 2008
MetalHead MetalHead is offline
Port Guard
 
Join Date: Sep 2008
Posts: 24
Default

Quote:
Originally Posted by J65nko View Post
If you create an /usr/local instead of an /usr, then the installer will create an /usr in the root partition '/'.

Is that a good or a bad thing?

If you plan to use the OBSD ports system a lot, then you could create an "/usr" as well as an "/usr/ports".
How about this..

/
/tmp
/var
/usr/local
/usr/ports
/home

TIA

P.S.

What would you recomend? If using OPBSD as a desktop how do you have your partition table layed out?
Reply With Quote
  #4   (View Single Post)  
Old 22nd November 2008
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,125
Default

I only would add an /usr
Code:
/
/tmp
/var
/usr
/usr/local
/usr/ports
/home
Now the next question: how many MB or GB for each partition?
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #5   (View Single Post)  
Old 22nd November 2008
MetalHead MetalHead is offline
Port Guard
 
Join Date: Sep 2008
Posts: 24
Default

Quote:
Originally Posted by J65nko View Post
I only would add an /usr
Code:
/
/tmp
/var
/usr
/usr/local
/usr/ports
/home
Now the next question: how many MB or GB for each partition?
Thanks! I think I have the MG/GB figured out....Just needed the correct layout....
Reply With Quote
  #6   (View Single Post)  
Old 22nd November 2008
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by MetalHead View Post
Thanks! I think I have the MG/GB figured out....Just needed the correct layout....
Given that you have specified /usr/ports, gives the impression that you anticipate building ports. If you also intend to ever build the kernel, userland, or Xenocara, then you should also consider making partitions for:
  • /usr/src
  • /usr/obj
  • /usr/xenocara
  • /usr/xobj
Reply With Quote
  #7   (View Single Post)  
Old 22nd November 2008
Oko's Avatar
Oko Oko is offline
Rc.conf Instructor
 
Join Date: May 2008
Location: Kosovo, Serbia
Posts: 1,102
Default

It is little bit off topic but I always like to keep /home on the separate hard drive. That is just me.

Last edited by Oko; 22nd November 2008 at 05:37 AM.
Reply With Quote
  #8   (View Single Post)  
Old 22nd November 2008
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,975
Default

jggimi's recommended procedure for partition planning for any new environment that has unknown capacity requirements.

Step 1: Set aside all preconceived notions of disk space requirements for any individual partition. Ignore anything anyone tells you is "typical" sizing requirements.

Step 2: Install everything in a single, great big root partition. Don't worry, this is temporary.

Step 3: Use the application set / environment for some length of time: days, weeks, months, as needed.

Step 4: By using du(1), determine what your hierarchy is actually consuming.

Step 5: Reinstall with your final configuration, or back up - reconfigure - restore.
Reply With Quote
  #9   (View Single Post)  
Old 22nd November 2008
TerryP's Avatar
TerryP TerryP is offline
Arp Constable
 
Join Date: May 2008
Location: USofA
Posts: 1,547
Default

jggimi I think, has just given you the best advice anyone can without knowing your situation in detail.

If you search J65nko's posts for topics like these, you'll also turn up some very good advice on finding just what you can pull off. Most systems at home won't need much, but adopting partitioning to machine purpose is helpful.


Personally, I prefer to have /usr/src and /usr/obj be network mounts where applicable, and split /usr and /usr/local into separate areas of my disks.
__________________
My Journal

Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.
Reply With Quote
Old 29th November 2008
ivanatora ivanatora is offline
Real Name: Ivan
Fdisk Soldier
 
Join Date: Jul 2008
Location: Bulgaria
Posts: 51
Default

Why not keep everything at one place?
Is this a desktop machine or kind of a server?
IMHO, playing around with a hard drive with a multiple data partitions is not as easy as it sounds. Nor productive. There is always a time when you run out of space to some of your partitions (be it a /home, or /usr or /var...) and the situation is narrow - you can't borrow space from some other partition even if you have plenty. So you delete files or add another hard drive. Both of these is too stupid when you have free space at the other partitions.
Ofcourse someone could do the math before installing the system and split his harddrive into 10 slices with a megabyte precision. Then after X months he runs out of space. Always. Desktop machine == data grow.
Using a simple / partition is a solution to many problems.
Reply With Quote
Old 29th November 2008
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Banned
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Default

Quote:
Originally Posted by ivanatora View Post
Using a simple / partition is a solution to many problems.
But you miss out on the bonus security benefits.. like mount point specific options. (nosuid, nodev.. noexec, etc)

It's always recommended to create separate partitions... it's fine creating one large / partition at first, but once you get used to the system, you'll find it worthwhile to create more.
Reply With Quote
Old 30th November 2008
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,975
Default

I recommended a single partition, above. For initial use and final layout determination.

FAQ 4.7 -- therefore the OpenBSD Project -- recommends partitioning as a best practice, for reasons of security, stability, speed, integrity, and size. It too, includes the recommendation of single-large-partition, prior to production.

I have systems that are permanently configured with a single large partition, including the laptop I am using to type this. But none of these systems are exposed directly to the Internet, and none run production services. Systems that run services, or are exposed, or both, are partitioned.
Reply With Quote
Old 30th November 2008
ivanatora ivanatora is offline
Real Name: Ivan
Fdisk Soldier
 
Join Date: Jul 2008
Location: Bulgaria
Posts: 51
Default

Yes, you both are correct that I'm not right for production servers. I was talked about home desktop systems, because it is what MetalHead needs.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
NetBSD 5 keyboard layout in gnome jaideep_jdof NetBSD Package System (pkgsrc) 1 17th September 2009 03:50 PM
recommended 802.11a/b/g/n wireless cards hamba General Hardware 3 27th October 2008 07:43 PM
Project layout, any comments? PatrickBaer FreeBSD General 1 12th October 2008 05:13 PM
Recommended network adapters ebzzry FreeBSD General 13 27th August 2008 01:00 AM
Keyboard Layout mfaridi FreeBSD General 6 26th June 2008 07:13 PM


All times are GMT. The time now is 06:16 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick