Homeserver VS coreutils

Most ATX cases support M-ATX mobo's too! So if you don't care about it being a midi tower thats your cheapest option. Just pick one that has enough drive bays, I always go with Fractal Design. If you want to go smaller you'll have to start looking for more niche cases/manufacturers. I suggest planning your other hardware first, then finding a case that fits it. Btw, I'm also interested in low power consumption. If you haven't seen this yet, it's great. It's essentially a TLDR from a german/dutch forum dedicated to low power machines. I'm going with the Fujitsu 3643-B, as that has 6 sata, 2 x16 PCIE 3.0 slots, and supports ECC memory. If you don't care about ECC and only need 4 sata ports, the Fujitsu D3643-H is the way to go. Both these boards can run full systems at 5W idle, which is insane. Good luck!

I have been tinkering in home servers and found this guide to be especially helpful. The guide has everything run on Manjaro through a lengthy docker-compose file.

Hi All! Thanks alot for your valuable inputs. based on your comments, and suggestions - and after some research - i think i have settled on the following "path". First of all - i can see that a SoC system might not be the smartest option - there the size and the fact that they are not very flexible - makes me think that this might not be the smartest way to go. so i found this site: https://github.com/zilexa/Homeserver/blob/master/Recommendations.md And it looks like there has been alot of research that i can reuse. now - in the link - a suggestion is made to buy the asRock desk mini 310, but - when i search - the processors for the LGA115x socket -is not that cheap / available in denmark - so i found this https://www.asrock.com/nettop/Intel/DeskMini%20H470%20Series/index.asp the Desk Mini H470 - sold as a barebone. it doesnt have ECC, but this is not a big concern for me. then i will add some RAM and based on the suggestions - i think 16GB will be the sweetspot have not yet decided what i will choose here. i guess a 1x16 will be smartest - so that i can add another 16 later on. for the OS + and main files ( personal files, as well as my music collection ) i will add the 2TB nvme from Samsung the PM9A1. next - i have decided to "scrap" my 8tb disk - and then go with a 2.5" 4tb - the Samsung Samsung QVO 870. this will host all my movies / tv series etc. no backup is needed here. i did a quick online cart - and theese are the prices - ( in danish ): Barebone Asrock: 1558,- Samsung PM9A1 M.2 2000 GB PCI Express 4.0 TLC NVMe : 1597,- Samsung MZ-77Q4T0BW 870 QVO SSD, 4000 GB, 2.5": 2590 SORAM GSkill D4 2400 8GB C16 Rip (F4-2400C16S-8GRS): 169 all in all :5.929 which is approx: 796,89 Euro. Any thought on this? alternative ways i should look?

Check out https://github.com/zilexa/Homeserver

These scripts are totally inspired from zilexa/Homeserver.

This is the docker-compose.yml

https://github.com/coreutils/coreutils/commit/fcfba90d0d27a1...

A summary of other changes just released in GNU coreutils 9.5 are:

* mv accepts --exchange to swap files

> some are simple like yes(1)

Not that simple: https://github.com/coreutils/coreutils/blob/master/src/yes.c

The -S / --split-string option[1] of /usr/bin/env is a relatively recent addition to GNU Coreutils. It's available starting from GNU Coreutils 8.30[2], released on 2018-07-01.

Beware of portability: it relies on a non-standard behavior from some operating systems. It only works for OS's that treat all the text after the first space as argument(s) to the shebanged executable; rather than just treating the whole string as an executable path (that can happen to contain spaces).

Fortunately this non-standard behavior is more the norm than the exception: it works at least on modern GNU/Linux, BSDs, and macOS.

[1] https://www.gnu.org/software/coreutils/manual/html_node/env-...

[2] https://github.com/coreutils/coreutils/blob/b09dc6306e7affaf...

> building a cat from scratch

> That would be an interesting project.

Here is the source code of the OpenBSD implementation of cat:

> https://github.com/openbsd/src/blob/master/bin/cat/cat.c

and here of the GNU coreutils implementation:

> https://github.com/coreutils/coreutils/blob/master/src/cat.c

Thus: I don't think building a cat from scratch or creating a tutorial about that topic is particularly hard (even though the HN audience would likely be interested in it). :-)

the yes command, writing to /dev/null, is making IO calls, which interfere with predictable scheduling.

If you look at the source code for yes, https://github.com/coreutils/coreutils/blob/master/src/yes.c

it builds a buffer of output and then writes that in a for loop

  while (full_write (STDOUT_FILENO, buf, bufused) == bufused)

Looking at the source of nohup, if the execvp() of the child happens then it _must_ have already done the signal (SIGHUP, SIG_IGN) so - WTF?

This got me wondering so I went and looked and it seems like lo and behold there was actually a commit to the GNU ls source just 2 weeks ago.

https://github.com/coreutils/coreutils/blob/master/src/ls.c

"maint: prefer char32_t to wchar_t"

even an empty file? Yes. so now it was a file with a copyright disclaimer and nothing else. And the koan-like question comes to mind is "Can you copyright nothing?" well AT&T sure tried.

Then somebody said our programs should be well defined and not depend on a fluke of unix, which at this point was probable a good idea. so it became "exit 0"

Then somebody said we should write our system utilities in C instead of shell so it runs faster. openbsd still has a good example of how this would look.

http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr....

At some point gnu bureaucracy got involved and said all programs must support the '-h' flag. so that got added, then they said all programs must support locale so that got added. now days gnu true is an astonishing 80 lines long.

https://github.com/coreutils/coreutils/blob/master/src/true....

http://trillian.mit.edu/~jc/humor/ATT_Copyright_true.html

> Yes, ls is maintained. Although, maintained is a very strong word. It exists.

Why would it be a strong word? Here it is, in src/ls.c: https://github.com/coreutils/coreutils

It is then packaged by tens of operating system distributions, who themselves maintain extra patchsets, some of which are then upstreamed.

It is installed and used on millions (billions?) of devices, for 3 decades.

It's a very reliable and trusty "sharp stick of metal" :)