@wildbus8979 @Mwa MacOS was Unix based after Steve Jobs created the Mach/Unix/Mac Finder stack for use on the Next computer, as soon as he returned to Apple, it was adopted there.
@wildbus8979 @Mwa MacOS was Unix based after Steve Jobs created the Mach/Unix/Mac Finder stack for use on the Next computer, as soon as he returned to Apple, it was adopted there.
@Mwa @wildbus8979 Yes, early on there was AT&T and Berkley, System-V became AT&T’s mainstream though there were off-shoots like CB-Unix for PDP11/70’s which only had 64k I+D space, and Berkeley had 4.2 and 4.3BSD, and now you have offshoots of those, such as FreeBSD and NETBSD, MacOS is a highly mutilated BSD sitting atop a Mach micro-kernel with the Mac finder sitting on top of the whole mess. The Mach microkernel provides a layer of hardware abstraction that makes it easy to jump between architectures as Mac has often done. What I do not like about MacOS is that they include only drivers necessary for their hardware and forbid the use on Non-Mac’s by license. This limits your selection of things like video cards to those they specifically chose to use.
@possiblylinux127 It was a very high powered CPU, i9-10980xe, overclocked for all I could get out of it. At max load, it drew around 540 watts. Supplies were rated at 1kw but both short lived, the Seasonic I replaced them with is 1200 watts, also even cables are better quality, previous supplies cables were 16 guage but those that came with Seasonic, 12 guage.
PSU definitely matters, I went initially with a ThermalTake, it failed after a couple of months, then a Gigabyte, same thing, now I’m running a Seasonic and finally appear to be stable.
@data1701d @evasync You don’t have to reboot to effect that, systemdctl daemon-reload will reload the /etc/fstab file.
@dustyData @evasync I’ve been working with Linux since 1992, I have a better idea of how I want my disks laid out then an installer script.
I can understand the desire for it in Alma, since it’s primarily a replacement for Scientific-Linux, and will be on a lot of cloud services, but anytime you add a requirement for something to basically function, you increase the likelihood that it won’t.
@dustyData @evasync When I install, I generally prepare the partitions ahead of time with gparted, whether or not I create an entirely new partition table depends upon whether it is the only OS on the disk or there are multiple. I’m not using any encrypted file systems, I need the machines to be able to boot without my being present to type in a password or pass phrase. So that is not an issue.
@possiblylinux127 It was this year. Glad it’s working for you. I’ll stick with what works for me and has provided adequate performance for years.
There well may be hardware issues, but with ext4 it rarely corrupts the entire file system. You might end up with some data not flushed so you’ll have some inodes that don’t point to anything that you’ll remove with fsck upon boot, but btrfs, I’ve had it corrupt and lose the entire file system. I’ve used ext2-through-ext4 for as long as they’ve existed and never lost a file system though back in the ext2 days I had to hand repair them a few times, but ext2 was sufficiently simple that that was not difficult, but within two weeks of turning up a btrfs file system it shit itself in ways I could not recover anything, the entire file system was lost. If I did not have backups, which of course I always do, I would have been completely fuxored. It is my opinion that btrfs and xfs, both of which have advantages, are also both not sufficiently stable for production use.
@possiblylinux127 @evasync I can’t speak for them, but I’ve had btrfs blow up in ways I could not fix. I didn’t just lose a file but the entire file system. I have NEVER had this happen in many years with ext4.
No thanks, adding unnecessary complexity decreases reliability and efficiency. Might make it easier to migrate things to AWS, also a negative.
Temporary files can be created by user programs. On my machines, I made /tmp an in memory file system and also disallow execution or setuid/gid in this directory as much malware tries to abuse it in this manner.
@Quail4789 @mik Anything that you execute, yes.
@Telorand I am not familiar with that distro, I am however familiar with how mount works. As far as what is immutable and what is not, you can set with chattr +i file/directory or chattr -i file/directory.
rm /home
mkdir /home
make /var/home a symlink to it.
Alternative, edit your /etc/fstab to mount on /var/home.
@zwekihoyy If you look at any botnet on the net, it’s going to be 99.999% windows machines, always. If you look at machines compromised by Ransomeware, that happens to Linux but rare, common on Windows. Windows is like a 20 year old asphalt road, patches upon patches.
@naeap As long as it remains the easiest distro for me to get from initial setup to mangled the way I want it to work I’ll stick with Ubuntu. It still tends to be more up to date than most other releases save Fedora but I do not care for the Redhat approach at all, they are rather like Windows in trying to force you to do it there way, “thou shall use LDAP and not NIS” for example. I don’t like distros that think I should change my whole organization to suit their needs. Yea at some point I probably will switch to LDAP but will do it on my own terms in my own time not dictated by a distribution vendor. It is rather trivial for me to excise snap from Ubuntu, a lot more work to hack NIS into a system that doesn’t natively support it.
@prole @mactan Whom are you addressing?