On 3/17/25 05:27, tlaro...@kergis.com wrote: > I wanted to install 9legacy as well as 9front (already installed) on > my main PC. > > The 9legacy install is the "old" one: I had my CD/DVD drive as the > first SATA device so all hell break loose (because the install insists > on using the first detected 9fat and was trying to write hence the > CDROM 9fat). > > So I shuffled my devices to put the MBR partitioned disk first, the > GPT partitioned (with 9front) second and the CD/DVD-RW last. > > 9legacy is then installed. After verifying that at least kerTeX > installs on it---hence the fix made two days ago---I went back to my > ether8169 duty. > > For this, cross reading sources from NetBSD, FreeBSD, Linux and > Realtek, I worked on NetBSD. > > The writing done so that it was worth then trying to compile and test, I > went back to 9front... > > Well: I _wanted_ to get back to 9front... But 9front has been installed > on what was /dev/sdE2 and is now /dev/sdE1. > > I modified my plan9.ini but no! The cwfs64 has its config, that says > "/dev/sdE2" and I loop back to bootargs prompting. > > Having read that the device was identified in the NVRAM, I dd'ed the > NVRAM blocks for inspection. Nothing except the record for Glenda. To > play it safe, I zeroed the NVRAM. Same result. It's not there. > > The paper says that the config is stored in the first block of the > device. It is unlikely to be in the MBR (if every OS would use it > for its own stuff, it would be a mess). It's not, for the same > reason, in the first block of the "primary" partition of Plan9. It's > not in the second block holding the plan9 proper partitioning. > > So where is the config? First block of "fscache"? of WORM? of "other"? > Elsewhere? > > I can put "-c" in bootargs to get to fsconfig. But what is the syntax > in order to not wreak havoc? The man page gives SCSI syntax, but what > about SATA sd drives?
The commands accepted are documented here http://man.9front.org/8/fsconfig. It is best to use the command mode instead of trying to manually modify the configuration block, the config block stores the actual partition names so copying it over will not do anything for you. You configure the system just as you would as if you were first installing it. I've had to do this before and assuming you're using a fairly standard cwfs install you can do the following: At bootargs: % cwfs64x -C -c -f /dev/newDisk/fscache config: filsys main c(/dev/newDisk/fscache)(/dev/newDisk/fsworm) config: filsys other (/dev/newDisk/other) config: filsys dump o config: end Yes this is a bit annoying, that's why it's been fixed in both hjfs and in gefs, which work fine with only a plan9.ini change (when changing the disk ordering). - Jacob Moody > > Can I give "-m /dev/sdE1/fscache" in bootargs that would magically > fix the config? > > Is there a way to specify to the file service "hic": "handle the device > you sit on", so that it is relative, "movable"---dd'ing the whole Plan9 > partition elsewhere will work? > > TIA for tips, explanations and magic invocations! ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Teea5d5b5e6678327-Md30b62505ebc33db224b0309 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
