[Cooker] Qmail-Scanner 0.96 and Perl 5.6 Problem under Mandrake 8.0
Qmail-scanner-general/Cooker readers,
It seems that qmail-scanner is not a perl 5.6 fan ! As far as I can see
the tainted mode is more restrictive and it is causing problems :
Hit RETURN to create initial directory structure under
/var/spool/qmailscan, and install qmail-scanner-queue.pl under /usr/bin:
X-Qmail-Scanner-0.96: cannot open for write
/var/spool/qmailscan/quarantine-attachments.db.tmp - Permission denied
Insecure $ENV{ENV} while running setuid at
/usr/bin/qmail-scanner-queue.pl line 680.
Even revoving the -T is not helping ! I still get the second problem !
Hit RETURN to create initial directory structure under
/var/spool/qmailscan, and install qmail-scanner-queue.pl under /usr/bin:
X-Qmail-Scanner-0.96: cannot open for write
/var/spool/qmailscan/quarantine-attachments.db.tmp - Permission denied
/bin/rm: cannot remove directory `/var/spool/qmailscan': Permission
denied
Ok let see what strace say:
[...]
unlink("/var/tmp/qmail-scanner-root/var/spool/qmailscan/quarantine-attachments.db.tmp")
= -1 ENOENT (No such file or directory)
open("/var/tmp/qmail-scanner-root/var/spool/qmailscan/quarantine-attachments.db.tmp",
O_RDWR|O_CREAT|O_EXCL, 0640) = 3
shmat(3, 0x3, 0x2ptrace: umoven: Input/output error ) = ?
fstat64(3, {st_mode=S_IFREG|0640, st_size=0, ...}) = 0
read(3, "", 512) = 0
close(3) = 0
stat64("/root/tmp", 0xbfffed00) = -1 EACCES (Permission denied)
[...]
It seems that the file can be created (open with file descriptor 3) !
Can it be the shared memory problem or file creation !!.
The 0.95 version which was used to work perfectly under Mandrake 7.2
have the same problem, so I suspect perl 5.6 !!
My guess is that perl try to use file if shm fails but then why the hell
the direcotry is /root/tmp !! /var/tmp would make more sense to me !!
Any idea ?
To increase your testing speed here is my SRPM ;*)
(I have a patch to add support for a client of AVPDAEMON so useless for
most, the second one is to remove the -T of suidperl.)
Name: qmail-scanner
Summary:An antivirus wrapper to be used with qmail
Version:0.96
Release:1
Serial: 1
Group: Applications/Mail
Copyright: GPL
Packager: Thomas Mangin <[EMAIL PROTECTED]>
URL:http://qmail-scanner.sourceforge.net/
Source0:qmail-scanner-%{version}.tgz
Patch0: qmail-scanner-avp-%{version}.patch
Patch1: qmail-scanner-perl-%{version}.patch
BuildRoot: %{_tmppath}/%{name}-root
Requires: perl-Time-HiRes
Requires: perl-DB_File
Requires: qmail
Requires: maildrop
Requires: maildrop >= 1.3.0
Requires: tnef >= 0.16
Requires: perl > 5.5
Prereq: /sbin/service
Provides: virus-scanning-wrapper
#Conflicts: virus-scanning-wrapper
%description
Qmail-Scanner, (also known as scan4virus) is an addon that enables a
Qmail
Email server to scan all gatewayed Email for certain characteristics.
It is typically used for its anti-virus protection functions, in which
case
it is used in conjunction with commercial virus scanners.
but also enables a site to react to Email (at a server/site level)
that contains specific strings in particular headers.
It also can be used as an archiving tool for auditing or backup
purposes.
%prep
%setup -q
%patch0 -p1
%patch1 -p1
%build
rm -rf %{buildroot}
mkdir -p %{buildroot}%{_bindir}
mkdir -p %{buildroot}/var/spool/qmailscan/archives
# The configure is not very RPM friendly ..
( echo YY ; echo ) | ./configure \
--qmaildir /var/qmail \
--spooldir %{buildroot}/var/spool/qmailscan \
--bindir %{buildroot}%{_bindir} \
--admin systems-virus \
--domain legend.net.uk \
--notify all \
--lang en_GB \
--archive archives \
--redundant yes \
--log-details yes \
--add-dscr-hdrs yes \
--debug yes \
--install
%install
# Correct the path in the perl scanner
# The best would be to have an optional field for install prefix
sed_root="`echo %{buildroot} | sed -e 's/\//\//g'`"
cp %{buildroot}%{_bindir}/qmail-scanner-queue.pl
%{buildroot}%{_bindir}/scanner.tmp
cat %{buildroot}%{_bindir}/scanner.tmp | \
sed -e "s/$sed_root//g" | \
cat > %{buildroot}%{_bindir}/qmail-scanner-queue.pl
rm -f %{buildroot}%{_bindir}/scanner.tmp
%preun
test "`/etc/init.d/qmail stop 2> /dev/null`" != "impossible"
%postun
export QBIN=%{_bindir}
export SMTPD=/var/qmail/supervise/qmail-smtpd
export QMQPD=/var/qmail/supervise/qmail-qmqpd
if [ -e $SMTPD/run -o -e $QMQPD/run ]; then
if [ -e $QMQPD/run ]; then
mv $QMQPD/run $QMQPD/run.rpmsave
cat $QMQPD/run.rpmsave | \
grep -v "QMAILQUEUE" | \
cat > $QMQPD/run
chgrp qmail $QMQPD/run
chmod 7
Re: Fwd: [Cooker] File named "3"
| > > if [ "$SECURE_TMP" = "yes" -o "$SECURE_TMP" = "1" -o "$SECURE_TMP" = "YES" | > > -o "$SECURE_TMP" > 3 ];then | > > | > > and I changed it to: | > > | > > if [ "$SECURE_TMP" = "yes" -o "$SECURE_TMP" = "1" -o "$SECURE_TMP" = "YES" | > > ];then | > > | > > not sure if this is correct, but now I don't get the "3" file showing up any | > > more. | > | > You should use: | > if [ "$SECURE_TMP" = "yes" -o "$SECURE_TMP" = "1" -o "$SECURE_TMP" = "YES" | > -o "$SECURE_TMP" -gt 3 ];then | | Nope. | | if [ "$SECURE_TMP" = "yes" -o "$SECURE_TMP" = "1" -o "$SECURE_TMP" = "YES" | -o "$SECURITY" -gt 3 ];then | | The SECURITY variable must be set in /etc/sysconfig/system, or else the | test will generate an error. Nope If you want to catch "yes", "YES", "Yes" as well as "YeS" and firends the best way is : SECURE_LOW=`echo "$SECURE_TMP" | tr [A-Z] [a-z]` if [ "$SECURE_LOW" = "yes" -o "$SECURE_LOW" = "1" -o "$SECURITY" -gt 3 ]; then Ps : I have no idea what so ever of what the code look like and I guess you can add the tr to the SECURE_TMP directly. Thomas
[Cooker] Beta 2 now works with AHA-2100S
Hi Pixel, You are stars !! (You can quote me on that) I am now able to boot my supermicro server and the new Lilo is more than cute. The RAID5 array (AHA-2100S) is now working properly. You made my day. Keep on like that. (Who was the chap I must be thanking for working until 24 last night ?) Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/
Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug
Hello Pixel, As promised I done another test. This time I used a network install on our local copy of the cooker. (updated from sunsite.se the 20 th) The installer have a problem as you will be able to see on the report.bug file. Hope you will be able to figure what is wrong. Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: Pixel <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 14, 2001 1:27 PM Subject: Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug | "Thomas Mangin" <[EMAIL PROTECTED]> writes: | | > Hello. | > | > If I boot from the CDROM, the installer starts fine. | > | > If I still boot from the CDROM, install a floppy with | > a auto_inst.conf.pl file, add a Linux kickstart=floppy | > (the kickstart was done with 7.2 but I don't think it | > is important for the problem) the installer loop : | | can you send me the auto_inst.cfg? | | also, can you mail me the report.bug? | to get it: | | during install, switch to console 2, | put a fat floppy in floppy drive, | and type "bug" | | -> it will put report.bug on floppy and this file interests me :) | | | thanks, cu Pixel. | | report.bug
Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug
Hi Pixel, I will give a try and let you know. Thank you. Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: Greg Sarsons <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 15, 2001 6:39 PM Subject: Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug | Pixel wrote: | > | > "Thomas Mangin" <[EMAIL PROTECTED]> writes: | > | > > If I manually install the dpt_i2o module it works, but the module is not in | > > the list of scci device !! | > > (or the name is not clear at all) | > | > beta2 is getting ready and it has dpt_i2o module associated with your card. So | > wait until tomorrow to try it and see if it works as it should... | | can I read into this that beta2 will be out tomorrow? | |
Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug
Damn !! I am stupid ! (TM)
Thank you for your help.
Thomas
--
Thomas Mangin [EMAIL PROTECTED]
Systems Manager[EMAIL PROTECTED]
Legend Internet Ltd. http://www.legend.co.uk:/
- Original Message -
From: Pixel <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 15, 2001 12:00 PM
Subject: Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug
| "Thomas Mangin, Systems" <[EMAIL PROTECTED]> writes:
|
| > | > If I still boot from the CDROM, install a floppy with
| > | > a auto_inst.conf.pl file, add a Linux kickstart=floppy
| > | > (the kickstart was done with 7.2 but I don't think it
| > | > is important for the problem) the installer loop :
|
| it only finds hard drive "hda"
|
|
| * partitions
|
| major minor #blocks name
|
|3 0 664906 hda
|
|
| whereas your partitions give sda and sdb partitions. Remove the lines 'hd'
=>
| 'sda' and it should work.
|
|'partitions' => [
| {
|'mntpoint' => '/',
|'size' => 479745,
|'type' => 131,
|'hd' => 'sda'
| },
| [...]
| {
|'mntpoint' => '/home',
|'size' => 1084545,
|'type' => 131,
|'hd' => 'sda'
| },
| {
|'mntpoint' => '/var/qmail',
|'size' => 907137,
|'type' => 131,
|'ratio' => 9,
|'hd' => 'sdb'
| }
|
|
Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug
If I manually install the dpt_i2o module it works, but the module is not in the list of scci device !! (or the name is not clear at all) Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: Pixel <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 14, 2001 1:27 PM Subject: Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug | "Thomas Mangin" <[EMAIL PROTECTED]> writes: | | > Hello. | > | > If I boot from the CDROM, the installer starts fine. | > | > If I still boot from the CDROM, install a floppy with | > a auto_inst.conf.pl file, add a Linux kickstart=floppy | > (the kickstart was done with 7.2 but I don't think it | > is important for the problem) the installer loop : | | can you send me the auto_inst.cfg? | | also, can you mail me the report.bug? | to get it: | | during install, switch to console 2, | put a fat floppy in floppy drive, | and type "bug" | | -> it will put report.bug on floppy and this file interests me :) | | | thanks, cu Pixel. | |
Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug
Here it is. Two attachments. I just removed the encrypted password for the configuration file. Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: Pixel <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 14, 2001 1:27 PM Subject: Re: [Cooker] Mandrake 8.0 Beta 1 Installer bug | "Thomas Mangin" <[EMAIL PROTECTED]> writes: | | > Hello. | > | > If I boot from the CDROM, the installer starts fine. | > | > If I still boot from the CDROM, install a floppy with | > a auto_inst.conf.pl file, add a Linux kickstart=floppy | > (the kickstart was done with 7.2 but I don't think it | > is important for the problem) the installer loop : | | can you send me the auto_inst.cfg? | | also, can you mail me the report.bug? | to get it: | | during install, switch to console 2, | put a fat floppy in floppy drive, | and type "bug" | | -> it will put report.bug on floppy and this file interests me :) | | | thanks, cu Pixel. | | auto_inst.cfg.pl report.bug
[Cooker] Mandrake 8.0 Beta 1 Installer bug
Hello. If I boot from the CDROM, the installer starts fine. If I still boot from the CDROM, install a floppy with a auto_inst.conf.pl file, add a Linux kickstart=floppy (the kickstart was done with 7.2 but I don't think it is important for the problem) the installer loop : extracting ppa.o extracting imm.o extracting ppa.o extracting imm.o [...] Looking on the VT4, I can see that no PPA device is detected. The Hardware is a Supermicro SC840 chassi with a supermicro serverworks dual PII 866 motherboard, (with 2 CPU), a ACA backplane, 256 of RAM, a second ethernet card 3COM 100 Mb, the first is on the motherboard. I am not sure Linux is currently supporting the Adaptec AHA-2100S with RAID 5 setup for 3x18 GB HD (Seagate ST318436LC) I performed some test and this Hardware is running fine under win2k. Any comment ;*) Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: Claudio (sekko) <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; Alberto Vorano <[EMAIL PROTECTED]> Sent: Wednesday, March 14, 2001 8:19 AM Subject: Re: [Cooker] Claudio's mainboard | On Tuesday 13 March 2001 22:04, Alberto Vorano wrote: | > I beg pardon to you all | > I have a question to Claudio: | > Can you please tell me what video board did you choose for your system? | > I know that the SM board you have chosen (and that I'm interested too) | > doesn't have an AGP connector. Are by chance some 64-bit PCI boards? | > Thank you | > Alberto Vorano | | Uh... talkin' to me?! | Well... I have a dual Pentium III (MSI 6321) and a common AGP video card: | Matrox G200 4 MB SDRAM, bought 2 years ago about. Nothing recent sorry ;P | | Claudio | |
[Cooker] RPM Question
Hello, I am creating an RPM and a file have to replace the same from one of the dependency. i.e. : package-crap provides /bin/crappy package-crap-bonus provides an improved /bin/crappy compatible with the previous one but even more crappy. However I don't want to oblige the user to do rpm --replacefiles. How can you solve this problem inside the spec file ? As I was unable to find any documentation about this case .. Can someone point my the FM to read ! (And don't tell me Maximum Rpm, please) Thank you. Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: jorgp <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 28, 2001 12:46 PM Subject: Re: [Cooker] 8.0 (Traktopel) Beta 1 | On Wednesday 28 February 2001 07:27, you wrote: | > New story on (http://www.mandrakeforum.com) | > | > The first Beta of the upcoming Linux-Mandrake 8.0 | > (Traktopel) is available. | > | Will there be a branch off into a mandrake 8 dir and leave cooker for | bleeding edge? | | -- | Thanks | Jorg | |
Re: [Cooker] Why don't recent kernels build initrd?
| Hi all!
|
| I've noticed that since, uhmm, kernel-2.4.0-xx no initrd is automatically
| built when updating the kernel package. (Hmm, thinking of it, has it ever
| been built automatically?)
| Well, why is this? IMO it would be better if the initrd were built. As I
| imagine (without looking at the .spec), it's just one additional command
for
| the %post section:
|
| mkinitrd /boot/initrd-%{version}-%{release} %{version}-%{release}
|
| This should do it. And so that fixing of /boot/grub/menu.lst is not
| necessary when updating kernels, I've also added a symlink
|
| /boot/initrd -> /boot/initrd-%{version}-%{release}.img
|
| This way, if only /boot/initrd is referenced in /boot/grub/menu.lst,
| /boot/grub/menu.lst doesn't need to be touched.
|
| I assume that something similiar also holds true for LILO, but I don't use
| LILO anymore, so I can't say for sure. I guess that a call to /sbin/lilo
| would be necessary if LILO is used.
|
No it is not that simple you must
- postuninstall : insert loop.o
- install the kernel
- postinstall : mkinitrd
- remove the loop.o
RedHat does it on its latest kernel if you want to get an easy spec file ..
Thomas
Re: [Cooker] Cooker-i586 20010225 4:16
As well I don't get why cut is not in /bin ? Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] Systems Manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk:/ - Original Message - From: Xavier Bertou <[EMAIL PROTECTED]> To: Cooker ML <[EMAIL PROTECTED]> Sent: Monday, February 26, 2001 5:53 PM Subject: [Cooker] Cooker-i586 20010225 4:16 | Hi, | some remarks about current cooker : | | I'm concerned about the installation of vi. There are a number of points | upon which I wouldn't agree : | - put vim in /bin/vim and not /usr/bin/vim. It has "always" be in | /usr/bin, and should really be in /usr/bin. | - put links to /etc/alternatives in /bin (vi is the only package I | installed to do so) | | I had a (lot of) crash(es) and had to use /bin/vi without /usr mounted. | It failed, and of course I used /bin/vim-minimal, but in automated | scripts or the like it would fail. | | I would really prefer vim-minimal package to install a /bin/vi, and | vim-enhanced to install a /usr/bin/vim. | | Then, kernel-2.4.1-22mdk does not work with my eth0 3c509 ISA PNP card, | as I said in a previous mail. I run kernel22-2.2.18-14mdk currently... | Any idea ? | | Some things about mutt package. Could the compressed folder patch be | added to mutt ? And also when I use mutt, the >128 charecters appear as | '?'. Of course it's Ok in xterm, vi, or whatever application I use. It | never happened to me before with other mutts (I always compiled them | myself because of the compressed folder patch). Any idea ? | | At last, I tried to launch netscape to give the URL of the patch of mutt | and the xterm in which I entered netscape disapeared. Surprised, I | launched another xterm, another netscape and beep, my computer rebooted | :( | Included here is the log of what happened. | (I have netscape-common-4.76-2mdk and netscape-communicator-4.76-2mdk) | | Appart from that, it works well ;-) | | -- | Xavier |
[Cooker] How to mount the floppy in the postInstall
> Pixel <[EMAIL PROTECTED]> writes:
[...]
>
> postInstallNonRooted => '
> /usr/bin/modprobe vfat
> ',
> postInstall => '
> mount -r -t vfat /dev/fd0 /mnt/floppy
> sleep 1000
> ',
As this discussion was private I found interesting to now post it on the
list.
This code is to mount the floppy on the postinstall and will only work with
the latest CVS.
Alternatively for the 7.2 installer Pixel give me this patch to add at the
end of the auto_install.cfg.pl
use install_steps_auto_install;
package install_steps_auto_install;
log::l("Patch mounting the floppy before the postinstall section");
my $f = \&exitInstall;
undef *exitInstall;
*exitInstall = sub {
my ($o) = @_;
$f->(@_);
eval { modules::load("vfat") };
fs::mount(devices::make('fd0'), "/mnt/mnt/floppy", "vfat", 1);
};
This mount the floppy on /mnt/floppy under the chrooted environment.
Thomas
Re: [Cooker] Can not mount the floppy in the postInstall section of the kickstart
[...] > I divide the package in three part : > - name > - name-devel > - name-config > > Name contain the file structure,binaries and doc > Devel like usual > Config contain any host dependant config file. > > Which allow to update the binary without hurting the config file or updating > the config file without touching the binaries. > > However, I am willing to perform some change after the installation > For example ethernet card order reorganistation to have the motherbard card > always as eth0, etc. > > As I don't want a BIG perl file with my postinstall, it is divided in > script/plugin. > But to run them I must mount the floppy !! I still need the vfat module to be loaded to do that ! The automatic section is nice but have some limitation (feel free to correct/insult me if I am wrong) If you want all the information on a floppy and a floppy per server, you want to store your IP, DNS, (+) information on the floppy. The problem is that if you have a bootable CD with a modified sysconfig file, you don't want to burn a CD per server to use the automatic keyword ! As well you can not perform more high level configuration action this way. As well, some post installation action can be server dependant (You don't allow the same IPCHAINS rules on a DNS and WEB server). Some of those configuration can be implemented as "config" RPM but it is not always convinient this way. As a consequence, I still would like the vfat module to be present before the postinstall. I can see not reason to not have it. I will not screw anything ;*) Feel free to let me know your thought. Thomas
Re: [Cooker] Can not mount the floppy in the postInstall section of the kickstart
> [...] > > > I am using a I modified version of the CD which include a linux > > kickstart=floppy statement. > > (1) kickstart is a synonym to auto_install > (2) postInstall is the key for scripting > (3) please read: http://www.linux-mandrake.com/drakx/auto_inst.html I already read this (and more). for once no one will tell me to RTFM ;*) > [...] > > > The problem is that I can not mount the floppy as the vfat module in not > > present !! > > At stage1 step, vfat module is no more needed (except for hd.img) since > redhat's kickstart is deprecated by my "automatic" equivalent; and stage2 > has got all the modules, including vfat, to do the auto_install stuff. > > -=-=-- from cvs/gi/mdk-stage1/TECH-INFOS > This feature is used to replace redhat kickstart. I use the kernel > parameter "automatic" with the following keywords: > > from list: > method nfs, ftp, http, cdrom, disk > -=-=-- > [...] Will look into the CVS . > > Worse even the insmod -f is not working !! > > When? During the postinstall using the installed system module (use the code Luck ;*) > > [...] > > > I have a /mnt/floppy with something like : > > [...] > > > insmod --force /lib/modules/2.2.17-21mdk/fs/vfat.o Try to insert the new installation vfat module as the lsmod reported that it wasn't inserted anymore. > [...] > > > echo "Mounting the floppy" > > /bin/mount -r -t vfat /dev/fd0H1440 /mnt/floppy Try to mount the floppy to be able to run some script !!! > I'm sorry I don't understand anything out of that. Please can you explain > more extensively what you try to do? I divide the package in three part : - name - name-devel - name-config Name contain the file structure,binaries and doc Devel like usual Config contain any host dependant config file. Which allow to update the binary without hurting the config file or updating the config file without touching the binaries. However, I am willing to perform some change after the installation For example ethernet card order reorganistation to have the motherbard card always as eth0, etc. As I don't want a BIG perl file with my postinstall, it is divided in script/plugin. But to run them I must mount the floppy !! Thomas
[Cooker] Can not mount the floppy in the postInstall section of the kickstart
Hello. I am currently creating a kickstart and having major pain as the vfat module in not inserted before the postinstall. I am using a I modified version of the CD which include a linux kickstart=floppy statement. It allow me to delete the vmlinuz and syslinux file from the floppy and install some script on it. The problem is that I can not mount the floppy as the vfat module in not present !! Worse even the insmod -f is not working !! The only solution I can see is to : - mount the cdrom - extract the vfat.o like the installer is doing for the BOOT9 kernel - insert it Let say that it is a major pain and could be solve elegantly with an insertion of the module by the installer before the postinstall section. Any plan to do so before 8.0 final ? I have a /mnt/floppy with something like : # #Print output on VT 1 # exec >/dev/tty1 # Prepare the system export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin # Try to insert the module by hand !! lsmod insmod --force /lib/modules/2.2.17-21mdk/fs/vfat.o sleep 10 lsmod sleep 10 ## # Mount floppy ## echo "Mounting the floppy" /bin/mount -r -t vfat /dev/fd0H1440 /mnt/floppy # I also tried msdos and fat type .. echo echo "mnt/floppy" echo ls -al /mnt/floppy sleep 5 # # Run installation script # echo "Running the legend configuration tools" /mnt/floppy/postinstall/run /bin/sleep 2 # Unmount the floppy echo "Umounting the floppy" /bin/umount /mnt/floppy #Closedown Regards, Thomas -- Thomas Mangin [EMAIL PROTECTED] IT manager[EMAIL PROTECTED] Legend Internet Ltd. http://www.legend.co.uk/
