topic title: antiX16-b5 iso-snapshot report
Posts: 148
chrispop99
Joined: 21 Apr 2011
#1
Note (1)
This is a bug report, not a request for help.

Note (2)
I have been able to create working ISO's from MX with no problems.

Test 1 - 32 bit on Thinkpad T23:
This install had a number of additional programs installed, and was customised WRT appearance. The ISO was created without any changes to the default options. It was larger than would fit on a CD, and the machine only has a CD optical drive, so the ISO was transferred to another machine for creation.
The resultant disk was then tried in both the original (T23) laptop, and in a Thinkpad T41. In each case it failed to boot, stopping around the time that 'X' would normally appear.
The process was repeated. It was noted this time that when the media creation was finished, the burning program (K3B) reported it had burnt 783 of 851MiB. I have never seen this before! The second DVD failed in the same way as the first.

Test 2 - 64 bit on desktop with Core i5 CPU:
This install was only altered from OOTB by the addition of Firefox, and updated to current. An ISO was created again using all defaults. It was burnt from within the antiX install. Nothing untoward was reported. A boot from the created media was attempted on the machine from which it was created, and it failed in the same way.
With the machine stalled, using Ctrl-Alt_F1 to a console showed that the last message on-screen was:

Code: Select all

antix16b5 login: / etc/rc.local: 30: / etc/rc.local: boot-log: not found
Chris
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#2
make sure you have all the latest updates from antiX repos before you use the snapshot.
rc.local in etc should basically only have this

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will"exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#

exit 0
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#3
The live rc.local in a snapshot should look something like this

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will"exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#

restore=/live/ etc/init.d/live-restore-services

[ -x $restore ] && $restore start

# Add a background image to every virtual console if the splash
# boot parameter was given
/sbin/splash-all --auto

# Enable fstab auto-stuff after udev has run
fstab_rules=/live/ etc/udev/rules.d/90-fstab-automount.rules
test -e /live/config/fstab-hotplug \
    && test -e $fstab_rules && cp $fstab_rules / etc/udev/rules.d/

# Detect and set up correct broadcom
/usr/local/bin/BroadcomStartup

exit 0
Maybe the latest hasn't hit the repos yet.
Posts: 148
chrispop99
Joined: 21 Apr 2011
#4
I did an apt-get upgrade before I started, and the second one was this am.

I will check the contents of those files.

Chris
Posts: 148
chrispop99
Joined: 21 Apr 2011
#5
anticapitalista wrote:make sure you have all the latest updates from antiX repos before you use the snapshot.
rc.local in etc should basically only have this

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will"exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#

exit 0
rc.local on both 32 and 64 bit installs is this:

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will"exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#

restore=/live/ etc/init.d/live-restore-services

[ -x $restore ] && $restore start

# Add a background image to every virtual console if the splash
# boot parameter was given
/sbin/splash-all --auto

# Enable fstab auto-stuff after udev has run
fstab_rules=/live/ etc/udev/rules.d/90-fstab-automount.rules
test -e /live/config/fstab-hotplug \
    && test -e $fstab_rules && cp $fstab_rules / etc/udev/rules.d/

# Detect and set up correct broadcom
/usr/local/bin/BroadcomStartup

test -d /root/LiveUSB-Storage && which boot-log &>/dev/null \
    && (sleep 10 && boot-log) &

exit 0
Chris
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#6
That second one is for the live set up.
Posts: 148
chrispop99
Joined: 21 Apr 2011
#7
anticapitalista wrote:That second one is for the live set up.
It was copied and pasted from an install, definitely not live, and the identical file exists on the other install.

Would that be the reason the snapshot failed? If so, I will do a fresh install, then see what rc.local contains.

Perhaps someone else could try to create a working snapshot?

Chris
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#8
There was an upgrade of rc.local via apt and you probably answered yes instead of no.
I'm making a snapshot and will see how it goes,
Posts: 148
chrispop99
Joined: 21 Apr 2011
#9
anticapitalista wrote:There was an upgrade of rc.local via apt and you probably answered yes instead of no.
Yes, I did. Was that change needed for some reason? Perhaps it needs reappraising?

In the meantime, a fresh install of the 64 bit leaves etc/rc.local with just the exit 0 command.

Chris
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#10
I made a snapshot (in VBox) of latest (not released pre-RC1 with various changes to b5) upgraded to Debian Testing. The resultant iso booted just fine to desktop again in VB.
Posts: 148
chrispop99
Joined: 21 Apr 2011
#11
Should/will there be any steps taken to prevent someone else doing this? If someone did, is the situation recoverable?

Chris
Posts: 148
chrispop99
Joined: 21 Apr 2011
#12
The change to rc.local during updates is not the cause of the failed snapshot ISO's I am experiencing.

I did a fresh install of 32 bit. I checked rc.local only contained the 'exit 0' line. I updated, being careful to keep the original rc.local configuration. I re-booted, and again checked rc.local hadn't changed.

I then created a snapshot ISO. When I tried this both in the original machine, and another, it failed in exactly the same way I reported earlier.

Chris
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#13
chris, could you clarify whether you used a DVD or a CD as the media. You mentioned that the T23 only has a cd drive, so that's why I'm asking.
Posts: 148
chrispop99
Joined: 21 Apr 2011
#14
dolphin_oracle wrote:chris, could you clarify whether you used a DVD or a CD as the media. You mentioned that the T23 only has a cd drive, so that's why I'm asking.
The T23 has a combination drive; it reads and writes CD's, but the DVD is read only.

I created the snapshot on the T23. Because I had added a few things it wouldn't fit on a CD, so I transferred the snapshot folder to another machine and created a DVD with it there.

During the tests I have been doing on this, I installed (64 bit) onto the desktop in my sig, and created a snapshot on it. I burnt the ISO to a DVD using that machine’s drive. It also failed to boot, with the identical error message.

Chris
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007

08 Jun 2016, 19:48 #15

Look in /usr/local/share/live-files/files/ etc/rc.local

It should look like this.

Code: Select all

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will"exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#

restore=/live/ etc/init.d/live-restore-services

[ -x $restore ] && $restore start

# Add a background image to every virtual console if the splash
# boot parameter was given
/sbin/splash-all --auto

# Enable fstab auto-stuff after udev has run
fstab_rules=/live/ etc/udev/rules.d/90-fstab-automount.rules
test -e /live/config/fstab-hotplug \
    && test -e $fstab_rules && cp $fstab_rules / etc/ udev/rules.d/

# Detect and set up correct broadcom
/usr/local/bin/BroadcomStartup

exit 0
[code]

BTW is the snapshot Personal or system? My success was with Personal