Posts: 13
keithpeter
Joined: 04 Jan 2010
#1
Hello All

Installed AntiX 8.2 on a low power pc (500MHz processor, 1Gb ram, mechanical hard drive) and all appears to be fine. I'm impressed with the low footprint and relatively responsive system! Absolute Linux and AntiX both work well on this tiny almost silent computer

A couple of questions:

Only error on update was

Code: Select all

open: 1; closed: 2575; defer: 6313; conflict: 5
The following packages have unmet dependencies:
  libzephyr3-krb: Conflicts: libzephyr3 but 2.1.20070719.SNAPSHOT-1.2 is installed.
  libzephyr3: Conflicts: libzephyr3-krb but 2.1.20070719.SNAPSHOT-1.2 is to be installed.
Do I need to do anything about that?

Any suggestions for processes I can stop? No need for wifi or ppp as this box is on a wired lan and I don't do torrents. What is the web server for?

Cheers & thanks
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#2
Where did the error come from?

Try
#apt-get -f install
and post the result.

Processes to stop:
Transmission, wicd (a real hog), lightppd (server app for those that want it), saned, cups (if you don't print)
Posts: 13
keithpeter
Joined: 04 Jan 2010
#3

Code: Select all

root@aleutia:/home/keith# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 706 not upgraded.
I used aptitude update and then aptitude safe-upgrade after the hard drive install just on the basis that it was an .iso produced a few months ago and there might be security/bug updates.

Is aptitude not a Good Thing on AntiX then?

Thanks very much
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#4
aptitude is fine, I prefer apt-get.
Posts: 13
keithpeter
Joined: 04 Jan 2010
#5
Hello

Running apt-get update and apt-get upgrade resulted in a large download and when the dust cleared, and I repeated the update/upgrade I was left with this.

Code: Select all

root@aleutia:/home/keith# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages have been kept back:
  abiword abiword-plugin-grammar abiword-plugin-mathview bc cdw cheese
  claws-mail claws-mail-bogofilter claws-mail-i18n conky consolekit cups
  dhcpcd diff dmraid dpkg-dev ffmpeg fusesmb gftp gftp-common gftp-gtk
  gftp-text gnumeric gnumeric-common gparted gqview gstreamer0.10-plugins-base
  gstreamer0.10-plugins-good gstreamer0.10-plugins-ugly gstreamer0.10-x
  gtk2-engines-pixbuf gvfs hal hardinfo iceweasel iceweasel-l10n-ar
  iceweasel-l10n-ca iceweasel-l10n-de iceweasel-l10n-el iceweasel-l10n-es-es
  iceweasel-l10n-fr iceweasel-l10n-nl iceweasel-l10n-pl iceweasel-l10n-pt-br
  iceweasel-l10n-ro icewm icewm-common libavcodec52 libavdevice52
  libavformat52 libbonoboui2-0 libc6 libc6-dev libc6-i686 libcamel1.2-14
  libebook1.2-9 libedataserver1.2-11 libgail18 libglibmm-2.4-1c2a
  libgoffice-0-8 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0
  libgtk2-perl libgtk2.0-0 libgtk2.0-bin libgtkmm-2.4-1c2a libjack0
  libjpeg-progs libpangomm-1.4-1 libpisock9 libpoppler-glib4 libpurple0
  libsmbclient libsoup2.4-1 libsox-fmt-alsa libsox-fmt-base libwbclient0
  locales mencoder moc newsbeuter nmap parted pcmanfm pidgin pidgin-data
  python-gconf python-gnome2 python-gobject python-pysqlite2 python2.5
  python2.5-minimal ripit sox udev update-inetd wireless-tools wvdial
  x11-common x11-utils x11-xserver-utils xserver-xorg xserver-xorg-core
  xserver-xorg-input-evdev xserver-xorg-input-kbd xserver-xorg-input-mouse
  xserver-xorg-input-synaptics xserver-xorg-input-wacom xserver-xorg-video-apm
  xserver-xorg-video-ark xserver-xorg-video-ati xserver-xorg-video-chips
  xserver-xorg-video-cirrus xserver-xorg-video-dummy xserver-xorg-video-fbdev
  xserver-xorg-video-glint xserver-xorg-video-i128 xserver-xorg-video-i740
  xserver-xorg-video-intel xserver-xorg-video-mach64 xserver-xorg-video-mga
  xserver-xorg-video-neomagic xserver-xorg-video-nv
  xserver-xorg-video-openchrome xserver-xorg-video-r128
  xserver-xorg-video-radeon xserver-xorg-video-radeonhd
  xserver-xorg-video-rendition xserver-xorg-video-s3
  xserver-xorg-video-s3virge xserver-xorg-video-savage
  xserver-xorg-video-siliconmotion xserver-xorg-video-sis
  xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-tga
  xserver-xorg-video-trident xserver-xorg-video-tseng xserver-xorg-video-v4l
  xserver-xorg-video-vesa xserver-xorg-video-vmware xserver-xorg-video-voodoo
0 upgraded, 0 newly installed, 0 to remove and 142 not upgraded.
root@aleutia:/home/keith# 
When I removed wicd from the Control Center | System | Choose Startup Services and rebooted, I kept getting a little dialogue box granting admin rights to wicd, and then an error message. So I removed (and later purged) wicd and did the apt-get autoremove thing to get rid of some python script that had something to do with wicd.

After the upgrade I'm getting the pale blue Debian log in window.

Is all this normal?
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#6
About the pale blue login, it's because slim (the login manager) was updated and it was set to its default theme. If you prefer antiX's one then you could set it back in /etc/slim.conf (or through the control panel). If you look at /usr/share/slim you may find the themes. Also the update process may have backed-up the former slim.conf.
The recommended updating process is 'apt-get dist-upgrade' because we're dealing with Debian testing. This may sometimes remove a package or replace a package but that follows the maintainers decisions.
'apt-get upgrade' only upgrades all installed packages but that may disorganize the system with time.

You already removed wicd and that's fine but that pop-up may have to do with it being set in Icewm startup file (~/.icewm/startup).

You may want to do an 'apt-get autoclean' to clear you packages cache from the old packages' versions.
Posts: 13
keithpeter
Joined: 04 Jan 2010
#7
secipolla wrote:About the pale blue login, it's because slim (the login manager) was updated and it was set to its default theme.
Thanks secipolla, and for the dist-upgrade reminder. I must think 'testing' and not 'stable'. I'll have another go and see what happens.

I did the apt-get autoclean thing when apt-get suggested it.
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#8
keithpeter wrote:I did the apt-get autoclean thing when apt-get suggested it.
Ain't you referring to 'apt-get autoremove'? (this uninstalls packages not needed anymore. 'apt-get autoclean' removes old versions from the packages cache)
Posts: 13
keithpeter
Joined: 04 Jan 2010
#9
secipolla wrote: Ain't you referring to 'apt-get autoremove'? (this uninstalls packages not needed anymore. 'apt-get autoclean' removes old versions from the packages cache)
Yup, I meant the autoremove.

I've had problems with apt-get update then apt-get dist-upgrade from a freshly installed Antix. There are a lot of confirmation boxes about various configuration files being different from the one installed (see example below). I've tried using both sets of options on different re-installs, all result in a system that boots but fails to reach the log-in screen.

I can successfully do an apt-get update and apt-get upgrade.

Have I misunderstood how to keep a given release of antix up to date with changes and security updates &c?

I'd like to persevere with this install as it has a lot of the right applications in it. Thanks all.
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#10
For the mepis network and ejecrcd errors:
anticapitalista wrote:To add about the lsb errors.
Following Debian Testing, the upgrade now wants users to use Dependency Based Boot via insserv (it is faster).
This happens automatically on upgrade, except it doesn't on antiX-M8.2 (and earlier) because of the lsb errors in ejecrcd and mepis-network.

Solution 1:
1. Remove /etc/init.d/ejecrcd file as root with the file manager and remove mepis-network (apt-get purge mepis-network)
2. In a rooot terminal dpkg-reconfigure sysv-rc and choose yes.

Solution 2:
1. In /etc/init.d edit the ejecrcd file to look like this and rename in ejectcd. Same with mepis-network
2. In a rooot terminal dpkg-reconfigure sysv-rc and choose yes.

Code: Select all

#!/bin/sh
### BEGIN INIT INFO
# Provides:          ejectcd
# Required-Start:    
# Required-Stop:     
# Default-Start:     
# Default-Stop:      
# Description: Starts ejectcd
# short-description: ejectcd
### END INIT INFO

# Try to cache everything we're likely to need after ejecting.  This
# is fragile and simple-minded, but our options are limited.
cache_path() {
    path="$1"

    if [ -d"$path" ]; then
        find"$path" -type f | xargs cat > /dev/null 2>&1
    elif [ -f"$path" ]; then
        if [ -x"$path" ]; then
            if file"$path" | grep -q 'dynamically linked'; then
                for lib in $(ldd"$path" | awk '{ print $3 }'); do
                    cache_path"$lib"
                done
            fi
        fi
        cat"$path" >/dev/null 2>&1
    fi
}

# Do if running from CD
if [ -e /proc/sys/kernel/real-root-dev ]; then
case"$(cat /proc/sys/kernel/real-root-dev 2>/dev/null)" in 256|0x100) 
  for path in $(which halt) $(which reboot) /etc/rc?.d /etc/default; do
    cache_path"$path"
  done
  # just do it
  # this is only relavent when booted from CD
  # otherwise /cdrom never exists
  eject -p -m /cdrom >/dev/null 2>&1
  sleep 5
  ;;
esac
fi

exit 0

Code: Select all

#!/bin/bash
### BEGIN INIT INFO
# Provides:          mepis-network
# Required-Start:    
# Required-Stop:    
# Default-Start:     
# Default-Stop:      
# Description: Starts mepis-network configuration 
# short-description: mepis-network configuration
### END INIT INFO

PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin"
export PATH

umask 022

# Ignore these signals: INT, TERM, SEGV
trap"" 2 3 11

# No kernel messages while probing modules
echo"0" > /proc/sys/kernel/printk

# Read in boot parameters
CMDLINE="$(cat /proc/cmdline)"

isbootparam(){
case"$CMDLINE" in *$1*) return 0;; esac
return 1
}
NDIS="yes"
if [ -f /etc/default/mepis-network ]; then
  . /etc/default/mepis-network
fi
if ["$NDIS" ="yes" ]; then
 if ! isbootparam"nonet"; then
  if ! isbootparam"nondis"; then
   modprobe ndiswrapper
  fi
 fi
fi
 # workaround: intel 536 driver has no module_device_table so it must be started manually
 /usr/bin/lspci | /bin/grep '536EP' >/dev/null 2>&1
 if [ $? = 0 ]; then
  /sbin/modprobe Intel536 >/dev/null 2>&1
 else
  # workaround: alsa sl modem needs setup delay before starting daemon
  # modem link will fail if another modem got it first
  /bin/lsmod | /bin/grep -e 'snd_intel8x0m' -e 'snd_via82xx_modem' -e 'snd_atiixp_modem' >/dev/null 2>&1
  if [ $? = 0 ]; then
   ln -s /dev/ttySL0 /dev/modem >/dev/null 2>&1
   /usr/sbin/slmodemd --alsa --country=USA >/dev/null 2>&1 &
  fi
 fi

echo"6" > /proc/sys/kernel/printk

# Re-enable signals
trap 2 3 11

exit 0

Then you may do an

Code: Select all

dpkg-reconfigure insserv
to enable the new way Debian boots.

Besides that you may eventually get some firmware-linux related errors too. To solve that:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post13754.html?hilit=firmware#p13754"
linktext was:"antix.freeforu ms.org/post13754.h ... are#p13754"
====================================
" onclick="window.open(this.href);return false

The above issues have been resolved in the new (still beta) release.

The general rule (unless you know what you're doing) is to accept the new configuration files that come with the updates (even though the default is set to 'N').
If I remember well there are some exceptions for packages modaliases and libsmpbase, but maybe that's only for Debian unstable.

As for the graphic environment not coming, I can't say for sure. But you should keep up with 'apt-get dist-upgrade', that's the proper way of doing things (but then it shows when some package or repository doesn't comply with the standards)
Posts: 13
keithpeter
Joined: 04 Jan 2010
#11
secipolla wrote:
The above issues have been resolved in the new (still beta) release.

The general rule (unless you know what you're doing) is to accept the new configuration files that come with the updates (even though the default is set to 'N').
If I remember well there are some exceptions for packages modaliases and libsmpbase, but maybe that's only for Debian unstable.

As for the graphic environment not coming, I can't say for sure. But you should keep up with 'apt-get dist-upgrade', that's the proper way of doing things (but then it shows when some package or repository doesn't comply with the standards)
Hello secipolla

Thanks for this research.

There were about 10 of these errors when I tried the dist-upgrade. I'll do a 'simulation' of the upgrade and try to track down each one as you have done with the dependency based boot example.

I tried saying Y to all these errors, but ended with the system not reaching log in or being able to respond to keyboard or mouse, so I tried the opposite logic which leaves me with a system that will start up and which generates no errors with the apt-get upgrade command.

This is all very educational!