You are not logged in.
Only a Mate file is in there. Any other ideas?
MiyoLinux wrote:
Yes, change those lines so that they look like this...default_user ron # Set to "yes" to enable this feature focus_password yes
Great. This worked! But still have the very long login time. Is there anything I can check or do about it to help?
Thanks MiyoLinux. Your fix for sudo worked. Also your login screen workaround also worked. But I would really like to just be prompted for my password. I noticed in slim.conf these 3 lines:
#default_user miyo
# Set to "yes" to enable this feature
#focus_password noIf I change miyo to ron and change no to yes, would that get me what I want?
Also, I made a mistake saying boot time. I meant login time. From the time I enter my password and hit enter, it takes 27 seconds to log in. However, I notice that if I giggle the mouse while I'm waiting that that speeds up the login.
Also I should mention that I installed the Mate desktop and uninstalled openbox, all things Xfce, and the other thing I can't remember, I think it ends in "fm." I did the same thing in Jessie and had no problems.
Just installed the new release (along side of Jessie and Mint). I'm having a couple of problems. The first thing is that boot time is way slow compared to Jessie's boot time. The other problem (to me it is a problem) is the login screen. Unlike Jessie where my user name is already selected, and I only have to type in my password, Ascii requires me to type in my user name, and then my password. I know this may seem trivial, but before I tried Miyo I tried two other distros that behaved the same; not having to type in my user name for login was a very big reason I went with Miyo. (It seems superfluous to have to type it in when there's only one user account.)
Another problem I don't think has to do with Ascii is that I'm trying to run Pale Moon's browser installer script and when it asks me for my password I get an error message. It says make sure this user has sudo rights, or something like that. My password works for Synaptic so I don't know why it doesn't work for this.
MiyoLinux wrote:
Then I'd recommend putting the # back on the backports repo.
I can't remember if I put them back. Should it look like this:
# jessie-backports
#deb http://auto.mirror.devuan.org/merged jessie-backports main
#deb-src http://auto.mirror.devuan.org/merged jessie-backports mainor just this:
# jessie-backports
deb http://auto.mirror.devuan.org/merged jessie-backports main
deb-src http://auto.mirror.devuan.org/merged jessie-backports mainAnother question, if I disable the backports then won't I not be offered an update on the new kernel when one is released?
Thanks guys. I marked as solved.
2. I really want to know why your anacrontab doesn't read:
1 8 automatic.trim /sbin/fstrim --all || true
Also, what's the rationale behind keeping the " || true" statement?
You mean I really don't even need the trim script file?
As for the || true, I have no idea. I kept the file exactly the same as it was in Mint. Also, thanks for the tip in #1, and your link in your previous post.
And before I forget, many thanks to both siva and GNUser. I'm getting closer to ditching Mint and going with Miyo full-time.
Okay, I think it's finally working in a way I can understand. First, I delete the trim file out of the /etc/cron.daily folder (and kept the one in my Documents folder). Then I went back to the anacron file in /etc and added this:
1 8 automatic.trim /bin/bash /home/ron/Documents/trim
I changed 10 minutes to 8 and using your suggestion named it automatic.trim. Rebooted and ran sudo cat /var/log/syslog | grep anacron and got this on one line:
May 1 19:06:28 localhost anacron[1661]: Will run job `automatic.trim' in 8 min.Finally, checked that the log file automatic.trim exists, opened it up and found this: 20180501.
So, can I finally consider this as SOLVED? ![]()
Okay, one thing I just realized in looking at the anacrontab file in /etc. There is the following line:
1 5 cron.daily run-parts --report /etc/cron.daily
I had previously put the script trim in /etc/cron.daily (and it's still there) so does that mean that trim ran?
I just finished all the steps you gave me. It appears to have worked but I have one question. When I ran sudo cat /var/log/syslog | grep anacron I got this:
May 1 18:09:38 localhost anacron[1659]: Anacron 2.3 started on 2018-05-01
May 1 18:09:38 localhost anacron[1659]: Will run job `cron.daily' in 5 min.
May 1 18:09:38 localhost anacron[1659]: Will run job `cron.weekly' in 10 min.
May 1 18:09:38 localhost anacron[1659]: Will run job `cron.monthly' in 15 min.
May 1 18:09:38 localhost anacron[1659]: Jobs will be executed sequentiallyAny idea why it says the daily cron will run in 5 minutes when it's set for 10?
EDIT: I think I know what happened. After installing anacron, I should have went back to re-add the line
1 10 example.daily /bin/bash /home/ron/Documents/trim. I'm going back to add it again and retry everything. It should work this time!
GNUser wrote:
Would you kindly share the contents of that file?
#!/bin/sh
# trim all mounted file systems which support it
/sbin/fstrim --all || truesiva wrote:
A) which program
B) find / -iname *program*
which anacron returned nothing while almost every line from find / -iname anacron ended with Permission denied.
siva wrote:
To reiterate, I'm not sure why you're pointing cron to a script that runs a simple command. I would use a script if there were a series of lines.
If I had to do it manually, I'd probably forget about it.
One thing I'm wondering about, can I turn this script into an .sh file that will run when I click on it?
Okay, I think I got a handle on this. I added the following line to /etc/anacrontab:
@daily 10 example.daily /bin/bash /home/ron/Documents/trimand made sure I copied the trim script into my Documents folder. Is that all there is to it? Once again, thanks for helping.
FTR, I'm just an average desktop user that regularly powers off (no hibernation/suspend).
EDIT: I just checked out the link in GNUser's post, and I don't have an anacron file in /usr/sbin, just a link. Does that mean anacron isn't working?
So taking everything that has been said and done in this thread, I gather that I may place the trim script file in /etc/cron.daily and it will do its job?
golinux wrote:
Not that it would make a difference but are you aware that sudo is not enabled by default in Devuan?
Maybe the Miyo guys enable it? I've never gotten an error message, I get a prompt for my password. Also I have used sudo to open read only files.
siva wrote:
Also, I have no idea why you didn't just run: /sbin/fstrim --all || true directly in a root shell.
I ran it in the terminal but got this:
fstrim: /: FITRIM ioctl failed: Operation not permittedThen I added sudo in front of it, and after putting in my password there was a brief pause, then "ron@miyolinux:~$" came back. So does that mean it worked? I rebooted and all seems well (so far).
Also, I want to thank everyone for taking the time to help me out with this things. I appreciate it much. I'm determined to become "systemd free."
siva wrote:
Have you ran this command in devuan yet (not as a cron job, just a command)?
I tried two ways, but can't get it to run right. First I just doubled clicked the file but it didn't run, it just opened up in my text editor. Then I tried pasting the path to it in the terminal and got this:
bash: /home/ron/Desktop/trim: Permission deniedThen I added sudo before the path and got this:
sudo: bash:: command not foundI'm starting to feel a little dumb. ![]()
Thanks MiyoLinux. That worked!
siva wrote:
If all you want is to know how to set up the cron job, then figure out which cron application your version of Mint uses first. In devuan, you can either...
a) learn the cron version and syntax that miyo uses and create a new job for your needs; or,
b) if you really want, and if it's in the devuan repos, use the version of cron that Mint ships. Just try to understand that you may end up setting up more than anticipated if it's not a miyo default.
Here's what I found in Mint:
Package: cron Version: 3.0pl1-128ubuntu2
and
Package: anacron Version: 2.3-23
I'm assuming that by default Mint uses the Ubuntu cron.
siva wrote:
I am assuming you understand what this command does and why.
Just that it runs a trim job, whatever that is. Anything beyond that is gooblygook to me.
Will the time ever come where systemd will become an even bigger entwined mess (than it is now) that Devuan would simply have to no longer be based on Debian, but become completely independent? Or for any other reason? I'm mostly just asking for curiosity's sake. ![]()
I successfully added the backports, but when I mark the kernel for installation I get this error message:
linux-image-4.9.0-0.bpo.6-amd64:
Depends: linux-base (>=4.3~) but 3.5 is to be installedIf I have the backport enabled, why am I not being offered an updated linux-base version?
Thanks MiyoLinux. I did some research and found this below on debian's site. Is this what I need to do on Miyo/Devuan to get the backports? Also I'm a bit confused, would it go in the file sources.list found in /etc/apt or would it go in the file devuan.list in /etc/apt/sources.list.d? Thanks for your help.
1. For jessie add this line
deb http://ftp.debian.org/debian jessie-backports main
to your sources.list (or add a new file with the ".list" extension to /etc/apt/sources.list.d/)
2. Run apt-get updateFirst, I'm assuming that everything I see in Synaptic comes from the Devuan repos; is that correct? My main question is what is the newest available kernel? The newest one I see is 3.16.0-5. Is that right? The number seems kind of low to me. Is this kernel patched for the Meltdown/Spectre flaws?
Another question I have is that I have both 3.16.0-4 and 3.16.0-5 installed. Does Miyo automatically boot into the newest kernel? I don't get any prompt on boot-up asking me which kernel I want to boot into. uname -r shows 3.16.0-5 so I assume that's the case. If I ever needed to boot into an older kernel, how would I go about that?
Thanks!
siva wrote:
@Ron: to your original question, I'm curious what doesn't work. Are you saying the file /etc/cron.weekly/fstrim doesn't exist?
Yes.
siva wrote:
It may be helpful to copy and paste the file /etc/cron.weekly/fstrim (from your mint system) into this conversation . . .
How do I attach a file to this forum? I don't see a way. Here's the text of the file:
#!/bin/sh
# trim all mounted file systems which support it
/sbin/fstrim --all || trueI would like to set the script file fstrim to daily. In Mint I use this command: sudo mv -v /etc/cron.weekly/fstrim /etc/cron.daily
but this doesn't work in Miyo. How do I set this in Miyo? Can I just copy the fstrim file from Mint over to Miyo?
MiyoLinux wrote:
thank you for pointing this out! I'll fix the file on Sourceforge.
You're welcome, and thanks for the fix!
I hope this is the proper place to report this. The checksums for the file Miyo-XTRA-Jessie-64bit-20180120.iso do not match. I've downloaded the file three different times and I keep getting the following sums:
md5 587675f6947aa086394085488844ae72
sha 256 6c6c214b09fef868ee49e1c0df6915afc827756d803821a7aa6878463e1c15e2On the checksum file they are listed as:
649ca81770ece7e7b8aa85bfeeabf3d7 - md5sum
472448b24b65488791a9ffba5a8f6f8e0df8ec0e962d2fc5f15d60882d4d06b7 - sha256sum
Is this just a mistake on the checksum file, I hope?