You are not logged in.
- Topics: Active | Unanswered
#151 Re: Installation » Upgrade Live USB to Ascii for testing? » 2017-07-30 17:30:50
From jessie to ascii 4.9 comes automatically in my experience, and I believe 4.11 comes with ceres, but
you will still be running 3.16 while you are doing an upgrade. When I do such hops I don't care about the next kernel as much as about the transition. I like to update/upgrade what is most essential for the transition, even though in 99% of times it may not matter. I like to upgrade apt,dpkg,synaptic,,.... first and then rerun the update/upgrade with whatever tool is used. The new tool is always safer doing the edition hop, even though it is running on an older kernel which I have yet to see a problem with. I always keep 1-2 kernels backup just in case the new runs into a bug.
So, to clarify things then, your plan would be as follows?
Install rsyslog as per the instructions of @fsmithred.
Modify the sources.list file to point to ascii.
Upgrade apt using the apt-get upgrade command.
Upgrade dpkg using the apt-get upgrade command.
Upgrade synaptic using the apt-get upgrade command.
Run the following commands in Terminal.
apt-get update
apt-get upgrade
apt-get dist-upgrade
Install the 4.9 kernel.
Which command should I use for installing the 4.9 kernel, apt-get update or apt-get upgrade?
Thanks, MTB.
#152 Re: Installation » Upgrade Live USB to Ascii for testing? » 2017-07-30 01:35:28
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.
Can and should 4.9 be installed before updating the sources.list file and running the apt-get commands?
Or should it be done after the apt-get commands?
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.
Which of the following should be used for rsyslog?
https://auto.mirror.devuan.org/merged/d … 4/Packages
https://auto.mirror.devuan.org/merged/d … 4/Packages
Thanks, MTB.
#153 Installation » Upgrade Live USB to Ascii for testing? » 2017-07-29 22:06:14
- mtbvfr
- Replies: 8
Hi All,
Can I upgrade a Live USB to Ascii for testing?
If so, which is the best method to use for providing any feedback incase of problems?
Should I manually modify the sources.list file to point to ascii instead of jessie and then use the following commands in Terminal?
apt-get update
apt-get upgrade
apt-get dist-upgrade
Can the same be achieved using Synaptic via the Repositories menu option?
Thanks, MTB.
#154 Re: Installation » [Solved] sha256 Checksum does not match » 2017-07-29 01:16:26
It starts with 65492d here. You should download it again.
Ok, the checksum is ok this time.
The previous download produced a slightly smaller file but I didn't get any notification that the download had failed in anyway.
So, let's see how it boots up etc.
#155 Installation » [Solved] sha256 Checksum does not match » 2017-07-29 00:25:29
- mtbvfr
- Replies: 2
Hi All,
I just downloaded devuan_jessie_1.0.0_amd64_uefi_desktop-live.iso and the sha256 Checksum that was generated was the following.
4b359ea21f4798b0e6a00b154a202fdc2b61fc97846e824bbcf8d3c9db36cea7 devuan_jessie_1.0.0_amd64_uefi_desktop-live.isoThe Checksum, listed in the SHA256SUMS file that I downloaded, says the following.
65492da45f5def8b99d09d3fb5246eb1e21bddf490cc7efe3287ac770b665748 devuan_jessie_1.0.0_amd64_uefi_desktop-live.isoI mounted the iso in Thunar and the structure appears correct. It was mounted with a label of ISOIMAGE.
Can someone confirm that the correct Checksum is what I generated in Terminal?
Thanks, MTB.
Board footer
