i wanted to find a website to download linux kernel documents offline in eother pdf or html or any kind but i dont know where to find and where to download any help would be appreciated the link i want to have all is linux docs where should i download all docs? is it even possible? should i download kernel source code?!

I want to provide information to users. For example, it would be helpful to provide curated lists of recommended programs tailored to users’ needs-such as a Disk Usage Analyzer for those managing storage space. This way, users can easily discover useful tools relevant to their tasks, rather than having to search for them on their own. I could do it through bash commands in the command line. Are there some useful tools to show coloured output and information in the command line? Perhaps using info? For instance I can run the command info ls Could do something similar.

If I want to get a brief usage message for a bash builtin, I can use help at a command prompt, e.g. $ help export export: export [-fn] [name[=value] ...] or export -p Set export attribute for shell variables. Marks each NAME for automatic export to the environment of subsequently executed commands. If VALUE is supplied, assign VALUE before exporting. Options: -f refer to shell functions -n remove the export property from each NAME -p display a list of all exported variables and functions An argument of `--' disables further option processing. Exit Status: Returns success unless an invalid option is given or NAME is invalid. How can I do this in zsh? I've tried % export --help zsh: bad option: -e and % help export zsh: command not found: help Also the word "help" isn't anywhere in man zshbuiltins.

Just being curious: **Question** * Is there an **official (re)source** where is list it all the categories of commands with their respective set of commands? Something like [Linux Foundation](https://www.linuxfoundation.org) for [Filesystem Hierarchy Standard **FHS**](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html) I did do a research on Google with the linux types of commands search term but appears few information. But at the top from AI Overview is shared as follows:

...

Navigation: 
cd: Changes the current working directory.
pwd: Displays the full path of the current working directory.

...

Networking: 
ping: Sends ICMP echo requests to check network connectivity.
ssh: Provides secure shell access to remote machines.
wget: Downloads files from the web.
curl: Transfers data using URLs.

...

Even though bash -n is a valid and widely used option, some manpages don't clearly document it in the bash options section, even though it is implemented. It's also not in the GNU Bash Reference Manual – Invoking Bash section: https://www.gnu.org/software/bash/manual/html_node/Invoking-Bash.html I can understand that the Bash man page (man bash) doesn't explicitly list -n as a command-line option for Bash itself but I would expect info bash to include it since I was under the impression that info documents are much more comprehensive than linux manpages. This omission is confusing and frustrating. The only place it's mentioned is in a stackoverflow answer: https://stackoverflow.com/a/171932

I'm periodically running dwww+++ to add to searchable docs what info I add to local drive. It writes "Executing index++" and it runs for minutes, whereas my CPU load is ~2-3% of one core. Why is it so slow and not using full CPU capacity of one core? I'm on Linux Mint 21 based system, my disk is rather fast.

This in reference to [this question](https://unix.stackexchange.com/q/758547/150047) . Many thanks to user Marcus Müller for providing the silver bullet for getting Emacs 29 from Debian backports. I've done this already, and profited. However, one thing remains: the Emacs 28 documentation still lingers. I'm assuming I need to do sudo apt install emacs-common-non-dfsg/bookworm-backports, but this gives me a "referred to by another package" message. Perhaps this is a mistake from the Debian side (the backport author simply forgot to include the package)? Hopefully I can get the ball rolling from any insight into this matter.

I am trying to comprehend some man7.org documentation about the User Namespace and the /bin/unshare command. I started by reading this page: https://man7.org/linux/man-pages/man7/user_namespaces.7.html On the page, there is a lot of mention of how the CLONE_NEWUSER flag can affect privileges and capabilities.  But it is unclear to me whether unshare -U /bin/bash or unshare -U -r /bin/bash uses CLONE_NEWUSER in any way. So I visited unshare(1) next to see if there is any explanation of the CLONE_NEWUSER flag usage in the /bin/unshare command.  But there is no discussion about CLONE_NEWUSER on this page. However, there is discussion about the CLONE_NEWUSER flag on the system call unshare(2) .  But it is unclear to me how the /bin/unshare is related to unshare(2) or if they are even related at all. Can anyone explain the relationship between /bin/unshare -U /bin/bash and CLONE_NEWUSER and unshare(2)? ---- Note: I am a front end HTML CSS developer trying to learn all this for the first time.  I welcome references to any reading material to address gaps in knowledge about Linux basics.

As someone who hasn't hammered in all the parts of the OSI layers, I got quite frustrated with the documentation of bridge filtering in nftables: https://wiki.nftables.org/wiki-nftables/index.php/Bridge_filtering Have I misunderstood or are IP address, ports, ICMP matching and the like not possible in bridge tables for nftables? Still, it does not complain when checking the rules with nft and the page documentation I included even gives IP ports as an example for bridge filtering. Is there faulty documentation, and have i misunderstood something?

You know, that colorized output made by special char sequences, for example: echo -e "\e[34m Hello\n \e[0m" This will produce word "Hello" colored in blue. To do this I had to search on the web, and it is hard, because different sources may say something different. I thought, that there must be some manuals, but I couldn't find them. Even with apropos color or something similar. So, the question is - where I can find reliable manuals?

I am working on understanding of how cgroups memory resource controller is enabled on Ubuntu 20.04. I have several Ubuntu machines that make up a Slurm 23.02.7 cluster. In cgroup.conf , SchedMD states : > Debian and derivatives (e.g. Ubuntu) usually exclude the memory and memsw (swap) cgroups by default. To include them, add the following parameters to the kernel command line: cgroup_enable=memory swapaccount=1 If I follow this advise and do :

root@node01:~# grep CONFIG_MEMCG /boot/config-5.4.0-169-generic
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
# CONFIG_MEMCG_SWAP_ENABLED is not set
CONFIG_MEMCG_KMEM=y

It seems that contrary to SchedMD's opinion, the cgroups memory controller is already enabled by default. However, I'd like formal documentation about what exactly every variable is in /boot/config-5.4.0-169-generic. I've searched for an associated man page, but cannot find one. **Question** : 1. What man page or other documentation exists describing the configurations set in /boot/config-5.4.0-169-generic?

I am setting up router inside freebsd jail with ipfw, I might be blind, but I could not find comprehensive documentation on IPFW, which would make subject clear. I read both "firewall" and "ipfw" man pages, unfortunately it did not make things clearer - is there a complete documentation for ipfw as a separate piece not in form of manpages?

I can look around the internet and find that the associated number for SIGKILL is 9, but is there linux documentation (such as, a man page) showing the complete list of signals and their numbers?

Is there a way I can do what stated in the title from the terminal commands, or will I have to look into the codes?

**Is there any documentation for the default permissions of the /tmp folder on \*nix, in particular Linux?\ (Or perhaps /tmp doesn't have specified default permissions?)** Background:\ I'm trying to ensure temporary files I store inside of /tmp are secured. In particular I'd like a guarantee that the sticky bit (aka restricted deletion flag) is set on /tmp, so that the files cannot be deleted or renamed by anyone except the file owner. Searching around the web, it seems the sticky bit is likely set, e.g. - https://www.thegeeksearch.com/what-is-the-correct-permission-for-tmp-directory-in-linux/ - https://en.wikipedia.org/wiki/Sticky_bit However, I'd like to have "official" documentation confirming it one way or the other for the desktops my program may run on (which are Linux (most likely distros are Ubuntu and Debian) and macOS). This is so that I can be sure it's treated like a contract, and able to rely on it being set. The wording I find is typically more suggestive, along the lines of "typically the sticky bit is applied to /tmp". The most official documentations I've found are the below two: - [Linux man page for chmod](https://man7.org/linux/man-pages/man1/chmod.1.html#RESTRICTED_DELETION_FLAG_OR_STICKY_BIT) : "the restricted deletion flag [...] is commonly found on world-writable directories like /tmp" Which is suggestive of it being set, whereas I'd like a statement confirming it. - [An answer in Red Hat's Customer portal](https://access.redhat.com/solutions/49267) : "The /tmp directory requires special permissions. This directory has Sticky Bit permissions." This is the only mention I've found where it confirms /tmp has the sticky bit set (albeit on Red Hat). But it is not their [official documentation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/) , so it doesn't give me fully the same confidence as a specification in their documentation would (which I would treat as a contract they will uphold).

On GNU/Linux is it possible to change the default pager for info command? I would like to use less as the pager (similar to man pages). I have customized less to use colors to make navigation of man pages much easier.

After downloading the source code for Bash, I was browsing through the doc directory and came across the following files: * [bash.1](http://git.savannah.gnu.org/cgit/bash.git/tree/doc/bash.1) is a regular [troff](https://en.wikipedia.org/wiki/Troff) file used to build the *man page*. * [bash.0](http://git.savannah.gnu.org/cgit/bash.git/tree/doc/bash.0) is like a plain text version of the man page – only that it has the [^H backspace control character](https://en.wikipedia.org/wiki/Backspace#.5EH) liberally distributed throughout it. These control characters are not displayed in the representation provided by the Git web interface but the [actual file can be downloaded](http://git.savannah.gnu.org/cgit/bash.git/plain/doc/bash.0) and examined in text editor such as Vim. Running the file command on bash.0 prints the following output: bash.0: ASCII text, with overstriking I’ve never come across this file format before and I was wondering what its purpose is and how it’s used. Searching the Web for the phrase *“ASCII text, with overstriking”* hasn’t been very enlightening.

Here is an example: $ cat file1 hello there $ cat file2 some,very,long,line,hello,csv some,very,long,line,nope,csv $ join -t, -1 1 -2 5 file1 file2 hello,some,very,long,line,csv This works as documented: the joined field is pulled out to the left, and the remaining fields are printed. But my desired output is to retain the CSV (file2) column ordering.  I can get to print the CSV intact with this command, which lists the CSV field numbers explicitly: join -t, -1 1 -2 5 -o $(head -n1 file2 | awk -F, '{print NF}' | xargs seq | sed 's/^/2./' | paste -d, -s) file1 file2 And it prints: some,very,long,line,hello,csv I _thought_ it's for this that join has an auto format. This is the precious little the man page of join has to say about the -o FORMAT: > If FORMAT is the keyword 'auto', then the first line of each file determines the number of fields output for each line. However, I don't know what that means or how I'm supposed to use the format as auto. I tried this, but didn't get anything different than I did previously: $ join -t, -1 1 -2 5 -o auto file1 file2 hello,some,very,long,line,csv A naive interpretation would be that I should list out the required fields as the first line of each file, but that's wrong, too. So, my question is, what is the auto for, and how am I supposed to use it? Can I use it to retain the column order of the input CSV?

I used to be able to just file bug reports on [Launchpad](https://launchpad.net/) , but now, with the ubuntu-bug application I am defeated. Specifying the package results in an error telling me that it cannot collect any information, presumably because the files are not text files not binaries or, perhaps because I'm running Pop! OS,-- even though apt-cache tells me that the package I'm trying to file a report on is maintained by Ubuntu Developers... (Despite the fact that Ubuntu Developers maintain the package, apparently [Ask Ubuntu](https://askubuntu.com/) is not the place to ask about Ubuntu Developer maintained packages if they're on other distributions.)

The [Fedora documentation on updating to a new Fedora release](https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/) recommends that, after we update, we should update the GRUB bootloader. They provide the following suggested advice on how to update: $ sudo mount | grep "/boot " /dev/sda4 on /boot type ext4 (rw,relatime,seclabel) $ sudo grub2-install /dev/sda So for a disk that has a device name like /dev/sda, we are supposed to start with the partition device /dev/sda4, remove the number (4), and obtain /dev/sda. However, my devices are numbered differently. I have a NVMe SSD, and for me, /boot is on /dev/nvme0n1p2. So it seems like the documentation is incomplete. What should the correct instructions be, to handle this case? How do I adapt these instructions, e.g., to systems with a NVMe SSD? For example: What is the correct command to run? What parameter do I use with grub2-install? Is grub2-install even the right command to run, or should I be running a different command? Is it possible to give instructions that cover both the case of BIOS systems and UEFI systems?