Stuff that makes things harder for me
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- linux, shell
调研方向
先阅读 UEFI/GRUB、chroot、runit 和 rc.conf 的文档章节,以及 Rosetta Stone 页面(如果它仍然存在)。明确分区大小方面的指导、musl 仓库和架构命令、远程 chroot 服务设置以及 rc.conf 的状态;当这些要求的文档缺口得到一致解决时,即视为完成。
由索引模型根据 Issue 内容生成。
描述
I was ask to voice my grievances, so here - we - go:
"UEFI booting with GRUB also requires a special partition of the type EFI System with a vfat filesystem mounted at /boot/efi. A reasonable size for this partition could be between 200MB and 1GB."
200MB to 1Gb? for /boot/efi? I would understand if it was /boot with the kernel it if it had 200MB, but even there 1GB? The kernel has 60mb, even says so in the documentation, right now. Do you think you need to store three of them at once? But it specifically said /boot/efi. Well, I listened to that, and now I have 156KB on a 799M partition.
In the Chroot part. It says you should choose your REPO, and later it says you have to set the Architecture. Well, I did it wrong apparently, because I set the variables as a user, but installed with sudo, and that's why I installed glibc instead of musl. That wouldn't have happened if it was mentioned that for musl you have to set the variables AND the repo url. Obvious to most of you, but I didn't know that. I thought, "de" in the repo name. Seems legit. Let's go! Changed the variables to x86_64-musl and installed via sudo xbps-install, but the variables I set as a user. You could tell people to look if musl or glibc is on the list of things to be installed.
Also why ARCH=x86_64-musl and then XBPS_ARCH=$ARCH? Why not XBPS_ARCH=x86_64-musl? And why $REPO? This could all be in one line. People copy it in there anyway.
This was a remote box for me, and if I hadn't done it before with Arch, I wouldn't have known that I also need to make sure that sshd and network was good to go. Obvious to you again, and this time to me as well, but not to others. Though what I didn't know, was that I had to ln -s things differently than when the system was actually running already. It's there in the runit section, but if it had been linked at least in the chroot section that would have been nice. I mean who uses chroot besides remote install people and when is the system also not running besides in a chroot?
rc.conf documentation is still a work in progress, right?
The rosetta stone page was really nice back in the day. Bring that back.
- 主要语言
- CSS
- 星标
- 217
- 派生
- 212
- 平均合并
- 2 天 21 小时
- 30 天内合并 PR
- 1
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
void-linux/void-docs 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
void-linux/void-docs#849 · 2 条评论 ·
-
bug good first issue
难度 1/5 1 小时以内 新手友好度 75/100
void-linux/void-docs#595 · 1 条评论 ·
-
难度 1/5 1 小时以内 新手友好度 62/100
void-linux/void-docs#532 ·
-
难度 4/5 3-5 天 新手友好度 48/100
void-linux/void-docs#899 · 5 条评论 · 2 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 45/100
void-linux/void-docs#897 · 5 个 reaction ·
查看 void-linux/void-docs 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
palladius/rails8-app-on-gcp#145 ·
-
NeedsTriage
难度 1/5 1 小时以内 新手友好度 90/100
-
error 未关闭
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 1/5 1 小时以内 新手友好度 85/100
-
textual definition
难度 1/5 1 小时以内 新手友好度 90/100
geneontology/go-ontology#32653 ·