I just wondered, what does the f in fdisk stand for?

some things I do get like kthreadd is for kernel thread demon. but fdisk I seriously don't know, lol. what am I mssing?

@Junaga Format

It seams so fcking obvious after hearing it, wtf

lol

so THAT'S what kthreadd means

x)

wtf, /sys isn't part of the FHS ?

@DmitryKudriavtsev ask your question on Unix & Linux

@Junaga neither is /proc

my guess is that they were omitted because they aren't "real" filesystems

just special kernel magic

@strugee yeah, actually I read: that they aren't defined because the way how they are build/filled is kernel version depended .

@Junaga ah, yes. that makes sense

the dir itself being present in / is defined by the fhs

now I am searching for the /sys content explanation for linux v3 but I can't find it._.

there isn't even a man page for /sys ... wtf /proc has one, has this maybe to do sth with my distro?

@strugee

do you know if the man pages are chosen by distros?

@Junaga what do you mean "chosen by distros"?

you mean written? packaged?

I know historically /proc and /sys had super terrible documentation but I don't know if that's still the case

@strugee all the man pages are just files right? first there is a man page for every package being there (and almost any from the distro installed binary) but there are also these kind of pages that do not belong to any program. If these man pages make it into the distro or not, is decided form the distro maker right?

@strugee yep, there is zero info about /sys. not even this question could be answered unix.stackexchange.com/questions/77036/sys-documentation maybe it's because /sys is pretty new and all the content found in /sys is also present in /proc for backwards compatibility reasons. Do you maybe know if that is the case? can all info form /sys be found in /proc ? just differently displayed and arranged?

@Junaga all manpages are just files

manpages don't particularly have a relation to packages (i.e. packages don't always have manpages associated with them)

oh, thats nice to know

binaries generally do however - some distros have a policy of not shipping binaries without associated manpages, and if upstream doesn't have a manpage the packager is expected to write one

Debian does this, IIRC

I though it is a requirement x) else it wouldn't make it into the repository

manpages that aren't associated with binaries sometimes come in their own packages, or maybe are shipped with the closest-related package

truthfully I'm not sure and it'll vary distro to distro anyway

but yeah I suppose you could say the distro maker decides which manpages make it in in the sense that they decide which manpages to package

and which packages are installed by default

packages can also be just data?

lol

@Junaga I'm no expert, but I'm 99% sure that /sys contains lots of info not found in /proc

only the oldest /sys stuff can be found in /proc, because that's what was available in /proc at the time /sys was added

@strugee wtf, than it should be documented somewhere

I think ill ask a question

@Junaga packages are basically made up of two parts: a bunch of files and some metadata

@Junaga the kernel is notorious for not always having the greatest documentation

some parts are fine but some are not so great

I'm not sure but I think a lot of kernel documentation is done by volunteers

@Junaga metadata is basically additional information about something

for example if you have a JPEG the data is the photo itself and metadata would be things like the camera that was used, the geolocation, the time the photo was taken, what the shutter speed was, what the aperture was... etc.

for packages the metadata is stuff like dependencies, a description, the license... etc.

@strugee unix.stackexchange.com/questions/318414/… what do you think about it?

I think is't a bit too much asked for