antiX-forum

Fine!
There was two GPL files, one plain text and the other html but I saved as full web page and it came with a folder with the images.
Maybe just leave the plain text.
I could have saved the web page html only but although Dillo did show it of course, it wouldn't stop loading because it couldn't find the image files. So it was just a matter of removing the image links in the page but since I don't know about that I didn't do it.

Summary: next time I'll upload a simple html file and do some tests to remove the image link from the code.

Secipolla:

Here is the result: main dialog and help, and a chunk of code:

'Persistence' should be 'Persistência' but maybe it didn't get translated because of the accent?
Also the buttons.. are they on the script or do they depend on antix2usb?
antix2usb will be translated for the next version of antiX (anti put it in Launchpad and it's already translated).

This is a new version, (pre-release?)

Bug fixes, improvements:

- when the persistence option is checked, cheatcodes:
homefs=UUID-of-antiXData-partition rootfs=UUID-of-antiXData-partition
are appended in menu.lst
- localisation: the environment variable LANG is checked; for LANG=fr_FR.UTF-8 for instance, lang=fr is appended silently to the kernel line; seems to work for fr, secipolla will try it for pt_BR
- portuguese (brazilian added)
- a dialog would pop up when the process is completed; the main dialog should then close... this relies on the presence of the logfile under /tmp/antix2usb.log... Do not forget to update **both** the gui.sh and the sh script
- there are two (not documented) options for antix2usb-gui.sg
-d : verbose output (debug)
-t : = for test only, verbose output, plus: iso-or-whatever-you-choose-file will not be writen to the device (saves time), but this will format, install grub,.. initrd

- both partitions are ext2

Do not use this tar file. Please see next posts

Here is all the output from the treminal. Also when it graphically finishes, succesfully I may add, the terminal is still on hold.

Code: Select all

(gtkdialog:6192): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
################# DO_DEBUG= #####################
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 630: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected

** (roxterm:6446): CRITICAL **: Error connecting to dbus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 6446: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3338.
This is normally a bug in some application using the D-Bus library.
process 6446: arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5297.
This is normally a bug in some application using the D-Bus library.

** (roxterm:6446): CRITICAL **: Unable to install D-BUS message filter: <unknown>

(roxterm:6446): Vte-CRITICAL **: vte_terminal_set_background_tint_color: assertion `color != NULL' failed
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
EXIT="OK"
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected
/usr/local/bin/antix2usb-gui.sh: line 254: [: =: unary operator expected



OK eriefisher

In a last minute change, I decided to pass the '-d' option to the antix2usb.sh script; to achieve this, I must not define the DO_DEBUG variable at the beginning of the script... and an undefined $DO_DEBUG is not the empty string "$DO_DEBUG".
Thanks, fixed

On my system, I do not see any dbus error
But I got:

(roxterm:7010): Vte-CRITICAL **: vte_terminal_set_background_tint_color: assertion `color != NULL' failed
execute_command: status: Failure

... I would prefer to have a simple xterm (as I got on Mepis)

Attached file.

lagopus, that bug in roxterm can be fixed when you open roxterm as root and then
Preferences->Edit Current Color Scheme->
Click on 'Set text and background colors'.

This is fixed for antiX-M8.5, so no need to worry about it.

I didn't test it because I don't have a usb key with me. But I fixed the translation (I had replaced 'fr' for 'br' and that replaced a couple of 'frame' for 'brame' and I also better translated one sentence).

I see that you didn't put in the license text in Portuguese so i didn't put it as well but if you think you'ld like to figure it:

#
# Este programa é um software livre; você pode redistribuí-lo e/ou
# modificá-lo dentro dos termos da Licença Pública Geral GNU como
# publicada pela Fundação do Software Livre (FSF); na versão 2 da
# Licença ou (à sua opção) qualquer versão posterior.
#
# Este programa é distribuido na esperança de que possa ser útil,
# mas SEM NENHUMA GARANTIA; nem mesmo uma garantia implícita de
# ADEQUAÇÂO a qualquer MERCADO ou APLICAÇÃO EM PARTICULAR. Veja a
# Licença Pública Geral GNU para maiores detalhes.
#
# Você deve ter recebido uma cópia da Licença Pública Geral GNU
# junto com este programa; se não, escreva para a Fundação do Software
# Livre(FSF) Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
#
# Nos sistemas Debian GNU/Linux o texto da licença GPL se encontra
# em /usr/share/common-licenses/GPL.
#
# A tradução oficial para o português do Brasil pode ser encontrada
# online em http://www.fsfla.org/svnwiki/trad/GPLv3
#

Last update

Now the antix2usb-gui.sh is started as simple used.
After selecting the iso, clicking Apply, you are prompted for the root password.

Technical note: the bash function execute_command() opens a roxterm which executes "gtksu -u root ... antix2usb.sh"
(found no option for setting the roxterm at the center of the screen, set position for my 1024x600 screen...)

Download the attached archive. Then:
1) Copy the downloaded file to a temporary directory, and untar the file:

yves@montcalm:~/temp$ cp ~/Downloads/antix2usb-0.2.2.tgz .
yves@montcalm:~/temp$ ls
antix2usb-0.2.2.tgz
yves@montcalm:~/temp$ tar zxvf antix2usb-0.2.2.tgz
antix2usb-0.2.2/
antix2usb-0.2.2/README
antix2usb-0.2.2/antix2usb-gui.sh
antix2usb-0.2.2/install.sh
antix2usb-0.2.2/antix2usb.sh

2) Change working directory and run the install.sh script as root:

yves@montcalm:~/temp$ cd antix2usb-0.2.2/
yves@montcalm:~/temp/antix2usb-0.2.2$ ./install.sh
Root privileges are required to install antix2usb scripts.
yves@montcalm:~/temp/antix2usb-0.2.2$ su
Password :
root@montcalm:/home/yves/temp/antix2usb-0.2.2# ./install.sh
This will install antix2usb scripts in /usr/local/bin
Continue (y|n): y
antix2usb scripts installed to /usr/local/bin

3) Exit and check the installation:

root@montcalm:/home/yves/temp/antix2usb-0.2.2# exit
yves@montcalm:~/temp/antix2usb-0.2.2$ which antix2usb-gui.sh
/usr/local/bin/antix2usb-gui.sh
yves@montcalm:~/temp/antix2usb-0.2.2$ antix2usb-gui.sh -v
antix2usb-gui.sh v0.2.2 2009-11-16
yves@montcalm:~/temp/antix2usb-0.2.2$ antix2usb.sh
bash: /usr/local/bin/antix2usb.sh: Permission non accordée

You will now be able to start antix2usb-gui.sh

I added an entry in ~/.icewm/menu, something like:

menu "Outils" folder {
prog "antix2usb" - antix2usb-gui.sh
...
...
}

Hope this will work for you.
Some error cases are not cleanly handled (key already mounted,...)

Here is the tar-file
(!!! tgz files are not allowed, replace .tgz by .tar.gz)

I feel like Homer Simpson Today. I was in a Puppy Linux State of Mind and thought that this script and feature was the equivalent of a pup_save_sfs for Antix Live USB.

DOH!

I can be thick headed at times. No wonder I confuse the hell out of you guys. Now it is starting to get through my thick skull that this is a way to make a installed version of Antix to USB . But with my batting average lately. I aint even sure I am right in thinking that either. I need to read up a few times in a row for things to sink in sometimes.
Just give me some time to sort out things in my brain a little. I will get there eventually.

Ps. It doesn't help when these netbook small screens are so friggin small and hard to read. And yeah, I got image zoom(firefox) and Opera 10 with zoom feature. But I was diagnosed with cataracts which I am working on to get removed.

lagopus,

I tested out the latest script and there are problems.

1. If you use the script from a menu (as user), when roxterm opens and tells you to be root
user it closes before you have time to do anything.
2. If antix2usb-gui.sh is opened as root (wrong thing to do) and you do not have a usb device
connected, you cannot cancel. Once the stick is inserted and detected, cancel works.

Running from a terminal, these errors are reported.

Code: Select all

$ antix2usb-gui.sh
/usr/local/bin/antix2usb-gui.sh: line 840: /tmp/antix2usb.pid: Permission denied
antiX@mepis1:~$ /usr/local/bin/antix2usb-gui.sh: line 644: kill: (12308) - No such process


Ok I will check these two points:

1. If you use the script from a menu (as user), when roxterm opens and tells you to be root
user it closes before you have time to do anything.
2. If antix2usb-gui.sh is opened as root (wrong thing to do) and you do not have a usb device
connected, you cannot cancel. Once the stick is inserted and detected, cancel works.

Point 1: I suspect where the problem lies... in fact I don't know how it can work for me

About this:

Code: Select all

$ antix2usb-gui.sh
/usr/local/bin/antix2usb-gui.sh: line 840: /tmp/antix2usb.pid: Permission denied
antiX@mepis1:~$ /usr/local/bin/antix2usb-gui.sh: line 644: kill: (12308) - No such process

I think the file /tmp/antix2usb.pid has been previously writen by root, user can't overwrite it. I am not sure I can use a tmpXXX file name... (I use this to close the first instance of the shell, which starts gtkdialog)

I'll try to fix it this evening.

I apologize for the bugs.
I made last minute modifications last night before packaging... and screwed up something.

Could not repeat this error:

If you use the script from a menu (as user), when roxterm opens and tells you to be root
user it closes before you have time to do anything.

Hope this will finally work

Hey lagopus, is this likely to work on an install of debian squeeze (my main production os.)?