nanook

@CasualTee @Quail4789 With torrent you are specifying the filename when you start the torrent, or at least I am. Thus any data can only go into that file. Usually when you use torrents the way I do, primarily for downloading distros, occasionally source code, an md5sum is provided. Thus before you use the downloaded data you do an md5sum on it and check it against the value it is provided. If it's not the same you remove the file and start over, if it is you know you didn't get any additional data.

@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.

@BaumGeist @Quail4789 If you get software from an untrusted source, and it does not matter if it's a torrent, ftp, https, scp, etc, you run this risk. And usually when you download with a torrent the supplying site will publish a hash which you can compare to make sure that it wasn't corrupted in transit.

@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.

@Quail4789 @rc__buggy@sh.it just.works there is not a known exploit in sudo but there IS a known exploit in the library it uses to elevate privileges, at least in older versions. Also I make full system weekly backups so worst comes to worst I'm never going to lose more than a weeks data.

@rc__buggy @Quail4789 And that is a very good point but the only thing I ever use transmission for is downloading distros. If my distro is already compromised then it's already all over, transmission aside.

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.