lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
_sfo has joined #armbian-rockchip
<DC-IRC>
<Robin> @rpardini that's correct, no?
<DC-IRC>
<Robin> I mean, I even replaced the files in the build itself...
<DC-IRC>
<rpardini> Yeah. I'm not sure why any of this wouldn't work. If you do it on a live board, does it work?
<DC-IRC>
<Robin> On a live board, the images are correct. Let me rebuild that boot thing one sec
<DC-IRC>
<Robin> Jep... then it works
<DC-IRC>
<Robin> HMM
<DC-IRC>
<Robin> I bet it's the `update-initramfs` that isn't working
<DC-IRC>
<rpardini> that's why I asked "did you regen initrd".
<DC-IRC>
<Robin> Well, yeah, in that build 😅
<DC-IRC>
<Robin> not on the "live" thing
<DC-IRC>
<Robin> But `update-initramfs -u` should work just fine, no?
<DC-IRC>
<Robin> (on the build)-
<DC-IRC>
<rpardini> if you're doing this in customize.sh -- it might not, things are not yet setup then.
<DC-IRC>
<Robin> left is the build (customize.sh) and right is running that build
<DC-IRC>
<Robin> If it's not possible to do this, what can I do to achieve the same result?
<DC-IRC>
<rpardini> I'm not even sure wth. it might be build does stuff after customize that breaks it, or, the opposite, something's missing. you'll have to investigate. try with `DEBUG=yes SHARE_LOG=yes` and search the logs for evidences...
<DC-IRC>
<rpardini> I've recently had nightmares with GRUB wallpaper/logo, where subtle differences between Debian and Ubuntu, FAT32 boot, etc made the thing work or not. (I've temporarily given up lest I lose my sanity).
<DC-IRC>
<Robin> Well, I've lost myself already here.... A client really wants this to work, so if it would witk with some hack, I'd be really happe 😅
<DC-IRC>
<IgorPec> become our client and you will be treated as deserved
<DC-IRC>
<IgorPec> this is open source, spent a weekend studying the code
<DC-IRC>
<rpardini> no idea what your customize.sh does (I should include a dump of its contents in the log), but looks like you're installing half the world in there.
<DC-IRC>
<rpardini> Try to reduce this to the minimum necessary to demonstrate the problem.
<DC-IRC>
<rpardini> Either way, initrd is built much after all this, and it's hitting a cache. Try zapping `cache/initrd` and rebuild and see.
<DC-IRC>
<Werner> I vote strongly against that not do that since it could contain sensitive data.
<DC-IRC>
<Tonymac32> I believe Werner is referring to dumping customize.sh in log, I agree. That would be the "special sauce" for anyone using Armbian in any serious capacity.
<DC-IRC>
<rpardini> Yeah well the log might be full of sensitive data anyway -- it's the user's decision to share or not.
<DC-IRC>
<Robin> There is no sensitive data in the log for me. Since I just install a bunch of base packages (to speed up provisioning) and then the provisioning itself hapens via Salt
<DC-IRC>
<rpardini> Yep but it would be easy to imagine you could have a Salt master key or some such secret in there.
<DC-IRC>
<Werner> Yeah. Secrets shared by accident can happen fast
<DC-IRC>
<rpardini> My point is: if you SHARE_LOG=yes secrets might leak, that's why it isn't enabled by default.
<DC-IRC>
<rpardini> Including the customize.sh script body in there does increase that chance, but helping someone customizing sans-secrets without it is very hard.
<DC-IRC>
<Werner> Fully understandable. However in that case it is the questioners due to provide such information. If they refuse their problem, not ours.