freeserve.co.uk> 5e9730f7
From: chris@cvine--nospam--.freeserve.co.uk
On Fri, 26 Nov 2021 07:09:09 +0100
Aragorn wrote:
> On 26.11.2021 at 04:43, eho scribbled:
>
> > Am Thu, 25 Nov 2021 08:27:02 +0100 schrieb Aragorn:
> > >> strange problems.
> > >
> > > I recommend always using a tmpfs for /tmp. I've been doing that for
> > > ages already. There's nothing in /tmp that should be expected to
> > > survive a reboot anyway.
> >
> > Well, now I know the origin of evil (the SBo tmp files),
> > I could clean /tmp manually, but ...
> >
> > This is a bit new to me. Does tmpfs for /tmp mean
> > an entry in /etc/fstab?
>
> In Slackware concretely, yes. In distributions based upon systemd as
> PID 1 , systemd usually already sets that up by itself — SUSE/openSUSE
> might be an exception, from what I've heard.
>
> > I have
> >
> > (...)
> > /dev/sda6 /tmp ext4 defaults 1 2
> > (...)
> >
> > And should I now write
> >
> > tmpfs /dev/sda6 tmpfs defaults 0 0
>
> That would work, yes. You can also tune the maximum amount of virtual
> memory that the tmpfs in question can use. The default is half your
> RAM. See... ↓
>
>
> $ man mount
>
>
> > BTW can it be a problem to have too much partitions?
>
> That depends on what you would consider "too many". I believe both the
> MBR and GPT partition table formats support 128 partitions per physical
> drive. So if you need anything more than that... :p
>
> But anyway, here's the layout from my system. ↓
>
>
> [nx-74205:/dev/pts/3][/home/aragorn]
> [06:55:45][aragorn] > lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
> sda 8:0 0 931.5G 0 disk
> ├─sda1 8:1 0 512M 0 part /boot/efi
> ├─sda2 8:2 0 512M 0 part /boot
> ├─sda3 8:3 0 1G 0 part /
> ├─sda4 8:4 0 22G 0 part /usr
> ├─sda5 8:5 0 512M 0 part /usr/local
> ├─sda6 8:6 0 2G 0 part /opt
> ├─sda7 8:7 0 1.5G 0 part
> ├─sda8 8:8 0 400G 0 part /srv
> ├─sda9 8:9 0 450G 0 part /home
> ├─sda10 8:10 0 10G 0 part
> └─sda11 8:11 0 20G 0 part /var
> sdb 8:16 0 698.6G 0 disk
> ├─sdb1 8:17 0 10G 0 part
> └─sdb2 8:18 0 683.6G 0 part
> sr0 11:0 1 1024M 0 rom
>
>
> /dev/sda is an SATA3-connected SSD. /dev/sdb is an SATA2 HDD that
> comes out of one of my previous computers.
>
> My /tmp resides on a tmpfs. /dev/sda7 is unused because it's my old
> /var, which proved too small. /dev/sda10 is my swap partition, but
> I've disabled swap about two years ago and it hasn't caused me any
> problems yet.
>
> /dev/sdb1 is another swap partition — disabled as well — and /dev/sdb2
> is the partition that I store my Timeshift backups on.
>
> /boot/efi is vfat (FAT32), as prescribed by the UEFI specification.
> /boot itself is ext4 because GRUB is picky about what it supports. All
> other partitions — except for the swap partitions of course — are btrfs.
>
> The system is working fine, and so I'm not going to change anything
> about the partitioning. However, I've already decided that for my next
> system, I'll be using btrfs subvolumes instead of dedicated partitions
> — subvolumes have all the advantages of dedicated partitions, but the
> free disk space is shared among all of them (unless you use quota, of
> course).
Your directory layout above looks insane. What's the point of so many
partitions? To share free disk space around your file system, the best
thing is not to have so many. One partition as the EFI partition, one
for swap and one for / will do fine for most purposes, so everything
under / (apart from EFI) is shared. You might possibly want a separate
partition for /home so that your home directory survives reinstallation
or an upgrade, but that would be about it in my experience.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
