external USB bootable devices are not supported
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- arch-linux, linux, shell
- Domain
- operating-systems
Research direction
Start by reproducing the installer flow with an external USB hard disk selected as the target, then inspect how the installer invokes GRUB and chooses its installation device. Done means an external device can boot independently, with all GRUB components placed on that device, while fixed-disk installation continues to work.
Written by the indexing model from the issue text.
Description
Installer really install Arch Linux on A fixed harddisks. But when user choose some external USB devices it is making problems.
Grub always install its machine loadable code to The fixed harddisk or even to a loop partition. As a result it is not possible to boot from external bootable device. It is very interesting phenomena. Because fixed harddisks are really supported. External USB harddisks are very fast in todays times. So it would be A good idea to think about forcing Grub boot loader to install all of its parts correctly.
Sure, when user select fixed harddisk device, it is absolutely all right and system work. Even hybernation mode is correctly supported.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from blind-computing/blindarch
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
All issues in blind-computing/blindarch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
[Bug]: e2e script flag parsing is brokenPossibly taken @ericcurtin claimed this today. Openarea/dev-infra area/tests kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agent-substrate/substrate#2217 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
FluidNumerics/fluid-walk-blocker#172 ·
Maintainers usually reply within 1 day