You are not logged in.
upgrade will only upgrade installed packages. dist-upgrade will install any new packages. You are likely to see differences between the two when moving from one release to another. Not so much (hardly ever) when upgrading within a release. Doing it in stages as fungus described is the safest way to do it.
The kernel will be upgraded to the latest version available if you have the kernel metapackage installed. (e.g. linux-image-amd64). Without the metapackage you need to install the newer kernel using your preferred method for installing packages: apt, apt-get, aptitude or synaptic.
Yes, please post the output of 'lspci'.
I removed the intel-microcode package, upgraded to a newer backports kernel and did a general upgrade, then made a new iso. This one has a normal initrd. If you get a chance, please try it and see if it boots. Thanks.
http://distro.ibiblio.org/refracta/file … 0_1501.iso
Edit: Almost forgot this...
I've been playing with uefi for a year with one laptop, and I've read a few reports of people using uefi and/or using the refracta tools on uefi. If the uefi works according to specifications, it's just weird. And since uefi implementations rarely or never follow specs, it's worse than weird. I'll refrain from swearing; otherwise what would come out would burn the eyes of anyone who read it.
You can install the kernel after you're finished with the upgrade. That's assuming it doesn't get installed with the upgrade.
Before the upgrade:
Add this to /etc/apt/sources.list
# jessie backports
deb http://packages.devuan.org/merged jessie-backports mainapt-get update
apt-get -t jessie-backports install rsyslogYou will get 8.23.0-2~bpo8+1
After you install it, comment out the backports line in sources.list, change the jessie lines to ascii and continue with the upgrade.
Depends on how you made the live usb. If you used the isohybrid feature (dd or cat the iso to /dev/sdX) then no. It's a read-only system. Any changes you make are lost on reboot. If you set up a persistent volume, then yes you could upgrade the live system, but it really doesn't make sense to do it that way. The persistent volume keeps copies of any files you add or change, so it would end up holding a copy of nearly the entire system.
You really need to install it and upgrade, then make a new live iso. Install to a spare partition, into a virtual machine or even onto another usb stick. Your upgrade procedure is correct. You might need to install the newer kernel manually - if so, look for linux-image-4.9-something. And you can always add the -s option (--simulate) to see what will happen before you really do it.
I don't remember what synaptic does, but you can probably do it all with that.
Oh yeah. I'm not sure of the current status of rsyslog. If it looks like it wants to cause problems, you can install rsyslog from backports (or else replace it with syslog-ng or busybox-syslogd.
Maybe some other problems. It's been a few weeks since I've tried an upgrade to ascii. Be flexible and you'll get there.
It starts with 65492d here. You should download it again.
If you don't want contrib and non-free enabled during the installation, then choose expert install, and it will ask. If you don't know enough to use expert install, your wireless firmware will be installed automatically, and you will be glad you have it. Especially if you can't do a wired connection.
I just had a look at the initrd in that iso, and it does not contain what I expected. Only thing in there is kernel/x86/microcode/GenuineIntel.bin. I don't kinow what that means. I'll can look into that when I get home in a few days.
How did you image the usb stick? I tested it here today. dd iso to usb, boot on uefi hardware. It works. Intel cpu here.
Edit2: this is not bpo kernel. This one is ascii.
Edit: you may have better luck with this one. It has a normal initrd. You just won't get a desktop until you add one after the install.
https://sourceforge.net/projects/refrac … o/download
I don't know if wget is installed or available on a mac, but if it is...
wget -c http://distro.ibiblio.org/refracta/files/experimental/devuan_jessie_amd64_bpo_desktop-live-20170522_1240.isoIf the download fails at some point, run the command again and the -c option will make the download continue from where it left off.
https://sourceforge.net/projects/linnix … =directory
There are a few flavors - go for the one with jwm in the file name.
Newer versions of mate packaged by Antofox are available here -
http://hezeh.org/the-hezeh-repository/
The plan is for these to be added to the main devuan repository. I don't have an exact timeline, but it shouldn't be too long. This is one of the higher priority tasks right now.
If that doesn't fix it, one workaround is to install pmount and use spacefm to mount/unmount usb drives.
One small warning. If the package gets upgraded, your edits will be replaced. One way around this is to make a separate desktop file. Edit the Name line so it looks different in the menu. If you want it not to show up, you could add to the original file something like
OnlyShowIn=LXDE(or change LXDE to whatever desktop you are not using.) That will still get wiped on upgrade, but you won't have to look at it until then,
Aha! More to it than I thought about. If you install from the regular installer isos, grub looks in /boot and lists the newest version kernel first. If you install from the live isos (using refractainstaller) it uses the symlinks /vmlinuz and /initrd.img which will be the most recent kernel you installed, regardless of the version. The kernel that gets replaced gets the /vmlinuz.old symlink.
i386, amd64 plus the embedded and virtual images.
All are here - https://files.devuan.org
I can think of two reasons for showing the old kernel - either you didn't install the newer kernel or you haven't rebooted yet. The kernel doesn't get automatically upgraded to a newer version unless you have the kernel metapackage installed. (something like linux-image-amd64)
Thanks for taking the plunge. I've been wanting to try an upgrade to ascii on miyo or vuudo for awhile but haven't gotten around to it.
'
If you do get the laptop, I hope you'll try the live iso with the backports kernel. I'm curious to know if it works, and you might help the next guy thinking of getting one of these laptops.
ascii is based on stretch. We don't do it the way ubuntu does. They copy the whole unstable repo and then start changing things to suit themselves. Devuan tracks releases more closely. Jessie has all the same software versions as Jessie (except where systemd dependencies have been removed) and ascii will have the same versions as stretch. Devuan doesn't keep most of the debian packages in the devuan repo. They get pulled from debian. When you install a package, amprolla decides which packages to pull from debian and which to replace with the devuanized versions, so you don't have to use debian sources yourself and accidentally install something that will want systemd.
Right now, the way to install ascii is to install jessie and upgrade. Two excptions I know of are:
1. Heads, which focuses on privacy and security, somilar to Tails - https://heads.dyne.org/
2. Refracta pre-alpha ascii, i386, No-X (cli only). https://sourceforge.net/projects/refrac … s/testing/
There may be more choices in a few weeks. If you install debian or ubuntu before that, maybe save a little hard drive space for testing.
In general, I would say that ascii is not ready, but it is possible to use it. If the instructions you saw are these - https://wiki.debian.org/InstallingDebia … PS_13_9360 - I have some comments.
They don't say why you need stretch. My best guess is that you need the newer kernel. One way around that would be to use the backports kernel in jessie. You can get wireless firmware from backports, too. I don't suppose costco would let you boot a live-usb on their floor model, but if they did, you could try a devuan live-iso I made with backports kernel and wireless firmware - http://distro.ibiblio.org/refracta/files/experimental/ (note: it's not an official release, but it was made and signed by the guy who did make the official desktop-live isos.)
The major deal-breaker I see is the recommendation to install gnome desktop environment. Gnome depends heavily on systemd, and parts of it are uninstallable in devuan. If you knew which parts of it were really needed for this laptop, you might be able to install just those parts. If you're counting on using devuan on this laptop, it might be a risky purchase.
1, 2 and 3 are correct. Devuan Jessie tracks Debian Jessie, ascii is tracking stretch, and ceres will always track sid. While stretch has reached stable, ascii still requires some work. I think it's less confusing if you stick with the codenames instead of talking about stable/testing/unstable. Right now, debian buster is in testing and devuan beowulf, which will track buster, does not yet exist. I think the beowulf repo will probably get set up after amprolla3 goes online, which should be soon.
postunpack is an error log generated by lib/libdevuansdk/zlibs/bootstrap.
I don't know if anyone has tried live-sdk on anything other than devuan. There are references to devaun in /usr/share/debootstrap/scripts/jessie in the devuan version of debootstrap, but I doubt you'll find them in debian or ubuntu. Maybe it's possible to install devuan debootstrap in ubuntu, and if so, maybe it will work. I don't know.
'apt-get remove' - packages that were automatically installed with the named package will be set to 'autoremove'. Run 'apt-get autoremove' to remove them.
'aptitude remove' - packages that were automatically installed with the named package will also be removed.
'apt-remove' - I don't know what it will do.
Ceres and Sid have the same version. It's probably because qupzilla was built with newer qt5 libraries that haven't made it into the repo yet. Wait a few days or a few weeks and things should catch up.
There are three choices for the sudo settings:
- Permit sudo adds the user to the sudo group.
- Sudo as default does the above, plus edits two files. *
In ~/.gconf/apps/gksu/%gconf.xml sudo_mode gets set to true
In ~/.su-to-rootrc "su" gets changed to "sudo"
- Sudo only for shutdown adds /etc/sudoers.d/user_shutdown. This is the default setting.
In all cases, if there is a root account, it is not disabled.
*Edit: more than two files. It also looks for kdesurc/tdesurc for KDE or TDE desktops.
Thanks for the appreciation. Glad it works for you.
You have to change limit_cpu="no" to "yes" for cpulimit to work. It's not on by default.
Changing the work and snapshot directories should work correctly. Check the config file to make sure you edited it correctly. Make sure the storage device is mounted. If you want a more verbose error log, run it in debug mode (add -d option or change the setting in the config file).
type - exit exits
Can't find the smiley with the big-eyed look of shock. Damn. Thanks for that. I didn't know.
Maybe the text over the entry box should say "username or command" instead of just "username". Check with the boss (a.k.a. She who has command over all things visual.)
If you have more than one window manager or desktop environment, the slim login screen will let you scroll through them with the F1 key.
rsyslog from jessie-backports installs and works in ascii, so that's another option. I haven't tried it in ceres.
To each, his own. I couldn't get away from the default slim background fast enough. Is it the blue one or the red one?
1. Yes, there should be a %sudo line in /etc/sudoers. Mine looks like this:
# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL2. You must have installed from one of the live isos and chosen "use sudo only for shutdown" instead of "use sudo as default".
If those are not both true, then something is wrong or I'm wrong about the situation.