Porteus

Yes, UUID is a foreign concept, especially for someone coming from Windows. Like brokenman, I have several partitions without labels on them. Here, we're looking at one script for one person's specific task, and I think UUID can be reasonably explained for that purpose. Another way to approach this ...

Well, I looked back at the timeconfig app and turns out I'm about as confused as usual, and taking so much time off didn't help. I did write it such that you couldn't select localtime and a timezone, and then we found out that it messed with a couple apps (seamonkey mail and an astronomy program tha...

Select UTC there and Porteus will then match up with Nemesis (as configured with timezone in your .profile) You should not be allowed to select both localtime and a timezone, I thought I wrote it such that the time zones were greyed out when localtime was selected. I'll look into that next time I ca...

Ed, In standard Porteus, please look at /etc/hardwareclock If the uncommented line is "localtime" then your Porteus install is not correctly configured. You should only use a timezone if your /etc/hardwareclock is set to UTC. I suspect that is what is going on based on the date outputs you gave. I u...

From the computer's standpoint, time travel actual does occur! I recall one time I downloaded sources to compile XFCE immediately after they were released. I was unable to compile the sources because the files were timestamped, from my system's standpoint, in the future! IIRC, GCC spit out a ton of ...

Hi Ed, What other OS's are you running? If it's Porteus, are you running with a timezone set? Does the clock continue to advance 5 hours on every subsequent boot of Nemesis, i.e. it's Noon in New York, you boot into Nemesis and your clock says it's 5pm; then you reboot into Porteus and it shows 5pm,...

Yep. And if his hard drive and/or flash drive will remain the same physical piece of hardware but might change letters (sdb instead of sda, etc) you can query the uuid out of blkid: #must be set manually by user BOOTUUID=ba155345-b858-4c96-9e21-13ba3ce84708 BOOTDEV=`blkid|grep $BOOTUUID|cut -d ':' -...

It appears to me that in Arch, the clock is set through (drumroll, please) systemd. You can use "timedatectl" to set the clock, see https://wiki.archlinux.org/index.php/Time Slackware based systems use "localtime" by default, meaning that the system clock matches the time of the hardware clock, with...

Are you looking to do this on one computer (only) where it will always be the same USB drive and the same hard drive (assuming F:\ is a hard drive?) or do you need something that will work using multiple USB drives on multiple computers? This will be relatively straightforward if it's only for one U...

@brokenman, I still haven't delved into how to get cliexec commands to have visible output on the screen while systemd is running the show, maybe I'll tackle that next. to get guiexec working, all you need to do is copy /opt/porteus-scripts/xorg/gui-autostart into your tree from standard Porteus (I ...

@beny Open a terminal and type the command 'halt'. Enter your password if you are not already root. The system will go through the entire shutdown process then hang right as it is supposed to turn off. If you use the command "poweroff", "reboot", or if you shutdown through the gui buttons, this hang...

@brokenman, systemctl commands don't affect my shutdown hangs, I've only experienced them at the very end of shutdown after the handoff back to /mnt/live/shutdown. I re-downloaded the iso and have tried it in vbox as well, with the same result, it still seems related to the halt command not executin...

@francois, I neglected to mention you must make the cheatcodes.sh script executable. Also double check after boot-up that the symlink is present in /etc/systemd/system/multi-user.target.wants When working this edits lxdm.conf to specify the user passed through the cheatcode. Editing lxdm.conf does h...

Merci beaucoup, Francois! Good to hear from you, my friend :) My system appears to hang on shutdown at the very tail end, and it occurs when I use the 'halt' command. Things work great with 'reboot' and 'poweroff'. I don't imagine this is a busybox problem...? Maybe it has to do with how systemd is ...

Sure thing....figuring out how to implement cheatcodes at the right time during systemd startup seems like a bit of a chore, but I imagine it will get easier with time and experience. I'm getting the dbus (?) error with 'su' as others mentioned in previous posts and tried to see if I could figure th...