Hi Ron! Thanks for the feedback.

Boot Time:

I'm not sure why your boot-time is slow. It's lightning fast for me...on both 64 and 32 bit versions...about 8 - 10 seconds from the time it leaves GRUB until the Login screen appears. How long is it taking for you?
____________________________________________________

Pale Moon:

Synaptic opens with your password, because I changed the command for its desktop file. Openbox is a bit of a different beast. Make sure to read the Miscellaneous Notes (in the Release Notes) about any other applications that you may install that require elevated privileges.

I don't use Pale Moon myself; however, during installation, did you put a check mark on the box to give you sudo rights? If so, did you also put a check mark on the box to use sudo as default? If you're not sure, let's make sure you have sudo rights.

1. Open your terminal, and enter the following command...

su

Hit Enter on your computer, and enter your root password.

2. Now, enter the following command in the terminal...

EDITOR=leafpad visudo

When the file opens, scroll down until you see the following line...

%sudo    ALL=(ALL:ALL) ALL

3. Immediately beneath that line, enter the following...(I will assume that your username is ron. If not replace ron with your actual username in all lower case letters.)

ron  ALL=(ALL:ALL) ALL

4. Save the file. Close it. Reboot.
_____________________________________________________

The Login Screen...

With this release, I changed over to Slim to help with resource usage. With LightDM, I could set that so that it would automatically show the User's name on the Login Screen after installation. That's not possible (for me to do it) with Slim...or if it is possible, I don't know how to do it.

HOWEVER, if you want your name to automatically show on the login screen...

1. Open your terminal, and enter the following command...

sudo leafpad /etc/slim.conf

When the file opens, scroll down until you see the following lines...they are close to the bottom of the file...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
# default_user miyo

2. Remove the # from the third line, and replace miyo with your username (use all lower case letters). So those lines will now look like this...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user ron

3. Save the file, close it, then reboot.

Your name will then appear (in all lowercase letters) on the login screen...allowing you to just hit Enter there...then type in your password...and hit Enter again.

Hope all that helped and made sense.

United States.

I'm a Southern Boy...live in the state of Georgia. Hope to move to Florida. May move to Alabama for a new job.

I'm an indecisive American.

Hi Ron! You can just leave the "deb" line uncommented (without the #). Unless you're planning on building something from source, you can put the # in front of the "deb-src" repos.

Sometimes I forget and give advice about my personal preferences. I never use backports myself, so I always leave them commented out.

As I said, unless you plan to build something from source, this is my recommendation for how it should look...

# jessie-backports
deb http://auto.mirror.devuan.org/merged jessie-backports main
#deb-src http://auto.mirror.devuan.org/merged jessie-backports main

If you plan to build from source, then leave it as...

# jessie-backports
deb http://auto.mirror.devuan.org/merged jessie-backports main
deb-src http://auto.mirror.devuan.org/merged jessie-backports main

Hope that helps!

I realize that this won't reach everyone...still, I want to say it.

For several days now, I've been trying to upload new releases to SourceForge; however, my internet hasn't been reliable, and it has lost the connection each time that I've tried to upload...wired and wireless. As a result, there have been "new releases" posted on Sourceforge that are only partial .isos. Though I've tried to delete them as soon as possible; unfortunately, there have been a few downloads of those partial .isos.

I apologize for any inconvenience this may have caused anyone...

I'm still trying to get them uploaded.

Sorry siva...I wasn't ignoring your post. I just saw it now for the first time...not sure how I missed it yesterday.

No, I wasn't joking. In trying not to muddy the waters, I was simply giving the "official" reason as to why 3.16 won't be patched as stated by Debian (in the link I provided)...since Devuan's kernel comes from Debian.

For those times when you and that special someone just need time to reflect...

https://www.youtube.com/watch?v=X2WH8mHJnhM

HOORAY!!!

Oh dear...yes, I forgot that you will need to install the linux-base from backports too. I'm sorry. Try this from your terminal...

sudo apt-get -t jessie-backports install linux-base linux-image-4.9.0-0.bpo.6-amd64

Yes, everything is Devuan repos.

The 3.16 kernel is older, but it's the LTS kernel...so it's tried, tested, and stable...and will continue being supported for two more years.

If you enable the backports repository, you can install a newer kernel from backports.

If you ever need to boot an older kernel...

When you turn on the computer and reach the grub screen, use your "down arrow" key to highlight "Advanced options for...", then use the arrow key again to highlight an older kernel and hit Enter on your keyboard.

To my knowledge, there have been no patches for meltdown and spectre in kernel 3.16, because it's believed that 3.16 isn't affected...

https://wiki.debian.org/DebianSecurity/SpectreMeltdown

I'm a bit handicapped since I don't have a 64 bit laptop to test this on...sorry.

Still, I tried it on my desktop to see what might happen (if that did any good), but I didn't experience the freeze. I clicked back and forth between on and off several times. Then I tried it on my 32 bit laptop. I never experienced the freeze on it. So, I'm not sure what the issue could be.

There is one issue that I'm aware of, but I'm attributing it to the fact that Ascii still isn't considered "stable" at this point. When editing a configuration file (or any file), if you close the file first and then choose the Save option...periodically, there are times when the system will freeze. However, if you Save the document first and then close it, I haven't experienced a freeze at all. Not sure what that's about.

If you do experience a freeze, open the right-click menu, and go to...

Openbox > Openbox > Restart Openbox

That has worked in "un-freezing" the system, and the document that I edited (which caused the freeze) was saved with the edits.

I'll try to see if I can figure anything out further.

Thanks for the feedback! Thanks Mke!

Well...guess I was wrong about the 64 bit booting up at 101 MBs of RAM...it's climbed all the way up to 102...   LOLOLOLOL!!!

Click to enlarge.

If anyone has installed this on a computer with wireless, please let me know if you experienced a pause in the boot sequence (while it was searching for eth0) after installation. As I mentioned, I'm almost sure that I fixed it so that it doesn't have that pause, but I can't test it myself. Thank you.

Sometime later this week, I will "hopefully" be posting links for .isos for the "normal" MiyoLinux based on Ascii...by normal, I mean they are Openbox only...no panel switcher. These will be "testing" .isos. I've pretty much gotten rid of the bugs, but I'm still working on the delay during the boot sequence (AFTER installation); in which, there is a delay while it's searching for a connection to eth0 if a user is using a wireless network. The fix is quick and easy after installation, but I wish I could head it off at the pass so that users don't have to take care of it themselves. Nothing I've tried up to this point has stopped it.

The .isos will contain all of the MiyoLinux accessories (except for the panel switcher). There has also been a few changes to make the system a little lighter. On my test machines, the 32 bit boots up at 68 MBs of RAM, and the 64 bit boots up at 101 MBs of RAM (your usage may vary)...not all machines are created equally. LOLOLOL!!!

My preemptive thanks to anyone who may try these out when I make them available.