-
xmerlindanmcd_, I'm trying to overlay /etc/system on a bootable pool, on the USB stick mounted at /mnt/. Normally, I place the files in /mnt/bootfs/etc and loader.conf.local in /mnt/boot. I saw that you made a post where you mentioned that on bootable volumes we can place files in /zones/boot/custom to make sure the changes are applied to all releases... can you confirm this? ...because it doesn't seem to be working for me.
-
danmcd_That works for "future installed boot images". From the piadm(8) man page:
-
danmcd_"Loader config files can also be placed in ${BOOTFS}/custom, and will be used by all subsequently installed boot images, but not existing ones."
-
danmcdSo I'd recommend:
-
danmcd- Set up $BOOTFS/custom
-
danmcd- Install the next SmartOS update (which is built, but not officially blessed-as-released yet, but will be by tomorrow)
-
danmcd- Boot the next SmartOS update
-
danmcdThat needs to be done in-order, per the man page's "subsequently installed boot images".
-
xmerlinTherefore, the paths will be /zones/boot/custom/loader.conf.local and /zones/boot/custom/etc/system ...correct?
-
danmcdDepends on what you put in there. It works like it did on the usb key. Here's examples I have for ppt:
-
danmcd(gist link coming soon...)
-
danmcd
-
danmcdIf you really need an old PI, you can hand-hack the $BOOTFS's `boot-XXXXX` directories.
-
danmcdAnd it's not a function of the PI, it's a function of the boot-XXXX directories. This is why we encourage updates from ISO. (We need to at some point allow piadm(8) to take a boot-XXXX.tgz + platform-XXXX.tgz to shrink things.)
-
xmerlindanmcd, I need to change the maximum arc usage and passthrough
-
danmcdSo the sample gist above will need you to uncomment some lines for /etc/system, and optionally the path if you don't wanna put them in $BOOTFS/system like I did.
-
danmcds/optionally the path/optionally change the path in the custom\/. file/g
-
xmerlindanmcd, solved ...a simple page in wiki will be appreciated
-
xmerlinthank you