Summary: | sysinstall(8): after restart, installation crashes, md0c filled up. | ||
---|---|---|---|
Product: | Base System | Reporter: | Yaad Golani <usey> |
Component: | bin | Assignee: | freebsd-sysinstall (Nobody) <sysinstall> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | ||
Priority: | Normal | ||
Version: | 4.6.2-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Yaad Golani
2002-08-29 15:20:02 UTC
Responsible Changed From-To: freebsd-bugs->qa Sounds like sysinstall forgot to chroot or chdir into the right directory. Assign this to the qa list. The problem is that sysinstall assumes that you have already done the chroot into /mnt if you do a restart. However, this is not always the case. Arguably since a restart kicks you back to the main menu, sysinstall should always chroot() in install.c. At the very least it should chroot if it hasn't done it yet. The line in question is: if (!Restarting && chroot("/mnt") == -1) { in installInitial() in install.c. -- John Baldwin <john@baldwin.cx> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ Responsible Changed From-To: freebsd-bugs->randi Taking this. Responsible Changed From-To: randi->brucec Grab - I have a patch to fix this. The problem is that to restart, sysinstall calls execl(), and then runs again. However, it checks to see if it's running as init by seeing if the PID is 1, which after restarting it won't be. It then goes on to assume it's running in an already installed system, where distributions etc. should be extracted to /, not /mnt. execl doesn't actually change the PID so John's correct that the problem will be with the chroot. I'll put together a patch to fix it. -- Bruce Cran Responsible Changed From-To: brucec->freebsd-sysinstall Back to the pool. sysinstall has been replaced by bsdinstall in FreeBSD 9.x. Closing. sysinstall has been replaced by bsdinstall in FreeBSD 9.x. Closing. |