Upgrade kernel from 2.67?
Hi and happy new year to everyone, I have a question regarding the possibility of upgrading the kernel on my debian sarge machine. I see from the synaptic manager that what I have installed is kernel-image-2.6.7-1-386, and that there is another available, kernel-image-2.6.9-1-386. Can anyone tell me if it is a good option to install this? When I had RedHat 9.0 there were periodic upgrades available for the kernel and I implemented them all, automatically. My machine has the following partitions: Directory Type /dev/hdh2 / ext3 /dev/hdh5 /usrext3 /dev/hdh6 /varext3 /dev/hdh7 /tmpext3 /dev/hdh8 /home ext3 tmpfs /dev/shmtmpfs MTIA for any help, Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade kernel from 2.67?
On Sun, 02 Jan 2005 00:20:10 +0100, Agustin wrote: > Hi and happy new year to everyone, > > I have a question regarding the possibility of upgrading the kernel on my > debian sarge machine. I see from the synaptic manager that what I have > installed is kernel-image-2.6.7-1-386, and that there is another > available, kernel-image-2.6.9-1-386. Can anyone tell me if it is a good > option to install this? When I had RedHat 9.0 there were periodic upgrades > available for the kernel and I implemented them all, automatically. My > machine has the following partitions: > > Directory Type > > /dev/hdh2 / ext3 > /dev/hdh5 /usrext3 > /dev/hdh6 /varext3 > /dev/hdh7 /tmpext3 > /dev/hdh8 /home ext3 > tmpfs /dev/shmtmpfs > > MTIA for any help, > > Agustin Actualizando mi post de anoche: Cuando intento instalar el kernel nuevo me aparece un fallo porque en hdh2 no hay espacio. No se como liberar espacio en hdh2- pensà probar a redimensionar con qtparted pero no tengo esa opciÃn para esa particiÃn. Log sigue: [EMAIL PROTECTED]:~$ su Password: DEBBIE:/home/agustin# apt-get install kernel-image-2.6.9-2-386 Leyendo lista de paquetes... Hecho Creando Ãrbol de dependencias... Hecho Paquetes sugeridos: lilo kernel-doc-2.6.9 kernel-source-2.6.9 Se instalarÃn los siguientes paquetes NUEVOS: kernel-image-2.6.9-2-386 0 actualizados, 1 se instalarÃn, 0 para eliminar y 623 no actualizados. 3 no instalados del todo o eliminados. Se necesita descargar 0B/14,2MB de archivos. Se utilizarÃn 42,4MB de espacio de disco adicional despuÃs de desempaquetar. (Leyendo la base de datos ... 122084 ficheros y directorios instalados actualmente.) Desempaquetando kernel-image-2.6.9-2-386 (de .../kernel-image-2.6.9-2-386_2.6.9-4_i386.deb) ... You are attempting to install a kernel image (version 2.6.9-2-386) However, the directory /lib/modules/2.6.9-2-386 still exists. If this directory belongs to a previous kernel-image-2.6.9-2-386 package, and if you have deselected some modules, or installed standalone modules packages, this could be bad. However, if this directory exists because you are also installing some stand alone modules right now, and they got unpacked before I did, then this is pretty benign. Unfortunately, I can not tell the difference. If /lib/modules/2.6.9-2-386 belongs to a old install of kernel-image-2.6.9-2-386, then this is your last chance to abort the installation of this kernel image (nothing has been changed yet). If this directory is because of stand alone modules being installed right now, or if it does belong to an older kernel-image-2.6.9-2-386 package but you know what you are doing, and if you feel that this image should be installed despite this anomaly, Please answer n to the question. Otherwise, I suggest you move /lib/modules/2.6.9-2-386 out of the way, perhaps to /lib/modules/2.6.9-2-386.old or something, and then try re-installing this image. Do you want to stop now? [Y/n]n dpkg: error al procesar /var/cache/apt/archives/kernel-image-2.6.9-2-386_2.6.9-4_i386.deb (--unpack): fallà en buffer_write(fd) (8, ret=-1): error en dpkg-deb durante `./boot/config-2.6.9-2-386': No queda espacio en el dispositivo dpkg-deb: el subproceso paste fue terminado por la seÃal (TuberÃa rota) Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /boot/vmlinuz-2.6.9-1-386 Found kernel: /boot/vmlinuz-2.6.7-1-386 Updating /boot/grub/menu.lst ... done Se encontraron errores al procesar: /var/cache/apt/archives/kernel-image-2.6.9-2-386_2.6.9-4_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) DEBBIE:/home/agustin# O sea, me pone una nueva entrada en Grub, pero ha sido una instalaciÃn fallida. Por donde sigo :) Gracias Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade kernel from 2.67?
On Sun, 02 Jan 2005 19:20:11 +0100, Agustin wrote: > On Sun, 02 Jan 2005 00:20:10 +0100, Agustin wrote: > >> Hi and happy new year to everyone, >> >> I have a question regarding the possibility of upgrading the kernel on my >> debian sarge machine. I see from the synaptic manager that what I have >> installed is kernel-image-2.6.7-1-386, and that there is another >> available, kernel-image-2.6.9-1-386. Can anyone tell me if it is a good >> option to install this? When I had RedHat 9.0 there were periodic upgrades >> available for the kernel and I implemented them all, automatically. My >> machine has the following partitions: >> >> Directory Type >> >> /dev/hdh2/ ext3 >> /dev/hdh5/usrext3 >> /dev/hdh6/varext3 >> /dev/hdh7/tmpext3 >> /dev/hdh8/home ext3 >> tmpfs/dev/shmtmpfs >> >> MTIA for any help, >> >> Agustin > > Actualizando mi post de anoche: > > Cuando intento instalar el kernel nuevo me aparece un fallo porque en hdh2 > no hay espacio. No se como liberar espacio en hdh2- pensà probar a > redimensionar con qtparted pero no tengo esa opciÃn para esa particiÃn. > > Log sigue: > > [EMAIL PROTECTED]:~$ su > Password: > DEBBIE:/home/agustin# apt-get install kernel-image-2.6.9-2-386 Leyendo > lista de paquetes... Hecho > Creando Ãrbol de dependencias... Hecho Paquetes sugeridos: > lilo kernel-doc-2.6.9 kernel-source-2.6.9 > Se instalarÃn los siguientes paquetes NUEVOS: > kernel-image-2.6.9-2-386 > 0 actualizados, 1 se instalarÃn, 0 para eliminar y 623 no actualizados. 3 > no instalados del todo o eliminados. Se necesita descargar 0B/14,2MB de > archivos. Se utilizarÃn 42,4MB de espacio de disco adicional despuÃs de > desempaquetar. (Leyendo la base de datos ... 122084 ficheros y directorios > instalados actualmente.) Desempaquetando kernel-image-2.6.9-2-386 (de > .../kernel-image-2.6.9-2-386_2.6.9-4_i386.deb) ... You are attempting to > install a kernel image (version 2.6.9-2-386) However, the directory > /lib/modules/2.6.9-2-386 still exists. If this directory belongs to a > previous kernel-image-2.6.9-2-386 package, and if you have deselected some > modules, or installed standalone modules packages, this could be bad. > However, if this directory exists because you are also installing some > stand alone modules right now, and they got unpacked before I did, then > this is pretty benign. Unfortunately, I can not tell the difference. > > If /lib/modules/2.6.9-2-386 belongs to a old install of > kernel-image-2.6.9-2-386, then this is your last chance to abort the > installation of this kernel image (nothing has been changed yet). > > If this directory is because of stand alone modules being installed right > now, or if it does belong to an older kernel-image-2.6.9-2-386 package but > you know what you are doing, and if you feel that this image should be > installed despite this anomaly, Please answer n to the question. > > Otherwise, I suggest you move /lib/modules/2.6.9-2-386 out of the way, > perhaps to /lib/modules/2.6.9-2-386.old or something, and then try > re-installing this image. > Do you want to stop now? [Y/n]n > dpkg: error al procesar > /var/cache/apt/archives/kernel-image-2.6.9-2-386_2.6.9-4_i386.deb > (--unpack): > fallà en buffer_write(fd) (8, ret=-1): error en dpkg-deb durante > `./boot/config-2.6.9-2-386': No queda espacio en el dispositivo > dpkg-deb: el subproceso paste fue terminado por la seÃal (TuberÃa rota) > Searching for GRUB installation directory ... found: /boot/grub . Testing > for an existing GRUB menu.list file... found: /boot/grub/menu.lst . > Searching for splash image... none found, skipping... Found kernel: > /boot/vmlinuz-2.6.9-1-386 Found kernel: /boot/vmlinuz-2.6.7-1-386 Updating > /boot/grub/menu.lst ... done > > Se encontraron errores al procesar: > /var/cache/apt/archives/kernel-image-2.6.9-2-386_2.6.9-4_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > DEBBIE:/home/agustin# > > O sea, me pone una nueva entrada en Grub, pero ha sido una instalaciÃn > fallida. Por donde sigo :) > > Gracias > > Agustin Sorry, this was meant for the Spanish-speaking forums. All the same, the question is still pertinent. I'm having difficulty upgrading the kernel because I get the message that my partition hdh2 is full, so installation is not possible. Any ideas are welcome. Regards, Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade kernel from 2.67?
On Mon, 03 Jan 2005 00:50:05 +0100, Adam Aube wrote: > Agustin wrote: > >> All the same, the question is still pertinent. I'm having difficulty >> upgrading the kernel because I get the message that my partition hdh2 is >> full, so installation is not possible. > > Free some space on hdh2 (your root partition). > > Adam Thanks, Adam. This is exactly what I want to do, but I'm not sure what I can delete or move. How will I find this out? Best regards, Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade kernel from 2.67?
On Mon, 03 Jan 2005 02:10:05 +0100, David Mandelberg wrote: > Agustin wrote: >> Thanks, Adam. This is exactly what I want to do, but I'm not sure what I >> can delete or move. How will I find this out? > You can get rid of older kernels (always keep the current one though), you can > delete old log files (in /var/log), another thing is, if /home is on the same > partition, you could compress/delete files from your home. Partition sizes and occupancy are as follows: Directory TypeSize Total Occupied /dev/hdh2 / ext3134 Mb 134 Mb /dev/hdh5 /usrext33,5 Gb 2,3 Gb /dev/hdh6 /varext31,7 Gb 972 Mb /dev/hdh7 /tmpext3294 Mb 8,1 Mb /dev/hdh8 /home ext33,6 Gb 2,5 Gb tmpfs /dev/shmtmpfs 237 Mb 0 bytes Thanks again, Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Presenting photos on CD/DVD with transitions and sound?
Hi, I am a Linux Debian user, and I am looking for an application which will enable me to prepare presentations of photos using transitions and audio, to be recorded on CD-ROM/DVD. With Windows I have successfully used software by Magix, which is ideal for a beginner like me, but I need something that will run under Linux. Does anyone have any sugggestion? MTIA AgustÃn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Working out Grub
Hi folks, My question is quite long, and addresses (for me) a fairly complex issue, so I have to thank you in advance for your patience. Here goes: I have two 80 Gb hard drives, connected to the motherboard as hda and hdb; the first is NTFS partitioned, and contains an installation of XP Pro. The second has two partitions - FAT32 (hdb1) for a second instalation of XP Pro, and ext3 where I have Guadalinex rc5 (a Junta de Andalucia version of debian woody. Apart from this I have a Promise Technology Ultra133 TX2 card to which two more hard drives are connected as primary master (hde1)and secondary slave (hdh). The first of these has a W98 installation, while the second is has a 7Gb partition for another more modern version of Guadalinex (hdh1). The rest of this hard drive was partitioned on installation of Debian Sarge a few weeks ago (hdh2, hdh5, hdh5, hdh7, hdh8). At the moment, if I want to start up one of the systems from hda1, hdb1 or hdb2 I make sure that BIOS shows hd0 as first device. The selection screen generated by my first Guadalinex appears and all is well. Except that this system does not see my Promise card or the two HDs connected there. If I want to boot Debian Sarge (my favourite), Guadalinex (new version) or W98, I change first device in BIOS to SCSI, and a different start-up menu appears, from here I can boot the systems located on hde1, hdh1 and hdh2. What I would like to do is to edit this last grub so that I can boot the other three systems from the same menu without messing around with BIOS so much, but here I've drawn a blank. For the newest Guadalinex the new grub says: Ruta a la imagen del nÃcleo: /boot/vmlinuz-2.6.5 Dispositivo del sistema de archivos raÃz: /dev/hdh1 Ruta a la imagen initrd: ParÃmetros:root=/dev/hdh1 whereas from the old grub, and for the older version of Guadalinex on hdb2: Ruta a la imagen del nÃcleo: /boot/vmlinuz-2.4.23-ck1 Dispositivo del sistema de archivos raÃz: /dev/hdb2 Ruta a la imagen initrd: ParÃmetros:root=/dev/hdb2 Excuse my not having translated the spanish terms. My question is: What should I put in the new grub in order to boot the linux I have on hdb2 (and also the two Xps and a Damn Small Linux yet to be put in). On the subject of grub, is it risky for me to play around with grub2, or should I stick with present grub legacy. Thanks for reading this long post and for any help supplied. Regards, Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Firefox Install
On Wed, 29 Sep 2004 21:20:13 +0200, Andrea Vettorello wrote: > I doubt firefox from firefox.org will run on Woody (different glibc, > gtk2..), anyway i will start running "firefox-installer", something > like "sh firefox-installer" or chmod it +x and the running it... > > > Andrea > > P.S. you'll better find some backports for Woody on apt-get.org Hi, Excuse my butting in. I guess I did the wrong thing,then, cos I am running sarge and couldn't see how to update 0.93 to 1.0 Preview using dpkg so I downloaded firefox-1.0PR-i686-linux-gtk2+xft.tar.gz and decompressed it to a new folder in the home directory. I then navigated to the firefox starter and ran the browser - everything worked fine, though it is applying all the extensions I installed for v 0.93, and accesses my bookmarks list perfectly well. Only thing is, if I click on the old access to firefox version 0.93 runs, which worries me because of possible issues regarding having two installations of firefox (or was that only with the earlier versions). Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question re: removing all traces of Windows ME OS
On Mon, 04 Oct 2004 20:10:25 +0200, Andrea Vettorello wrote: > - Original Message - > From: Chris Moffa <[EMAIL PROTECTED]> Date: Mon, 4 Oct 2004 13:25:14 > -0400 > Subject: question re: removing all traces of Windows ME OS To: > [EMAIL PROTECTED] > > [...[ > >> What's the protocol for removing all traces of Windows ME? How's about >> good old "format C:\?" Whatever the protocol, once the OS is removed >> will the computer boot from the Debian CD and allow me to install it? > > If you are going to install Debian, during the installation process > you'll be asked if you want to erase the content of your HD, so you > don't need to do it before. > >> Sorry to ask such a broad question. If the answer is too involved to >> reply by email, can you suggest a web site? > > On the Debian home page you'll find an installation guide > (http://www.debian.org/releases/stable/installmanual) for Woody, the > latest Debian stable version released. The new stable, Sarge, should be > released real soon now. A lot of people have found Sarge to works well, > but can still have some rough egdes... > > > Andrea Hi, Follow Andrea's advice; it's good. My experience: I recently installed Debian (sarge) on my multi-boot. I downloaded a 113 MiB image named sarge-i386-netinst.iso from here: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/ and I put it on a CD-Rom. I booted from CD-Rom and let it run the installation setup. This put a minimal installation on the hard-drive following the partitioning and formatting steps that Andrea has already mentioned. That partitioning effectively takes care of any remnants of your MS system, particularly as the original partion will be trashed and replaced by several new ones - mine put in /root /home /tmp /var /dev/shm and /usr all on different partitions. I understand that the theory behind this is that if my kernel goes into a panic I should be able to restitute the system without having to touch my other partitions (maybe). In my case I had a router connected to my computer which was immediately detected by the installer, on reboot, which simplified the rest of the installation, as all I had to do was choose what kind of setup I wanted. Took quite a while to finish the installation but I have found it to be unbeatable regarding freeze-ups etc. I can imagine that other users, with different hardware from mine, might prefer to use Woody, but I felt that I needed as much compatibility as possible. I'm very happy with sarge, for now, but if I were you I'd check carfully to see which build and version is appropriate for the hardware on your laptop. Good luck Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question re: removing all traces of Windows ME OS
On Mon, 04 Oct 2004 20:10:25 +0200, Andrea Vettorello wrote: > - Original Message - > From: Chris Moffa <[EMAIL PROTECTED]> Date: Mon, 4 Oct 2004 13:25:14 > -0400 > Subject: question re: removing all traces of Windows ME OS To: > [EMAIL PROTECTED] > > [...[ > >> What's the protocol for removing all traces of Windows ME? How's about >> good old "format C:\?" Whatever the protocol, once the OS is removed >> will the computer boot from the Debian CD and allow me to install it? > > If you are going to install Debian, during the installation process > you'll be asked if you want to erase the content of your HD, so you > don't need to do it before. > >> Sorry to ask such a broad question. If the answer is too involved to >> reply by email, can you suggest a web site? > > On the Debian home page you'll find an installation guide > (http://www.debian.org/releases/stable/installmanual) for Woody, the > latest Debian stable version released. The new stable, Sarge, should be > released real soon now. A lot of people have found Sarge to works well, > but can still have some rough egdes... > > > Andrea Hi, Follow Andrea's advice; it's good. My experience: I recently installed Debian (sarge) on my multi-boot. I downloaded a 113 MiB image named sarge-i386-netinst.iso from here: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/ and I put it on a CD-Rom. I booted from CD-Rom and let it run the installation setup. This put a minimal installation on the hard-drive following the partitioning and formatting steps that Andrea has already mentioned. That partitioning effectively takes care of any remnants of your MS system, particularly as the original partion will be trashed and replaced by several new ones - mine put in /root /home /tmp /var /dev/shm and /usr all on different partitions. I understand that the theory behind this is that if my kernel goes into a panic I should be able to restitute the system without having to touch my other partitions (maybe). In my case I had a router connected to my computer which was immediately detected by the installer, on reboot, which simplified the rest of the installation, as all I had to do was choose what kind of setup I wanted. Took quite a while to finish the installation but I have found it to be unbeatable regarding freeze-ups etc. I can imagine that other users, with different hardware from mine, might prefer to use Woody, but I felt that I needed as much compatibility as possible. I'm very happy with sarge, for now, but if I were you I'd check carfully to see which build and version is appropriate for the hardware on your laptop. Good luck Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [R] Announcement: Automatic ATLAS support under Debian GNU/Linux
What about other distributions? Can ATLAS be used with, i.e., SuSe? Thanks Agus Dr. Agustin Lobo Instituto de Ciencias de la Tierra (CSIC) Lluis Sole Sabaris s/n 08028 Barcelona SPAIN tel 34 93409 5410 fax 34 93411 0012 [EMAIL PROTECTED]
Re: Unable to disable IDE DMA on boot
Hi, Johannes, I had to deal with this problem too and got some experience on it Then I tried to create a custom initrd image using "mkinitrd" from "initrd-tools" (0.1.56). I noticed that the default "/sbin/init" script will try to pass the IDE options specified on the kernel command line to "ide-mod" module. However, this module has been renamed to "ide-core" so That will be fixed in one of initrd-tools next uploads (see #240734). In the meantime you can use alias ide-mod ide-core but I suggest you to do the thing below. By the way, even with a fixed initrd-tools there is a problem about how 2.6 kernel passes options to the modules (see #240886 for details) so there will be problems with 2.6. Then I added into "/etc/mkinitrd/modules" the line (also tried other variations above) ide-core ide=nodma ide-core options="ide=nodma" This is the expected format (see ide.txt) and this is the way I suggest you (ide kernel command line boot options are grouped together by initrd-tools and prefixed by options). This will not work in 2.6 if more than one ide option is there, because of the above mentioned bug, but will casually work if is just as above. I then created the new custom initrd image using just "mkinitrd -o /boot/myinitrd.img", updated the "/initrd.img" link and ran lilo. However, this did not help at all. The DMA was still enabled. I did my tests keeping a safe boot image with DMA disabled from which I can always boot from, and doing my tests in an initrd image having DMA enabled by default. To make sure I am doing exactly the same that is done at package installation I reconfigured the kernel-image package, e.g. # dpkg-reconfigure kernel-image-2.4.25-1-586tsc although if you are building a initrd for your running kernel your call should work. Hope this helps -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Help with setting Debian Testinf
Following https://wiki.debian.org/DebianTesting I have set the following etc/apt/sources.list file: alobo@Delia:~$ more /etc/apt/sources.list # # deb cdrom:[Official Debian GNU/Linux Live 9.4.0 xfce 2018-03-10T11:37]/ stretc h main #deb cdrom:[Official Debian GNU/Linux Live 9.4.0 xfce 2018-03-10T11:37]/ stretch main deb http://ftp.es.debian.org/debian/ testing main deb-src http://ftp.es.debian.org/debian/ testing main deb http://security.debian.org/debian-security testing/updates main #deb-src http://security.debian.org/debian-security stretch/updates main deb-src http://security.debian.org/debian-security testing/updates main # stretch-updates, previously known as 'volatile' deb http://ftp.es.debian.org/debian/ testing-updates main deb-src http://ftp.es.debian.org/debian/ testing-updates main deb http://httpredir.debian.org/debian/ testing main contrib non-free but Synaptics reports different repositories: https://www.dropbox.com/s/spwovspzu6hqrvp/Screenshot%20from%202018-07-04%2007-42-42.png?dl=0 Do I have a conflict? Is there anything else I should do to have a properly set Debian Testing system? Thanks
Re: Bug#21412: tob deletes system files
Dirk Eddelbuettel wrote:
>
>
> Please chill out a little and read the emails you got yesterday. I released
> tob_0.14-5 yesterday which added the following test
>
> cleanup ()
> {
> message 'Cleaning up.'
> # add a safety check here --edd 20 Apr 98, regarding #21412
> -> if [ "$TMPLIST" != "" -a "$FILELIST" != "" ] ; then
> $RM -f $TMPLIST* $FILELIST*
> fi
> postcommand
> }
>
>
Just one minor comment, $TMPLIST and $FILELIST void means problems in
/etc/tob/tob.rc, that can be caused by an incorrect local adaptation.
May be it would worth to add a warning message to the if, and even exit
tob if that situation is found (perhaps this last be too drastical),
something like
cleanup ()
{
message 'Cleaning up.'
# add a safety check here --edd 20 Apr 98, regarding
#21412
if [ "$TMPLIST" != "" -a "$FILELIST" != "" ] ; then
$RM -f $TMPLIST* $FILELIST*
else
message 'Warning: Empty \$TMPLIST or \$FILELIST. Check
your /etc/tob/tob.rc'
# exit # In this case change above line to error:
fi
postcommand
}
Regards,
--
=
Agustín Martín Domingo, Dpto. de Física, ETS Arquitectura Madrid,
(U. Politécnica de Madrid) tel: +34 +1 3366536, Fax: +34 +1 3366554,
email:[EMAIL PROTECTED], http://corbu.aq.upm.es/~agmartin/welcome.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
