You are not logged in.
Wow. MAJOR SECURITY FLAW where for at least one boot choice anyone can just Ctrl-Alt-Fn to another terminal session .... that is already logged in. Yep. Choice of each/any of all six of 'em, all conveniently pre-logged in.
You must be looking at one of the live isos. Autologin to desktop and console has been a standard debian-live feature for as long as I've been using it. (since Lenny). I think the reasoning behind it is that if you are running a live session, then you are probably sitting at the computer and will shut down the session and take your live media with you when you are finished. Autologin gets disabled for the installed system unless you change the defaults in the installer.
Note that on a regular installation, if you ctrl-alt-Fn to console and login and don't log out, that login will still be accessible even if you go back to desktop and lock the screen. This is not new and not unique to devuan. I first discovered it on debian.
Yes, it uses refractainstaller. The desktop icon (and the apps menu) runs a wrapper script that starts either the uefi or non-uefi version of the graphical installer. The cli installer is there, too.
Any changes in sofware or configuration of the system get copied to the hard drive. I would anticipate some potential problems around the fact that the destop was installed with metapackages, so removal of a single package could result in a slash and burn of the desktop, including the graphical installer. That's not as bad as it sounds - since it's a live system, you can just reboot and try it again. Also, you need to have enough RAM to update the package cache and the installed packages.
I just installed lirc in devuan, and the messages I get at the end of the install say that there is no /etc/lircd.conf and to configure it manually. Running 'dpkg-reconfigure lirc' returns without any messages and without runing the ncurses debconf. Installing the same package in debian jessie does not give me the messages about the config file. Running 'dpkg-reconfigure lirc' again returns without any messages and without ncurses debconf. So, I don't know if it's broken or not. Can you use it? Do you have or know what goes in the missing config file?
edbarx' post was a solution to a problem with the beta installer. That problem has been fixed. The devuan installation disks will now detect your wireless hardware and provide the correct firmware. The regular install does this automatically, and the expert install asks if you want the non-free firmware or not. The live images have the firmware pre-installed and provide a script to remove all the non-free packages.
Refracta was declared stable last August. The main things that were holding up Devuan from being declared stable had to do with the installer and desktop-base. Refracta doesn't use either of those, so there was no reason to wait. Devuan is as stable as Debian because it IS Debian with a few unnecessary dependencies removed.
Thanks for pointing that out. I thought I enabled the pre-install scripts for simple install. Time zone and locale debconf dialogs should run at the beginning of the installation. They do in expert install, and post-rc2 also has keyboard settings at the same time. The simple install button is going to disappear in a future installer. Simple can be achieved with the expert install by ignoring all the checkboxes and proceeding without changing anything.
The default timezone should be UTC. That's what I get when I boot live media.
You can set the locale at boot, too. Take the second item in the boot menu, press TAB, and backspace to erase the locale code. Then replace it with your own. That runs a hook script that creates a file with the following lines (with your locale code for example.)
/etc/profile.d/zz_locale.sh
export LANG=en_GB.UTF-8
export LC_ALL=en_GB.UTF-8But that won't change the keyboard. When editing the boot command, you could also add
keyboard-layouts=xxwhere xx is the lower-case two-letter country code. In your case, I think that would be gb.
Or, on the xfce desktop, and the keyboard layout plugin to the panel, add codes (choose from the list) and use that to switch layouts.
Edit: keyboard-layouts gets a two-letter code.
Maybe you need to install the firmware from backports.
apt-get -t jessie-backports install firmware-iwlwifiI just tried it in a live-usb (with a post-rc2 iso) and the off switch works. I got mixed results on the wired connection. Once it connected about a minute after I killed the wireless connection, and on a subsequent reboot, it did not. I've noticed similar when I boot up with the wire unplugged and then plug it in. Sometime the connection will come up on its own, and sometimes I have to start it with 'dhclient eth0'. Maybe this is the buggy behavior I've heard people complain about. I always rely on manually connecting and disconnecting when I use the wireless.
I also tried it in debian, where hitting the 'shut off wifi' button changes it from saying 'connected' to saying 'disconnected'. But that's just what it said - I could not get out to the internet regardless of what it said.
Yes, go with backports. Disable ascii. All the devs have been focused on getting jessie ready, and not much work has been done on ascii.
apt-get -t jessie-backports install linux-image-4.9.0-0.bpo.2-amd64Yes, this is a good place to ask. I don't know lirc, but it should work the same as in debian. That package wasn't altered.
The desktop-live has the same packages as a default desktop install, and the minimal-live has much less (and more, in some ways). Maybe some package is missing and isn't listed as a Depends, but I don't know what that might be.
I have this feeling that it might be related to the fact I needed to add nomodeset to linux boot line in grub
Trust the Force, Luke. You are correct.
I just booted with 'nomodeset' and redshift no longer works. Neither does my brightness script that I've been using.
Upgrading those four packages was probably not the right thing to do. I don't know if that will cause problems or not.
There is no randr package. Sorry. But you can run 'xrandr' on the command line to see your display settings. You should be able to change settings with xrandr, too, but maybe it's not working. Run it with no arguments to get the display name (maybe VGA-1, DVI-something, or maybe it's just called 'default').
Then try
xrandr --output <the display name> --brightness 0.7and see if it decreases the brightness to 70%.
You might be able to use one of the other methods listed. There's a line for it in the config file. Mine says "adjustment-method=randr". You could try replacing randr with the other methods (vidmode, drm or dummy). That's my best guess. I don't really know anything about it.
Make sure randr is installed. Check in synaptic. You can also see what methods are available to redshift with
redshift -m listI can start 'redshift-gtk' on the command line if I give it my latitude and longitude. It works, it puts an icon in the system tray, and I can get an information window from that.
1. First. Important: What golinux said. Don't upgrade to ascii, just take what you need and then disable ascii. I can confirm that it runs on jessie. I only tested it on command-line. I didn't set it up to run automatically, and I don't like that it wants my latitude and longitude.
This works:
2111 redshift -O 3500
2112 redshift -O 5500apt-cache policy shows:
Version table:
redshift-gtk
1.11-1 0
90 http://us.mirror.devuan.org/merged/ ascii/main amd64 Packages
gtk-redshift
1.9.1-4 0
500 http://us.mirror.devuan.org/merged/ jessie/main amd64 PackagesHi,
What is the reason for switching from live-build to live-sdk?
Phil
I'm not sure. I know that live-sdk uses some of the same libraries as the devuan sdk that's used for building all the other images, so at least part of the decision was for consistency. I also know that early on, it was impossible to build an iso with live build-that didn't include systemd. I just tried the version of live-build in jessie, and it looks like it was neglected. It still uses debian repos. I just changed that and it's running. I'll know more in a little while.
I'm hoping Ozi will say something here. He uses live-build and knows more about it.
Edit: This is with version 4.0.3-1+devuan2, which looks to be the only one in jessie, ascii and ceres.
The following packages have unmet dependencies:
live-config-systemd : Depends: systemd but it is not installable
Recommends: dbus but it is not going to be installed
E: Unable to correct problems, you have held broken packages.Wow. It took me five attempts to get it right. Here's a video of manual partitioning (you can get there from non-expert as well as expert install).
Create a boot partition
Create a partition to be used as physical volume for encryption.
Uh... watch the video.
There are a lot of places where I drop the highlight down below the item I'm about to select, and then move up one line and select it. Did that in case it's hard to read in the red highlight.
http://distro.ibiblio.org/refracta/misc … rypt-4.ogv
@FOSSuser: Good call.
@hughparker1: the correct locale to choose is en_GB
Wow. The Russian is weird. Are all system messages in Russian? You can change language/locale by running
dpkg-reconfigure localesBut I don't think that will help. That's a grub message. I know there are language files in /boot/grub, but I don't know anything about how they work. Maybe some setting in /boot/grub/grub.cfg or /etc/grub.d/* thinks you want Russian.
I just learned that a big part of your problem with this install is the fact that grub-efi-amd64 is not installed in the iso. That's my error, and it will be fixed. So yes, it will be easier. You'll get a window that has some choices for what to do with grub, and one of them is to let the installer add the bootloader. All you need to do is press one button.
OK, my problem is all better now. I could not create users or groups. Went through the vaious software fixes proposed in similar posts, and none of them seemed to apply. Problem went away with a complete poweroff and blowing out dust. I can now create users and groups, and mysql-server installed without any trouble.
I can believe that encrypted install with the debian-installer failed. It is not intuitive or straightforward, but if you can find the right path through the maze, you will get to the end. Here's a guide. Unfortunately, the pictures are long gone, but the words should help you get the steps in the right order. Also, if you go to forums.debian.net and search for posts about encrypted lvm install, you will find a couple of guides.
I have one install that has mysql-server for one app that needs it for its database. It only gets used from localhost, and it works fine. I just upgraded it after many months, and it still works.
I just tried to install mysql-server on my main box, and it's failing with this error message:
dpkg: error processing archive /var/cache/apt/archives/mysql-server-5.5_5.5.55-0+deb8u1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1Attempting to add the group manually:
groupadd -g 121 mysql
groupadd: failure while writing changes to /etc/groupThis is strange. I got the same error a few days ago trying to install something, but that was in a chroot, and I needed to make the bind-mounts with sys, dev and proc. Right now, I'm not in a chroot. I'm installing directly on hardware in the running system. If someone else wants to try, you can let me know if the problem is just with my setup.
I don't think it's a file permission problem:
-rw-r--r-- 1 root root 904 Mar 8 18:38 /etc/groupThe regular installer isos use the debian installer, so encryption is supported. You can encrypt individual partitions or use lvm to have multiple partitions inside one encrypted volume. For lvm, you can do it manually or let the installer do the partitioning for you.
The devuan-live isos use refractainstaller, which supports encryption of separate root and/or home partitions. It does not support lvm, and it does not support encrypted swap partition, but it can create a swapfile inside the encrypted root partition.
When you start synaptic from the menu, you should get a window that asks for a password. If you set up the system to use a root account, use the root password, and if you set it up for sudo, use your password. If you're not getting the pop-up window for authentication, the start it from a terminal like you did until that issue is solved.
For the grub problem. You're right. Editing the config on devuan won't help if debian is in charge of boot. I can think of three ways to fix it.
1. Boot into Devuan and reinstall grub-efi-amd64
2. Boot into Devuan and run 'sudo grub-install' in a terminal. (no device name needed with uefi)
- optional for 2: run 'sudo grub-install --bootloader-id=some-name'
In either of those cases above, grub will create a bootloader and I expect it will put itself first in the list of bootloaders. Then you'll need to run update-grub to get debian in the boot menu. WARNING: I don't know this for a fact. UEFI implementations vary from manufacturer to manufacturer, so your system might not act like mine. COMMENT: I would try #2 with the bootloader-id first, and use an id name that is something other than debian, devuan or boot. Then you will know for sure that it's the one you just made.
In my system, Debian's bootloader is in /boot/efi/EFI/debian and Devuan's is in /boot/efi/EFI/devuan. There is a /boot/efi/EFI/boot/, too. I forget where that came from, and I don't use it. Whenever I install a linux and allow grub to install, it becomes first. If I change the order of the bootloaders using efibootmgr, it shows me that the boot order has changed, and then it reverts to the previous order as soon as I reboot. Yours may act differently.
3. Boot into Debian and copy the menuentry for Devuan from /boot/grub/grub.cfg into /etc/grub.d/40_custom, add nomodeset to the linux line, and run update-grub. There will be an extra entry for Devuan in the boot menu, and that one will have nomodeset in the boot command. The entry starts with the word, menuentry and ends with a closing curly brace `}'
Read this if you haven't, re-read it if you have: http://www.rodsbooks.com/efi-bootloaders/index.html
Wow! Great review. Thanks, and welcome to Devuan.
1. Graphics card or driver. Whichever one you want to blame. You could try the proprietary driver, but if it's working ok, there's no need.
2. Yes. Add nomodeset to /etc/default/grub and then run update-grub to generate a new menu. Then you don't have to edit at boot every time.
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"