DeadlineX

Oh, That's a thought! I didn't try such option. Will do it. What I have now: I've created both /var/log/v2ray and /var/log.hdd/v2ray sub-directories. As a result, both of them survive shrinking. What is most interesting, V2ray starts to write to /var//log/v2ray, though '/var/log.hdd/v2ray" is set in the config, as the log directory. After few seconds (or tens of seconds) it stops to write lod there and starts to write to "log.hdd". I'm puzzled. But of course this is not your script problem, as I believe. As for "journal" missing, please look at the screenshot attached. This is an obvious mistake. In fact we have a link instead of the real directory, and have nothing instead of link. You see the "log.hdd" sub-directory. And once again, everything is OK in the partition before SD card insertion into the boot slot. I.e. we have directory in the "log.hdd" and the link to it in the "log". Also, I'd like to ask, if there is an option do not show all those fast scrolling lines during the process.

Hi, I've found a problem. I've installed V2Ray, and assigned its logs to /var/log.hdd/v2ray/. This sub-directory is missing in the image file, so V2Ray hangs on startup. Is there any way to add this (or any other) sub-directory to the image file explicitly? I only see explicit exceptions file. Or should I customize the script myself? Thank you. P.S. Further investigations show, that /var/log.hdd/v2ray exists on the written SD (when root is ~1,8 GB) yet before SD insertion into the slot and reboot. But after image shrinking this sub-directory is absent. Moreover, /var/log/journal (which is a link to /var/log.hdd/journal sub-directory), also is absent in the shrunk partition. I used -az option for image creation. -a option leads to the same result.

Hi, It is very hard to start OS (community version, downloaded from here). The system doesn't start at all, if the keyboard is already attached. I've discovered some magic moment during the startup process, when I can attach keyboard and system goes further. In most of moments the boot process stops, as soon as I'm attaching the keyboard. Lines are scrolled too fast to let me note what moment is "successful". Also I've noticed that the chip is very hot, when the keyboard is attached. It's much colder when keyboard is detached. Another small issue is that functional keys don't work. Though Ctrl/Alt and other similar keys do. My keyboard is an "aluminum" Apple keyboard. Didn't try other. Also I wonder if there is any way to change screen resolution for console. It looks like environment setting doesn't take effect. Only 1920x1080 resolution works. It's not so suitable for me.