Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Friday, November 26, 2010

Debian -sgfxi smxi

As time permits, script documentation will be added and updated, check there now and then to see how the documentation is developing. You can also just go to the project home page, although it's usually not up to date.
For latest script options, always check with the -h option, which lists all supported options for users.
These change now and then, so make sure you know all the possible choices.
sgfxi and svmi are now sited at their own svns
sgfxi and svmi are made for Debian Sid/Testing, and mostly work in Stable as well, and should work fine as stand alone scripts in all cases. They also have more options when run alone than when fired by smxi, so check them out to see if there's something in them that might be of use to you.
sgfxi now has its own svn because it needs to become more of a standalone project, like the new inxi irc/system information script
svmi, a script to install and maintain some virtualbox and vmware components on your debian system, also has its own own svn because it needs to become more of a standalone project.

smxi and related scripts
smxi stands for a variety of things, like system maintenance, sid maintenance or sidux maintenance. The 'xi' in smxi does not stand for anything in particular, but you can make up anything you like. The name smxi does fit nicely with two stand-alone smxi modules: sgfxi, the smxi graphics installer engine script, and svmi, the smxi virtual machine installer engine script.
If you like this script, and want to donate something, please feel free to do so using the black/yellow "Make a Donation" link above. Donations of any size are very much appreciated, and help keep my systems running, as well as offsetting some of the expenses I incure hosting this stuff.
Debian, sidux, and other Debian derived distros, and smxi
If you're looking for a fast, cutting edge distro, try sidux. Sidux is a fast, clean Free Desktop built on Debian Sid.
smxi is a general utility script that handles the standard system upkeep for Debian Sid (and Sid based, distros like sidux), Debian Testing, and Debian Stable - kernel installs, dist-upgrade/upgrade, package installs, cleanup, and graphics install. Has full logging, and will create logs on error of key parts. For non sidux systems, like Debian, you can select whether to use aptitude or apt-get, as well as dist-upgrade or upgrade, as smxi defaults when you first start the script. Source
smxi with Linux Mint Debian Edition.
32 bit on EeePC 1000HE.
Did user login and then sudo -s
Could not get wireless network to start, it had been working in GUI before I did ctrl-alt-F1, so I quit smxi and plugged in a cable.
Then reran smxi from the prompt.
It started fine.
I picked Liquorix sources, aptitude and full-upgrade and just followed along and did an update.
Tons of updates, but it was a fresh (version 1) install from a DVD so not too surprising.
I got a bunch of warnings from insserve about mint missing LSB tags and overrides and finally "udev active, skipping device node creation". then "inserve:warning: script 'K01mintsystem' missing LSB tags and overrides" followed by "inserve:warning: script 'mintsystem' missing LSB tags and overrides" then it hung, I waited for about five minutes to confirm the freeze, there was no disk activity.
Hard rebooted after ctrl-alt-del shutdown hung too.
Did a "sudo dpkg --configure -a" from the "sudo -s" command prompt and everything completed with continued warnings about 'K01mintsystem' and 'mintsystem'.
I reran smxi and it breezed throught the now empty upgrade and I picked "kernel options" and the apt kernel and aptitude informed me that I had to install a bunch of what looked like unrelated gnome and some qt4 stuff not sure why but it all installed without complaint then the Liquorix Kernel 2.6.35-6 came up and installed fine.
I then went to graphics and got an xorg.conf installed and reinstalled the Intel driver.
Rebooted with the Liquorix kernel and thus far everything seems to be working fine.
Maybe just a bad night when the stars didn't quite align, maybe I should have selected apt-get instead of aptitude.

No comments: