VSCAN installing error
I get the following error when I try to install VSCA. [EMAIL PROTECTED] /usr/ports/security/vscan # make install === Installing for uvscan-4.24e === uvscan-4.24e depends on file: /usr/local/sbin/update_dat - not found ===Verifying install for /usr/local/sbin/update_dat in /usr/ports/security/uvscan-dat dat-4265.tar doesn't seem to exist in /usr/ports/distfiles/. Attempting to fetch from http://download.nai.com/products/datfiles/4.x/nai/. fetch: http://download.nai.com/products/datfiles/4.x/nai/dat-4265.tar: Not Found Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/dat-4265.tar: File unavailable (e.g., file not found, no access) Couldn't fetch it - please try to retrieve this port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /usr/ports/security/uvscan-dat. *** Error code 1 Stop in /usr/ports/security/vscan. It seems that It' looking for the dat-4265.tar file but this file does not exists. WHY ?? Thanks in advance. -- No guts No glory =] PASSELAC Armand [= ( @ @ ) Ingenieur Systemes-Reseaux Securite ORBYTES INGENIERIE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
I don't have the solution. But I known a program taht allow you to restore partitions : http://www.cgsecurity.org/index.html?testdisk.html It seems to be very powerfull. With it you could get your data from broken partitions. PS : I know the developper, so if you have problem ... [ On Sun, 24 Aug, 2003 at 21:26, Thomas Gutzler wrote: ] Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] [ End of original mail from Thomas Gutzler ] -- No guts No glory =] PASSELAC Armand [= ( @ @ ) Ingenieur Systemes-Reseaux Securite ORBYTES INGENIERIE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
How create /dev/apm* ???
Hi, I have installed a FreeBSD 5.1 on my Laptop (Compaq Armada E500). I have a problem with the power management : - I can't use the ACPI module : the kernel can't be loaded. OK no problem ! As I saw within many FAQs, it's normal (it depends on the type of the laptop). - I would like to use APM so ! I realize the following stages (see http://freebsd.unixtech.be/doc/en_US.ISO8859-1/articles/laptop/x61.html) : * I build my kernel with device apm * /boot/device.hints : hint.acpi.0.disabled=1 #hw.acpi.ec.event_driven=1 hint.apm.0.disabled=0 hint.apm.0.flags=0x20 * /boot/loader.conf : apm_load=YES * /etc/rc.conf apm_enable=YES But during the boot I get an error : can't open /dev/apm Indeed, there is no device with apm* name within /dev How can I create this device (In the freebsd-questions list somebody tails me that's not possible with 5.X there is no possibility to use a kind of makedev). Thanks a lot. -- No guts No glory =] PASSELAC Armand [= ( @ @ ) Ingenieur Systemes-Reseaux Securite ORBYTES INGENIERIE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How create /dev/apm* ???
[ On Fri, 22 Aug, 2003 at 8:41, Kevin Oberman wrote: ] Date: Fri, 22 Aug 2003 16:10:16 +0200 From: Armand Passelac [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi, I have installed a FreeBSD 5.1 on my Laptop (Compaq Armada E500). I have a problem with the power management : - I can't use the ACPI module : the kernel can't be loaded. OK no problem ! As I saw within many FAQs, it's normal (it depends on the type of the laptop). - I would like to use APM so ! I realize the following stages (see http://freebsd.unixtech.be/doc/en_US.ISO8859-1/articles/laptop/x61.html) : * I build my kernel with device apm * /boot/device.hints : hint.acpi.0.disabled=1 #hw.acpi.ec.event_driven=1 hint.apm.0.disabled=0 hint.apm.0.flags=0x20 * /boot/loader.conf : apm_load=YES * /etc/rc.conf apm_enable=YES But during the boot I get an error : can't open /dev/apm Indeed, there is no device with apm* name within /dev How can I create this device (In the freebsd-questions list somebody tails me that's not possible with 5.X there is no possibility to use a kind of makedev). That is correct. The apm driver creates the device automagically with devfs. S0 the question is why it is not doing so. Please attach the output of dmesg. (Actually, all of the apm stuff should be in the first 15 lines.) My dmesg is in attach. I see nothing aboutt apm ! But during the boot I can see the message tailling /dev/apm no such file -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 [ End of original mail from Kevin Oberman ] -- No guts No glory =] PASSELAC Armand [= ( @ @ ) Ingenieur Systemes-Reseaux Securite ORBYTES INGENIERIE Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #0: Sat Jul 19 23:33:27 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEBIE Preloaded elf kernel /boot/kernel/kernel at 0xc06f1000. Preloaded elf module /boot/kernel/snd_driver.ko at 0xc06f11cc. Preloaded elf module /boot/kernel/snd_vibes.ko at 0xc06f127c. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc06f132c. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc06f13d8. Preloaded elf module /boot/kernel/snd_t4dwave.ko at 0xc06f148c. Preloaded elf module /boot/kernel/snd_solo.ko at 0xc06f153c. Preloaded elf module /boot/kernel/snd_sbc.ko at 0xc06f15ec. Preloaded elf module /boot/kernel/snd_sb16.ko at 0xc06f1698. Preloaded elf module /boot/kernel/snd_sb8.ko at 0xc06f1748. Preloaded elf module /boot/kernel/snd_neomagic.ko at 0xc06f17f4. Preloaded elf module /boot/kernel/snd_mss.ko at 0xc06f18a8. Preloaded elf module /boot/kernel/snd_maestro3.ko at 0xc06f1954. Preloaded elf module /boot/kernel/snd_maestro.ko at 0xc06f1a08. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc06f1ab8. Preloaded elf module /boot/kernel/snd_fm801.ko at 0xc06f1b64. Preloaded elf module /boot/kernel/snd_ess.ko at 0xc06f1c14. Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc06f1cc0. Preloaded elf module /boot/kernel/snd_emu10k1.ko at 0xc06f1d70. Preloaded elf module /boot/kernel/snd_ds1.ko at 0xc06f1e20. Preloaded elf module /boot/kernel/snd_csa.ko at 0xc06f1ecc. Preloaded elf module /boot/kernel/snd_cs4281.ko at 0xc06f1f78. Preloaded elf module /boot/kernel/snd_cmi.ko at 0xc06f2028. Preloaded elf module /boot/kernel/snd_als4000.ko at 0xc06f20d4. Preloaded elf module /boot/kernel/snd_ad1816.ko at 0xc06f2184. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 596923840 Hz CPU: Intel Pentium III (596.92-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 201261056 (191 MB) avail memory = 187969536 (179 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0x5000-0x53ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) cbb0: TI1225 PCI-CardBus Bridge mem 0x4110-0x41100fff irq 11 at device 4.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: TI1225 PCI-CardBus Bridge mem 0x4118-0x41180fff irq 11 at device 4.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x3420-0x342f
