You are not logged in.
Instructions for putting the image on the device are in the README.txt found in the same directory as the images. But I will assume that you already know how to do that, because you did it with Debian. Say a little more about what you did and what doesn't work, and maybe someone will have a solution.
Right. All the mirrors are mirroring packages.devuan.org, which is the original amprolla.
For now, amprolla3 is only on pkgmaster.devuan.org. I think there are a few more details to be worked out before all the mirrors use the amprolla3 repo.
'update-rc.d remove' will remove the symlinks. You do not need to remove the init script. I'm not sure if the symlinks will be regererated with normal updates, but. I just checked, and wicd is still installed here and turned off since I installed the system almost two years ago.
It’s over twice as fast as Firefox from 6 months ago
I think that's right around when i noticed that firefox suddenly became about half as fast (or twice as slow). I think they're pulling a "New Coke". (They added lemon, called it new, waited for complaints, then returned to "original" but replaced sugar with HFCS. The lemon phase was to get you to forget what it really tasted like.)
Last night someone told me that noscript will be ready for FF57 very soon. That's good news.
Here's a bug report. I guess you can ignore the warning.
https://lists.debian.org/deity/2015/10/msg00085.html
Check your version of apt. It's supposed to be fixed in 1.1. Jessie has 1.0.9 and ascii should have 1.4.
dpkg -l apt
Yes, that will work. The part about getting back to udev might be tricky. I'm pretty sure you have to force a downgrade by telling apt which version to install. (apt-get install somepackage=1.2.3)
The 10, 100 and 500 are priority numbers. All except the 500 are there because I pinned those repos at lower priority to prevent accidental install from the wrong repo. However, I haven't actually tested that. I won't share my full sources.list because it would be hazardous for anyone to use it. Including me. It's like that only so I can see what versions are in which release. One of these days I'll need to comment out all but the jessie repos and do another upgrade. Or maybe not - I really want to switch my main system to ascii soon.
Be aware that the version of eudev in that iso has an epoch of 220 in the version. When eudev gets into the main repo (and even when it gets back into experimental again) it will have either no epoch or an epoch of 1. To get any updates, you'll need to do some package manager contortions to downgrade to the newer version with the lower number. I don't have exact instruction, because I haven't tried it yet. If you want some moral support when you decide to do that, look me up in irc (#devuan or #devuan-dev on freenode).
I'll delete those posts from that other thread.
The first one has a different name, the second one is named as you show it. Are you using auto.mirror.devuan.org or pkgmaster.devuan.org?
aptitude search libevent
...
i A libevent-2.0-5 - Asynchronous event notification library
p libevent-2.1-6 - Asynchronous event notification library
...
apt-cache policy libevent-2.0-5
libevent-2.0-5:
Installed: 2.0.21-stable-2+deb8u1
Candidate: 2.0.21-stable-2+deb8u1
Version table:
2.0.21-stable-3 0
100 http://pkgmaster.devuan.org/merged/ ascii/main amd64 Packages
100 http://pkgmaster.devuan.org/merged/ ceres/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ stretch/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ buster/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ sid/main amd64 Packages
*** 2.0.21-stable-2+deb8u1 0
500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 Packages
500 http://auto.mirror.devuan.org/merged/ jessie-security/main amd64 Packages
500 http://debian.csail.mit.edu/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
apt-cache policy libzstd1
libzstd1:
Installed: (none)
Candidate: 1.3.2+dfsg-1
Version table:
1.3.2+dfsg-1 0
100 http://pkgmaster.devuan.org/merged/ ceres/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ buster/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ sid/main amd64 Packages
1.1.2-1 0
100 http://pkgmaster.devuan.org/merged/ ascii/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ stretch/main amd64 Packages
I'm sure there were changes upstream from 1.6 to 1.75 in debian. I think the only changes that devuan made to 1.75 was to remove the dependency on libsystemd0, but it may have been more involved than that. The only way to know for sure what changes were made would be to compare the source code of both packages.
One possible simple solution is to try one of the generic drivers. I think you'll find them at the end of the list of drivers when you're adding a printer in the cups admin. (http://localhost:631)
Right now, all the devs are focused on ascii, so getting changes/fixes in jessie or doing anything with wheezy packages is unlikely to happen. There may be a way to get your printer working by editing some cups config files, but I don't know my way around that enough to even give you a hint.
Looking under /devuan, there doesn't seem to be anything in jessie-proposed-security or jessie-proposed-backports. And there's almost nothing in jessie-proposed-updates - I think it's just an old version of desktop-base. I think it makes sense to use only the /merged sources unless you know there's a particular package in the /devuan sources that you need. (like you're testing a new build for a packager.)
You probably need the netboot files.
https://packages.devuan.org/merged/dist … s/netboot/
https://packages.devuan.org/merged/dist … s/netboot/
NO! Don't do it. (Not sure exactly what the package manager is trying to do there, but it looks bad.)
There's no python3.5 in jessie or jessie backports. You can get 3.4 from the regular jessie repo.
apt-get install python3
Comment out the backports lines and run 'apt-get update' again. Then install python3. If you did a full desktop install, you probably already have it.
If you want to see a list of all the python packages that are installed, run
dpkg -l | grep python
The need for nomodeset is fairly common. It depends on the video card. I got a black screen without it on my old nvidia card and a black screen with it on my new nvidia card.
I looked at refractainstaller-uefi and found some errors. It won't see the mmc drive for the grub selection, but it should see it for /, /home and /boot choices. What does fdisk show for the drive's device name? I would expect something like /dev/mmcblk0p1 for the first partition on the first drive. I'd like to know if I need to change my search pattern. Thanks.
If you want to try a corrected version of the script, I can post it somewhere.
I can think of some other options. When I was adding support for nvme disks in refractainstaller, I didn't have any nvme disks to test it, so I also made it aware of mmc devices. I know it sees them and displays them as choices for partitions/drives, but I've never tested an actual install to one. Nothing here will boot from mmc. So there are a couple of options for using that installer.
1. Try the devuan desktop-live uefi iso. It's jessie, but since the installer will see your drive, it might work.
https://files.devuan.org/devuan_jessie/desktop-live/
2. Try a refracta iso with the same installer.
Those are here - https://sourceforge.net/projects/refrac … isohybrid/
3. If you really do need a newer kernel, I made a devuan desktop-live iso with 4.9 kernel from backports.
That's here - http://distro.ibiblio.org/refracta/files/experimental/
Also in that same directory is ascii with openrc and eudev. That one is more experimental and was made for testing purposes. It's probably not your best choice.
4. Try a refracta-ascii no-X iso - https://sourceforge.net/projects/refrac … s/testing/
That one has the same installer, cli version. It's labeled as pre-alpha, but keep in mind that ascii is based on stretch, so it's really pretty stable. Refracta is a re-spin of Devuan and uses Devuan repositories for packages.
5. Use a refracta iso to do a debootstrap install of ascii.
In Debian and Devuan (and many other derivatives), runlevels 2-5 are the same.
To disable wicd in all runlevels:
update-rc.d -f wicd remove
To reverse the above:
update-rc.d wicd defaults
Another way to do it is to install sysv-rc-conf and un-check all runlevels on the wicd line. (use arrow keys and space bar)
Are you gonna show us your script? How do you get the window to stay up when you make a selection?
apt-get install hddtemp libxfcegui4-4 ristretto xfce4-artwork xfce4-battery-plugin...
and any other packages from the autoremoval list that you want to keep. They will then be marked as manually installed.
Those libraries are only jessie. Find out why they are there.
aptitude why libgnutls-deb0-28
Maybe apt can fix the breakage...
apt-get -f install
or re-run the dist-upgrade. (I had to do that on a couple of jessie to ascii upgrades.)
Maybe tell apt which chromium you want.
apt-get install chromium=62.0.3202.89-1~deb9u1
xclock is part of x11-apps, which has other cool stuff like xeyes and xcalc. That's just there to have something non-essential to kill. Break the line up into multiple lines, and it will make more sense. The numbers set the exit code for each button, the ans="$?" stores the exit code, then you test to see which action to perform based on the exit code.
xclock &
yad --button="Kill panel":0 --button="Say hello":1 ; ans="$?" ; if [[ $ans = 0 ]] ; then killall xclock ; elif [[ $ans = 1 ]] ; then echo "Hi" ; else echo "Bye" ; fi
The second way is easier. The first way should work, but I can never do it correctly.
The devuan live isos are made with live-config and live-boot, same as debian, so the options are the same.
One thing different from the debian-live isos - the current (jessie) devuan-live isos have a pre-configured user, so you should not use "config" or "components" (live-config or live-components) on the command line. If you do use that option, you will only get the components that you named. (i.e. you must name every component that you want. See /var/log/live/config during a live session. That will show you which ones were used.)
If you use the hookscript, it will create a file, /etc/profile.d/zz_locale.sh (or maybe tt_locale.sh) which will contain:
export LANG=fr_FR.UTF-8
export LC_ALL=fr_FR.UTF-8
Every user on the system will get French. If you want only one user to have French, remove that file and put those lines in ~/.profile for that user.
I've seen that happen, but I don't know what causes it. It hasn't happened in a long time. Tell me more about your setup. Is there another OS installed? Did you start with a new hard drive with nothing on it? How did you partition it?
And are you the same person who was telling me about this in irc a couple days ago?
Yes, devuan is following debian releases. Most of the packages in devuan are unchanged from debian. The plan is to change as little as possible to provide a debian-based system without systemd.