New filesystem upgrade replaces fstab

drcouzelis · 2012-11-28 15:35:27

This specific "pacnew" situation was a little confusing, simply because it's been so long since I've made any changes to my fstab file that I've completely forgotten that an empty fstab file wasn't the default before.

rene wrote:

pacman has this nifty "pacman -Qc" feature to show a package changelog.

You just blew my mind.

Jristz · 2012-11-28 16:49:00

drcouzelis wrote:

This specific "pacnew" situation was a little confusing, simply because it's been so long since I've made any changes to my fstab file that I've completely forgotten that an empty fstab file wasn't the default before.
rene wrote:
pacman has this nifty "pacman -Qc" feature to show a package changelog.
You just blew my mind.

An in a 700 packages only 2 use the Changelog, and Linux neither filesystem are ...

Really dev need provide changelog for base packages, I sure that is more user know this option and more dev/TU use it, les headaches an themes like this can exist

root · 2012-11-28 21:28:16

So if I understand this update correctly what Scimmia points out in #8 is the way to go or what other considerations one has to bear in mind with regard to this update?

I installed my system when the old AIF was still active using the auto partition option. The only change I have made to my fstab was when I noticed that my installation had set for all partitions the fsck option to 1 (not including swap) and set the non-root ones to 2.

root · 2012-12-01 08:11:45

Could someone please confirm what Jristz asked for in #24? buri's answer is a bit unclear to me

Therefore inn order to set a specific size for the /tmp on the hdd

a) one should keep the /tmp entry in fstab but specify the size in tmp.mount (I presume in personalized unit file in /etc/systemd/system)

b) one does not need to keep the /tmp entry in fstab as it is still redundant and everything should be dealt with through the personalized tmp.mount file (/tmp mounting and size).

Thanks in advance.

root · 2012-12-03 20:50:17

As far as I can tell option b) is working fine so far in my case.

loafer · 2012-12-03 21:04:51

root wrote:

As far as I can tell option b) is working fine so far in my case.

By far the best thing to do in these scenarios is to test the various options oneself in order to find the best one for you.

root · 2012-12-03 21:21:33

@loafer

The thing is that, at least in my case, with some things one can feel more comfortable tweaking around than with regard to others (core system related f.e. fstab).

Still I am willing to think that the results of my test will help people to have a (more detailed) clue concerning the recent fstab update.

Arch Linux

#26 2012-11-28 15:35:27

Re: New filesystem upgrade replaces fstab

#27 2012-11-28 16:49:00

Re: New filesystem upgrade replaces fstab

#28 2012-11-28 21:28:16

Re: New filesystem upgrade replaces fstab

#29 2012-12-01 08:11:45

Re: New filesystem upgrade replaces fstab

#30 2012-12-03 20:50:17

Re: New filesystem upgrade replaces fstab

#31 2012-12-03 21:04:51

Re: New filesystem upgrade replaces fstab

#32 2012-12-03 21:21:33

Re: New filesystem upgrade replaces fstab

Board footer