Re: cannot su?
On Sat, Jan 15, 2005 at 10:46:03PM -0500, Robert William Vesterman wrote:
I have a similar problem, but only after I use X. I can su perfectly
fine before using X, and I can su perfectly fine while using X (and a
terminal window), but after exiting X, if I want to su, I have to reboot.
You might want to try the following C program to check that getlogin
is returning the right name at each stage.
David.
10:18:gonzo 17% cat printlogin.c
#include stdio.h
#include unistd.h
int main(void) { puts(getlogin()); }
10:18:gonzo 18% gcc -o printlogin printlogin.c
10:18:gonzo 19% ./printlogin
dwmalone
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB mouse not working
On Sunday 16 January 2005 03:47, Robert William Vesterman wrote: I found that my USB mouse works if and only if I boot without APCI support. Ok, it didn't work to me. I added hint.acpi.0.disabled=1 (and also tried adding hint.apm.0.disabled=0 too) 'dmesg | grep acpi' returns no results, same as 'devinfo | grep acpi'. So I suppose acpi is disabled at boot time. I also noticed that when moused start while booting the machine, it throws me this error: 'unable to open /dev/ums0: Device busy'. Any idea? However, I can't figure out how to configure moused with my mouse: I have this settings in /etc/rc.conf: usbd_enable=YES usbd_flags= moused_enable=YES moused_type=auto moused_flags= moused_port=/dev/ums0 -- Imobach González Sosa imobachgs en banot punto net osoh en jabber.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twa breakage on AMD64 with 9.1.5.2 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit
Hello On 15/01/2005, at 12:40 PM, Vinod Kashyap wrote: Could you give the attached patch a try? Just a hunch... I did... same behavior. it just hangs right after displaying the twa0 line. Actually, hangs is incorrect. As I had to drive to the office to reload a previous kernel (never, ever rely on nextboot my friends!) When I got there I saw that it went a little bit further, so it seems that it doesn't just hang... it is just very very slow Jean-Yves --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: [EMAIL PROTECTED], general: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot su?
Thomas Dymond wrote: Could this be anything to do with : security.bsd.suser_enabled what's yours set to ? security.bsd.suser_enabled: 1 But, I noticed I've got security.mac.* enabled somehow (it's not my kernel...) - could MAC be interfering? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make buildworld for RELENG_5 failing on RELENG_5_3 in /usr/src/usr.sbin/syslogd, _PATH_LOG_PRIV not defined
I'm getting the following error on a RELENG_5_3 box when trying to compile the RELENG_5 sources. I've been cvsupping now for about a week and continuing to get the same error when we get to syslogd. /usr/src/usr.sbin/syslogd/syslogd.c:141: error: `_PATH_LOG_PRIV' undeclared here (not in a function) /usr/src/usr.sbin/syslogd/syslogd.c:141: error: initializer element is not constant /usr/src/usr.sbin/syslogd/syslogd.c:141: error: (near initialization for `funix_secure.name') /usr/src/usr.sbin/syslogd/syslogd.c:142: error: initializer element is not constant /usr/src/usr.sbin/syslogd/syslogd.c:142: error: (near initialization for `funix_secure.next') If I apply the following patch then buildworld continues to completion. Note the same error appears in libc and the patch fixes that as well. Judging by the build logs and lack of others complaining I'm the only one with this problem, so clearly this isn't the correct solution, but it works for me. --- /usr/src/usr.sbin/syslogd/syslogd.c.old Sun Jan 16 12:16:25 2005 +++ /usr/src/usr.sbin/syslogd/syslogd.c Sun Jan 16 12:17:53 2005 @@ -74,6 +74,7 @@ #define DEFSPRI(LOG_KERN|LOG_CRIT) #define TIMERINTVL 30 /* interval for checking flush, mark */ #define TTYMSGTIME 1 /* timeout passed to ttymsg */ +#define _PATH_LOG_PRIV /var/run/logpriv #include sys/param.h #include sys/ioctl.h --- /usr/src/lib/libc/gen/syslog.c.oldSun Jan 16 14:12:49 2005 +++ /usr/src/lib/libc/gen/syslog.cSun Jan 16 13:03:41 2005 @@ -60,6 +60,8 @@ #include libc_private.h +#define _PATH_LOG_PRIV /var/run/logpriv + static int LogFile = -1; /* fd for log */ static int status; /* connection status */ static int opened; /* have done openlog() */ Any ideas on what could be wrong with my system? FYI In general I use ccache but i've disabled it for this run, by editing out the commands in /etc/make.conf. Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot su?
On Sunday, 16. January 2005 01:07, Ivan Voras wrote: What could be the reasons for su root to not work? I have a user that's in wheel group. Logging in as root works on the console, but su-ing from the user just writes 'Sorry', like the password's wrong. There are no clues in log files. Make sure /usr/sbin/su is suid root (and /usr isn't mounted nosuid). -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7JevHKBYyG.pgp Description: PGP signature
Re: Unkillable OpenOffice.org process in 5.3p2
On Sat, 15 Jan 2005 13:23:44 -0800 Jeffrey Williams [EMAIL PROTECTED] wrote: When you rebooted, was the computer actually able to halt on its own? Every time mine has locked up, I have had to do a hard power down, the OS is unable to kill the process even when halting. I have noticed A can confirm this on my system (5.3 RELEASE, AMD 1400+, OO 1.1.3/1.1.4, java 1.4.2-p6). My OO frequently freezes when I start a new document or try load one (or spreadsheet or whatever). Very annoying. that the OO app freezes typically after having Mozilla to use java and/or adobe plugins, I am not sure which is the trigger yet. I am No Mozilla java-adobe plugin here. wondering if it is a problem with the interaction between the OO and java, or OO the pdf libraries, or a some shared library that facilitates the interaction between these components. I am afraid I I extensively use Java applications (jEdit, DBVisualizer, jCVS, Java Web Start and apps launched by JWS). I am going to try to experiment with all these in mind on Monday (at work). Here, at home I can't reproduce this , however. Its also an AMD machine, much faster (2600+), 5.3 B7 (latest RELEASE doesn't work unfortunately). Bye Zsolt = Zsolt Kuti ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot su?
+++ Ivan Voras [Sunday 16 January 2005 02:18]: Kris Kennaway wrote: On Sun, Jan 16, 2005 at 01:15:34AM +0100, Ivan Voras wrote: Kris Kennaway wrote: /etc/pam.d/su is identical to another machine where everything works ok. OK. /etc/pam.d/su on 5.3 includes /etc/pam.d/system, so also make sure they're in sync. /etc/pam.d/system is the same as on the working system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Could this be anything to do with : security.bsd.suser_enabled what's yours set to ? Cheers -- Thomas Dymond a mouse is a device used to point at the xterm you want to type in PGP ID : 0x8D423A2B PGP Key : http://www.kmem.org/~tom/pgp/pubkey.asc pgpX3VfY7ZEmd.pgp Description: PGP signature
Re: make buildworld for RELENG_5 failing on RELENG_5_3 in /usr/src/usr.sbin/syslogd, _PATH_LOG_PRIV not defined
On Sun, Jan 16, 2005 at 02:22:05PM +, Steve Hodgson wrote: I'm getting the following error on a RELENG_5_3 box when trying to compile the RELENG_5 sources. I've been cvsupping now for about a week and continuing to get the same error when we get to syslogd. /usr/src/usr.sbin/syslogd/syslogd.c:141: error: `_PATH_LOG_PRIV' undeclared here (not in a function) /usr/src/usr.sbin/syslogd/syslogd.c:141: error: initializer element is not constant /usr/src/usr.sbin/syslogd/syslogd.c:141: error: (near initialization for `funix_secure.name') /usr/src/usr.sbin/syslogd/syslogd.c:142: error: initializer element is not constant /usr/src/usr.sbin/syslogd/syslogd.c:142: error: (near initialization for `funix_secure.next') If I apply the following patch then buildworld continues to completion. Note the same error appears in libc and the patch fixes that as well. Judging by the build logs and lack of others complaining I'm the only one with this problem, so clearly this isn't the correct solution, but it works for me. --- /usr/src/usr.sbin/syslogd/syslogd.c.old Sun Jan 16 12:16:25 2005 +++ /usr/src/usr.sbin/syslogd/syslogd.c Sun Jan 16 12:17:53 2005 @@ -74,6 +74,7 @@ #define DEFSPRI(LOG_KERN|LOG_CRIT) #define TIMERINTVL 30 /* interval for checking flush, mark */ #define TTYMSGTIME 1 /* timeout passed to ttymsg */ +#define _PATH_LOG_PRIV /var/run/logpriv #include sys/param.h #include sys/ioctl.h --- /usr/src/lib/libc/gen/syslog.c.oldSun Jan 16 14:12:49 2005 +++ /usr/src/lib/libc/gen/syslog.cSun Jan 16 13:03:41 2005 @@ -60,6 +60,8 @@ #include libc_private.h +#define _PATH_LOG_PRIV /var/run/logpriv + static int LogFile = -1; /* fd for log */ static int status; /* connection status */ static int opened; /* have done openlog() */ Any ideas on what could be wrong with my system? FYI In general I use ccache but i've disabled it for this run, by editing out the commands in /etc/make.conf. Try make cleandir make cleandir make buildworld Kris pgpW7VbfSaATt.pgp Description: PGP signature
panic in ffs_write() on RELENG_5
One of my U10s running RELENG_5 panicked with the following: panic: trap: data access error cpuid = 0 KDB: enter: panic [thread 100047] Stopped at kdb_enter+0x38: ta %xcc, 1 db tr panic() at panic+0x214 trap() at trap+0x13c -- data access error %o7=0xc014fcb8 -- copyin() at copyin+0x64 ffs_write() at ffs_write+0x338 vn_rdwr() at vn_rdwr+0xb8 vn_rdwr_inchunks() at vn_rdwr_inchunks+0x98 elf64_coredump() at elf64_coredump+0x128 sigexit() at sigexit+0x884 postsig() at postsig+0x3a4 ast() at ast+0x440 -- data access error %o7=0x109600 -- Kris pgpGPGLtIZDoO.pgp Description: PGP signature
Re: USB mouse not working
On Sun, Jan 16, 2005 at 10:33:46AM +, Imobach Gonz?lez Sosa wrote: On Sunday 16 January 2005 03:47, Robert William Vesterman wrote: I found that my USB mouse works if and only if I boot without APCI support. Ok, it didn't work to me. I added hint.acpi.0.disabled=1 (and also tried adding hint.apm.0.disabled=0 too) 'dmesg | grep acpi' returns no results, same as 'devinfo | grep acpi'. So I suppose acpi is disabled at boot time. I also noticed that when moused start while booting the machine, it throws me this error: 'unable to open /dev/ums0: Device busy'. Any idea? However, I can't figure out how to configure moused with my mouse: I have this settings in /etc/rc.conf: usbd_enable=YES usbd_flags= moused_enable=YES moused_type=auto moused_flags= moused_port=/dev/ums0 What brand of mouse you using? I have 2 IBM optical mice that need disconnected and reconnected about 1/2 the time before they will work. This happens to me in Linux, FreeBSD, and Windows so seems to be a mouse issue. Happens to my brother as well - he has the same mouse. Even when the mouse works at bootup, I get a /dev/ums0: Device busy error. Only thing I can see that is different in my setup compared to yours is that I have: usbd_flags=-vv in rc.conf. I can't for the life of me remember why (scrolling maybe?). Cheers. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot su?
On Sun, Jan 16, 2005 at 01:07:07AM +0100, Ivan Voras wrote: What could be the reasons for su root to not work? I have a user that's in wheel group. Logging in as root works on the console, but su-ing from the user just writes 'Sorry', like the password's wrong. There are no clues in log files. /etc/pam.d/su is identical to another machine where everything works ok. Are you using NIS? I've had issues where the machine tries to look up the root password using NIS because of improperly placed + and - commands in /etc/passwd. -- -- Skylar Thompson ([EMAIL PROTECTED]) -- http://www.cs.earlham.edu/~skylar/ pgp5eBPo7aKqm.pgp Description: PGP signature
Re: USB mouse not working
On Sunday 16 January 2005 18:10, Jason Morgan wrote: What brand of mouse you using? I have 2 IBM optical mice that need disconnected and reconnected about 1/2 the time before they will work. This happens to me in Linux, FreeBSD, and Windows so seems to be a mouse issue. Happens to my brother as well - he has the same mouse. Even when the mouse works at bootup, I get a /dev/ums0: Device busy error. Only thing I can see that is different in my setup compared to yours is that I have: I have a Logitech Coordless Desktop Comfort; it's a receiver with keyboard+optical mouse. usbd_flags=-vv This make no sense for me. in rc.conf. I can't for the life of me remember why (scrolling maybe?). Ok, so now the good news: I've installed a 'macally mice' (a simple usb mouse) and it seems to work just fine. Anyway, I still wanna use my Logitech mice, so I suppose I'll continue trying with it. Thank you all for your responses. Anybody on this list have a Logitech mice as mine? -- Imobach González Sosa imobachgs en banot punto net osoh en jabber.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Machine(s) not able to reboot
Hello, I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down or reboot on their own. I always have to physically power them off and then back on. They are SMP machines and I am using ACPI. There are no other apparent problems although one machine did panic today and as a result I had to drive in and power cycle it. I saw some posts about this in mail archives, but they were very old. Has anyone else experienced this problem? What should I look for to fix this? -Will ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic in ffs_write() on RELENG_5
On Sun, Jan 16, 2005 at 09:33:18AM -0800, Kris Kennaway wrote: One of my U10s running RELENG_5 panicked with the following: panic: trap: data access error cpuid = 0 KDB: enter: panic [thread 100047] Stopped at kdb_enter+0x38: ta %xcc, 1 db tr panic() at panic+0x214 trap() at trap+0x13c -- data access error %o7=0xc014fcb8 -- copyin() at copyin+0x64 ffs_write() at ffs_write+0x338 vn_rdwr() at vn_rdwr+0xb8 vn_rdwr_inchunks() at vn_rdwr_inchunks+0x98 elf64_coredump() at elf64_coredump+0x128 sigexit() at sigexit+0x884 postsig() at postsig+0x3a4 ast() at ast+0x440 -- data access error %o7=0x109600 -- I think this was bad RAM; I got a RED exception when I tried to dump. Kris pgpUyRA2M34vW.pgp Description: PGP signature
RE: Machine(s) not able to reboot
-Original Message- From: Peter Jeremy [mailto:[EMAIL PROTECTED] Sent: Sunday, January 16, 2005 6:56 PM To: Will Saxon Cc: [EMAIL PROTECTED] Subject: Re: Machine(s) not able to reboot [Please wrap your mail before 80 columns] Sorry, have to do it manually and I forgot. On 2005-Jan-16 18:39:41 -0500, Will Saxon [EMAIL PROTECTED] wrote: I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down or reboot on their own. I always have to physically power them off and then back on. I have this problem with some DL380's. I have been unable to work out what the root cause is but I've found that the problem is triggered by kldload(8). If I don't use any modules other than acpi.ko (which is loaded by /boot/loader) then I don't have the problem. This works for me also. I had not added device vlan to my kernel config and was also loading the sysvipc stuff, usb and linux/linprocfs. Thanks! -Will ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 4.11-RC3 available
Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 4.11-RC3. This will be the last Release Candidate for the FreeBSD 4.11 release unless a show-stopper problem is found while testing RC3. A schedule for the Release Cycle is available at: http://www.freebsd.org/releases/4.11R/schedule.html We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images and support for doing FTP based installs is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_4_11. Problem reports can be submitted using the send-pr(1) command. It has been decided to provide two disc1 ISO images, one with the KDE windowing system packages on it and the other with the GNOME windowing system packages. They are named disc1-kde and disc1-gnome respectively. Other than which major windowing system is on them they are identical. Most users can choose one of the disc1 ISOs to download and install from. At this time disc1-gnome for Alpha is not available. It may be made available later this week. At the moment there are no known severe issues. Changes since RC2: - fix to some string handling in file(1) - additional device support to mpt(4) - tcp fix to make RST attacks harder plus knob to turn off new behavior - fixes to sk(4) and em(4) - fixes to USB - fixes to kernel linux emulation - addition of ips(4) driver - lots of doc fixes/updates Availability The RC3 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (4.11-RC3-alpha-disc1-kde.iso) = b0b829a27d32e035e10d76fa5c517376 MD5 (4.11-RC3-alpha-disc2.iso) = 1a842a0b0f039b4059ccc84da3dc854e MD5 (4.11-RC3-alpha-miniinst.iso) = 4d8e8ea552cbe1a76de29ae5f56211f2 MD5 (4.11-RC3-i386-disc1-gnome.iso) = 35a1edeec3efdabccd2ba2a90bfe4cd0 MD5 (4.11-RC3-i386-disc1-kde.iso) = dd3eb1a0a9474557fb607bd7467fcee2 MD5 (4.11-RC3-i386-disc2.iso) = c081a7a6f0762a1e2bf5ca34a3a8ac85 MD5 (4.11-RC3-i386-miniinst.iso) = 8bfa7a081641cfe0befe1ea9679459ed pgpeZDnBlTk95.pgp Description: PGP signature
Re: Unkillable OpenOffice.org process in 5.3p2
Hi Peter, Peter Jeremy wrote: I have an OOo process that refuses to die. ps says it is stopped and waiting I had the same problem here as well however I upgraded to 5.3-STABLE as of Jan 6 and have had no problems since. I also had PREEMPTION enabled in the kernel, which I have removed. Carl. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: PAE with 16GB ram
Hi, I use Tyan S2882 with dual Opteron and FreeBSD 4.10-RELEASE with PAE support. it works fine with 8GB and 12GB ram, but panics with 16GB (with the same kernel) : Fatal trap 12: page fault while in kernel mode mp_lock = 0009; cpuid = 0; lapic.id = fault virtual address = 0x69bc8000 fault code = supervisor write, page not present instruction pointer = 0x8:0x6a259d26 stack pointer = 0x10:0x6a3b3f44 frame pointer = 0x10:0x6a3b3f5c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam - SMP: XXX trap number = 12 panic: page fault mp_lock = 0009; cpuid = 0; lapic.id = Uptime: 0s The same thing occurs in both 4.10-RELEASE and 4.11-stable. I even loaded the fault-safe setting in BIOS but it was still not working. my dmesg is in http://www.in2home.org/download/dmesg, and kernel config is in http://www.in2home.org/download/kernel . thanks for your help. :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Machine(s) not able to reboot
On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon [EMAIL PROTECTED] wrote: Hello, I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down or reboot on their own. I always have to physically power them off and then back on. They are SMP machines and I am using ACPI. There are no other apparent problems although one machine did panic today and as a result I had to drive in and power cycle it. I haven't heard of this problem before, and I was wondering if today's 5.3-R errata notice (more than one IPI per APIC causes deadlock) might have something to do with it. Are these machines running SMP? - John ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Machine(s) not able to reboot
-Original Message- From: jmc [mailto:[EMAIL PROTECTED] Sent: Sunday, January 16, 2005 11:39 PM To: Will Saxon Cc: [EMAIL PROTECTED] Subject: Re: Machine(s) not able to reboot On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon [EMAIL PROTECTED] wrote: Hello, I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down or reboot on their own. I always have to physically power them off and then back on. They are SMP machines and I am using ACPI. There are no other apparent problems although one machine did panic today and as a result I had to drive in and power cycle it. I haven't heard of this problem before, and I was wondering if today's 5.3-R errata notice (more than one IPI per APIC causes deadlock) might have something to do with it. Are these machines running SMP? - John They are. I believe the panic could be related to the problem announced today also, as the panicked machine occasionally sees bursts of high load caused by multiple hungry processes. The other email response to this issue, about this happening when using loaded modules, fixed the problem for me. I compiled new kernels with linux emulation, etc. in kernel and the problem stopped. What a relief. I have verified that at least on one machine the hangup problem will continue even when only usb and acpi are loaded via module. This will happen by default on the Proliant servers since by default usbd is loaded at boot. -Will ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
twa module - make kernel (modules) failure RELENG_5 i386
Hello All, I have make kernel failure during compiling twa module (see below). cvsupped RELENG_5 Fri Jan 14. have no any twa devices in the system. (please Cc: me in reply - not subscribed to stable@) thanks. === twa cc -O -pipe -march=pentium2 -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/twa/../../dev/twa/twa_freebsd.c cc -O -pipe -march=pentium2 -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /usr/obj/usr/src/sys/xy.blank.spb.ru/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/xy.blank.spb.ru -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c: In function `twa_scsi_complete': /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: structure has no member named `err_desc' /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:630: error: structure has no member named `err_desc' /usr/src/sys/modules/twa/../../dev/twa/twa_cam.c:636: error: structure has no member named `err_desc' *** Error code 1 Stop in /usr/src/sys/modules/twa. *** Error code 1 /etc/make.conf: CPUTYPE=p2 NO_CVS=true NO_BIND=true NO_BLUETOOTH=true NO_FORTRAN=true NO_GDB=true NO_I4B=true NO_IPFILTER=true NO_PF=true NO_AUTHPF=true NO_KERBEROS=true NO_NIS=true NO_TCSH=true NO_USB=true NO_VINUM=true NOATM=true NOGAMES=true NOINET6=true NOINFO=true NOPROFILE=true ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
