Will Andrews <[EMAIL PROTECTED]> writes:
> Probably the recent change (IIRC) that someone turned running an
> executable into a mtime change.
Which change is that?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
y.
I might misunderstand how the make-bootfloppies process works, but
isn't it possible to add IPSEC to GENERIC and have dokern.sh remove it
for the kernel that gets put on the floppies? If so, that's what I
think we should do.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
Olivier Cortes <[EMAIL PROTECTED]> writes:
> fool, fool, fool am i. here it is :
>
> --
> mkdep -f .depend -a -nostdinc -DDISASSEMBLER -DNO_X -I/usr/obj/usr/build/src/i
>386/usr/include
Make sure you have usr.bin/doscmd/Makefile version 1.28 (or
Jun Kuriyama <[EMAIL PROTECTED]> writes:
> Today's nightly build reports breakage of the world...
Please update to kerberos5/lib/libasn1/Makefile:1.9 or apply the
appended patch (relative to 1.8).
/assar
Index: Makefile
=
Garance A Drosihn <[EMAIL PROTECTED]> writes:
> I think that it's reasonable to just make it a specific error, and
> thus end this thread. No harm will come of making it a specific
> error on open, and it will address the problems mentioned earlier.
What about t
istoric BSD didn't have sra or any other authentication
mechanism that uses libmp. Or are you saying that we cannot change
`historical BSD software'?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ense. My plan is to
install both the program and man-page as kadmind instead.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
long time ago but since autologin was
not enabled, nobody noticed this. I've changed this in
secure/lib/libtelnet/Makefile:1.19
Jordan: I think we should MFC this before 4.3. Opinions?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
s) to handle the escapes and signal characters and is not likely
to happen by me today. And we should think of 4.3.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
gin and are connected, telnet can then again be escaped
> with CTRL-].
Thanks. The problem is with SRA using fgets/getpass for its prompts.
The simplest way of fixing this is by disabling SRA with the following
patch:
/assar
Index: secure/lib/libtelnet/Makefile
=
gt; [...]
> description:
>
> revision 1.6
> date: 2001/03/12 03:54:48; author: assar; state: Exp; lines: +14 -1
> enable auto-negotiation of encrypt and decrypt
> =
>
> Telnet no lo
Jun Kuriyama <[EMAIL PROTECTED]> writes:
> Assar, can you review and commit this?
This is ok, but jhb has already fixed this.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
testing. I've commited the fix.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
x27;s import), MAKE_KERBEROS5=yes required
> that you also have MAKE_KERBEROS4=yes due to such dependencies.
Which is bogus. I think Jun Kuriyama's patch is correct and I'm
trying it now, but buildworld takes a little while to complete :-)
/assar
To Unsubscribe: send mail to [EMAIL PROTE
I wrote:
> Right, but stealing these small snippets from NetBSD wasn't very hard,
> see patch below.
Here's a better patch, including stty. If there are no objects, I'll
commit this.
/assar
Index: bin/stty/modes.c
===
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> My concern is that just adding these defines doesn't actually implement
> anything in the drivers/libraries. :)
Right, but stealing these small snippets from NetBSD wasn't very hard,
see patch below.
/assar
In
work. Now here's a patch that survived building a
kernel and modules. ok?
/assar
Index: vm_zone.c
===
RCS file: /home/ncvs/src/sys/vm/vm_zone.c,v
retrieving revision 1.35
diff -u -w -r1.35 vm_zone.c
--- vm_zone.c 2000/12/13 10:01:
Matt Dillon <[EMAIL PROTECTED]> writes:
> We can't just go do an end-run around the established API as a
> hack around the problem.
I fail too se how my suggestion would change the API at all, but in
case I was unclear, diffs are below.
/assar
ormance benefit is minimal at best. That will solve the SMP and
> INVARIENTS mixing problem (at least for zalloc/zfree).
Just make them always call zalloci() and zfreei().
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
nough, but it probably shouldn't just
> swallow the error.
Yeah, your patch to subr_prf.c is better.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
() at exception_return
Yes, this is possible, (at least) when following symbolic links. This
was discussed here on -current some time ago and I proposed the
appended simple patch, but I didn't get any feedback on it.
/assar
Index: nfs_socket.c
===
John Indra <[EMAIL PROTECTED]> writes:
> Yeah... finally, my world is in sync with the kernel, what a joy :)
> Until know... the system is pretty stable.
> Will this be committed to the tree soon?
It has been comitted, I just wanted to test building first.
/assar
To Unsubscrib
reference to `M_AGP'
> agp_amd.o(.text+0xd5): undefined reference to `M_AGP'
> agp_amd.o(.text+0x105): undefined reference to `M_AGP'
> agp_amd.o(.text+0x112): undefined reference to `M_AGP'
> agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow
> *** E
places so doing the
check there should also work.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
cture. That is as far as I
> could take it however..
Since proc can be NULL and most of the other code in nfs_socket
handles it I do think this actually is the right thing to do.
Comments?
/assar
Index: nfs_socket.c
===
RCS
e sys/ufs/ffs/ffs_softdep_stub.c 1.15 which should
solve the problem in a more general way.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
f/eqn/../../../../contrib/groff/eqn/lex.cc:22: eqn_tab.h:
>No such file or directory
I got rid of that with 'rm *' in
/usr/obj/usr/src/gnu/usr.bin/groff/eqn.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Warner Losh <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]> Assar Westerlund writes:
> : The problem is that the source files are hidden in the kernel source
> : directory and not installed. Where should vnode_if.{src,pl} get
> : installed? It seems much
at I can tell from a quick look at the code, it does this.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I have a proposed patch to ls that fixes bin/19354 and makes things
more consistent. Comments?
/assar
Index: extern.h
===
RCS file: /home/ncvs/src/bin/ls/extern.h,v
retrieving revision 1.13
diff -u -w -r1.13 extern.h
--- extern.h
source
> files, not the generated output.
The problem is that the source files are hidden in the kernel source
directory and not installed. Where should vnode_if.{src,pl} get
installed? It seems much simpler just to install vnode_if.h in
/usr/include/sys. Patc
I think it's wrong that vnode_if.h is not installed, this means that
you need to have kernel source to compile any third-party file system.
So I propose the patch below, to create vnode_if.h and then add it to CVS.
Any objectsions/comments/whatever?
/assar
Index: Mak
I would like to commit the patch below to -current and 4-stable in a
little while. It allows KLDs to be compiled without optimization.
Any objections/comments/anything?
/assar
Index: signalvar.h
===
RCS file: /home/ncvs/src/sys
"Andrew Tulloch" <[EMAIL PROTECTED]> writes:
> Device char-major=116 minor=196608 opened in block mode, convert to char
> mode with /dev/MAKEDEV before 2000-07-01
It has been fixed in sys/kern/vfs_subr.c:1.255. cvsup or grab the
patch and apply.
/assar
To Unsubscrib
gt; +va_list va;
> +
> +va_start(va, ctl);
> +if (vasprintf(pptr, ctl, va) < 0)
> + msgFatal("Out of memory!");
> +va_end(va);
> }
> /* Create a path biased from the VAR_INSTALL_ROOT variable (if not /) */
It would seem to me a good idea to make a v-version of this function,
even if there's no place right now that wants to call it.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
h /dev/MAKEDEV before 2000-07-01
>
> There is a bug somewhere in the rootmount code.
The following patch fixed the problem for me. For extra points,
rename the function.
/assar
--- vfs_subr.c~ Sat May 6 00:08:38 2000
+++ vfs_subr.c Sat May 13 21:47:08 2000
@@ -1296,7 +1
way of dealing with that?
> I wish these stupid standards committees would just choose
> something that people are already using rather then make up new names!
The problem is that __func__ and __FUNCTION__ are not the same thing.
And thus it makes sense for them not the use same name.
/as
n of vnode_if.h into
src/include/Makefile.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
in as `extern
__inline' instead of `static __inline'. I don't think there's any
particular good reason to not have everything build without -O and
the fix (included in the PR) for this problem is trivial. See PR
kern/17614.
Comments?
/assar
To Unsubscribe:
ttimeofday(2):
Note: timezone is no longer used; this information is kept outside the
kernel.
And single unix standard says:
If tzp is not a null pointer, the behaviour is unspecified.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
on't have any problems with that...
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ults for csh, which might not be the
right ones for other shells.
What result do you get with `which which' for example?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:
1) It hangs instead of rebooting
2) It doesn't manage to write a dump.
It doesn't happen every reboot and I haven't been able to figure out
what's triggering it.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
te loop of `ad0: timeout waiting for
DRQ'. Any ideas?
/assar
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #8: Fri Jan 28 23:47:23 CET 2000
[EMAIL PRO
environment variablesm were executed to trigger the crash.
This might be related to kern/15204. But I don't have any fix, sorry
:-(
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
difference between it's not done by default and
it will not work. I did it because I had hardwired it in my previous
config.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> no. Try to disable ep1 (if you can).
Not hardwiring ep0 in the configuration file made it work. Thanks
again.
Here's an trivial patch to GENERIC to add comments about these
characteristics about ep0.
/assar
ost'
ep1 and hangs hard when trying to `ifconfig ep0'. Any idea as to why
that happens?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
bled in the BIOS.
Any hints and/or suggestions?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bruce Evans <[EMAIL PROTECTED]> writes:
> That's a really old bug. I fixed it a year or two ago in my version,
> and optimised the !SMP case following a suggestion of tegge (waiting
> for the lock is useless in the !SMP case).
Looks fine. Can you commit your patch?
/as
er clear that it can cause
this. I proposed simple change is below.
Comments?
/assar
--- kern_lock.c.origMon Nov 8 03:55:26 1999
+++ kern_lock.c Mon Nov 8 04:24:13 1999
@@ -116,9 +119,11 @@
simple_lock(&lkp->lk_interlock);
glue generated by DEV_MODULE.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
S of course) is to add two new functions:
> alloc_cmaj() and alloc_bmaj() and use those.
Like the following code? And should they be used by cdevsw_add when
d_maj and d_bmaj are some magical value such as -1?
/assar
Index: kern/kern_conf.c
==
s or is it an accident that I should go
and rectify?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
TED]:/cvs/binutils. That might
not fit your definition of `beta' but it's publicly available and has
3Dnow support it in (I haven't tested it...).
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> X11R6 xdm for kerberos 5 floating around.
That's quite different.
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
modern code. And besides, the protocol doesn't do what you want
(IMNSHO), because it only authenticates the initial connection and
doesn't do anything to authenticate or protect the X session after
that. If somebody is working on adding some better mechanism of using
K5 in X11 I would
eze when you ejected the PC Card?
My laptop (Thinkpad 560) doesn't crash when ejecting the card (a
3c589c) with the patch.
/assar
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
handled
by isa_strayintr, and the reason for that was that inthand_remove
didn't manage to remove the interrupt (and get it replaced by the
stray function) correctly. After applying the patch at the end of
this mail I can once again sleep my laptop succe
Jonathan Lemon writes:
> How about getting profiling working for ELF kernels before
> before completely abandoning a.out?
There are patches for that in kern/9413 but I haven't got any feedback
on them at all.
/assar
To Unsubscribe: send mail to majord...@freebsd.org
with "uns
ld the kernel and that KLDs would need some way
of figuring out the these options. How should that be done? By
installing opt_global.h after building the kernel?
/assar
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
th
zalloc and zfree. So it seems to me that one of the following could
be done to solve it:
a. make zalloc and zfree non-inline
b. call zalloci and zfreei in code that can end up in KLDs
c. call zalloci and zfreei everywhere where it's not performance-critical
/assar
To Unsubscribe: sen
62 matches
Mail list logo
