Submit #1173
closed
src/share/examples/rconfig/hammer.sh does not create a usable system
Description
With hammer.sh the way it is, when you boot the system of the hdd, it will
boot, but you wont be able to login or do anything else useful. The problem is
that /mnt/usr is another mount point and another cpdup has to be run.
Attached is the patch for this + added some cleanup (deletes /mnt/autorun* &
co.)
--
Regards,
Rumko
Files
Updated by rumcic almost 16 years ago
Rumko wrote:
new version ... added kern.bootfile to sysctl.conf ... its hardcoded
to /boot/kernel for now ... maybe something like "/boot`sysctl kern.bootfile |
cut -d ':' -f 2`" would work? ...
without this, savecore cant create a memory dump in case of a panic
--
Regards,
Rumko
Updated by
Updated by swildner almost 16 years ago
It does work usually, but sometimes it doesn't.
Not sure if working or not working is correct here. Question is if cpdup
is supposed to not cross the mount_hammer mountpoint only (which is '/'
so it should work) or is it also supposed to not cross the mount_null
mountpoints (in which case it shouldn't work)?
Failure seems kinda random, e.g. some weeks ago, I ended up with an
empty /boot when installing with hammer.sh. Re-running the script
without modification fixed things.
Sounds weird? I think so too.
Sascha
Updated by tuxillo almost 10 years ago
- Tracker changed from Bug to Submit
- Description updated (diff)
- Category set to Userland
- Assignee changed from 0 to tuxillo
- Priority changed from High to Low
- Target version set to 4.2
Grab.
Also moving it to submit tracker.
Updated by tuxillo almost 10 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 6c13d3bd09ff0f73c2d47840d17a7e88fecfdadb.