The differences between a usb flash drive and a SATA or NVME flash SSD is poorer vs higher-quality proprietary flash control software and a single lower quality and slower NAND vs higher quality and faster NAND chips.
@Wiz@waifu@romin@RA2lover@caronnov >spending hours compiling your own kernel is fine Compiling with a custom GNU Linux-libre .config takes 20 minutes on an old thinkpad.
If that's too long, you just download a precompiled kernel from the website.
>running a few powershell scripts to fix You need to run no scripts to limit the spying, as GNU/Linux-libre does not spy on you, which is time saved.
The scripts only work partially and temporarily anyway - soon comes along a proprietary forced update that adds more spyware and undoes changed settings.
@p I'd like to point out that, GNU had in the past put a lot of work into ensuring that existing free software on Unix could be compiled on GNU without having to be re-written and of course such compatibility remains.
Such compatibility was implemented long before Linux was even a thing.
Linux does barely anything really - GNU bash passes the elf to glibc's ld-linux-x86-64.so (or ld-hurdxxx.so), which loads the program for execution and all Linux really does is schedule the machines resources (the program is allowed unfettered access to CPU cycles until its scheduled time is over and then Linux goes and halts execution and dumps the current execution state to a stack and runs the scheduled program) and implement SYSCALLs (via glibc, which does a lot of things internally, but does need to call SYSCALLs for things like a read or a write to a file).
Although efficient scheduling and SYSCALLs and drivers are exiting as they are complicated, they are a far cry short from what you need to get an operating system.
@p (In case you were wondering, with the exception of GRUB, every nontrivial bootloader I've looked at has been chock full of proprietary software, as is typical of software not written for the users freedom).
@p >Sure seems to support the standard Unix kernel interfaces and run Unix software. >Look at the photo. >It is GNU bash running GNU Compiler Collection to compile and link the software against glibc. Facepalm into the nether realm.
>cal instead of gcal Sad!
>uname name --help; Usage: uname [OPTION]... Print certain system information. ***With no OPTION, same as -s****. -s, --kernel-name print the kernel name ... -o, --operating-system print the operating system --help display this help and exit --version output version information and exit
uname -o; GNU/Linux
uname --version uname (GNU coreutils) 9.5 Packaged by Gentoo (9.5 (p0)) Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Written by David MacKenzie.
>When did GPLv2 turn "proprietary"? Linux was proprietary software in 1991, but was released under the GPLv2-ambigious in 1996.
It only took until 1996 before the first proprietary program was added to Linux and Linux became proprietary software again.
@p >If the kernel doesn't respond to syscalls, nothing happens. If GNUboot doesn't init the hardware and then launch the GNU GRUB OS on my computer and then launch GNU Linux-libre and then launch the init and then launch the rest of the GNU and other software, nothing happens.
Of course you can boot Hurd from GRUB instead just fine and the Church of Emacs runs just as well.
>it emulates the interfaces well enough that it runs Unix software from the 1970s Any of such interfaces have been implemented by GNU and not Linux.
In this case, printf() is a function implemented by glibc, not Linux.
>it does not present a Unix interface to the software it runs? If you try to pass a proprietary binary compiled for a Unix to Linux via a loader, Linux won't be able to make any sense of it, as it does not re-implement *any* Unix interface - it implements its own custom interfaces.
The thing that presents an interface to software is GNU, although in certain cases the programmer can decide to interface directly with Linux's non-Unix SYSCALL interface.
>you are trying to make the case that it is not a complete operating system It is a FACT that Linux is only a kernel and is certainly not a complete operating system, but many people don't want the facts to get in the way of their proprietary dreams.
@p >But you should use a smaller one I should run a proprietary bootloader that doesn't respect my freedom because it's smaller?
Are you kidding me?
>See linux-0.11.tar.gz's include/unistd.h I am absolutely certain that such internal header file is not compatible with Unix's interfaces, therefore it is nonsense to claim that was "implementing Unix interfaces".
While it was written to be a Unix-kernel-like, it never pretended to be Unix, as a kernel cannot pretend to be an OS, no matter what.
The "Kopimi" mark alone unfortunately just gives an indication you probably won't be sued if you merely distribute a copy of such work, but such actions would still infringe copyright, as the mark isn't a license.
[[[ To any NSA, CIA & FBI agents reading my profile; please consider ]]][[[ whether defending the US Constitution against all enemies, ]]][[[ foreign or domestic, requires you to follow Snowden's example. ]]]Free software extremist who enjoys freedom and posting ですぅ.Please don't confuse me with an "open source" supporter ですぅ.GNU+Jihad against proprietary and "open source" software ですぅぅぅぅぅぅ!!!ⓘ User is part of an online terrorist organization.ですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅですぅです