Michael Lucas wrote:
> Hello,
>
> Shouldn't I get a response email from
> [EMAIL PROTECTED]? Or is this a casualty of the mail
> breakage?
>
> Would I be better of using the web form, or just waiting until after
> Linuxworld?
Web interface isn't working either. I've got following when tried to
On Fri, Feb 04, 2000 at 11:40:34AM +0200, Ruslan Ermilov wrote:
>
> > Might I advice some more time before we actually do something?
> >
> > What's all this rush-it-in before anyone can actually fix the larger
> > problem?
> >
> I'm positive about this as well.
>
The main reason for the backou
On Thu, Feb 03, 2000 at 10:09:22AM -0800, Kris Kennaway wrote:
> AFAIK this has always been the way it works: if you install libdescrypt,
> the system makes the (mistaken) assumption you want DES passwords all the
> time.
This is true for the initial installation. However, `make world' used to
r
On Thu, Feb 03, 2000 at 10:09:22AM -0800, Kris Kennaway wrote:
> a proper fix might be to add a login class which determines which of
> MD5 and DES you should use for new passwords
I believe PAM is the more "approved" way to implement this
functionality. Before PAM it would be /etc/auth.conf.
I
> > AFAIK this has always been the way it works: if you install libdescrypt,
> > the system makes the (mistaken) assumption you want DES passwords all the
> > time.
>
> This is true for the initial installation. However, `make world' used to
> respect the an existing symlink. src/secure/lib/lib
I've pulled a cvsup update on my 3.4-STABLE machine, and deleted /usr/obj
to start afresh.
I get the following performing a make upgrade however:
[cut]
===> ranlib
sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 ranlib
/usr/obj/aout/usr/src/i386/usr/libexec/elf
===> size
sh /usr/s
On Fri, 4 Feb 2000, Josef Karthauser wrote:
> I've pulled a cvsup update on my 3.4-STABLE machine, and deleted /usr/obj
> to start afresh.
>
> I get the following performing a make upgrade however:
>
>From /usr/src/Makefile:
# upgrade - Upgrade a.out (2.2.x/3.0) system to the new ELF
Hi everyone,
I just had a strange panic with yesterday's current:
FreeBSD relativity.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Jan 28
16:15:13 CET 2000 root@:/usr/src/sys/compile/RELATIVITY5 i386
A backtrace seems impossible (but I'm inexperienced with kgdb and I'm also
> On Thu, Feb 03, 2000 at 10:09:22AM -0800, Kris Kennaway wrote:
> > a proper fix might be to add a login class which determines which of
> > MD5 and DES you should use for new passwords
>
> I believe PAM is the more "approved" way to implement this
> functionality. Before PAM it would be /etc/a
Josef Karthauser wrote:
> The reason for adopting a fall back solution it that it is not clear that
> setflags/getflags is the best choice of function name for manipulating
> file flags as it's a bit too generic a name. Whilst we're debating
> this point there's no point in having them as librar
Whenever I try to do a 'make installworld' the following error occurs:
/usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
When I do a 'make -k installworld', make continues but the error occurs
several times.
When I do a simple 'make installworld' the followin happens :
install -c -
cd src/usr.bin/xinstall
make all install
cd ../../
make installworld
;)
I'm already have some experience in this problem... ;=|
bauer>Whenever I try to do a 'make installworld' the following error occurs:
bauer>
bauer>/usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
bauer>
bauer>
On Fri, 4 Feb 2000, Josef Karthauser wrote:
> On Fri, Feb 04, 2000 at 11:40:34AM +0200, Ruslan Ermilov wrote:
> >
> > > Might I advice some more time before we actually do something?
> > >
> > > What's all this rush-it-in before anyone can actually fix the larger
> > > problem?
> > >
> > I'm p
On Thu, Feb 03, 2000 at 12:45:45PM -0500, "Matthew N. Dodd" <[EMAIL PROTECTED]> wrote:
> Get me a copy of your boot output and the output of 'pnpinfo'.
Sorry for the delay, I had other things to cover first. For the record,
got the cards working by brutally removing some PnP related includes and
On Fri, 4 Feb 2000, Marcel Moolenaar wrote:
> The patch looks good, but contains style (ordering) bugs :-)
> I can't actually test the patch, but assume that's been done.
It also contains style (syntax) bugs. `extern' declarations of
functions are not KNF. They are only only necessary to suppo
For some reason, under FreeBSD 4.0, setproctitle() isn't working any
longer:
ps ax | grep sockd | more
40015 ?? Ss 0:00.67 /usr/local/sbin/sockd -lD
40016 ?? S 0:00.02 /usr/local/sbin/sockd -lD
40017 ?? S 0:00.06 /usr/local/sbin/sockd -lD
40018 ?? S 0:00.03 /usr/local/
On Fri, Feb 04, 2000 at 11:05:01AM +, Josef Karthauser wrote:
> On Fri, Feb 04, 2000 at 11:40:34AM +0200, Ruslan Ermilov wrote:
> >
> > > Might I advice some more time before we actually do something?
> > >
> > > What's all this rush-it-in before anyone can actually fix the larger
> > > prob
On Fri, Feb 04, 2000 at 03:17:49PM +0100, Kurt Bauer wrote:
> Whenever I try to do a 'make installworld' the following error occurs:
>
> /usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
>
That is the case I was talking about when I fixed bsd.lib.mk's
PRECIOUSLIB breakage.
Unfortun
On Fri, Feb 04, 2000 at 10:49:33AM -0500, "Matthew N. Dodd" <[EMAIL PROTECTED]> wrote:
> > Sorry for the delay, I had other things to cover first. For the
> > record, got the cards working by brutally removing some PnP related
> > includes and so on in the kernel source. I still don't have even a
approved
> Hi,
>
> would it be ok to commit the following patch to
> /usr/src/sys/boot/i386/loader/Makefile so that we can build
> a smaller loader without Forth support, which is still useful
> to boot a picobsd kernel ?
>
> cheers
> luigi
>
> rizzo# diff -ubwr Makefile.40RC Make
On Tue, Feb 01, 2000 at 09:07:49PM -0800, Brian Beattie wrote:
> A kernel, current, sources cvsuped today. When I try to record from line,
> (source does not seem to matter), I get full scale white noise.
>
> The remainder of the system is from about a week ago, I will try a
> buildworld/installw
On Fri, 4 Feb 2000, Vallo Kallaste wrote:
> lnc0 at port 0x300-0x317 irq 5 drq 3 on isa0
> lnc0: PCnet-ISA+ address 00:80:5a:01:64:3a
> lnc1 at port 0x320-0x337 irq 10 drq 5 on isa0
> lnc1: PCnet-ISA+ address 00:80:5a:01:64:36
Humm... Well, I guess its time to convert if_lnc to newbus though I d
On Fri, 4 Feb 2000, Vallo Kallaste wrote:
> Sorry for the delay, I had other things to cover first. For the
> record, got the cards working by brutally removing some PnP related
> includes and so on in the kernel source. I still don't have even a bit
> of clue what I did, but the changes removed P
On Fri, 4 Feb 2000, Christopher Masto wrote:
> On Tue, Feb 01, 2000 at 09:07:49PM -0800, Brian Beattie wrote:
> > A kernel, current, sources cvsuped today. When I try to record from line,
> > (source does not seem to matter), I get full scale white noise.
> >
> > The remainder of the system is f
On 04-Feb-00 Ruslan Ermilov wrote:
> On Fri, Feb 04, 2000 at 11:05:01AM +, Josef Karthauser wrote:
>> On Fri, Feb 04, 2000 at 11:40:34AM +0200, Ruslan Ermilov wrote:
>> >
>> > > Might I advice some more time before we actually do something?
>> > >
>> > > What's all this rush-it-in before an
Hi,
would it be ok to commit the following patch to
/usr/src/sys/boot/i386/loader/Makefile so that we can build
a smaller loader without Forth support, which is still useful
to boot a picobsd kernel ?
cheers
luigi
rizzo# diff -ubwr Makefile.40RC Makefile
--- Makefile.40RC
Is it possible to boot current diskless?
I'd say (from the times I tried it in 3.1 or something) to use netboot,
but that fails because it can't boot an ELF kernel.
Should I build an aout kernel, and how do I do that for current?
Can I do it another way?
One might say that with the rc.diskless
On Fri, Feb 04, 2000 at 01:22:49PM -0500, John Baldwin wrote:
>
> On 04-Feb-00 Ruslan Ermilov wrote:
> > On Fri, Feb 04, 2000 at 11:05:01AM +, Josef Karthauser wrote:
> >> On Fri, Feb 04, 2000 at 11:40:34AM +0200, Ruslan Ermilov wrote:
> >> >
> >> > > Might I advice some more time before we
Hi,
I'm in the middle of trying to load up a new Dell GX1 550 for
the 1st time and am seeing some strange behaviour.
I am unsure of whether it is the machine or the code. What I
receive from sysinstall is the following:
man/man1/xmseconfig.1.gz
137 blocks
sysconfig in free(): warning: jun
Hi,
Can I get approval for the attached patch to LINT (and MFC) before 4.0
rolls out of the door? It just documents the ASUSCOM_IPAC option for
the Asus ISDNLink 128K ISDN card. This card is listed in the Handbook
as being supported, but there aren't any entries in LINT for it.
Grovelling t
-current,
Peter Jeremy forwarded this to me. I'm happy to commit it, because
it solves the problem. However, I don't understand the cause of the
problem, so I don't know whether or not the fix is an appropriate one
or not.
N
- Forwarded message from Peter Jeremy <[EMAIL PROTECTED]> -
Richard Wackerbarth writes:
> > When we do a 'make install' on the kernel, it automatically copies
> > /kernel to /kernel.old, and copies the new kernel in ... is there no way
> > of extending this to the modules?
> >
> > The one thing I was thinking might be to have it so that if you
> >
On Fri, 4 Feb 2000, John Baldwin wrote:
> > 2. Right after we resolve this issue, your patch (provided that you
> >fix errors Bruce pointed out), should be committed to make it
> >possible to compile -current xinstall in a host environment, e.g.
> >from 3.x (IMHO, the most important c
:This has an easy solution. One, get rid of setflags usage by reverting
:the Makefiles somewhat. Two, remove setflags from the headers. Three,
:make libc have an _XXX_setflags and __weak_reference() it to setflags.
:This won't break anyone, or make apps not be able to use [gs]etflags.
:
:Of cou
On Fri, Feb 04, 2000 at 03:11:57PM +0200, Mark Murray wrote:
>
> You want to work on PAM's, go ahead!
I had time for this then, but not now. :-(
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 05-Feb-00 Matthew Dillon wrote:
>:This has an easy solution. One, get rid of setflags usage by reverting
>:the Makefiles somewhat. Two, remove setflags from the headers. Three,
>:make libc have an _XXX_setflags and __weak_reference() it to setflags.
>:This won't break anyone, or make apps n
http://www.bitwizard.nl/sig11/
-- Danny J. Zerkel
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'm experiencing the same problems but the proposed solution of
"make -k -DNOFSCHG installworld " doesn't allow the following "make
installworld" to succeed. The error messages remain unchanged. I
cvsup'd about 24 hours ago.
cheers
On 4 Feb 00, at 17:44, Ruslan Ermilov wrote:
> On Fri, Feb
On Sat, Feb 05, 2000 at 07:41:56PM +1300, Dan Langille wrote:
> I'm experiencing the same problems but the proposed solution of
> "make -k -DNOFSCHG installworld " doesn't allow the following "make
> installworld" to succeed. The error messages remain unchanged. I
> cvsup'd about 24 hours ago
On 5 Feb 00, at 9:28, Ruslan Ermilov wrote:
> On Sat, Feb 05, 2000 at 07:41:56PM +1300, Dan Langille wrote:
> > I'm experiencing the same problems but the proposed solution of
> > "make -k -DNOFSCHG installworld " doesn't allow the following "make
> > installworld" to succeed. The error messag
Of all the gin joints in all the towns in all the world, Kenneth D.
Merry had to walk into mine and say:
> > Talking of the XMAC II, there's one other thing I forgot to mention earlier.
> > The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't.
> > At least, not yet. The XMAC
41 matches
Mail list logo