Please test latest /bin/sh
There had been some trouble with fixing a pipeline bug in /bin/sh. The last version appears to work, although it was developed on observation, not understanding, if you know what I mean ;-) If you have complicated shell scripts, would you please test -current's /bin/sh (with eval.c v. 1.25) on it? Critical are long pipelines, especially in backquote or here-documents and when receivers (not senders) terminate the run. Thanks Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe
subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
Luoqi Chen wrote:
Since sometime last month, rc5des failed to start from my rc.local. I did
a little investigation and it turned out that rc5des was started but later
terminated by a SIGHUP. During its brief lifetime, /dev/console was its
control terminal. Does anyone know what was going on?
Something is revoking /dev/console, most of the time, but it varies.
Other times, you get garbage when /etc/rc exits (when using a serial
console).
For example, run from rc.d:
336 con- I+ 0:00.01 /bin/sh /usr/local/bin/safe_mysqld --user=mysql
355 con- S+ 0:00.04 /usr/local/libexec/mysqld --basedir=/usr/local --data
revoke(2)ed.
This is a plain syscons boot, nothing special, didn't go into single user.
syslog(3) also suffers as a result of this - it closes and reopens /dev/
console to get around it when asked to do LOG_CONS. fstat(2) on the fd to
/dev/console returns EBADF. This broke postfix too.
Each time I raised the issue, bde told me it wasn't happening. But *something*
is revoking /dev/console, either directly or via a revoke on /dev/ttyv0:
pwroot@overcee[10:50pm]~-104# fstat | grep none
root sh 3362 - -none-
root cron 2180 - -none-
root cron 2181 - -none-
root cron 2182 - -none-
root syslogd 1458 - -none-
root adjkerntz 400 - -none-
root adjkerntz 401 - -none-
root adjkerntz 402 - -none-
pwroot@overcee[10:59pm]~ports/sysutils/lsof-111# lsof | grep revoke
adjkerntz 40root0u VBAD (revoked)
adjkerntz 40root1u VBAD (revoked)
adjkerntz 40root2u VBAD (revoked)
syslogd145root8w VBAD (revoked)
cron 218root0u VBAD (revoked)
cron 218root1u VBAD (revoked)
cron 218root2u VBAD (revoked)
sh 336root2u VBAD (revoked)
init(8) does a revoke on /dev/ttyv0 after /etc/rc finishes and before the
ttyv0 getty fires up, so I suspect an aliasing problem, but I can't see
what's doing it. (I haven't been annoyed enough to find out what's really
happening)
Oh, also, the rc5des client has changed over the last few months. I found I
had to change it's startup method a few times.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
On Thu, 18 Nov 1999, Peter Wemm wrote: Luoqi Chen wrote: Since sometime last month, rc5des failed to start from my rc.local. I did a little investigation and it turned out that rc5des was started but later terminated by a SIGHUP. During its brief lifetime, /dev/console was its control terminal. Does anyone know what was going on? Something is revoking /dev/console, most of the time, but it varies. Other times, you get garbage when /etc/rc exits (when using a serial console). /etc/rc's shell is a controlling process with control terminal /etc/console, so /dev/console is supposed to be revoked when /etc/rc's shell exits. syslog(3) also suffers as a result of this - it closes and reopens /dev/ console to get around it when asked to do LOG_CONS. fstat(2) on the fd to /dev/console returns EBADF. This broke postfix too. I think you mean syslogd(8). syslog(3) writes directly to the console, so it has to open it. Each time I raised the issue, bde told me it wasn't happening. But *something* I don't remember it. There were different problems with /dev/console being aliased with user ttys. is revoking /dev/console, either directly or via a revoke on /dev/ttyv0: pwroot@overcee[10:50pm]~-104# fstat | grep none root sh 3362 - -none- root cron 2180 - -none- root cron 2181 - -none- root cron 2182 - -none- root syslogd 1458 - -none- root adjkerntz 400 - -none- root adjkerntz 401 - -none- root adjkerntz 402 - -none- This is almost what I'd expect. adjkerntz calls daemon() with the noclose flag set so it soon ends up with dead file descriptors instead of closed ones. Most other daemons started by /etc/rc are apparently more careful. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How to upgrade from 3.3 to 4
Hello everyone! I'm trying to update from 3.3-R to 4.0-current but without success. cc every time died on the same place. I upgraded via sources to 3.3-stable without any problem. When I try again cc died with message "Bad system call" I wrote in /etc/makefile.conf CC=/usr/local/bin/gcc295 CXX=/usr/local/bin/g++295 NOTOOLS= and now it can't locale libc.so.4 :( I took a look at maillist and found the same problem 2.2.x-3.0 upgrade. If I understood right it was because of a function moved from kernel to library. Is my problem known or I should post more logs? Vadim Chekan. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gdb slain in drive-by commit, film at 11
Gdb has stopped working recently in -current. In a snapshot from
October 24th, it's fine. In a snapshot from November 15th (before
the great gcc switchover), it's hosed. I've been told it's hosed in
today's -current as well. Here are the symptoms:
tuba# uname -sr
FreeBSD 4.0-19991115-CURRENT
tuba# cat f.c
#include stdio.h
main()
{
printf("hello world\n");
}
tuba# cc -g f.c
tuba# gdb -q a.out
(gdb) run
Starting program: /tmp/a.out
warning: find_solib: Can't read pathname for load map: Bad address
Segmentation fault (core dumped)
tuba#
A statically compiled executable works though:
tuba# cc -static -g f.c
tuba# gdb -q a.out
(gdb) run
Starting program: /tmp/a.out
hello world
Program exited with code 014.
(gdb)
Okay, 'fess up: who's the wise guy.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
=
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
FreeBSD version of DRM?
Now that a working version of the Direct Rendering Manager (along with an open source version of glide 3) has been released for Linux on a decent consumer level card, is anyone interested in porting it over to FreeBSD? It could well displace my TNT2U. Stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4
Vadim Chekan wrote: Hello everyone! I'm trying to update from 3.3-R to 4.0-current but without success. cc every time died on the same place. I upgraded via sources to 3.3-stable without any problem. When I try again cc died with message "Bad system call" I wrote in /etc/makefile.conf CC=/usr/local/bin/gcc295 CXX=/usr/local/bin/g++295 NOTOOLS= Remove that, it would not work anyway! and now it can't locale libc.so.4 :( I took a look at maillist and found the same problem 2.2.x-3.0 upgrade. If I understood right it was because of a function moved from kernel to library. Is my problem known or I should post more logs? As I'm understanding, currently upgrading process should be as following: 1) Build 4.0 /usr/sbin/config using installed 3.3 tools 2) Using this config configure and build 4.0 kernel using standard 3.3 tools 3) Reboot using 4.0 kernel (preferably to the single-user mode to avoid possible ponflicts between 3.3 userland and 4.0 kernel). 4) Build and install everything (world) 5) Using mergemaster (which is in the 4.0 base tree now) update your configuration files in /etc -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD version of DRM?
On Thu, Nov 18, 1999 at 05:16:55PM +, Stephen Hocking wrote: Now that a working version of the Direct Rendering Manager (along with an open source version of glide 3) has been released for Linux on a decent consumer level card, is anyone interested in porting it over to FreeBSD? It could well displace my TNT2U. If you do get a group together, please keep me in the loop. I've love to have more people involved with the project now that it is open. We're working on getting a public repository in place, and it would be good to have all this code in one place. - |Daryll To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world fails
sorry i'm don't put error message i'm build and install -CURRENT kernel , and trying make world cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/lex.c /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/lex.c: In function `reinit_parse_for_block':/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/lex.c:1502: `RETURN_KEYWORD' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/lex.c:1502: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/lex.c:1502: for eachfunction it appears in.) *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD version of DRM?
Hi Daryll, is anyone interested in porting it over to FreeBSD? I'm interested in porting Glide to FreeBSD. I've got a Voodoo 3 2000. Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD version of DRM?
I have no programming skills, but I will test it when testers are needed. - Original Message - From: Roger Hardiman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, November 18, 1999 12:52 PM Subject: Re: FreeBSD version of DRM? Hi Daryll, is anyone interested in porting it over to FreeBSD? I'm interested in porting Glide to FreeBSD. I've got a Voodoo 3 2000. Roger -- Roger Hardiman| Telepresence Research Group [EMAIL PROTECTED] | DMEM, University of Strathclyde tel: 0141 548 2897| Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557| http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In message Pine.BSF.4.10.9911172341110.397-10@localhost Alex Zepeda writes: : Or perhaps restricting -U to root only? Since -e w/out -U isn't harmful, : no? -e w/o -U is still harmful. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
On Thu, 18 Nov 1999 23:01:10 +0800, Peter Wemm [EMAIL PROTECTED] said: root cron 2180 - -none- root cron 2181 - -none- root cron 2182 - -none- root adjkerntz 400 - -none- root adjkerntz 401 - -none- root adjkerntz 402 - -none- Buggy daemons that don't close their standard file descriptors. (On my machine I also have radiusd and amd.) init(8) does a revoke on /dev/ttyv0 after /etc/rc finishes and before the ttyv0 getty fires up, so I suspect an aliasing problem, but I can't see what's doing it. (I haven't been annoyed enough to find out what's really happening) As Bruce explained, the revocation happens automatically when the session leader of the /etc/rc process exits. (It happens automatically when any session leader exits, in point of fact.) Beyond the issue of buggy daemons, this all looks peachy to me. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4 - Clarification please!
Hi! I'm in almost the same situation as mr Chekan. I have a 3.3-STABLE (SMP) system and I want to move to CURRENT. I have modified my cvs-scripts and updated the sources a few times the last couple of weeks. The problem is when I try to do buildworld. It crashes with things like: cc -static -O -pipe -I. -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/objc -I/usr/obj/usr/src/tmp/usr/include -static -o gencheck gencheck.o ./gencheck tree-check.h *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Alexander Langer wrote: Yes. Probably you've not built/booted a -current kernel before you build world. Do you mean that I should build a new kernel *before* I do buildworld? Is that possible? Some clarification would be great. I've looked at the FreeBSD Diary about staying current and the checking the handbook, but can't get this to work... help? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4 - Clarification please!
Thus spake Jag ([EMAIL PROTECTED]): I'm in almost the same situation as mr Chekan. I have a 3.3-STABLE (SMP) system and I want to move to CURRENT. I have modified my cvs-scripts and updated the sources a few times the last couple of weeks. The problem is when I try to do buildworld. It crashes with things like: Hmm. in some of these days the cc should change (to egcs or such, don't know exaclty). See the last HEADS-UP mail to -current. Alexander Langer wrote: Yes. Probably you've not built/booted a -current kernel before you build world. Do you mean that I should build a new kernel *before* I do buildworld? Is that possible? Yes. It will boot with some warnings but you can build everything. Only xdm didn't work for me, I had to startx manually. BTW: Thas has been on -current a while ago, see the archives for the reasons why you need this. Search for some "HEADS UP" mails. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4 - Clarification please!
Jag [EMAIL PROTECTED] wrote: Alexander Langer wrote: Yes. Probably you've not built/booted a -current kernel before you build wo rld. Do you mean that I should build a new kernel *before* I do buildworld? Is that possible? Yes and yes. Some clarification would be great. I've looked at the FreeBSD Diary about staying current and the checking the handbook, but can't get this to work... help? If you try to use -current, the handbook (unfortunately) and any web site (such as FreeBSD diary) are likely to be of little help (and, in this case, are misleading), due the constantly-changing nature of -current. As others have said, in numerous postings since seemingly time immemorial, anyone who wants to use -current must also follow the -current mailing list (and preferably others). At the very least (if you've just joined -current), one should scan through the old -current archives for at least a month or two back. *THOROUGHLY reading /usr/src/UPDATING is also a must. Yes, this does appear to be a lot of work, but, if you do this, you get to find out about problems like "you must first build a kernel" (and also the method for doing so). Also, you may run into other problems. You'll find out about any if you read -current. Also note that -current is not guaranteed to work. As -current is used for developing new features and additions, it can be buggy, and may completely crash and burn at times. Use it at your own risk. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
/etc/rc's shell is a controlling process with control terminal /etc/console, so /dev/console is supposed to be revoked when /etc/rc's shell exits. Control terminal is for job control, and we don't need job control during /etc/rc's execution, so why don't we change init not to acquire a control terminal when executing /etc/rc. Then there's no need for the revoke, syslogd/postfix would be happy, and anything that doesn't daemonize could also be safely started as a background process. For now, I'll be using nohup to start rc5des. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4 - Clarification please!
Yes, there was a change in the signal handling that requires the kernel for 4.0 to be built and booted prior to building userland for 4.0. (This is not from experience, this is from watching the current mailing list for the past year). I believe the -current mailing list had lots of traffic on this starting sometime in October. m "To keep in silence our designs, my friends would think I was a nut" Peter Gabriel, Solsbury Hill On Thu, 18 Nov 1999, Jag wrote: Hi! I'm in almost the same situation as mr Chekan. I have a 3.3-STABLE (SMP) system and I want to move to CURRENT. I have modified my cvs-scripts and updated the sources a few times the last couple of weeks. The problem is when I try to do buildworld. It crashes with things like: cc -static -O -pipe -I. -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/objc -I/usr/obj/usr/src/tmp/usr/include -static -o gencheck gencheck.o ./gencheck tree-check.h *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Alexander Langer wrote: Yes. Probably you've not built/booted a -current kernel before you build world. Do you mean that I should build a new kernel *before* I do buildworld? Is that possible? Some clarification would be great. I've looked at the FreeBSD Diary about staying current and the checking the handbook, but can't get this to work... help? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
: : /etc/rc's shell is a controlling process with control terminal /etc/console, : so /dev/console is supposed to be revoked when /etc/rc's shell exits. : :Control terminal is for job control, and we don't need job control during :/etc/rc's execution, so why don't we change init not to acquire a control :terminal when executing /etc/rc. Then there's no need for the revoke, :syslogd/postfix would be happy, and anything that doesn't daemonize could :also be safely started as a background process. For now, I'll be using :nohup to start rc5des. : :-lq no control terminal == no signals == no ^C'ing hung programs during startup (for example, when you need to boot a machine without a working network and sendmail and other programs stop the boot sequence in its tracks trying to do DNS lookups). -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
arplookup 127.0.0.1 failed: could not allocate llinfo
With the latest current, whenever I start amd, I would see a lot of log messages repeating: arplookup 127.0.0.1 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 127.0.0.1rt If I ifconfig my ether interface down, as expected, the messages would stop. It's puzzling that a packet destined for 127.0.0.1 could end up on the output queue of an ethernet card. It happens only if I run amd, I could telnet to localhost without any problem. Any idea? -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
: :In message Pine.BSF.4.10.9911172341110.397-10@localhost Alex Zepeda writes: :: Or perhaps restricting -U to root only? Since -e w/out -U isn't harmful, :: no? : :-e w/o -U is still harmful. : :Warner I am all for removing -e, but I don't really like the idea of making it optional nor do I like the idea of trying to maintain the capability for the user's own processes - that simply makes the code even more complex then it already is. The danger is that the option exists in the first place. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In message [EMAIL PROTECTED] Matthew Dillon writes: : I am all for removing -e, but I don't really like the idea of making : it optional nor do I like the idea of trying to maintain the capability : for the user's own processes - that simply makes the code even more : complex then it already is. The danger is that the option exists in : the first place. I'm not for removing -e. It is useful to root for debugging. If ps can get this info from procfs, procfs could effectively enforce this restriction. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In article [EMAIL PROTECTED] you write: I am all for removing -e, but I don't really like the idea of making it optional nor do I like the idea of trying to maintain the capability for the user's own processes - that simply makes the code even more complex then it already is. The danger is that the option exists in the first place. I both do and do not want it to be removed. The code _does not_ need to be more complex, as procfs already implements the correct restrictions. (Simply dropping the SGID bit off of ps(1), and teaching it to use procfs only, will do it; dropping the SGID bit, and having it use /proc/pid/mem instead of /dev/kmem, will do the same thing. I believe; I don't know ps well enough to figure this all out yet, but that was certainly one of my goals when I wrote the bloody thing.) P.S. You see that Reply-To: line in the header? It's there for a reason. If you must override it, don't send it to both me and the list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cpu name
supped made world a min ago: check out the CPU: name I am using AMD K6-2 333Mhz Byung --- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Nov 18 21:23:27 EST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/NOWCOOL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 334400765 Hz CPU: \^E (334.40-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 67100672 (65528K bytes) avail memory = 62357504 (60896K bytes) Preloaded elf kernel "kernel" at 0xc029f000. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
:
: no control terminal == no signals == no ^C'ing hung programs during
: startup (for example, when you need to boot a machine without a working
: network and sendmail and other programs stop the boot sequence in its
: tracks trying to do DNS lookups).
:
: -Matt
: Matthew Dillon
: [EMAIL PROTECTED]
:
:Hmm, good point. So I still need to find a way to start up rc5des, it seems
:that rc5des installs a SIGHUP handler and therefore nohup is useless. I wish
:there were a noctty...
:
:-lq
Your wish is my command ... I needed the same thing for BEST for many
things. I call the program 'notty'. Included below.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
/*
* NOTTY.C
*
* NOTTY [-012] command
*/
#include stdio.h
#include stdlib.h
#include string.h
#include stdarg.h
#include fcntl.h
#include signal.h
#include sys/ioctl.h
#include sys/time.h
#include sys/wait.h
main(ac, av)
char *av[];
{
char *opts = "";
int ttyfd;
if (av[1]) {
if (av[1][0] == '-') {
opts = av[1];
++av;
}
}
ttyfd = open("/dev/null", O_RDWR);
if (strchr(opts, '0') == NULL ttyfd != 0)
dup2(ttyfd, 0);
if (strchr(opts, '1') == NULL ttyfd != 1)
dup2(ttyfd, 1);
if (strchr(opts, '2') == NULL ttyfd != 2)
dup2(ttyfd, 2);
if (ttyfd 2)
close(ttyfd);
{
int fd = open("/dev/tty", O_RDWR);
if (fd = 0) {
ioctl(fd, TIOCNOTTY, 0);
close(fd);
}
}
/* signal(SIGCHLD, SIG_IGN); */
if (fork() == 0) {
setpgrp();
exit(execvp(av[1], av + 1));
}
exit(0);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
Sean Eric Fagan wrote: In article [EMAIL PROTECTED] m you write: I am all for removing -e, but I don't really like the idea of making it optional nor do I like the idea of trying to maintain the capability for the user's own processes - that simply makes the code even more complex then it already is. The danger is that the option exists in the first place. I both do and do not want it to be removed. The code _does not_ need to be more complex, as procfs already implements the correct restrictions. (Simply dropping the SGID bit off of ps(1), and teaching it to use procfs only, will do it; dropping the SGID bit, and having it use /proc/pid/mem instead of /dev/kmem, will do the same thing. I believe; I don't know ps well enough to figure this all out yet, but that was certainly one of my goals when I wrote the bloody thing.) Well, it's already done. It (ps) hasn't used /dev/kmem for a Very Long Time. The only thing it used procfs for was the argv, envp and getting p_stats from the user struct. The code to get p_stats via procfs has been directly implicated in causing panics and crashes, so it (ps) gets it with the sysctl it uses to get the rest of the information. The sole user of / proc in ps now is to get the envp, and ps is no longer setgid. ps now depends on /proc's permissions enforcement to allow access to /proc/*/mem for getting envp for processes that the user owns. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: init runs with console as control terminal?
On Thu, 18 Nov 1999 22:59:28 -0500 (EST), Luoqi Chen [EMAIL PROTECTED] said:
Hmm, good point. So I still need to find a way to start up rc5des, it seems
that rc5des installs a SIGHUP handler and therefore nohup is
useless.
Bug the authors to fix it? daemon(3) is provided for a reason!
Here's my version of a simple daemonizing program Neither
TIOCNOTTY nor setpgid() is sufficient to detach from a terminal
session in a POSIX environment; setsid() is required. daemon(3) does
a nice job of encapsulating this along with the other more obvious
prerequisites.
#include sys/types.h
#include err.h
#include stdlib.h
int
main(int argv, char *argv)
{
static char *shargs[4] = { "sh", "-c" };
if (argv[1] == 0 || argv[2] != 0)
errx(1, "must specify exactly one argument");
if (daemon(1, 0) 0)
err(1, "daemon");
shargs[2] = argv[1];
execv("/bin/sh", shargs);
/*
* Not much point in printing an error message since the tty
* is already gone. It doesn't really matter what we return
* here, either, since the only one waiting is init.
*/
return 1;
}
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4 - Clarification please!
People, 1) Search -current archives if you are new to the list. 2) See that /usr/src/UPDATING file? READ IT! HandbookFreeBSD diary are *NOT* the kind of resource you resort to if you want to run -current. Things in -current have not been documented because they are happening here and now. And if you are not subscribed to cvs-all and _reading it_, back off from -current. Simply put, -current is not for users, and users are not supported. Heck, nobody is supported, people are expected to bring their own support with them. :-) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: man reads /etc/rc.conf?
On Wed, Nov 10, 1999 at 01:47:46PM +0100, [EMAIL PROTECTED] wrote: /usr/bin/apropos contains: ---snip--- # If possible check global system configuration file for additional # man locales installed if [ -r /etc/defaults/rc.conf ] ; then . /etc/defaults/rc.conf elif [ -r /etc/rc.conf ] ; then . /etc/rc.conf fi ---snip--- Hmm... aside from whether or not apropos should be reading in rc.conf, isn't this code fragment doing the wrong thing in regards to the way we have /etc/defaults/rc.conf and /etc/rc.conf setup nowadays? Shouldn't it read _both_ if present? Ie: if [ -r /etc/defaults/rc.conf ] ; then . /etc/defaults/rc.conf fi if [ -r /etc/rc.conf ] ; then . /etc/rc.conf fi William R. Somsky [EMAIL PROTECTED] Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
On Thu, 18 Nov 1999, Warner Losh wrote: In message Pine.BSF.4.10.9911172341110.397-10@localhost Alex Zepeda writes: : Or perhaps restricting -U to root only? Since -e w/out -U isn't harmful, : no? -e w/o -U is still harmful. ps -e w/out -U only shows variables for processes owned by that user, no? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
On Thu, Nov 18, 1999 at 05:04:20PM -0800, Matthew Dillon wrote: I am all for removing -e, but I don't really like the idea of making it optional nor do I like the idea of trying to maintain the capability for the user's own processes - that simply makes the code even more complex then it already is. The danger is that the option exists in the first place. Though I respect your statement about code complexity I'm not for removing the option, which has been available to the ps command for such a long time and definitively is a useful debugging tool (for root !). This would create a major difference to the other BSD's which is not easily understandable. "ps -e" and "ps -e -U" is useful for debugging purposes, so it should simply be restricted to root as it has been done for putting a network device into promiscous mode or other things. By simply removing it (without thinking about alternatives) I think FreeBSD looses some points ... I thought we were the team that doesn't do radical changes without a good reason ;-) Security is a good reason. But simply removing it without restricting it is in my opineon not a good style. Another alternative to restricting it to root would be, to combine it with the security level, that we can configure in rc.conf. But that's only an idea, I personally don't like magic things to happen, only because I raised a security level by one. Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cpu name
-On [19991119 04:02], Byung Yang ([EMAIL PROTECTED]) wrote:
supped made world a min ago:
check out the CPU: name
I am using AMD K6-2 333Mhz
---
CPU: \^E (334.40-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x580 Stepping = 0
Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX
AMD Features=0x8800SYSCALL,3DNow!
I made world yesterday morning on two boxes, both are GenuineIntel and
have no problems whatsoever.
Looking at /usr/src/sys/i386/i386/identcpu.c I see that the 0x580 is:
case 0x580:
strcat(cpu_model, "K6-2");
break;
Which gets copied into:
printf("CPU: ");
strncpy(cpu_model, i386_cpus[cpu].cpu_name, sizeof cpu_model);
But I can't find anything remotely related that would corrupt the
strncpy to print \^E.
--
Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl
The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai
Network/Security SpecialistBSD: Technical excellence at its best
I succeed him; no one could replace him.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In message Pine.BSF.4.10.9911182311590.338-10@localhost Alex Zepeda writes: : ps -e w/out -U only shows variables for processes owned by that user, no? ps -ea. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In message [EMAIL PROTECTED] Andreas Klemm writes: : By simply removing it (without thinking about alternatives) I : think FreeBSD looses some points ... I thought we were the team : that doesn't do radical changes without a good reason ;-) That's why I'm not in favor of removing it. That's far too radical. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current hangs when dump is run?
Current seems to hangs, when amanda tries to run dump. This appeared approximately 2 weeks ago, and is present in yesterdays current also. #0 0xc013daa4 in boot () (kgdb) bt #0 0xc013daa4 in boot () #1 0xc013de41 in panic () #2 0xc011d739 in db_panic () #3 0xc011d6d9 in db_command () #4 0xc011d79e in db_command_loop () #5 0xc011f82f in db_trap () #6 0xc02011fb in kdb_trap () #7 0xc020f444 in trap () #8 0xc0201457 in Debugger () #9 0xc01fcb12 in scgetc () #10 0xc01f827d in sckbdevent () #11 0xc01f1a9b in atkbd_intr () #12 0xc021cd84 in atkbd_isa_intr () #13 0xc0202fe2 in vec1 () #14 0xc0140a55 in tsleep () #15 0xc0146889 in diskopen () #16 0xc0170251 in spec_open () #17 0xc017014d in spec_vnoperate () #18 0xc01bb579 in ufs_vnoperatespec () #19 0xc016a57c in vn_open () #20 0xc01669dd in open () #21 0xc020fd12 in syscall () #22 0xc0201b06 in Xint0x80_syscall () #23 0x804b91a in ?? () #24 0x804b6b3 in ?? () #25 0x80491c0 in ?? () and ps shows [127:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.4 -N kernel.4 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND amanda 380 99.0 0.0 6280 ?? R 1Jan70 0:00.00 (dump) root 1 0.0 0.0 5160 ?? ILs 1Jan70 0:00.02 /sbin/init -- root 2 0.0 0.0 00 ?? RL1Jan70 0:00.01 (pagedaemon) root 3 0.0 0.0 00 ?? DL1Jan70 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? RL1Jan70 0:00.01 (bufdaemon) root 5 0.0 0.0 00 ?? RL1Jan70 0:00.28 (syncer) . I have kernel and core saved, if someone needs them. best regards, taavi --- Taavi Talvik| Internet: [EMAIL PROTECTED] Unineti Andmeside AS| phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
On Fri, 19 Nov 1999, Warner Losh wrote: In message Pine.BSF.4.10.9911182311590.338-10@localhost Alex Zepeda writes: : ps -e w/out -U only shows variables for processes owned by that user, no? ps -ea. Then perhaps -a and -U should be disabled? *grin* - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In message Pine.BSF.4.10.9911182331120.338-10@localhost Alex Zepeda writes: : Then perhaps -a and -U should be disabled? *grin* No. -e, -a, -U are all use for the sysadmin. They can provide sensitive information, so should have sensible access policies placed upon their use. While the current set of access policies may be less than idea, it doesn't militate for their complete removal. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
On Fri, 19 Nov 1999, Warner Losh wrote: In message Pine.BSF.4.10.9911182331120.338-10@localhost Alex Zepeda writes: : Then perhaps -a and -U should be disabled? *grin* No. -e, -a, -U are all use for the sysadmin. They can provide sensitive information, so should have sensible access policies placed upon their use. While the current set of access policies may be less than idea, it doesn't militate for their complete removal. Erk. That came out wrong. I meant removal for non root or perhaps non gid wheel? or somesuch. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: man reads /etc/rc.conf?
On 18 Nov, William R. Somsky wrote: Hmm... aside from whether or not apropos should be reading in rc.conf, isn't this code fragment doing the wrong thing in regards to the way we have /etc/defaults/rc.conf and /etc/rc.conf setup nowadays? No, look at the last lines of /etc/defaults/rc.conf and also search for rc_conf_files in it. Bye, Alexander. -- Actually, a more important date is January 1, 2000, when many computer programs across the world could break. Richard W. Stevens, Advanced Programming in the UNIX Environment, _1993_ http://netchild.home.pages.de A.Leidinger @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH for testing
In message Pine.BSF.4.10.9911182338520.338-10@localhost Alex Zepeda writes: : Erk. That came out wrong. I meant removal for non root or : perhaps non gid wheel? or somesuch. Actually, you wanna do access control like procfs does (will do?) for its cmdline file. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs when dump is run?
If you're using the ata driver, please remove the ad_sleep() call at the bottom of the adopen() in ata-disk.c and see if that helps you. Poul-Henning In message [EMAIL PROTECTED], Taavi Talvi k writes: Current seems to hangs, when amanda tries to run dump. This appeared approximately 2 weeks ago, and is present in yesterdays current also. #0 0xc013daa4 in boot () (kgdb) bt #0 0xc013daa4 in boot () #1 0xc013de41 in panic () #2 0xc011d739 in db_panic () #3 0xc011d6d9 in db_command () #4 0xc011d79e in db_command_loop () #5 0xc011f82f in db_trap () #6 0xc02011fb in kdb_trap () #7 0xc020f444 in trap () #8 0xc0201457 in Debugger () #9 0xc01fcb12 in scgetc () #10 0xc01f827d in sckbdevent () #11 0xc01f1a9b in atkbd_intr () #12 0xc021cd84 in atkbd_isa_intr () #13 0xc0202fe2 in vec1 () #14 0xc0140a55 in tsleep () #15 0xc0146889 in diskopen () #16 0xc0170251 in spec_open () #17 0xc017014d in spec_vnoperate () #18 0xc01bb579 in ufs_vnoperatespec () #19 0xc016a57c in vn_open () #20 0xc01669dd in open () #21 0xc020fd12 in syscall () #22 0xc0201b06 in Xint0x80_syscall () #23 0x804b91a in ?? () #24 0x804b6b3 in ?? () #25 0x80491c0 in ?? () and ps shows [127:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.4 -N kernel.4 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND amanda 380 99.0 0.0 6280 ?? R 1Jan70 0:00.00 (dump) root 1 0.0 0.0 5160 ?? ILs 1Jan70 0:00.02 /sbin/init -- root 2 0.0 0.0 00 ?? RL1Jan70 0:00.01 (pagedaemon) root 3 0.0 0.0 00 ?? DL1Jan70 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? RL1Jan70 0:00.01 (bufdaemon) root 5 0.0 0.0 00 ?? RL1Jan70 0:00.28 (syncer) . I have kernel and core saved, if someone needs them. best regards, taavi --- Taavi Talvik| Internet: [EMAIL PROTECTED] Unineti Andmeside AS| phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: man reads /etc/rc.conf?
On Fri, Nov 19, 1999 at 08:41:30AM +0100, Alexander Leidinger wrote: On 18 Nov, William R. Somsky wrote: Hmm... aside from whether or not apropos should be reading in rc.conf, isn't this code fragment doing the wrong thing in regards to the way we have /etc/defaults/rc.conf and /etc/rc.conf setup nowadays? No, look at the last lines of /etc/defaults/rc.conf and also search for rc_conf_files in it. Um... yeah... I knew that... at one time anyway... nevermind... William R. Somsky [EMAIL PROTECTED] Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to upgrade from 3.3 to 4
Vadim Chekan wrote: Hello everyone! I'm trying to update from 3.3-R to 4.0-current but without success. Thanks to all! Now I know what to do. 4.0 kernel is installed and is bootable. I need to chouse few hours to build world. Vadim Chekan. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mounting double-ended SCSI disks
Hi, In our project, we're trying to connect two PCs to both ends of a SCSI chain. I've got it somewhat working, but have a couple of questions re. mounting the filesystems. If I mount the filesystem from one machine (A) as read-write, then the other one (B) can't mount it read-write because the clean flag is not set. This is ok. Also, I can mount the disk read-only from both A and B. (I even read the entire contents of a 20GB partition from both machines at the same time -- worked without a hitch.) However, if I try to mount it from B read-only while A is mounting it read-write, it succeeds. This looks dangerous, as A writing data onto the disk could cause B's cache to go stale without B knowing it. Is it a good idea to allow read-only mounts of a dirty filesystem anyway? (The filesystem could be corrupted, right?) Another problem is if A is mounting it read-only and then B tries to mount it read-write. This succeeds and is dangerous for the same reason as the last example. Since A can't write anything to the disk, I guess there is no way we can avoid this situation. (The only way I could think of avoiding a crash due to stale cache data was to have A check the clean flag before every read, but that seems excessively expensive.) Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: mounting double-ended SCSI disks
However, if I try to mount it from B read-only while A is mounting it read-write, it succeeds. This looks dangerous, as A writing data onto the disk could cause B's cache to go stale without B knowing it. Is it a good idea to allow read-only mounts of a dirty filesystem anyway? (The filesystem could be corrupted, right?) UFS/FFS doesn't expect anybody else to muck about on the device while they have it open, and violating that is a bad idea, I cannot tell if it would lead to panics, but I can imagine a couple of ways it would become quantum mechanical in such a setup. A couple of filesystem have been designed over the years which allow for multiple machine access, but they tend to have lousy performance because of caching being so inefficient. One of the better implementations cheated, they stored the stuff in an Oracle database on a third machine, but used a filesystem interface... -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: a few suggestions/comments on 3.0-RELEASE
Igor Roshchin wrote: I've encountered this problems while installing 3.0-RELEASE on a PII-350 with ASUS P2B-LS motherboard (i.e. there is Adaptec U2W adapter and Intel EtherExpress 100/10 on board) All HDDs are UW SCSI. 2. I didn't find any documentation in the man pages which describes the features of the new bootstrap - i.e. that it is capable of handling slice number. /boot.help doesn't have that reference either. (I mean the possibility of specifying 2:da(1,2,a)kernel where the second 2 is for the slice number) The only place I found where it was addressed was somebody's answer in -questions archive, and on the -stable list. The documentation is slowly being updated to reflect the features of the new boot code. There's nothing about specifying slices yet; though the preferred way to accomplish most boot stuff in 3.x is by way of the all-singing, all-dancing /boot/loader program rather than boot2. Also, it might be nice if the disklabel(8) man pages explicitely say that the bootstrap code can be installed on each slice. (am I wrong ?) You're right, the bootblocks can be installed on each slice, and this also needs documenting. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: mounting double-ended SCSI disks
* However, if I try to mount it from B read-only while A is mounting it * read-write, it succeeds. This looks dangerous, as A writing data onto * the disk could cause B's cache to go stale without B knowing it. Is * it a good idea to allow read-only mounts of a dirty filesystem anyway? * (The filesystem could be corrupted, right?) * * UFS/FFS doesn't expect anybody else to muck about on the device * while they have it open, and violating that is a bad idea, I cannot I know that, but that's not the point here. If the filesystem is marked dirty, it could very well be corrupted. Why am I allowed to mount it (even read-only)? I use softupdates on these filesystems, and my understanding is that it is theoretically safe to mount a filesystem without fsck after a crash if it's using softupdates. But I don't see mount checking that (if it is, it should allow read-write mounts too -- mount -f is not quite the same thing is it will override the check even for non-softupdates case). * tell if it would lead to panics, but I can imagine a couple of ways * it would become quantum mechanical in such a setup. * A couple of filesystem have been designed over the years which allow * for multiple machine access, but they tend to have lousy performance * because of caching being so inefficient. One of the better * implementations cheated, they stored the stuff in an Oracle database * on a third machine, but used a filesystem interface... To clarify, we're not trying to build a distributed filesystem here. We're planning to use the disks from both machines read-only most of the time, and unmount it from one machine if the other needs to write to it. I was just wondering what kind of safety belts the OS already has, so we can decide what else we need to implement. Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3.0.1 soon ?
On Fri, Jan 15, 1999 at 11:45:02PM -0500, Mike Tancsa wrote: Just wondering if there is an updated timeline for 3.0.1 release ? 15.01. + 'five' more days (Jordan said on -committers) -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CTM CVSUP differences
On Fri, Jan 15, 1999 at 08:46:23PM -0500, Chuck Robey wrote: Are you using any other tool besides ctm to touch your cvs archive? Are you doing commits locally? No. In terms of convenience, cvsup is supreme, but in terms of stability, Poul's baby here is the champ, so you have to really consider other places of corruption first. Mh, it seems that I have to double-check my environment. :-( Until now i've mounted my partitions async. Maybe it gets hosed somewhere (altought I didn't get any error messages). Yesterday I switched to soft-updates. I'll see, if it will be get better now. Boris -- b...@dva.in-berlin.de Boris Staeblow To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3.0.1 soon ?
On Fri, Jan 15, 1999 at 11:45:02PM -0500, Mike Tancsa wrote: Just wondering if there is an updated timeline for 3.0.1 release ? 15.01. + 'five' more days (Jordan said on -committers) + 0.1.0 - 0.0.1 release numbers luigi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: mounting double-ended SCSI disks
In message 199901161046.caa47...@silvia.hip.berkeley.edu, Satoshi Asami write s: * However, if I try to mount it from B read-only while A is mounting it * read-write, it succeeds. This looks dangerous, as A writing data onto * the disk could cause B's cache to go stale without B knowing it. Is * it a good idea to allow read-only mounts of a dirty filesystem anyway? * (The filesystem could be corrupted, right?) * * UFS/FFS doesn't expect anybody else to muck about on the device * while they have it open, and violating that is a bad idea, I cannot I know that, but that's not the point here. If the filesystem is marked dirty, it could very well be corrupted. Why am I allowed to mount it (even read-only)? how else would you fsck / if it was dirty ? -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't compile new kernel after CVSup...
A number of things seem to be changing rapidly. 1) cvsup and Do a make buildworld/installworld. worked for me yesterday. 2) See if you can build the GENERIC kernel. Worked for me. 3) check the stuff in your custom kernel vs. the GENERIC. There has been some sizable changes. You'l have to do a bit of cutting and pasting. Eddie. oZZ!!! wrote: Hello! After cvsuped my source tree, i try to compile a new kernel, c following: # config -r MY_KERNEL # cd ../../compile/MY_KERNEL # make depend # make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../libkern/umoddi3.c cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../pci/es1370.c ./../pci/es1370.c:150: warning: initialization from incompatible pointer type ../../i386/isa/snd/ulaw.h:40: warning: `dsp_ulaw' defined but not used cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../pci/ide_pci.c ../../pci/ide_pci.c: In function `ide_pci_candma': ../../pci/ide_pci.c:1462: structure has no member named `ctrlr' *** Error code 1 Stop. Something wrong? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, o...@etrust.ru P.S. 16.01.1999 - 4 days before 3.0-STABLE? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
trouble to link new kernel
Did a make world and then rm -rf ../../compile/TITAN config TITAN cd ../../compile/TITAN make depend all See errors below ... Am I missing something ? loading kernel syscons.o: In function `scvidprobe': syscons.o(.text+0x231): undefined reference to `vid_configure' syscons.o(.text+0x24e): undefined reference to `vid_allocate' syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' syscons.o: In function `sckbdprobe': syscons.o(.text+0x29a): undefined reference to `kbd_configure' syscons.o(.text+0x2be): undefined reference to `kbd_allocate' syscons.o(.text+0x2db): undefined reference to `kbd_get_keyboard' syscons.o: In function `scattach': syscons.o(.text+0x3a0): undefined reference to `kbdsw' syscons.o: In function `scopen': syscons.o(.text+0x5c2): undefined reference to `kbdsw' syscons.o: In function `sckbdevent': syscons.o(.text+0x822): undefined reference to `kbd_release' syscons.o(.text+0x8df): undefined reference to `kbdsw' syscons.o: In function `scioctl': syscons.o(.text+0x1d85): undefined reference to `kbdsw' syscons.o(.text+0x1df3): undefined reference to `kbdsw' syscons.o(.text+0x1e32): undefined reference to `kbdsw' syscons.o(.text+0x1f06): undefined reference to `kbdsw' syscons.o(.text+0x1f9e): undefined reference to `kbd_get_keyboard' syscons.o(.text+0x1fd9): undefined reference to `kbd_allocate' syscons.o(.text+0x2006): undefined reference to `kbd_release' syscons.o(.text+0x200f): undefined reference to `kbd_get_keyboard' syscons.o(.text+0x202c): undefined reference to `kbdsw' syscons.o(.text+0x209e): undefined reference to `kbd_release' syscons.o(.text+0x211e): undefined reference to `kbdsw' syscons.o: In function `sccngetch': syscons.o(.text+0x26c9): undefined reference to `kbdsw' syscons.o(.text+0x26fa): undefined reference to `kbdsw' syscons.o(.text+0x2748): undefined reference to `kbdsw' syscons.o(.text+0x276f): undefined reference to `kbdsw' syscons.o: In function `scrn_timer': syscons.o(.text+0x290d): undefined reference to `kbd_allocate' syscons.o(.text+0x291f): undefined reference to `kbd_get_keyboard' syscons.o(.text+0x2935): undefined reference to `kbdsw' syscons.o: In function `exchange_scr': syscons.o(.text+0x2eab): undefined reference to `vidsw' syscons.o(.text+0x2efc): undefined reference to `kbdsw' syscons.o: In function `scinit': syscons.o(.text+0x453e): undefined reference to `vid_get_adapter' syscons.o(.text+0x454b): undefined reference to `vidsw' syscons.o(.text+0x4567): undefined reference to `vidsw' syscons.o(.text+0x4725): undefined reference to `vidsw' syscons.o(.text+0x4744): undefined reference to `vidsw' syscons.o: In function `init_scp': syscons.o(.text+0x4a14): undefined reference to `vid_get_adapter' syscons.o(.text+0x4a20): undefined reference to `vidsw' syscons.o: In function `scgetc': syscons.o(.text+0x4dbe): undefined reference to `kbdsw' syscons.o(.text+0x53ac): undefined reference to `kbdsw' syscons.o: In function `scmmap': syscons.o(.text+0x55c7): undefined reference to `vidsw' syscons.o: In function `save_kbd_state': syscons.o(.text+0x5669): undefined reference to `kbdsw' syscons.o: In function `update_kbd_state': syscons.o(.text+0x56cd): undefined reference to `kbdsw' syscons.o(.text+0x5724): undefined reference to `kbdsw' syscons.o: In function `update_kbd_leds': syscons.o(.text+0x576e): undefined reference to `kbdsw' syscons.o: In function `set_mode': syscons.o(.text+0x57a9): undefined reference to `vidsw' syscons.o(.text+0x57e3): undefined reference to `vidsw' syscons.o(.text+0x586e): undefined reference to `vidsw' syscons.o(.text+0x58cb): undefined reference to `vidsw' syscons.o: In function `set_border': syscons.o(.text+0x58fb): undefined reference to `vidsw' syscons.o(.text+0x5a3c): more undefined references to `vidsw' follow psm.o: In function `enable_aux_dev': psm.o(.text+0xd): undefined reference to `send_aux_command' psm.o: In function `disable_aux_dev': psm.o(.text+0x4d): undefined reference to `send_aux_command' psm.o: In function `get_mouse_status': psm.o(.text+0xa9): undefined reference to `empty_aux_buffer' psm.o(.text+0xb0): undefined reference to `send_aux_command' psm.o(.text+0xfa): undefined reference to `read_aux_data' psm.o: In function `get_aux_id': psm.o(.text+0x154): undefined reference to `empty_aux_buffer' psm.o(.text+0x15f): undefined reference to `send_aux_command' psm.o(.text+0x19c): undefined reference to `read_aux_data' psm.o: In function `set_mouse_sampling_rate': psm.o(.text+0x1d6): undefined reference to `send_aux_command_and_data' psm.o: In function `set_mouse_scaling': psm.o(.text+0x232): undefined reference to `send_aux_command' psm.o: In function `set_mouse_resolution': psm.o(.text+0x28e): undefined reference to `send_aux_command_and_data' psm.o: In function `recover_from_error': psm.o(.text+0x393): undefined reference to `empty_both_buffers' psm.o(.text+0x399): undefined reference to `test_controller' psm.o(.text+0x3b5): undefined reference to `test_kbd_port' psm.o: In function `restore_controller':
SANE-1.0 Problems on CAM
I just pulled the latest SANE-1.0 package today for CAM/3.0-current (I'm on 3.0R). On my Microtek E6, it positions the head and gets ready to scan (sounding like normal) but as soon as it begins the movement to scan down the page, I get a dialog: Error during read: Error during device I/O. Seems like something in the SCSI subsystem or SANE isn't happy with getting the data back from the scanner. Anyone have an idea? Thanks, Randall FreeBSD-current/packages/All: -rw-r--r-- 1 569 207 1009577 Jan 13 01:47 sane-1.00.tgz To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SANE-1.0 Problems on CAM
On Sat, 16 Jan 1999, Randall Hopper wrote: I just pulled the latest SANE-1.0 package today for CAM/3.0-current (I'm on 3.0R). On my Microtek E6, it positions the head and gets ready to scan (sounding like normal) but as soon as it begins the movement to scan down the page, I get a dialog: Error during read: Error during device I/O. Seems like something in the SCSI subsystem or SANE isn't happy with getting the data back from the scanner. Anyone have an idea? Search hackers and current for information, someone posted patches to SANE that oughta help you out. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/3.0-current Thanks, Randall To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: trouble to link new kernel
Did a make world and then rm -rf ../../compile/TITAN config TITAN cd ../../compile/TITAN make depend all See errors below ... Am I missing something ? See http://www.freebsd.org/~yokota/sc_update.txt and update your kernel config file. Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CTM CVSUP differences
On Fri, 15 Jan 1999, Boris Staeblow wrote: Hello, Is it possible that there are slight differences between the CTM's and the real world ? Yes, there are differences. You can't get the optional security stuff via CTM while you can with CVSUP. Last time I tried it, this means you can't do a make release as Jordan's release Makefiles can't handle a total absense of that stuff (eBones? whatever its called). While you can download the missing security stuff, make release wants to check it out of your local cvs archive. I haven't found a way to put it there but I'm a cvs novice. -- David Kelly N4HHE, dke...@nospam.hiwaay.net = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. -- David Kelly N4HHE, dke...@nospam.hiwaay.net = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can the bootloader create a file or set a flag in the bootblocks?
Jaye Mathisen writes: It would be kind of cool if when managing a remote system if /kernel failed to boot, then on the next boot, the loader will fire up /kernel.old, or a /kernel.somethingorother. Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and have at least some assurance that I'll eventually be able to get back to a kernel I could use. In case in that discussion it wasn't clear, there *is* a way to do this: see man nextboot. Nextboot is woefully inadequate (and not supported anymore anyway). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Today's Make World
I haven't been able to make world since the texinfo problem. I don't see anyone else on the list with problems. Did I miss another change? Am I doing something wrong? Thanks, ed P.S. This is where I stopped this time. cvsup finished about 9:25 CST. DynaLoader.c:282: `NULL' undeclared (first use this function) DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
At 10:23 AM 1/16/99 -0600, Edwin Culp wrote: I haven't been able to make world since the texinfo problem. I don't see anyone else on the list with problems. Did I miss another change? Am I doing something wrong? Thanks, ed P.S. This is where I stopped this time. cvsup finished about 9:25 CST. DynaLoader.c:282: `NULL' undeclared (first use this function) DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type *** Error code 1 Stop. *** Error code 1 I have been getting that error all day yesterday. Remade world 2-3 times... after cvsupping... none of the changes fixed it, and I still 'perished' at the same spot you did. I figured... I might as well wait a few more days before the next cvsup so they can fix whatever they are working on. -Carroll Kong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: a few suggestions/comments on 3.0-RELEASE
Also, it might be nice if the disklabel(8) man pages explicitely say that the bootstrap code can be installed on each slice. (am I wrong ?) You're right, the bootblocks can be installed on each slice, and this also needs documenting. This doesn't need documenting. disklabel(8) knows nothing of slices. It installs labels and bootblocks on disk-like devices. Slices are just one type of disk-like device. All regular files larger than 1K and many devices are disk-like, thanks to device independence. For the bootstrap code to actual work, more is required. E.g., slices on vn disks are not bootable because the boot loader doesn't support vn disks. disklabel(8) knows nothing of this limitation. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
Carroll Kong wrote: I have been getting that error all day yesterday. Remade world 2-3 times... after cvsupping... none of the changes fixed it, and I still 'perished' at the same spot you did. I figured... I might as well wait a few more days before the next cvsup so they can fix whatever they are working on. -Carroll Kong Thanks, misery loves company. Have a great day ed To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: mounting double-ended SCSI disks
I know that, but that's not the point here. If the filesystem is marked dirty, it could very well be corrupted. Why am I allowed to mount it (even read-only)? Because you are root, and root never makes mistakes :-). how else would you fsck / if it was dirty ? Boot from an alternative device to clean up. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Suspend on Current
Is it just me, or is there anyone else experiencing system freezes on current after a zzz? -- Daniel C. Sobral(8-DCS) d...@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /boot/loader problem with unusual setup.
On Wed, Jan 13, 1999 at 10:00:48PM +0100, Andrzej Bialecki wrote:
Where ${rootdev} points to? Shouldn't you set it accordingly to disk3s1a:?
rootdev isn't set at all (as show says).
I can't imagine that this will make a change, as I am booting from
disk3, the problem stems from FreeBSD not realizing that this is wd0, i
think.
In fact, I tried it out, and it didn't help :-(
CU,
Sec (happy that the new bootblock also supports elf kernels)
--
Aufgrund eines Bugs in unserem Newsserver ist es nicht moeglich,
diesen offensichlich versehentlich geposteten Artikel zu canceln.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: ZIP+ detection, need testers for the patch
On Fri, Jan 15, 1999 at 11:13:09AM +, Doug Rabson wrote: On Fri, 15 Jan 1999, Nicolas Souchu wrote: Hi there, Currently, the ZIP+ probe is intrusive and sends char to the printer if no ZIP+ is connected. Here is a patch that corrects the problem for my printer, but I haven't any ZIP+ :) So, please check the ZIP+ is still detected. With this patch, I can *not* detect my ZIP+ (attached to a machine which detects it using the existing code). Ok :( Does the last ppbus committed code (with IEEE1284 support) detects your ZIP+ at boot? Something like IEEE1284 device found /NIBBLE... with its id 2 lines after? This may be another way to detect properly the ZIP+ Nicholas. -- Doug RabsonMail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /boot/loader problem with unusual setup.
On Sat, 16 Jan 1999, Stefan `Sec` Zehl wrote:
On Wed, Jan 13, 1999 at 10:00:48PM +0100, Andrzej Bialecki wrote:
Where ${rootdev} points to? Shouldn't you set it accordingly to disk3s1a:?
rootdev isn't set at all (as show says).
I can't imagine that this will make a change, as I am booting from
disk3, the problem stems from FreeBSD not realizing that this is wd0, i
^^
I missed that part. What happens when you set rootdev to disk1s1a:?
Andrzej Bialecki
++---++ -
ab...@nask.pl ||PicoBSD|| FreeBSD in your pocket? Go and see:
Research Academic |+---+| Small Embedded FreeBSD
Network in Poland | |TT~~~| |http://www.freebsd.org/~picobsd/
~-+==---+-+ -
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: ZIP+ detection, need testers for the patch
On Sat, 16 Jan 1999, Nicolas Souchu wrote: On Fri, Jan 15, 1999 at 11:13:09AM +, Doug Rabson wrote: On Fri, 15 Jan 1999, Nicolas Souchu wrote: Hi there, Currently, the ZIP+ probe is intrusive and sends char to the printer if no ZIP+ is connected. Here is a patch that corrects the problem for my printer, but I haven't any ZIP+ :) So, please check the ZIP+ is still detected. With this patch, I can *not* detect my ZIP+ (attached to a machine which detects it using the existing code). Ok :( Does the last ppbus committed code (with IEEE1284 support) detects your ZIP+ at boot? Something like IEEE1284 device found /NIBBLE... with its id 2 lines after? This may be another way to detect properly the ZIP+ Afraid not :-(. The ppb_1284_negociate fails with an error of PPB_NOT_IEEE1284. I haven't tried using the PERIPH_1284 option which seems to affect the negotiation - is it worth trying? P.S. The correct spelling is 'negotiate'. I keep wanting to do a global-replace :-) -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
trivial rc/rc.local observation
Just noticed that both rc and rc.local print starting local daemons and the terminating .. Would it not be more aesthetically pleasing if only rc.local did so? Mike -- Mike Zanker, Academic Computing Service, The Open University, UK Tel: +44 1908 652726, Fax: +44 1908 652193 Views expressed are personal and do not necessarily reflect University opinion. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can the bootloader create a file or set a flag in the bootblocks?
Mike Smith writes: It would be kind of cool if when managing a remote system if /kernel failed to boot, then on the next boot, the loader will fire up /kernel.old, or a /kernel.somethingorother. We're trying to work out a clean way of managing that sort of persistent state that doesn't involve nasty hacks like the 'nextboot' code did. It's kinda tricky if you don't want write implemented in all your filesystems (bloat!) Maybe I don't understand the problem here, but something akin to how kernel configuration changes are handled seems like a good way to deal with this problem. /boot/loader could stuff something into memory (sort of like the way you can stuff a splash screen into memory), and a user-level program can read that information and stuff it wherever it needs to be stuffed. That may be a little hard with tftp, but with most of the other media types it seems like it should be relatively straightforward. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SOFTUPDATES
Does softupdates give any gain over async? I have /usr/src and /usr/obj both mounted async, noatime, and it does seem to be rather nicely fast over default mountops. Async isn't fully async in FreeBSD (some directory operations are still sync), so softupdates is much faster in some cases. Fully async async seems to be a little faster than softupdates. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Suspend on Current
On Sun, 17 Jan 1999, Daniel C. Sobral wrote: Is it just me, or is there anyone else experiencing system freezes on current after a zzz? I tried it on an Intel chipset a while back, and got the same result. Of course, I disabled APM from then on :) -- Daniel C. Sobral (8-DCS) d...@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: a few suggestions/comments on 3.0-RELEASE
Bruce Evans wrote: Also, it might be nice if the disklabel(8) man pages explicitely say that the bootstrap code can be installed on each slice. (am I wrong ?) You're right, the bootblocks can be installed on each slice, and this also needs documenting. This doesn't need documenting. disklabel(8) knows nothing of slices. It installs labels and bootblocks on disk-like devices. Slices are just one type of disk-like device. All regular files larger than 1K and many devices are disk-like, thanks to device independence. I think one does well to avoid No! No! No! reponses to useful feedback. The original suggestion highlights aspects of the new bootblocks that are incompletely documented and potentially confusing. My reply was intentionally phrased to acknowledge this while omitting all reference to the disklabel man page. This does need documenting. disklabel(8) is merely an installation tool for bootstrap stages 1 2, as is install(1) for bootstrap stage 3. Of course one does not document programs on the man pages of their installation tools. However this does not mean that one does not document them (or their installation procedures) at all. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
correction for find(1)'s man page
Hello I was reading the man page for find(1), looking for the precise option to follow symbolic links. This option is -follow, of course, but it is not described in the man page (I do not find in the cgi query : http://www.freebsd.org/cgi/man.cgi?query=findapropos=0sektion=0manpath=FreeBSD+3.0-currentformat=html ) What if someone reread the man page ? TfH To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: trivial rc/rc.local observation
On Sat, 16 Jan 1999, Mike Zanker wrote: Just noticed that both rc and rc.local print starting local daemons and the terminating .. Would it not be more aesthetically pleasing if only rc.local did so? rc.local was removed from the tree on Dec. 12th. If you're still using it you're on your own, edit it as you wish. :) -- Jack O'NeillSystems Administrator / Systems Analyst j...@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger j...@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages /dev/null -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
Edwin Culp wrote: I haven't been able to make world since the texinfo problem. I don't see anyone else on the list with problems. Did I miss another change? Am I doing something wrong? Thanks, ed P.S. This is where I stopped this time. cvsup finished about 9:25 CST. DynaLoader.c:282: `NULL' undeclared (first use this function) DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Try setting KERNFORMAT and OBJFORMAT in the environment before building. In my case they were set to elf. I was able to successfully buildworld this morning after setting those. I noticed that there used to be an elf and an aout directory in /usr/obj. Now there doesn't seem to be, maybe that is causing the problem? -- Dave To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
'make buildworld' seems to create wrong symlinks for 'obj'
After recvsupping -current from the uk Mirror this morning, 'make buildworld' completed without any problem, but a subsequent 'make installworld' failed when trying to install shared libraries (in this case, libdescrypt.so.2). Further investigation showed that building the aout part of world seems to clobber the symlinks to the 'obj' directories from the source tree, i.e. instead of linking obj into the default 'elf' part of the tree (usr/obj/usr...) the link was pointing into the aout part of the object tree and therefore all elf libraries could not be installed. After completely nuking everything in /usr/obj the problem persisted, but remaking the world with -DNOAOUT did the trick. Could somebody with more experience regarding 'make world' please look into this? Cheers, Timo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
Huh? Isn't a 'make world' or 'make buildworld' supposed to just do the right thing? I mean, I *have* converted to elf... On Sat, 16 Jan 1999, David A. Gobeille wrote: Edwin Culp wrote: I haven't been able to make world since the texinfo problem. I don't see anyone else on the list with problems. Did I miss another change? Am I doing something wrong? Thanks, ed P.S. This is where I stopped this time. cvsup finished about 9:25 CST. DynaLoader.c:282: `NULL' undeclared (first use this function) DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Try setting KERNFORMAT and OBJFORMAT in the environment before building. In my case they were set to elf. I was able to successfully buildworld this morning after setting those. I noticed that there used to be an elf and an aout directory in /usr/obj. Now there doesn't seem to be, maybe that is causing the problem? -- Dave To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
We're all seeing this error, not to worry. Happily, it's clearly Mark's baby since he both imported the new texinfo *and* does the perl5 stuff. :-) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
On Sat, 16 Jan 1999, Jordan K. Hubbard wrote: We're all seeing this error, not to worry. Happily, it's clearly Mark's baby since he both imported the new texinfo *and* does the perl5 stuff. :-) Backing out /usr/src/gnu/usr.bin/perl/libperl/config.SH* to 14jan allowed make world to complete for me. (revision 1.7 in the case of config.SH-elf.i386). To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ZIP+ detection, need testers for the patch
On Sat, Jan 16, 1999 at 06:49:25PM +, Doug Rabson wrote: On Sat, 16 Jan 1999, Nicolas Souchu wrote: On Fri, Jan 15, 1999 at 11:13:09AM +, Doug Rabson wrote: On Fri, 15 Jan 1999, Nicolas Souchu wrote: Hi there, Currently, the ZIP+ probe is intrusive and sends char to the printer if no ZIP+ is connected. Here is a patch that corrects the problem for my printer, but I haven't any ZIP+ :) So, please check the ZIP+ is still detected. With this patch, I can *not* detect my ZIP+ (attached to a machine which detects it using the existing code). Ok :( Does the last ppbus committed code (with IEEE1284 support) detects your ZIP+ at boot? Something like IEEE1284 device found /NIBBLE... with its id 2 lines after? This may be another way to detect properly the ZIP+ Afraid not :-(. The ppb_1284_negociate fails with an error of PPB_NOT_IEEE1284. I haven't tried using the PERIPH_1284 option which seems to affect the negotiation - is it worth trying? No. PERIPH_1284 should allow a computer to act as a IEEE1284 compliant peripheral when connected to another computer. P.S. The correct spelling is 'negotiate'. I keep wanting to do a global-replace :-) Now, everybody on -current knows it :) I'm burned, as we say here. -- Doug RabsonMail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problem booting from aic7890/91 Ultra2 SCSI
Ok, first the conclusion... I am not able to boot anymore from a 3.0-current system while I can boot quite nicely from the 3.0-RELEASE generic kernel. The system hangs on checking the scsi chain and remains stopped here. The last thing I can see on the screen is the : Waiting 3 seconds for SCSI devices to settle And nothing else happens anymore. So I have to hard reset the box. here is a dmesg from the 3.0-RELEASE generic kernel. ### dmesg of 3.0-RELEASE generic kernel ### Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #0: Sat Oct 17 17:45:06 GMT 1998 j...@kickme.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter i8254 frequency 1193182 Hz cost 3038 ns CPU: Pentium II (quarter-micron) (400.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x651 Stepping=1 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,b24 real memory = 134217728 (131072K bytes) avail memory = 127537152 (124548K bytes) Preloaded a.out kernel kernel.GENERIC at 0x0xf02ed000. Probing for devices on PCI bus 0: chip0: Intel 82443BX host to PCI bridge rev 0x02 on pci0.0.0 chip1: Intel 82443BX host to AGP bridge rev 0x02 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x02 on pci0.4.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.4.1 chip3: Intel 82371AB USB host controller rev 0x01 int d irq 255 on pci0.4.2 chip4: Intel 82371AB Power management controller rev 0x02 on pci0.4.3 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter rev 0x00 int a irq 14 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs de0: Digital 21041 Ethernet rev 0x11 int a irq 14 on pci0.9.0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:40:05:36:7a:72 Probing for devices on PCI bus 1: vga0: Matrox model 0521 graphics accelerator rev 0x01 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color 16 virtual consoles, flags=0x0 ed0 not found at 0x280 fe0 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface de0: enabling 10baseT port Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: TANDBERG TDC 3500 =01: Removable Sequential Access SCSI2 device sa0: 3.300MB/s transfers da0 at ahc0 bus 0 target 0 lun 0 da0: QUANTUM XP39100W LYK8 Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Quantum VP32170 89TC Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (10.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 2069MB (4238640 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present ### End dmesg ### My kernel is : ### Begin kernel ### machine i386 cpu I686_CPU ident GMARCO maxusers32 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options PROCFS #Process filesystem options FFS_ROOT options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on da0 controller isa0 controller pci0 controller fdc0at isa? port IO_FD1 bio irq 6 drq 2 vector fdintr diskfd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device sa0 device cd0 controller atkbdc0 at isa? port IO_KBD tty
Re: Problem booting from aic7890/91 Ultra2 SCSI
At 12:49 AM 1/17/99 +0100, Gianmarco Giovannelli wrote: Ok, first the conclusion... I am not able to boot anymore from a 3.0-current system while I can boot quite nicely from the 3.0-RELEASE generic kernel. The system hangs on checking the scsi chain and remains stopped here. The last thing I can see on the screen is the : Waiting 3 seconds for SCSI devices to settle And nothing else happens anymore. So I have to hard reset the box. I have been seeing this for the two weeks or so. A shutdown -r will always hang. A complete powerdown has been the only way I can reboot my box of late. -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
kernel build breaks after the latest cvsup
Hello folks, I just did a cvsup and tried rebuilding world and the kernel, but I keep getting an error during the kernel linking stage. loading kernel syscons.o: In function `scvidprobe': syscons.o(.text+0x231): undefined reference to `vid_configure' syscons.o(.text+0x24e): undefined reference to `vid_allocate' syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' ... and many more... psm.o: In function `enable_aux_dev': psm.o(.text+0xd): undefined reference to `send_aux_command' psm.o: In function `disable_aux_dev': psm.o(.text+0x4d): undefined reference to `send_aux_command' ... and psm.o having many such undefined references too. I have not done any changes to my kernel config since the last make update. Any ideas? Any help is appreciated. Thanks! rv To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problem booting from aic7890/91 Ultra2 SCSI
+[ Christopher Knight ]- | At 12:49 AM 1/17/99 +0100, Gianmarco Giovannelli wrote: | | Ok, first the conclusion... | | I am not able to boot anymore from a 3.0-current system while I can boot | quite nicely from the 3.0-RELEASE generic kernel. | | The system hangs on checking the scsi chain and remains stopped here. The | last thing I can see on the screen is the : | Waiting 3 seconds for SCSI devices to settle | | And nothing else happens anymore. So I have to hard reset the box. | | | I have been seeing this for the two weeks or so. A shutdown -r will always | hang. A complete powerdown has been the only way I can reboot my box of late. I recently (last night) added USB support to my kernel (just to see :-) and it hung at the same place. Removing the USB entries fixed it. This was also at the same time as the syscons/atkbd changeover for me as well so I wasn't expecting it really to be the USB driver (since I have no USB devices). If you have USB support compiled in try removing it. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068|a...@theinternet.com.au|Specialist To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kernel build breaks after the latest cvsup
On Sat, 16 Jan 1999, Rajesh Vaidheeswarran wrote: Hello folks, I just did a cvsup and tried rebuilding world and the kernel, but I keep getting an error during the kernel linking stage. loading kernel syscons.o: In function `scvidprobe': syscons.o(.text+0x231): undefined reference to `vid_configure' syscons.o(.text+0x24e): undefined reference to `vid_allocate' syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' ... and many more... psm.o: In function `enable_aux_dev': psm.o(.text+0xd): undefined reference to `send_aux_command' psm.o: In function `disable_aux_dev': psm.o(.text+0x4d): undefined reference to `send_aux_command' ... and psm.o having many such undefined references too. I have not done any changes to my kernel config since the last make update. Any ideas? Any help is appreciated. Thanks! You may c /usr/src/UPDATING /sys/i386/conf/LINT kernel sources is changed. I think you must read following for compile new kernel: http://www.freebsd.org/~yokota/sc_update.txt rv Rgdz, Sergey A. Osokin aka oZZ, o...@etrust.ru To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CTM CVSUP differences
According to David Kelly: via CTM while you can with CVSUP. Last time I tried it, this means you can't do a make release as Jordan's release Makefiles can't handle a total absense of that stuff (eBones? whatever its called). It is available on internat.freebsd.org with CTM... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problem booting from aic7890/91 Ultra2 SCSI
At 12:56 PM 1/17/99 +1000, you wrote: I recently (last night) added USB support to my kernel (just to see :-) and it hung at the same place. Removing the USB entries fixed it. This was also at the same time as the syscons/atkbd changeover for me as well so I wasn't expecting it really to be the USB driver (since I have no USB devices). If you have USB support compiled in try removing it. I do not have USB support compiled in, nor did I when I first started noticing this problem. -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kernel build breaks after the latest cvsup
You probably need to add kbd0 and update sc0 in your kernel config file. Have a look in the GENERIC kernel config to see how it is done now... On Sat, 16 Jan 1999, Rajesh Vaidheeswarran wrote: Hello folks, I just did a cvsup and tried rebuilding world and the kernel, but I keep getting an error during the kernel linking stage. loading kernel syscons.o: In function `scvidprobe': syscons.o(.text+0x231): undefined reference to `vid_configure' syscons.o(.text+0x24e): undefined reference to `vid_allocate' syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' ... and many more... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kernel build breaks after the latest cvsup
Thanks Chris, and thank you all who have replied to my message. I did as per your suggestions, and my kernel compiles now. (I haven't yet tried a reboot though). Thanks, once again. rv -- using MH template repl.format -- In a previous message, Chris Timmons writes: You probably need to add kbd0 and update sc0 in your kernel config file. Have a look in the GENERIC kernel config to see how it is done now... On Sat, 16 Jan 1999, Rajesh Vaidheeswarran wrote: Hello folks, I just did a cvsup and tried rebuilding world and the kernel, but I keep getting an error during the kernel linking stage. loading kernel syscons.o: In function `scvidprobe': syscons.o(.text+0x231): undefined reference to `vid_configure' syscons.o(.text+0x24e): undefined reference to `vid_allocate' syscons.o(.text+0x26b): undefined reference to `vid_get_adapter' ... and many more... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CTM CVSUP differences
Ollivier Robert writes: According to David Kelly: via CTM while you can with CVSUP. Last time I tried it, this means you can't do a make release as Jordan's release Makefiles can't handle a total absense of that stuff (eBones? whatever its called). It is available on internat.freebsd.org with CTM... And its legal for me to import it to the US? Thought something like that had to be available but it didn't come up last time I mentioned it. -- David Kelly N4HHE, dke...@nospam.hiwaay.net = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/i386/isa wd.c wdreg.h src/sys/pci ide_pci.c
Watch out for bugs awoken by this. bde 1999/01/16 21:46:25 PST Modified files: sys/i386/isa wd.c wdreg.h sys/pci ide_pci.c Log: Pass the unit number to the DMA cookie lookup routine and use it to look up cookies properly, at least for standard controllers. Cookies are used so that we don't have to pass around lots of args. All of the dmainit functions use the unit number so it is essential that we pass them a cookie with the correct unit number. This may break working configurations if there are bugs in the dmainit functions like the ones I just fixed for VIA chipsets. Broken in: rev 1.4 of ide_pci.c and rev.1.139 of wd.c. Revision ChangesPath 1.186 +5 -3 src/sys/i386/isa/wd.c 1.25 +2 -2 src/sys/i386/isa/wdreg.h 1.28 +6 -5 src/sys/pci/ide_pci.c Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: mounting double-ended SCSI disks
:Another problem is if A is mounting it read-only and then B tries to :mount it read-write. This succeeds and is dangerous for the same :reason as the last example. Since A can't write anything to the disk, :I guess there is no way we can avoid this situation. (The only way I :could think of avoiding a crash due to stale cache data was to have A :check the clean flag before every read, but that seems excessively :expensive.) : :Satoshi You have to be able to mount an unclean filesystem read-only -- otherwise the system would not be able to mount root and then fsck it from /etc/rc, nor would you be able to mount a corrupted partition in order to attempt to recover some of it. The clean flag was never designed to handle multi-headed configurations and should not be used for such. The filesystems - even read-only mounts, are also not designed to handle multi-headed configurations. You need a separate mechanism ( like a tcp connection or perhaps you can even use the SCSI reservation stuff manually ) to control access to the filesystems. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Annoying messages on startup..
j...@zippy- dmesg|grep Freeing Freeing (NOT implemented) redirected ISA irq 11. Freeing (NOT implemented) redirected ISA irq 10. Freeing (NOT implemented) redirected ISA irq 10. Freeing (NOT implemented) redirected ISA irq 10. Freeing (NOT implemented) redirected ISA irq 9. Freeing (NOT implemented) redirected ISA irq 10. Can these just go away? They certainly don't tell *me* anything useful and if it's a feature which should be implemented then we ought to implement it. If it's just a harmless warning, then we ought to just remove it. :-) Thanks... It would be nice to have this one dealt with before we branch in 4 days.. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: world compile break, -current (extremely recent), krbIV support
Robert Watson wrote: This seems only to affect the krbIV stuff in -world. cd /usr/src/kerberosIV/lib/libacl;/usr/obj/elf/usr/src/tmp/usr/bin/make befor einstall make: don't know how to make /usr/src/kerberosIV/lib/libacl/../../../crypto/k erberosIV/lib/acl/acl.h. Stop *** Error code 2 Huh!?!? Do you have kerberos sources in src/crypto/kerberosIV ?? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CTM CVSUP differences
David Kelly wrote: It is available on internat.freebsd.org with CTM... And its legal for me to import it to the US? No problem. It is illegal to export _from_ the US. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CTM CVSUP differences
David Kelly wrote: While you can download the missing security stuff, make release wants to check it out of your local cvs archive. I haven't found a way to put it there but I'm a cvs novice. There is an international repository of crypto sources. Lemme know if you want it. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
Jordan K. Hubbard wrote: We're all seeing this error, not to worry. Happily, it's clearly Mark's baby since he both imported the new texinfo *and* does the perl5 stuff. :-) ... and he is not getting the errors! I have done N make worlds in the last 48 hours; clean as a whistle. (I do blow away /usr/obj/* each time, and I'm pretty anal about cleaning garbage out of the source tree before building; garbage includes editor backup files, .#* files from CVS, .o .so files from builds without obj/ and so forth. I want the tree to be _really_ clean before I try). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Today's Make World
Every -current release I try and build falls over with this one. Tried making a release lately? :) - Jordan Jordan K. Hubbard wrote: We're all seeing this error, not to worry. Happily, it's clearly Mark's baby since he both imported the new texinfo *and* does the perl5 stuff. :-) ... and he is not getting the errors! I have done N make worlds in the last 48 hours; clean as a whistle. (I do blow away /usr/obj/* each time, and I'm pretty anal about cleaning garbage out of the source tree before building; garbage includes editor backup files, .#* files from CVS, .o .so files from builds without obj/ and so forth. I want the tree to be _really_ clean before I try). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
