Installing Koji kernel. Booting specific kernel by default.

jetstream commented

2021-10-12 00:34:50 +00:00

Contributor

Added the following changes:

quickdoc for installing kernel from Koji
booting page and HowTo for booting a specific kernel by default

Added the following changes: - quickdoc for installing kernel from Koji - booting page and HowTo for booting a specific kernel by default

ankursinha commented

2021-10-12 08:17:18 +00:00

Contributor

Could you add an example here please? I mean show the output of ls /boot on your machine, and then what the command should be? (These docs are for users who will not be techies and so we need explicit instructions with examples to make sure they can follow steps). Also: does the command always need the x86_64 suffix, and is /boot the correct place for UEFI boots also?

Could you add an example here please? I mean show the output of `ls /boot` on your machine, and then what the command should be? (These docs are for users who will not be techies and so we need explicit instructions with examples to make sure they can follow steps). Also: does the command always need the `x86_64` suffix, and is `/boot` the correct place for UEFI boots also?

ankursinha commented

2021-10-12 08:18:11 +00:00

Contributor

I'd remove the Fedora 23 guide. Even if it's relevant, that version of Fedora is long gone and we don't want users to be looking at other information there assuming everything there still applies :/

ankursinha commented

2021-10-12 08:19:00 +00:00

Contributor

Is this heading required? The include has its own heading (and it's about changing the default not just "booting" in general?

ankursinha commented

2021-10-12 08:20:05 +00:00

Contributor

I'd split each sentence into a line by itself. See https://sembr.org/

ankursinha commented

2021-10-12 08:20:58 +00:00

Contributor

"If there is a need to install a kernel that is not currently available in the Fedora repositories"?

ankursinha commented

2021-10-12 08:21:51 +00:00

Contributor

package -> client ?

ankursinha commented

2021-10-12 08:23:10 +00:00

Contributor

So, one needs to first check if a kernel with this NVR was actually ever built for Fedora, by going to the Koji web interface.

I think it'll be good to give two methods here: one by going to the koji web interface, finding the necessary build, and then downloading files using the browser; and then the second can be this cli based method which is for more advanced users.

So, one needs to first check if a kernel with this NVR was actually ever built for Fedora, by going to the Koji web interface. I think it'll be good to give two methods here: one by going to the koji web interface, finding the necessary build, and then downloading files using the browser; and then the second can be this cli based method which is for more advanced users.

ankursinha commented

2021-10-12 08:24:22 +00:00

Contributor

I think it's best to use - instead of n.nn and so on everywhere. That way the command is self explanatory?

I think it's best to use <version>-<release> instead of `n.nn` and so on everywhere. That way the command is self explanatory?

ankursinha commented

2021-10-12 08:24:31 +00:00

Contributor

Metadata Update from @ankursinha:

Request assigned

**Metadata Update from @ankursinha**: - Request assigned

ankursinha commented

2021-10-12 08:24:39 +00:00

Contributor

Metadata Update from @ankursinha:

Pull-request tagged with: improvement, needs changes

**Metadata Update from @ankursinha**: - Pull-request tagged with: improvement, needs changes

ankursinha commented

2021-10-12 08:25:06 +00:00

Contributor

Thanks very much for this @jetstream . I've done a first round of review here now ^

jetstream commented

2021-10-19 00:23:20 +00:00

Author

Contributor

Could you add an example here please? I mean show the output of ls /boot on your machine, and then what the command should be? (These docs are for users who will not be techies and so we need explicit instructions with examples to make sure they can follow steps). Also: does the command always need the x86_64 suffix, and is /boot the correct place for UEFI boots also?

Sure. Adding an example in the next push.

I reckon it can be generalised to <arch>. Including the change in the next update.

AFAIK, kernels are located in /boot by default (for BIOS as well as UEFI systems)

> Could you add an example here please? I mean show the output of `ls /boot` on your machine, and then what the command should be? (These docs are for users who will not be techies and so we need explicit instructions with examples to make sure they can follow steps). Also: does the command always need the `x86_64` suffix, and is `/boot` the correct place for UEFI boots also? Sure. Adding an example in the next push. I reckon it can be generalised to `<arch>`. Including the change in the next update. AFAIK, kernels are located in `/boot` by default (for BIOS as well as UEFI systems)

jetstream commented

2021-10-19 00:44:03 +00:00

Author

Contributor

Is this heading required? The include has its own heading (and it's about changing the default not just "booting" in general?

I was trying to align the addition to the existing structure. Here's my understanding.

Introduced a page for Booting (hence the heading Booting) under the section Kernel and Booting. This page has one include (for booting a kernel by default) for now. Any additional quick-docs on booting could be added as includes to this page.

Is that moving away from the current layout?

> Is this heading required? The include has its own heading (and it's about changing the default not just "booting" in general? I was trying to align the addition to the existing structure. Here's my understanding. Introduced a page for `Booting` (hence the heading `Booting`) under the section `Kernel and Booting`. This page has one include (for booting a kernel by default) for now. Any additional quick-docs on booting could be added as includes to this page. Is that moving away from the current layout?

jetstream commented

2021-10-19 01:00:59 +00:00

Author

Contributor

"If there is a need to install a kernel that is not currently available in the Fedora repositories"?

Not sure I understood. Did you want me to change the wording to the sentence you suggested? I thought Koji is a Fedora repository.

> "If there is a need to install a kernel that is not currently available in the Fedora repositories"? Not sure I understood. Did you want me to change the wording to the sentence you suggested? I thought Koji is a Fedora repository.

ankursinha commented

2021-11-17 09:06:59 +00:00

Contributor

"If there is a need to install a kernel that is not currently available in the Fedora repositories"?

Not sure I understood. Did you want me to change the wording to the sentence you suggested? I thought Koji is a Fedora repository.

Yes please. Koji is not a repository, it's the build system which archives a certain number of old builds. The repositories only include a version of software that was released with a new Fedora release in the fedora repository, and then another version in the updates repository---they won't contain all the different update versions that may be available on koji. dnf does not speak to koji, it only knows of the repositories.

Is this heading required? The include has its own heading (and it's about changing the default not just "booting" in general?

I was trying to align the addition to the existing structure. Here's my understanding.

Introduced a page for Booting (hence the heading Booting) under the section Kernel and Booting. This page has one include (for booting a kernel by default) for now. Any additional quick-docs on booting could be added as includes to this page.

Is that moving away from the current layout?

Let's leave this as is for the time being, it can be easily tweaked later.

Please drop a comment when you've made more changes. Thanks again

> > "If there is a need to install a kernel that is not currently available in the Fedora repositories"? > > Not sure I understood. Did you want me to change the wording to the sentence you suggested? I thought Koji is a Fedora repository. Yes please. Koji is not a repository, it's the build system which archives a certain number of old builds. The repositories only include a version of software that was released with a new Fedora release in the `fedora` repository, and then another version in the `updates` repository---they won't contain all the different update versions that may be available on koji. `dnf` does not speak to koji, it only knows of the repositories. > > Is this heading required? The include has its own heading (and it's about changing the default not just "booting" in general? > > I was trying to align the addition to the existing structure. Here's my understanding. > > Introduced a page for `Booting` (hence the heading `Booting`) under the section `Kernel and Booting`. This page has one include (for booting a kernel by default) for now. Any additional quick-docs on booting could be added as includes to this page. > > Is that moving away from the current layout? Let's leave this as is for the time being, it can be easily tweaked later. Please drop a comment when you've made more changes. Thanks again

jetstream commented

2022-01-08 03:53:58 +00:00

Author

Contributor

1 new commit added