Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#4020 - 0.7.1 Unable to install to /dev/hda25 (no dev nodes)

Attached to Project: Arch Linux
Opened by Jari Aalto (jaalto) - Monday, 20 February 2006, 19:17 GMT
Last edited by arjan timmerman (blaasvis) - Monday, 20 February 2006, 20:44 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have several partition up to hda40 on one disk. The install CD cannot handle this,
becasue there are not that many device nodes created in /dev

The /dev is read only (when booting on CD), so I couldn't even run mknod(1) to
create the destination partition node for /

Please create enough nodes 0 .. 40 to all hda ... hdh (if you run Promise cards, the
high devices might go as high as hdh)

This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 11 November 2006, 20:12 GMT
Reason for closing:  Won't fix
Comment by Jari Aalto (jaalto) - Monday, 20 February 2006, 21:01 GMT
I worked around this bug by

mount -o remount,rw /

And after that creating the mknod(1) device for the partition. Then repeating the install.
However this is clear bug in the install program. It presents the /dev/hd* choices, but
they should be in /dev as well.

I also feel that / should be "rw" during installation; especially when you might want to
drop on console.
Comment by arjan timmerman (blaasvis) - Wednesday, 07 June 2006, 17:37 GMT
hwo is it on 0.7.2 ?
Comment by Jari Aalto (jaalto) - Friday, 09 June 2006, 18:07 GMT
I'm unable to comment. The bug was reported to 0.7.1 which was the current install CD at the time.
Later 0.7.2 was released. Since this bug is not yet marked as "fixed" by the developers, I assume that is still holds.

Loading...