LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-21-2013, 02:28 PM   #1
smith517
LQ Newbie
 
Registered: Jan 2013
Distribution: Slackware
Posts: 7

Rep: Reputation: Disabled
First (real) Slackware installation - Looking for file system advice


I have looked over the Slackware setup utility and have become quite familiar with it. I've got the whole bootloader thing down. I have generally messed around with Slackware in a virtual installation. Now that I'm going to install it on a physical computer, I want to know what file system setup is the most efficient. This computer is relatively older but not quite ancient.

I've generally come up with this scheme:

/ - ext2
/boot - ext2
/home - ext4
/var - xfs
/var/log - (maybe xfs. but I hear that log-based file systems are better. advice?)
/usr - ext3

If you have any advice on how/why I should change this, please post. Advice on why I should use another partition scheme would welcome, too.

----------------------------------------

EDIT: Updated scheme:

/boot - ext2
/ - ext4
/home - ext4
swap - swap (duh)

----------------------------------------

EDIT: I've installed Slackware and am satisfied with the setup.
I've used the updated scheme above.
I've separated the \boot partition in case a hypothetical ext5 get released before the computer turns to dust (Unlikely. Might happen any day now).
I've used ext4 on the other two becase the performance and safety balance was just right.
The swap is obviously setup as swap. :P
Thank you, for all that have provided answers.

Last edited by smith517; 01-22-2013 at 07:05 PM. Reason: Marked as solved.
 
Old 01-21-2013, 04:02 PM   #2
nivieru
Member
 
Registered: Feb 2008
Posts: 48

Rep: Reputation: 7
how the computer will be used?
unless there are some specific tasks for which one file system is significantly better than the others, choosing a simple configuration, e.g. all ext4, would work just fine.
also, the rational for fragmenting the fs into /, /boot, /usr, home and so on doesn't always justify the additional complexity.
for a desktop with no special requirements, the simpler option might the better one.
oh, I almost forgot - welcome to slackland!

Last edited by nivieru; 01-21-2013 at 04:05 PM.
 
Old 01-21-2013, 05:01 PM   #3
smith517
LQ Newbie
 
Registered: Jan 2013
Distribution: Slackware
Posts: 7

Original Poster
Rep: Reputation: Disabled
The computer will generally be used for ... general things. I do program stuff in multiple languages and don't really do much media stuff. What partition scheme do you recommend?
 
Old 01-21-2013, 05:04 PM   #4
Celyr
Member
 
Registered: Mar 2012
Location: Italy
Distribution: Slackware+Debian
Posts: 314

Rep: Reputation: 77
/ in ext4
and eventually /home in ext4
 
Old 01-21-2013, 05:18 PM   #5
Bazzaah
Member
 
Registered: Mar 2007
Distribution: Slackware64-current, Slackware64 14
Posts: 324

Rep: Reputation: 49
ext4 here too for / and /home.

I've never had any problems in any way whatsoever with this simple set up.

I'd be interested to hear arguments in favour of using different file systems for different directories.
 
Old 01-21-2013, 05:45 PM   #6
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,640

Rep: Reputation: 568Reputation: 568Reputation: 568Reputation: 568Reputation: 568Reputation: 568
I now use ext4 for new installs, although I keep some ext3 partitions working on older machines.

I have found that keeping /home on a separate partition is well worth any potential conflicts with configs.

I am not a distro hopper, but I multi-boot different Slackware versions on the same machine at times and often share the home directories between them - takes a little thought...

So ext4 (ext-du-jour) for both / and /home is usually good for most uses for me.

At one time I began using a separate /boot partition shared among versions due to restrictions on kernel image locations on large hard drives. This worked well and became a habit, but is not really necessary any more.

Finally, I always setup one or more shared data partitions which I mount with fstab entries (like /mnt/sdata, /mnt/sdata2, etc), then use symlinks to access them for various purposes. For example, I sometimes move my mysql data directories onto a shared partition and symlink it from /var/mysql/ to allow sharing of data across versions and make my sometimes large and multiple databases generally more maintainable and portable.

Last edited by astrogeek; 01-21-2013 at 05:49 PM.
 
Old 01-21-2013, 05:45 PM   #7
smith517
LQ Newbie
 
Registered: Jan 2013
Distribution: Slackware
Posts: 7

Original Poster
Rep: Reputation: Disabled
No separate /boot? I always have a separate /boot partition. Is there a reason not to?
What is the generally recommended size for the / partition? Half the disk? Less? More?
On the virtual machine, I just had one partition. Bad practice I'm assuming...

EDIT: Ninja'd by astrogeek.

EDIT2: Updated the first post to reflect some changes.

Last edited by smith517; 01-21-2013 at 08:35 PM.
 
Old 01-21-2013, 11:25 PM   #8
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 72
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by smith517 View Post
EDIT: Updated scheme:

/boot - ext2
/ - ext4
/home - ext4
swap - swap (duh)
Using ext2, is not good idea.
ext2 doesn't provide journaling options.
In case of improper shutdown, you are not able to recover files.

Quote:
Originally Posted by smith517 View Post
No separate /boot? I always have a separate /boot partition. Is there a reason not to?
Using separate /boot partition is good idea.
Just for an example, in future ext5 is released and your bootloader not able boot from ext5.
In such condition, you can convert / partition with ext5, because you are using separate /boot partition.

I am sharing /boot partition with two linux distroes.
 
Old 01-21-2013, 11:40 PM   #9
jamesf
Member
 
Registered: Dec 2004
Location: USA
Distribution: Slackware 12 and higher
Posts: 218

Rep: Reputation: 44
I've gotten in the habit of (at least) three partitions:

swap partition - slightly larger than RAM for suspend/hibernate to work.

/boot - about 1Gig ext2 because if it is damaged then there's no journal or complicated data structures to worry about. Rescue CDs will have a pretty easy time of getting the partition into a state where it will either work or I can copy over what was lost to get the machine back on-line quickly. Really, how often is /boot changing, anyway?

/ - What is left is usually ext4 because of journaling, etc. Better data protection at the cost of (slightly) greater difficulty in recovery.

After that, partitions as needed for other distros, data, Windows, etc.
 
Old 01-22-2013, 03:03 AM   #10
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
I would recommend JFS, as being efficient and having low CPU usage.

XFS is good as well.

If you can give some system specs I can be more specific.
 
Old 01-22-2013, 06:24 AM   #11
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,364
Blog Entries: 2

Rep: Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981
Keep in mind that the choice of the right filesystem also can be dependent on your hardware. For example, if you use SSDs you should use filesystems that support the TRIM feature, which would rule out ext2/3,
 
1 members found this post helpful.
Old 01-22-2013, 06:47 AM   #12
smith517
LQ Newbie
 
Registered: Jan 2013
Distribution: Slackware
Posts: 7

Original Poster
Rep: Reputation: Disabled
@linuxxer: I don't really touch the \boot after I get it up and running. So, the no-journaling isn't an issue.

@H_TeXMeX_H: The computer has 4G of ram a core i3 and 500G of rom. I prefer the console over extreme flashy interfaces, so graphics card is a minor detail.

@TobiSGD: I have a 500G hard driver and it's not super fast. It's about average, but I've found it to be reliable (knocked on wood).
 
Old 01-22-2013, 06:59 AM   #13
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, exMandriva
Posts: 361

Rep: Reputation: 28
Quote:
Originally Posted by smith517 View Post
No separate /boot? I always have a separate /boot partition. Is there a reason not to?
What is the generally recommended size for the / partition? Half the disk? Less? More?
On the virtual machine, I just had one partition. Bad practice I'm assuming...

EDIT: Ninja'd by astrogeek.

EDIT2: Updated the first post to reflect some changes.
and what is reason to separate /boot in nowadays?
and why system on one partition is "bad practice"? i almost always use one partition for all system ( /boot, /home, /var , /usr, etc) and not have any drawbacks for that...
sometimes /home on different partition is not bad idea, but separate /boot, /var, etc...? :-O
 
Old 01-22-2013, 07:27 AM   #14
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,364
Blog Entries: 2

Rep: Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981
Quote:
Originally Posted by WiseDraco View Post
and what is reason to separate /boot in nowadays?
If you want to use LVM for the /-partition or have an encrypted system a separate /boot is the way to go.

Quote:
and why system on one partition is "bad practice"? i almost always use one partition for all system ( /boot, /home, /var , /usr, etc) and not have any drawbacks for that...
sometimes /home on different partition is not bad idea, but separate /boot, /var, etc...? :-O
It depends on the usage of the machine. I for one am not using a separate /home on my machines (desktop usage), I use a separate partition for my data, my user's config files are backed up automatically every day, so no need for separate /home.
Putting other directories, like /var or /usr/local may be a good idea under several circumstances.
For example, a separate /var may make sense on web- and mailservers to keep data and OS apart for lower downtime if an OS has to get a new install/restore from backup.
A separate /usr/local may also be convenient if you use it for user-compiled programs and you have to re-install the OS.

For the "normal" desktop user I don't see advantages to separate directories to different partitions.
 
Old 01-22-2013, 07:58 AM   #15
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, exMandriva
Posts: 361

Rep: Reputation: 28
Quote:
Originally Posted by TobiSGD View Post
If you want to use LVM for the /-partition or have an encrypted system a separate /boot is the way to go.
Or RAID differ than RAID1....but small number of us use that features, especially on desktop, as so...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Need advice installing slackware to a GPT/UEFI system arubin Slackware 38 10-21-2012 11:31 AM
File System Advice AxXium Linux From Scratch 3 08-02-2005 11:30 AM
file system advice sought jagmandan Linux - General 2 07-01-2004 08:37 PM
File system Help \ Newbie Advice KarmaKill Linux - Newbie 4 06-23-2004 11:53 AM


All times are GMT -5. The time now is 06:53 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration