Re: How big should wd0e (/var) be
I may have missed it, but I don't think this thread would be complete without bringing up LVM. Assigning the bulk of your storage to LVM allows you to start with more small partitions and grow them over time as needed. That would get you a step closer to your accustomed FreeBSD/ZFS scheme. Gary Duzan p.s. NetBSD does have ZFS, but I haven't tried it, and I seem to recall some discussion of stability issues. > I think a fourth of the disk should be for /var and a fourth for / > and the rest for /home > > > xu...@sdf.org > SDF Public Access UNIX System - http://sdf.org > > On Wed, 13 Dec 2023, jo...@sdf.org wrote: > >> >>> I look at it in exactly the opposite way - it fills me with joy to >>> see that something has gone wild and filled a partition, and I didn't >>> even notice, as everything I'm doing is elsewhere, not being bothered. >>> [Turn on process accounting, and do a few full builds, and /var/account >>> will soon take over whatever space you have allowed it to occupy.] >> >> I stopped using many partitions on my BSD servers (except OpenBSD router >> where I use defaults), and my Rock64 type devices have only 1 partition >> (plus tmpfs etc); but for those Aarch64 devices that's how the image >> comes. >> >> It's interesting though that my (FreeBSD) ZFS server has many mount >> points >> because of various datasets. So, I decreased the OS partitions generally >> but more than made up for it in datasets. >> >> -Joel >> >> >> >
Re: How big should wd0e (/var) be
I think a fourth of the disk should be for /var and a fourth for / and the rest for /home xu...@sdf.org SDF Public Access UNIX System - http://sdf.org On Wed, 13 Dec 2023, jo...@sdf.org wrote: I look at it in exactly the opposite way - it fills me with joy to see that something has gone wild and filled a partition, and I didn't even notice, as everything I'm doing is elsewhere, not being bothered. [Turn on process accounting, and do a few full builds, and /var/account will soon take over whatever space you have allowed it to occupy.] I stopped using many partitions on my BSD servers (except OpenBSD router where I use defaults), and my Rock64 type devices have only 1 partition (plus tmpfs etc); but for those Aarch64 devices that's how the image comes. It's interesting though that my (FreeBSD) ZFS server has many mount points because of various datasets. So, I decreased the OS partitions generally but more than made up for it in datasets. -Joel
Re: How big should wd0e (/var) be
> I look at it in exactly the opposite way - it fills me with joy to > see that something has gone wild and filled a partition, and I didn't > even notice, as everything I'm doing is elsewhere, not being bothered. > [Turn on process accounting, and do a few full builds, and /var/account > will soon take over whatever space you have allowed it to occupy.] I stopped using many partitions on my BSD servers (except OpenBSD router where I use defaults), and my Rock64 type devices have only 1 partition (plus tmpfs etc); but for those Aarch64 devices that's how the image comes. It's interesting though that my (FreeBSD) ZFS server has many mount points because of various datasets. So, I decreased the OS partitions generally but more than made up for it in datasets. -Joel
Re: NetBSD-10.0RC
OK ... back to GTX-1880. Now GLAXIU (sp?) works file. When I doomlegacy the screen goes black ; I hear shooting etc; then the box pops up and says: Mode 1920x1080. I now think the problem is specific to DOOM. What can I try -- specific to doomlegacy? On Tue, Dec 12, 2023 at 9:17 AM Rhialto wrote: > > On Sun 10 Dec 2023 at 16:27:10 -0500, Todd Gruhn wrote: > > GTX-1660 works fine with NetBSd-10.0RC1 -- I had to re-slice HD and > > re-install NetBSD. > > > > The problem moved -- now It says /var is too small; NetBSD cannot > > write dow log files. > > How big should /var be on a personal computer??? > > I have these sizes, but I found that recently /usr tends to be too > small, because there are some *very* space-consuming packages, such as > libreoffice and kicad. So if I had occasion to re-partition I would make > it bigger, at least 50% or so. > > /home simply uses whatever space is left over. > > FilesystemSizeUsed Avail %Cap Mounted on > /dev/dk4 722M390M296M 56% / > /dev/dk5 2.9G1.0G1.8G 36% /var > /dev/dk7 19G 15G3.6G 80% /usr > /dev/dk9 993M160M783M 17% /tmp > /dev/dk3 128M236K128M 0% /mnt/efi > kernfs1.0K1.0K 0B 100% /kern > ptyfs 1.0K1.0K 0B 100% /dev/pts > procfs4.0K4.0K 0B 100% /proc > tmpfs 3.2G295M2.9G 9% /var/shm > > -Olaf. > -- > ___ Olaf 'Rhialto' Seibert > \X/ There is no AI. There is just someone else's work. --I. Rose
Re: How big should wd0e (/var) be
On Mon, Dec 11, 2023 at 06:07:57PM -0500, Greg Troxel wrote: > > Yes, but if / isn't the whole disk or really large, you run into the > same space issue with / that you did with /var. > Of course there are always limits but avoiding unnecessary partitioning prevents the situation of watching one partition filling up and forlornly looking at the huge free space on another one and wishing you had made better choices. The laptop I am on at the moment has two partitions, / and /home and /home is only there because it is on CGD. > On my current, non-space-challenged system which has 32G of RAM and a 4T > SSD, I have ... > 40 GB swap > Interesting that you have gone with the old 1.5X RAM for swap. I thought that came from the ancient days where every page had to be backed by swap when it was in use which has not been true for a very long time. I know that you said that extra 50Gb would not make much difference to your ZFS but just calling it out :) -- Brett Lymn -- Sent from my NetBSD device. "We are were wolves", "You mean werewolves?", "No we were wolves, now we are something else entirely", "Oh"
Re: NetBSD-10.0RC
On Sun 10 Dec 2023 at 16:27:10 -0500, Todd Gruhn wrote: > GTX-1660 works fine with NetBSd-10.0RC1 -- I had to re-slice HD and > re-install NetBSD. > > The problem moved -- now It says /var is too small; NetBSD cannot > write dow log files. > How big should /var be on a personal computer??? I have these sizes, but I found that recently /usr tends to be too small, because there are some *very* space-consuming packages, such as libreoffice and kicad. So if I had occasion to re-partition I would make it bigger, at least 50% or so. /home simply uses whatever space is left over. FilesystemSizeUsed Avail %Cap Mounted on /dev/dk4 722M390M296M 56% / /dev/dk5 2.9G1.0G1.8G 36% /var /dev/dk7 19G 15G3.6G 80% /usr /dev/dk9 993M160M783M 17% /tmp /dev/dk3 128M236K128M 0% /mnt/efi kernfs1.0K1.0K 0B 100% /kern ptyfs 1.0K1.0K 0B 100% /dev/pts procfs4.0K4.0K 0B 100% /proc tmpfs 3.2G295M2.9G 9% /var/shm -Olaf. -- ___ Olaf 'Rhialto' Seibert \X/ There is no AI. There is just someone else's work. --I. Rose signature.asc Description: PGP signature
