topic title: Upgrade from antix12 to antix13
5 posts
• Page 1 of 1
-
Posts: 21
- Joined: 04 Apr 2013
#1
I have been using antix12 live persistence usb installation and have remastered. Can I upgrade to antix13 and keep my customizations? What about keeping my home directory?
-
Posts: 1,308
- Joined: 31 Aug 2009
#2
I *think* you can upgrade via apt-get or synaptic but other people know a lot more about this than I do.
I suggest you start using the new initrd.gz that comes inside the antiX-13 iso files. If you don't want to download an entire iso to get a file that is only a few Meg, I can email it to you if you send me a PM.
On the vast majority of systems, the initrd.gz files are interchangeable. There are a few systems that need kernel drivers from the initrd in which case the initrd must match the kernel, but I think you would know if you needed this.
There are three new persistence features in the initrd that may be useful to you:
The filesystem checks and cleaner shutdown are a bonus. They should increase reliability.
Since you can easily bork your system by blindly changing the initrd.gz file, I suggest you add a new menu.lst entry (assuming you are using Grub) for the new initrd.gz file. For example, if you have a current entry like:Then copy the new initrd.gz file to /live/bootdev/antiX/initrd.new and add a new entry:The same trick works if you are using syslinux as your boot loader but the syntax of the file is slightly different.
The antiX-13 Live bootloader has more menu options and a few other little tricks. You should be able to use it just by copying the file /boot/grub/message file from an antiX-13 iso to /live/bootdev/boot/grub/message. Unfortunately, if this goes wrong then it will make your stick unbootable. On the plus side, I don't think there is much to go wrong as long as the copy is successful. Some of the new options won't work until you upgrade to the antiX-13 Live init.d scripts.
Someone else can probably help you with upgrading your actual system which is probably what you are mainly interested in. I'm just suggesting that you update your initrd.gz first and start using static root persistence before you do a major system update that might run out or RAM.
BTW: to enable static root persistence, just add",static" or",s" to the"persist=..." boot parameter.
I suggest you start using the new initrd.gz that comes inside the antiX-13 iso files. If you don't want to download an entire iso to get a file that is only a few Meg, I can email it to you if you send me a PM.
On the vast majority of systems, the initrd.gz files are interchangeable. There are a few systems that need kernel drivers from the initrd in which case the initrd must match the kernel, but I think you would know if you needed this.
There are three new persistence features in the initrd that may be useful to you:
- 1) Static root persistence
2) Fsck of ext2/3/4 filesystems at boot time
3) Cleaner shutdown
The filesystem checks and cleaner shutdown are a bonus. They should increase reliability.
Since you can easily bork your system by blindly changing the initrd.gz file, I suggest you add a new menu.lst entry (assuming you are using Grub) for the new initrd.gz file. For example, if you have a current entry like:
Code: Select all
title antiX-12_386-full (10 October 2012)
kernel /antiX/vmlinuz quiet antiX=MLX
initrd /antiX/initrd.gz
Code: Select all
title antiX-12_386-full New Initrd (14 June 2013)
kernel /antiX/vmlinuz quiet antiX=MLX
initrd /antiX/initrd.new
The antiX-13 Live bootloader has more menu options and a few other little tricks. You should be able to use it just by copying the file /boot/grub/message file from an antiX-13 iso to /live/bootdev/boot/grub/message. Unfortunately, if this goes wrong then it will make your stick unbootable. On the plus side, I don't think there is much to go wrong as long as the copy is successful. Some of the new options won't work until you upgrade to the antiX-13 Live init.d scripts.
Someone else can probably help you with upgrading your actual system which is probably what you are mainly interested in. I'm just suggesting that you update your initrd.gz first and start using static root persistence before you do a major system update that might run out or RAM.
BTW: to enable static root persistence, just add",static" or",s" to the"persist=..." boot parameter.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#3
jsr - give us some more information about what you have updated when using antiX-12 with persistence.
-
Posts: 21
- Joined: 04 Apr 2013
#4
BitJam and anticapitalista: Thank you both for the quick replies. You have always been helpful with my previous questions.
BitJam: Thanks for the explanation on the new root persistence - that is a real improvement. I started using antix12 late in the cycle and could never do a full dist-upgrade on even a 2gb ram computer - I had to manually select packages without exceeding a rough limit on total size for each update. I am not sure I want to do a partial change to 12, nor risk breaking 12 until I get 13 running. I realize that most distros don't provide for a simple means to upgrade a version while keeping personalization or the /home directory intact. Puppy live allows, in some cases, simply copying three main files from the new upgrade .iso to the old installed version for a seamless upgrade. Since I am using the live persistence installation of antix, I wondered if I could do something similar. You indicate that I might be able to, but the procedure might be more complicated and not provide a total upgrade to 13.
anticapitalista: My antix12 has a current, complete dist-upgrade. I have also added a few minor games, Thunderbird (which works well with imap), printer/scanner drivers, a few other packages, and personalization. I have fiddled with enough linux distros that it does not take me too long to get them setup and personalized. As noted above, I thought I would ask if there was an easy process to upgrade 12 to 13, but do not want to ask for your and BitJam's valuable time beyond that.
Over several years, I think I have tried all the"portable", ram-based, live linux distros that install on a usb stick, cycling through them as they have upgraded. They are amazing, creative attempts to provide a full linux distro experience in a small package. Antix, the distro and the support, is by far the best for me - thank you for what you have done.
BitJam: Thanks for the explanation on the new root persistence - that is a real improvement. I started using antix12 late in the cycle and could never do a full dist-upgrade on even a 2gb ram computer - I had to manually select packages without exceeding a rough limit on total size for each update. I am not sure I want to do a partial change to 12, nor risk breaking 12 until I get 13 running. I realize that most distros don't provide for a simple means to upgrade a version while keeping personalization or the /home directory intact. Puppy live allows, in some cases, simply copying three main files from the new upgrade .iso to the old installed version for a seamless upgrade. Since I am using the live persistence installation of antix, I wondered if I could do something similar. You indicate that I might be able to, but the procedure might be more complicated and not provide a total upgrade to 13.
anticapitalista: My antix12 has a current, complete dist-upgrade. I have also added a few minor games, Thunderbird (which works well with imap), printer/scanner drivers, a few other packages, and personalization. I have fiddled with enough linux distros that it does not take me too long to get them setup and personalized. As noted above, I thought I would ask if there was an easy process to upgrade 12 to 13, but do not want to ask for your and BitJam's valuable time beyond that.
Over several years, I think I have tried all the"portable", ram-based, live linux distros that install on a usb stick, cycling through them as they have upgraded. They are amazing, creative attempts to provide a full linux distro experience in a small package. Antix, the distro and the support, is by far the best for me - thank you for what you have done.
-
Posts: 1,308
- Joined: 31 Aug 2009
#5
jsr, it was your problem upgrading a persistent system in April that sparked me to implement static persistence. The static persistence was easy. It was the clean umount and the fsck that took all the work but I didn't want to do static persistence without them.