Re: since 2 days apm / ACPI doesn't work and boot instabilities
On Fri, 7 Nov 2003, Andreas Klemm wrote: wanted to let you know, that since yesterday ACPI on my Dell Latitude D600 doesn't work anymore. /usr/src/UPDATING 20031103: The i386 APIC_IO kernel option has been replaced by 'device apic'. The ACPI module has also been temporarily disabled, so ACPI must be statically compiled into your kernel using 'device acpi' if you wish to use the ACPI driver. Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: who am i
On Fri, 4 Jul 2003, Ruslan Ermilov wrote: Hello, Doh, forgot to mention: the following patch fixes it for me. This indeed fixes it. Thanks! Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
who am i
Hello, Please take a look at this: = [snowlap] ~$ who am i richard ttyp5Jul 4 00:34 (:0.0) [snowlap] ~$ su - Password: Last login: Fri Jul 4 00:31:17 on ttyp5 snowlap# who am i root ttyp5Jul 4 00:34 snowlap# exit logout [snowlap] ~$ who am i root ttyp5Jul 4 00:34 = Of course the latest 'who am i' should return 'richard' and not(!) 'root' Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk Geometry Error
On Sun, 29 Jun 2003, Systems Engineering wrote: I am attempting an installation via the 5.1-R iso. During the partitioning process, fdisk reports that the detected disk geometry is probably incorrect. Subsequently, I attempt to specify the geometry reported by bios (CSH:19158,255,16). This geometry is, however, rejected. I have tried some variations, including the sane proposal that fdisk makes after it reports that the detected disk geometry is invalid. fdisk accepts them but this does not produce a bootable system (not surprising). Let me guess. Is it limited to 2 GB? Youre disk probably has a jumper on it with enables it above 2GB. Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB umass BBB mass storage support
On Sun, 8 Jun 2003, Vincent wrote: Vincent, My PhotoClip DM2132 camera which works under Linux, produces the following messages in the system log but produces and IO error when I try to mount it. I'm also working on a USB device (PQI 128 MB Flash Drive) that's not working (yet). Can you put the following in your kernel config: options USB_DEBUG options CAMDEBUG options CAM_DEBUG_BUS=-1 options CAM_DEBUG_TARGET=-1 options CAM_DEBUG_LUN=-1 options CAM_DEBUG_FLAGS=(CAM_DEBUG_INFO|CAM_DEBUG_TRACE|CAM_DEBUG_CDB) Rebuild the kernel and after reboot attach the device again. You should see a lot of debug in /var/log/messages. Maybe this can help you to see where it goes wrong. Also take a look at this page: http://www.root.org/~nate/freebsd/quirks.html If this does not help you, please send the debug output as well as the output from 'usbdevs -v' and 'camcontrol devlist'. Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-RELEASE TODO
On Sat, 31 May 2003, Robert Watson wrote: |---++---+---| | || | The recently upgraded | | || | if_wi driver is more | | || | tuned to Prism hardware | | || | than to Lucent hardware, | | if_wi problems on || | resulting in system | | Lucent hardware | -- | --| lockups and poor | | || | performance when using| | || | Lucent hardware. These| | || | problems are believed to | | || | be fixed but more testing | | || | is welcome. | |---++---+---| Got a Lucent mini-pci card in my laptop and a Lucent(Avaya) Gold card. I don't see any problems with both cards. Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compaq deskpro won't reboot
On Thu, 29 May 2003, Dan Pelleg wrote: power failure w/o waiting for the user to powercycle. Nothing seems to work. Any suggestions? Try 'shutdown -r now' Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.0 - CURRENT - KERNEL COMPILE - HELP
On Tue, 18 Mar 2003, CARTER Anthony wrote: udbp.o: In function `udbp_attach': udbp.o(.text+0x40d): undefined reference to `ng_newtype' udbp.o(.text+0x43b): undefined reference to `ng_make_node_common' udbp.o(.text+0x482): undefined reference to `ng_name_node' udbp.o(.text+0x4c1): undefined reference to `dumpnode' udbp.o(.text+0x4dd): undefined reference to `ng_unref_node' udbp.o(.text+0x52c): undefined reference to `dumpnode' For the udbp device, you also need 'options NETGRAPH' in your kernel config. Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
general protection fault while in kernel mode
Hello, With kernel sources from today, I just got the following panic (but no crashdump): Mar 18 19:54:57 snowlap syslogd: kernel boot file is /boot/kernel/kernel Mar 18 19:54:57 snowlap kernel: Mar 18 19:54:57 snowlap kernel: Mar 18 19:54:57 snowlap kernel: Fatal trap 9: general protection fault while in kernel mode Mar 18 19:54:57 snowlap kernel: instruction pointer = 0x8:0xc0377642 Mar 18 19:54:57 snowlap kernel: stack pointer = 0x10:0xd1d4cce8 Mar 18 19:54:57 snowlap kernel: frame pointer = 0x10:0xd1d4cce8 Mar 18 19:54:57 snowlap kernel: code segment= base 0x0, limit 0xf, type 0x1b Mar 18 19:54:57 snowlap kernel: = DPL 0, pres 1, def32 1, gran 1 Mar 18 19:54:57 snowlap kernel: processor eflags= interrupt enabled, resume, IOPL = 0 Mar 18 19:54:57 snowlap kernel: current process = 11 (idle) Mar 18 19:54:57 snowlap kernel: trap number = 9 Mar 18 19:54:57 snowlap kernel: panic: general protection fault Mar 18 19:54:57 snowlap kernel: Mar 18 19:54:58 snowlap kernel: syncing disks, buffers remaining... 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 2154 Mar 18 19:54:58 snowlap kernel: giving up on 809 buffers Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m7s Mar 18 19:54:58 snowlap kernel: Dumping 383 MB Mar 18 19:54:58 snowlap kernel: ata0: resetting devices .. Mar 18 19:54:58 snowlap kernel: done Mar 18 19:54:58 snowlap kernel: 16 32 48ad0: timeout waiting for DRQata0: resetting devices .. Mar 18 19:54:58 snowlap kernel: done Mar 18 19:54:58 snowlap kernel: ad0: timeout waiting for DRQata0: resetting devices .. Mar 18 19:54:58 snowlap kernel: done Mar 18 19:54:58 snowlap kernel: ad0: timeout waiting for DRQata0: resetting devices .. Mar 18 19:54:58 snowlap kernel: done Mar 18 19:54:58 snowlap kernel: ad0: timeout waiting for DRQ Mar 18 19:54:58 snowlap kernel: Mar 18 19:54:58 snowlap kernel: Fatal trap 12: page fault while in kernel mode Mar 18 19:54:58 snowlap kernel: fault virtual address = 0x28 Mar 18 19:54:58 snowlap kernel: fault code = supervisor write, page not present Mar 18 19:54:58 snowlap kernel: instruction pointer = 0x8:0xc01520a6 Mar 18 19:54:58 snowlap kernel: stack pointer = 0x10:0xd1d4c8f0 Mar 18 19:54:58 snowlap kernel: frame pointer = 0x10:0xd1d4c938 Mar 18 19:54:58 snowlap kernel: code segment= base 0x0, limit 0xf, type 0x1b Mar 18 19:54:58 snowlap kernel: = DPL 0, pres 1, def32 1, gran 1 Mar 18 19:54:58 snowlap kernel: processor eflags= interrupt enabled, resume, IOPL = 0 Mar 18 19:54:58 snowlap kernel: current process = 11 (idle) Mar 18 19:54:58 snowlap kernel: trap number = 12 Mar 18 19:54:58 snowlap kernel: panic: page fault Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: ad0: timeout waiting for DRQ Mar 18 19:54:58 snowlap kernel: Mar 18 19:54:58 snowlap kernel: Fatal trap 12: page fault while in kernel mode Mar 18 19:54:58 snowlap kernel: fault virtual address = 0x28 Mar 18 19:54:58 snowlap kernel: fault code = supervisor write, page not present Mar 18 19:54:58 snowlap kernel: instruction pointer = 0x8:0xc01520a6 Mar 18 19:54:58 snowlap kernel: stack pointer = 0x10:0xd1d7cc50 Mar 18 19:54:58 snowlap kernel: frame pointer = 0x10:0xd1d7cc98 Mar 18 19:54:58 snowlap kernel: code segment= base 0x0, limit 0xf, type 0x1b Mar 18 19:54:58 snowlap kernel: = DPL 0, pres 1, def32 1, gran 1 Mar 18 19:54:58 snowlap kernel: processor eflags= interrupt enabled, resume, IOPL = 0 Mar 18 19:54:58 snowlap kernel: current process = 24 (irq14: ata0) Mar 18 19:54:58 snowlap kernel: trap number = 12 Mar 18 19:54:58 snowlap kernel: panic: page fault Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap kernel: Uptime: 2h15m17s Mar 18 19:54:58 snowlap kernel: panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Mar 18 19:54:58 snowlap
Panic after sleep.
Hello, My laptop paniced when he tried coming back from a sleep. This happens a few times a week. [snowlap] /var/crash$ uname -a FreeBSD snowlap.unixguru.nl 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Mar 11 15:11:05 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNOWLAP i386 Script started on Wed Mar 12 09:42:18 2003 snowlap# gdb -k kernel.11-03-2003 vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... --- Uptime: 36m36s Terminate ACPI Rebooting... 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.0-CURRENT #1: Tue Mar 11 15:11:05 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNOWLAP Preloaded elf kernel /boot/kernel/kernel at 0xc0568000. Preloaded elf module /boot/kernel/acpi.ko at 0xc05680a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 797579512 Hz CPU: Intel Pentium III (797.58-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 401997824 (383 MB) avail memory = 384536576 (366 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00f01c0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU port 0x530-0x537 on acpi0 acpi_tz0: thermal zone on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 fxp0: Intel Pro/100 Ethernet port 0xdf40-0xdf7f mem 0xf7dff000-0xf7df irq 11 at device 8.0 on pci2 fxp0: Ethernet address 00:00:39:be:6a:32 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cbb0: TI1410 PCI-CardBus Bridge at device 12.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 pcib2: slot 12 INTA is routed to irq 11 cbb1: ToPIC100 PCI-CardBus Bridge at device 13.0 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 pcib2: slot 13 INTA is routed to irq 11 cbb2: ToPIC100 PCI-CardBus Bridge at device 13.1 on pci2 cardbus2: CardBus bus on cbb2 pccard2: 16-bit PCCard bus on cbb2 pcib2: slot 13 INTB is routed to irq 11 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xcff0-0xcfff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xcf80-0xcf9f irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xcf60-0xcf7f irq 11 at device 31.4 on pci0 usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: Intel 82801BA (ICH2) port 0xcdc0-0xcdff,0xce00-0xceff irq 11 at device 31.5 on pci0 pcm0: unknown ac97 codec (id=0x594d4800) pci0: simple comms at device 31.6 (no driver attached) acpi_lid0: Control Method Lid Switch on acpi0 acpi_cmbat0: Control method Battery on acpi0 acpi_acad0: AC adapter on acpi0 speaker0 port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven
Re: -current buildworld fails 24 hours
On Sun, 23 Feb 2003, Yamada Ken Takeshi wrote: I have the following error with make buildworld since Feb. 21th, 0900GMT with my P3x2 box. boot2 seems exceeding the size limit, any fix? Same here, with the sources of today (upped en builded twice, but both time's the same error) Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BOOT2_UFS=UFS1_ONLY works for today's current
On Sun, 23 Feb 2003, David Syphers wrote: David, I added BOOT2_UFS=UFS2_ONLY to my make.conf, and my buildworld still dies in boot2. I'm trying to upgrade from a Feb. 19 -current (because it's crashing all the time, and I need to enable debugging stuff). Is there a fix, or would other information be helpful? Same problem over here. I reverted back the last commit on /usr/src/sys/ufs/ffs/fs.h in my source tree and that fixed the build. Of course, this is a workaround !! Regards, Richard. Paul Vixie in an interview with Sendmail.net: Now that the Internet has the full spectrum of humanity as users, the technology is showing its weakness: it was designed to be used by friendly, smart people. Spammers, as an example of a class, are neither friendly nor smart. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Resolution (Was: Re: The future of perl on FreeBSD)
On Thu, 9 May 2002, Terry Lambert wrote: Uh, csh. Preferrably with tcsh extensions, so it won't run anywhere else. In a pinch, I guess you could use bash. As far i can see, (almost?) everything is already moved from perl to something else. Asked it, went away for a few hours and all the work is done :-) Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
strange file
Hello, Yesterday installed current from a snapshot and instantly updated it via CVS. Today i noticed a strange file in /usr with the name @LongLink. # cat /usr/@LongLink ports/java/jdk13/files/patch-..::src::solaris::native::com::sun::media::sound::engine::HAE_API_BSDOS_Capture.c I containes a piece of logging from CVS. C ports/java/jdk13/files/patch-..::src::solaris::native::com::sun::media::sound::engine::HAE_API_BSDOS_Capture.c,v . . 2#871#110#10189856643#8663#444 1.1 2002.04.16.19.34.24 2#871#110#10189856643#5943#644 Anyone an idea how this is possible??? Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
truss
Hello, On a fresh current i get this # truss /bin/echo hello truss: cannot open /proc/13245/mem: No such file or directory truss: cannot open /proc/curproc/mem: No such file or directory Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: truss
On Sun, 28 Apr 2002, Harti Brandt wrote: You need to mount procfs. Oops youre right... Why isn't it listed in /etc/fstab??? Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: truss
On Sun, 28 Apr 2002, Kris Kennaway wrote: procfs is not mounted by default. New to current (one day old baby :-), so didn't know that. sorry() Why isn't it mounted by default?? Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: truss
On Sun, 28 Apr 2002, Robert Watson wrote: The rationale for disabling procfs is that its functionality is largely redundant to existing sysctls and debugging mechanisms, and that it has been, and will likely continue to be, an important source of system security holes. Okay disable it :-) I think truss is one of the last stragglers that relies on it -- the other is 'ps -e', which gropes through the memory of each process to dig out the environmental variables. This requires that ps both have substantial privilege, and that procfs be present. Can't we take the privileges away, so that an user only can see his own procs and only root can see all?? Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: truss
On Sun, 28 Apr 2002, Robert Watson wrote: BTW, 5.0 will also allow (once we commit the MAC framework from the TrustedBSD Project) kernel modules to tweak process visibility protections in the kernel at runtime. For example, you can kldload a mac_seeotheruids.ko policy module, which can limit what processes can view of other processes based on a number of factors, including uids, and information it tags onto the processes. It can also limit access to socket information listed in netstat, etc. When will the TrustedBSD modules commited to current?? Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
