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!
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!
FS#136 - possible filesystem creation bug on setup script
Attached to Project:
Arch Linux
Opened by (almostlucky2) - Wednesday, 13 August 2003, 18:49 GMT
Last edited by Judd Vinet (judd) - Sunday, 14 September 2003, 18:58 GMT
Opened by (almostlucky2) - Wednesday, 13 August 2003, 18:49 GMT
Last edited by Judd Vinet (judd) - Sunday, 14 September 2003, 18:58 GMT
|
DetailsWhen installing over various partitions (/ /boot /usr /home /var and /tmp all seperate) i would get stuck in a loop, prompting me to abort the install. All but home filesystems were created by the installer (home was just mounted).
This did not occur when i used only /boot /root and swap. |
This task depends upon
Whenever you create and mount a /tmp with the installer, the installer umounts /tmp, which is tmpfs. The result will be an empty /tmp directory on a read-only filesystem, causing setup not being able to write in /tmp. The result is a dialog asking to abort.