khoaofgod

Basically, with go File, after each reboot, we successful comment out the ca::ctrlaltdel already. Also, the udev file created successful after each reboot. but after login into Unraid UI, CTRL ALT DEL still working and reboot the UI... Grugurgurgu I give up then

thanks bro, I did everything you said, also the append kernel, and verified the /etc/inittab already have # to comment out the ca ctrl alt del combo, but reboot is fine also, but it just not work.... sad

I put some code to disable ctrl alt del on config/go file # Disable ctrl-alt-del on Unraid host sed -i 's/ca::ctrlaltdel/# ca::ctrlaltdel/' /etc/inittab /sbin/telinit q /sbin/init q After reboot, I open terminal and verify the file, I already see "/etc/inittab got comment out # the line" However, CTRL ALT DEL still reboot unraid UI , I tried both telinit q, init q and both of them, but no use. Am I do something wrong? I want to disable the CTRL ALT DEL. ( And please dont tell me pass USB Input to VM. I just want to disable the CTRL ALT DEL )

Hi there, I'm new, I have 4 disks and 1 parity enabled. I have a couple questions, hope you guys know and answer me: 1. Will WRITE directly to /mnt/disk1/share /mnt/disk2/share .. etc have Parity Protected? Or just /mnt/user/share have partity protected? Because I see when I do dd write test, direct to disk is much faster than go with many layouts of /mnt/user 2. The disk3 is an nvme, and Partity1 is SATA. Will READ Speed of /mnt/user/share be the speed of NVME, or will it limited to read speed of the SATA? Because when I test with dd, read from direct disk nvme is also aster than a lot compare to /mnt/user/share Thanks guys