During make of kernel:
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
-DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c
Is doscmd working for anyone on current? Here I just get:
-
I have tried it on a single processor and SMP -current and both do the same
thing. I had it working a while back, so I think my configuration is ok.
Ideas on how to look into this?
Start by invoking it
John Hay wrote:
Hmmm I see the sigreturn man page hasn't been updated, it still says that
sigreturn takes a struct sigcontext * argument, while the signal.h file
says it takes ucontext_t *.
Sigreturn still takes a struct sigcontext*. It also takes a ucontext_t.
I think the header should
"David O'Brien" writes:
On Sat, Nov 06, 1999 at 10:34:18AM +0100, Gary Jennejohn wrote:
Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have
Here is the patch I've been working on (before I 1st got BDE's reply).
The changes are mostly from OpenBSD + style changes for the way
Taavi Talvik wrote:
Only alternative to get these from outside is to upgrade graduall.. but
who knows which intermediate source repository dates are good for it?
Mike once said (and, ergo, can be found on the mailing list
archives):
"We do not support upgrading to -current from anything
"Daniel C. Sobral" wrote:
Taavi Talvik wrote:
Only alternative to get these from outside is to upgrade graduall.. but
who knows which intermediate source repository dates are good for it?
Mike once said (and, ergo, can be found on the mailing list
archives):
"We do not support
On Sat, Nov 06, 1999 at 01:29:16PM -0600, Jonathan Lemon wrote:
From the manual page for flock:
NOTES
Locks are on files, not file descriptors. That is, file descriptors du-
plicated through dup(2) or fork(2) do not result in multiple instances of
a lock, but rather
On Sun, Nov 07, 1999 at 02:01:02AM +0100, Ollivier Robert wrote:
Right but in Postfix case this is not the case. The "master" process run to
check whether Postfix is running or not is definitely NOT a child of the real
"master" process.
But if the real master process forks and then it's
Lauri Laupmaa wrote:
On Fri, 5 Nov 1999, Michael Reifenberger wrote:
The flag is probably -fformat-extensions so eliminate it from
/usr/share/mk/bsd.kern.mk.
Then build linker/kernel/world.
Thank you all who replied! The trick was to take new loader from running
system, because it
Thierry Herbelot wrote:
Mike once said (and, ergo, can be found on the mailing list
archives):
"We do not support upgrading to -current from anything else than the
latest -stable."
Does this still hold after the recent signal changes ?
TfH
(I assume Yes, if one first
[bringing this back to -current, with a Bcc to -security]
"Kenneth D. Merry" [EMAIL PROTECTED] writes:
Jonathan Lemon wrote...
In article local.mail.freebsd-current/[EMAIL PROTECTED] you
write:
Before I spend a lot of time hunting this down, I figured it might be worth
asking -- is
From the keyboard of Charlie ROOT:
During make of kernel:
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
-DKERNEL -include opt_global.h
Is doscmd working for anyone on current? Here I just get:
-
I have tried it on a single processor and SMP -current and both do the same
thing. I had it working a while back, so I think my configuration is ok.
Ideas on how to look into this?
Start by
On Nov 11, 1999 at 01:41:48PM +0100, Dag-Erling Smorgrav wrote:
[bringing this back to -current, with a Bcc to -security]
"Kenneth D. Merry" [EMAIL PROTECTED] writes:
Jonathan Lemon wrote...
In article local.mail.freebsd-current/[EMAIL PROTECTED] you
write:
Before I spend a lot of
David Malone wrote:
On Sat, Nov 06, 1999 at 01:29:16PM -0600, Jonathan Lemon wrote:
From the manual page for flock:
NOTES
Locks are on files, not file descriptors. That is, file descriptors du-
plicated through dup(2) or fork(2) do not result in multiple instances of
a
Peter Wemm wrote:
As to why the 1869 isn't working for you, that's anybody's guess. You
might try posting the 'dmesg' output (not from syslog) and your complete
config file, as well as any other pertinant information you can think of.
Ok
here is the (hopefully) complete information.
Warner Losh wrote:
In message [EMAIL PROTECTED] "D. Rock" writes:
: device sio0at isa? port IO_COM1 flags 0x10 irq 4
: device sio1at isa? port IO_COM2 irq 3
These look good. IIRC, the kernel I tested with also had:
device sio2at isa? port IO_COM3
From the keyboard of Leif Neland:
PnP support for i4b in -current was disabled during the conversion of
-current to the new-bus/new-pnp architecture; as a result all PnP ISDN
cards i4b supports do no longer work.
Anybody working on re-enabling it, and if so, any time-horisonts?
Yes,
On Sun, Nov 07, 1999 at 03:16:48PM +0100, Leif Neland wrote:
PnP support for i4b in -current was disabled during the conversion of
-current to the new-bus/new-pnp architecture; as a result all PnP ISDN
cards i4b supports do no longer work.
Anybody working on re-enabling it, and if so,
On Sat, 6 Nov 1999, Dmitrij Tejblum wrote:
Brian Fundakowski Feldman wrote:
There were zero comments about what order things happen in; in fact,
the ordering in this case is Just Plain Lame (TM). It's much more
correct to explicitly check for fp-f_count == 1.
Not sure what you mean.
-On [19991106 04:01], Andrzej Bialecki ([EMAIL PROTECTED]) wrote:
Today I noticed accidentally that either libvgl is broken, or the demo
program does something wrong - the mouse cursor doesn't move.
But this brings more general question regarding console graphics library.
As it is today, libvgl
According to David Malone:
But if the real master process forks and then it's child closes the fd
which the lock was on, then the master process will have lost it's lock.
Is this likely? Does the real master fork children to do stuff?
All the time. "master" is an inetd-like daemon which spawn
Problem: ~daemon/tmp should not be the same directory as ~root/tmp/
Suggestion: new home directory:
daemon:*:1:1::0:0:Owner of many system processes:/daemon:/sbin/nologin
+ extend BSD.root.dist to create ~daemon/tmp
Given existing current/src/:
etc/master.passwd:
"We do not support upgrading to -current from anything else than the
latest -stable."
Does this still hold after the recent signal changes ?
TfH
(I assume Yes, if one first upgrade the kernel, then the world)
You assume correctly. -stable loader can load -current
Ok, with these patches doscmd is working for me again. I can boot dos and
run the topspeed C compiler like I used to a few months ago.
If nobody has any complaints I'll commit it. I'm just not 100% sure about
the patch to doscmd.c and would like if someone with more knowledge about
the signal
"Daniel C. Sobral" writes:
Gary Jennejohn wrote:
Any idea why GCC 2.95.2 produces so much more code ?
Mmmm... O'Brien, could you make sure the space-critical code in
sys/boot compiles ok?
I still have GCC 2.95.2 installed. This is what I get in /sys/boot:
=== i386/boot2
(cd
Marcel,
Just curious as to what the motivation for re-ordering the
sa_flags and sa_mask members in sigaction were? The manpage
still describes the old order BTW.
My Alpha box has been limping through a package build and I've
noticed a number of ports that seem to be falling over for
On Sun, 7 Nov 1999, David Malone wrote:
The lock doesn't seem to be released until *explicitly* released, like
the manual page says. I don't think closing the descriptor counts as
an explicit unlock, though I am probably wrong. Run this program,
you'll see the parent still has the lock.
Does anybody can explain why two absolutely identical attempts to remove
unexistent files on UFS and FAT32 yields different error codes ("No such
file or directory" and "Invalid argument" respectively)? This breaks "rm
-f" behaviour, because instead of expected "0", "rm -f" on FAT returns
error
Please note that you've mailed this to a freebsd specific mailing list
which is designed for discussions of issues with freebsd-current.
This is is not subtitled, "A reference for script-kiddie wannabies."
Please insert 50c for your next attempt, and good day.
(Translation: You've sent your
On Mon, 8 Nov 1999, Maxim Sobolev wrote:
Does anybody can explain why two absolutely identical attempts to remove
unexistent files on UFS and FAT32 yields different error codes ("No such
file or directory" and "Invalid argument" respectively)? This breaks "rm
-f" behaviour, because instead
Try this in -current
$ cat some_file | head
I have to use ^C to regain control.
Jean-Marc
--
Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Jean-Marc Zucconi writes:
Try this in -current
$ cat some_file | head
I have to use ^C to regain control.
... and reverting to rev. 1.22 of eval.c fixes the problem.
Jean-Marc
--
Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED]
To Unsubscribe: send mail to
Gary Jennejohn wrote:
Mmmm... O'Brien, could you make sure the space-critical code in
sys/boot compiles ok?
I still have GCC 2.95.2 installed. This is what I get in /sys/boot:
=== i386/boot2
(cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o
ld
34 matches
Mail list logo
