That "Beginners Guide" wiki page... #343
Replies: 6 comments 4 replies
-
We appreciate the contribution. It is off to a good start and I'm sure with a few refinements it will be a resource for those interested in Debian. The plan is to remove the notice of unofficiality once one of us has actually been through the full guide and are comfortable recommending to people looking for help. In the meantime, neither of us has had the time to review everything. I started making some edits because somebody on IRC was having difficulty following your guide. I wanted to clean up some formatting and clarify a few points. Also, the guide originally overlooked the mounting of filesystems you created; because the root filesystem is Regarding formatting, I swapped some explicit URLs for more descriptive hyperlinks and started making liberal use of code ticks to designate "machine" aspects when talking about them in text. For example, instead of just referring to "/dev/sda" (or, worse, "/dev/sd*"), surround in backticks to get I don't mind the intent of the tables explaining command arguments, but I'm not sure if that's the best format for presenting the information; especially when I started back-quoting the parameters in the left column, the tables started to wrap weird. My edits currently run through the end of Section 2. |
Beta Was this translation helpful? Give feedback.
-
Sorry about the canmount, that's the type of thing I was hoping to pick up with a full run-through. I was going back and revising some sections as I found mistakes in what I had done, so I'm not sure that I captured everything. Shall I finish the rest of the code ticks and descriptive hyperlinks? I'm not so sure about the argument tables anymore either. I think there is value in explaining what various cryptic commands do, but they are kind of starting to dominate the document. Do you think they might be better hidden in collapsed detail tags, perhaps with a summary of "(command explanation)", and maybe just make them paragraphs with **bold descriptions: ** or something like that? Otherwise I'm not sure if it would be best to keep them as is or remove them all together. |
Beta Was this translation helpful? Give feedback.
-
Yeah, you can finish the reformat and do whatever you think is appropriate with respect to the tables. |
Beta Was this translation helpful? Give feedback.
-
Status update: I started an end-to-end test, but quickly ran into a problem with
|
Beta Was this translation helpful? Give feedback.
-
Your machine is missing `kpartx`. Being able to successfully run that will
help.
…On Tue, Nov 8, 2022, 11:44 AM John ***@***.***> wrote:
Clarification: The issue seems to occur between the first two calls to
sgdisk to create the EFI partitions, which succeed (not shown in above
exampe), and the second two calls to sgdisk to create the root partitions
(shown above), which fail to notify the kernel.
—
Reply to this email directly, view it on GitHub
<#343 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJ3NJJB5DVUMVO6CMOYWPDWHIVJFANCNFSM6AAAAAARFVVYZA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi, After many end-to-end tests and corrections, I am finally confident that following the steps in the document will result in a working system, at least On My Machine(tm). I have also been using another machine, that I built using an early version of the document, as a daily driver for a couple of months so I'm also reasonably confident that the system you end up with is suitable for general use. I think I'll leave it there for now. It doesn't cover building an EFI image with remote access, but I have linked to the new "Building in Containers" page which does, so hopefully that will meet the needs of anyone who requires that. I took the liberty of removing "still a work in progress" from the notice at the start, as that didn't seem correct any more - hope that was right? |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, I'm John, the guy who has been working on the "Complete Beginner's Guide" page in the wiki. I thought that I should say hi and introduce myself / explain why it's there and where it's up to, since it's been taking forever to finish and Andrew has had to put a disclaimer at the top of it...
I started writing it in response to this discussion with u/E39M5S62 on the Reddit ZBM 2.0 announcement post:
https://www.reddit.com/r/zfs/comments/vmqw63/comment/iewc6tf/
(I'm not sure if E39M5S62 is one of you guys?)
As per that discussion, I'm delighted to have access to a boot manager that can manage/recover my ZFS boot environments, and I thought it might help if I put together an example of the type of detailed step-by-step documentation that I thought could help end-users like myself adopt ZBM with Root-on-ZFS more easily, either as a suggestion for other documentation, or if I managed to get it right, as an additional documentation asset. I have been building it in the wiki rather than making a markdown pull request because all the other end-user guides seem to be there too.
It took me a long time to write because I have been learning as I go, and there are some parts I did not understand at first and that I need to rewrite, in particular the part about having to double-enter the pool decryption password and putting the decryption key in the initramfs instead - I have since got that working, an I think that's a much better way to go that what I first wrote. I think it could also use an appendix with how to optionally build ZBM with dropbear for ssh access rather than just using the pre-build EFI image, and also how to set up a script to mount swap on a degraded mdraid array if one of the raid1 partitions is unavailable at boot.
I still need to give it an end-to-end test by using it to install ZBM onto a spare machine, to make sure that I have everything in order and that following the instructions actually results in a working system - hopefully I should be able to find time for that over the next few weeks.
Does what I have written seem to be roughly on-track, and like it might be of some use?
Beta Was this translation helpful? Give feedback.
All reactions