You are not logged in.
If /dev/sda15 contains an encrypted filesystem, then fsck should not be trying to check it. Instead, it should be checking the decrypted filesystem, which would be /dev/mapper/sda15_crypt or some other label.
What's in your /etc/fstab and your /etc/crypttab?
What's the output of blkid?
Is devuan the only operating system on the computer?
Don't use debian mirrors in your sources.list (or in synaptic). Only use devuan.
Make sure you have non-free repos enabled.
Update (Reload? I forget what it says in synaptic)
Install firmware-iwlwifi
That one usually works for me without a reboot. Usually.
Wasn't that fixed a year ago?
https://security-tracker.debian.org/tra … -2016-5195
I've heard a few other people who had trouble with rufus. Try rawrite:
http://www.netbsd.org/~martin/rawrite32/
The wireless firmware package that you need is already installed in the live isos. What error message did you get, and what did you do to get that message?
Can you use a wire for the install instead of wireless? Sometimes it's easier to set up the wireless after you get the system installed.
Yeah, I see this frequently. I use pmount/pumount for removables. I think I get leftover directories under /media when I pull the usb out without unmounting it. It might be something else I'm doing, too. When it happens, I just delete the dir (as root.)
I just ran into this doing a debootstrap install of ascii. Here's a way around it. The needed packages are in ascii-proposed. When they move into the main ascii repo, this will no longer be a problem.
In chroot: add the following line to /etc/apt/sources.list (note that it's /devuan not /merged like the others.)
deb http://pkgmaster.devuan.org/devuan/ ascii-proposed mainThen run
apt-get update
apt-get -t ascii-proposed install util-linux libfdisk1Then you can install other things. I have no idea what's missing in your system now. I had to do the above before I could install the kernel. You probably need to run upgrade and dist-upgrade again, maybe apt --fix-missing, or maybe you'll get other instructions.
You probably should have come here before anwering Yes to that. To fix it, you can boot a live CD or usb, chroot into the installed system and re-install or do whatever to get those packages back. There's not enough information in your post to know what caused the problem. How was that system different from the others you upgraded?
I have a partial answer to the original dilemma. I made a live usb of devuan ascii (and udev), with persistence. There's no 70-persistent-net.rules in the live isos by design, and there's none in my ascii anyway. Normally (jessie and older) with persistence, the one that gets created at boot sticks around, and you have to either delete it or change your settings to eth1, 2... or wlan1, 2 (I think I've gone up to 8 in the past.)
This particular system has wicd on it, and there are settings for default wired and wireless interfaces. They're set to eth0 and wlan0. I added net.ifnames=0 so that the old names will be used.
Booted one laptop and was automatically connected with the wire. Wicd saw the nearby wireless signals.
Booted another laptop and was automatically connected. Wicd worked, too.
In both cases, the only interfaces were eth0 and wlan0. They did not increment.
Explanation: Hand-waving-argument, magic. I don't know. But I think you'll be ok when you move your system to different hardware.
Bug me in a couple of weeks to see if I tried it with eudev yet.
Anybody hear of anyone re-compiling quantum with ALSA support (disable dependency on Pulse)?
Paging FSR.......;)
I think you overestimate my abilities. I've heard some talk about recompiling for alsa, and also that packaging firefox is difficult. After a quick look at the source package, I believe it. Doesn't apulse work anymore?
BTW, noscript is ready for 57. Support for noscript in firefox-esr52 will continue until June, when it will shift to 59.
https://noscript.net/getit
Huh? What's missing? What extra stuff is disturbing you? I never noticed a difference.
To enable multi-arch:
dpkg --add-architecture i386Then you should be able to install the i386 versions of packages.
I ran into similar problems when I tried to use my conkyrc from jessie on a new ascii install.
Add conky.config = {and put the rest in braces}
Add a space after the =
Add a comma at the end of each line except the last.
Values go in single quotes, booleans don't.
Do that much, and you'll probably get rid of most of the errors. Some of the options may have changed. Here's what's working for me:
conky.config = {
alignment = 'bottom_left',
background = true,
border_width = 1,
cpu_avg_samples = 2,
default_color = 'white',
default_outline_color = 'white',
default_shade_color = 'white',
draw_borders = false,
draw_graph_borders = true,
draw_outline = false,
draw_shades = false,
use_xft = true,
font = 'DejaVu Sans Mono:size=10',
gap_x = 4,
gap_y = 4,
minimum_height = 5,
minimum_width = 10,
maximum_width = 366,
net_avg_samples = 2,
no_buffers = true,
out_to_console = false,
out_to_stderr = false,
extra_newline = false,
own_window = true,
own_window_class = 'Conky',
own_window_type = 'desktop',
own_window_transparent = true,
stippled_borders = 0,
update_interval = 1.0,
uppercase = false,
use_spacer = 'none',
show_graph_scale = false,
show_graph_range = false
}It's safer if you use codenames. Use "jessie" instead of "stable" and "ascii" rather than "testing." When ascii becomes the stable release, you can change sources.list to say "ascii" instead of "jessie." That way, you get to decide when you do the dist-upgrade instead of running into it when it happens.
To see what driver is in use, look in /var/log/Xorg.0.log or run 'lspci -k'.
To select which driver to use, create /etc/X11/xorg.conf with a Device section, where you list which driver to use.
For detailed instructions on configuration, look at debian. It's done the same way in devuan.
I call it the s/f rario, signal to fluff. Only I include a level of doubt that not all fluff is innocent, and not all sheep is vegetarian. I see sheep with sharp front teeth and saliva dripping.
I know we're drifting off topic here, but this is relevant to the drift and potentially very important:
https://yro.slashdot.org/story/17/11/20 … -keystroke
@golinux: I like the greens better than the roots.
Translation: Too much javascript.
(fungus obviously has a lower threshold than my limit of 4-5 allowances. I could see it fine once I unlocked a few doors.)
All the installer isos must be used with auto.mirror.devuan.org (or some-country-code.mirror.devuan.org or packages.devuan.org). They do not have the signing key for amprolla3 (pkgmaster.devuan.org). If/when there's a point-release of jessie, that situation will be remedied.
It looks like you could just replace the systemd commands with non-systemd commands. I don't know i3. How does it handle running those commands as root? Or does user have privilege for the shutdown and reboot commands? For hibernate and suspend, you can use 'pm-hibernate' and 'pm-suspend'.
Whenever I use a window manager without a diplay manager, I give my user sudo nopasswd permission for those commands.
It's also possible to let dbus manage the session, and then you can use dbus commands for shutdown, etc. I think that's been discussed somewhere on this forum. If you need that and can't find it, just say so.
This looks like the easy solution. No idea here if it works. (Note: Tags to put this in a code box are right above the message text box when you're composing.)
#!/bin/sh
lock() {
i3lock
}
case "$1" in
lock)
lock
;;
logout)
i3-msg exit
;;
suspend)
lock && pm-suspend
;;
hibernate)
lock && pm-hibernate
;;
reboot)
reboot
;;
shutdown)
poweroff
;;
*)
echo "Usage: $0 {lock|logout|suspend|hibernate|reboot|shutdown}"
exit 2
esac
exit 0Instructions 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 aptYes, 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).