On Thu, Jul 05, 2001 at 07:57:41AM +0200, Riccardo Torrini wrote:
> Maybe this is a stupid(?) question, but how DEVFS is supposed
> to work with softlink? How can I make them reboot-resistant?
>
See /etc/rc.devfs (which should probably be referenced in devfs(5)).
--
Chris D. Faulhaber - [EMAI
rarpd fails to compile (again the WARNS?=2 problem.
- JimP
beta2 6# make
cc -O -pipe -mcpu=ev4 -DTFTP_DIR=\"/tftpboot\" -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -c
/usr/src/usr.
Yes, I found && fixed that, but I haven't checked it in yet.
On Thu, 5 Jul 2001, Jim Pirzyk wrote:
> rarpd fails to compile (again the WARNS?=2 problem.
>
> - JimP
>
>
> beta2 6# make
> cc -O -pipe -mcpu=ev4 -DTFTP_DIR=\"/tftpboot\" -W -Wall -Wstrict-prototypes
> -Wmissing-prototypes -Wpoint
On Wed, Jul 04, 2001 at 12:12:22AM -0700, Kris Kennaway wrote:
> This kind of language isn't called for. People make mistakes, and
> insulting them for it serves no useful purpose.
People are making more and more mistakes that break the Alpha build.
We will soon have two more arches. We need to
On Thu, Jul 05, 2001 at 05:49:56PM -0700, David O'Brien wrote:
> On Wed, Jul 04, 2001 at 12:12:22AM -0700, Kris Kennaway wrote:
> > This kind of language isn't called for. People make mistakes, and
> > insulting them for it serves no useful purpose.
>
> People are making more and more mistakes t
On Thu, Jul 05, 2001 at 09:41:21PM -0700, Matthew Jacob wrote:
> Did you read my other mails? I doesn't appear that you have. Or you
> didn't understand them. I was laughing because, yes, WARNS was turned on
> prematurely which killed things.
Well, your email didn't translate well, because it ca
On Thu, 5 Jul 2001, Kris Kennaway wrote:
> On Thu, Jul 05, 2001 at 09:41:21PM -0700, Matthew Jacob wrote:
>
> > Did you read my other mails? I doesn't appear that you have. Or you
> > didn't understand them. I was laughing because, yes, WARNS was turned on
> > prematurely which killed things.
On 2001-Jul-05 20:31:43 -0700, Matthew Jacob <[EMAIL PROTECTED]> wrote:
>Perhaps what we really need- and this is really a toolchain issues- is a
>compiler that is just as stringent on i386 as on alpha?
IMHO, the compiler _is_ just as stringent on i386 as Alpha (it's the
same compiler). IMHO, th
On Fri, 6 Jul 2001, Peter Jeremy wrote:
> On 2001-Jul-05 20:31:43 -0700, Matthew Jacob <[EMAIL PROTECTED]> wrote:
> >Perhaps what we really need- and this is really a toolchain issues- is a
> >compiler that is just as stringent on i386 as on alpha?
>
> IMHO, the compiler _is_ just as stringent
On 2001-Jul-05 22:22:11 -0700, Matthew Jacob <[EMAIL PROTECTED]> wrote:
>> IMHO, the problem splits into two categories:
>> Firstly, sizeof(long) (and sizeof(void *)) differ between the Alpha
>> and the i386.
>
>Yes. This tends to be caught by the alpha compiler but the i386.
>It'd be nice if t
>Date: Thu, 5 Jul 2001 10:44:39 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>OK; I got today's -CURRENT built and running:
>FreeBSD m147.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #60: Thu Jul 5 09:27:49 PDT
>2001 [EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W i386
>b
hi,
after some weeks without softupdates, i recently reenabled them on my
notebook. it seems, that my problems still exist. background checking
one of my partitions leads to a panic() complaining about some "block
too large" error. sorry, i didn't capture the message, and for obvious
reasons i
On 05-Jul-01 Matthew Jacob wrote:
>
> ha/alpha/genassym.c
> ../../../vm/vm_zeroidle.c:13: opt_npx.h: No such file or directory
> ../../../vm/vm_zeroidle.c:17: opt_reset.h: No such file or directory
> ../../../vm/vm_zeroidle.c:38: machine/pcb_ext.h: No such file or
> directory
> ../../../vm/vm_ze
On Thu, Jul 05, 2001 at 11:00:09AM +0200, Dag-Erling Smorgrav wrote:
> Matthew Jacob <[EMAIL PROTECTED]> writes:
> > it's just the same old same old refrain of "beast is broken" or
> > "oh well", etc. etc. etc but yer right, insulting does no
> > good.
> >
> > I beg too much hard cider at din
David claimed he would upgrade beast at some point- but he's pretty
busy.
1. If I had the authority to do so, I'd drive over to Concord and do it.
I can do that next week some time.
2. If I had > 144KBit DSL, I'd pay the extra power bills and leave up a
PC164 at Feral all the time for people to
On Fri, 6 Jul 2001, Bruce Evans wrote:
...
> if_foo.c -> /sys/modules/foo -> foo.ko. There is no driver named if_foo.
>
that seems to be right.
No man if_ed(4) yust ed(4)...
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
> On Fri, 6 Jul 2001, Bruce Evans wrote:
> ...
> > if_foo.c -> /sys/modules/foo -> foo.ko. There is no driver named if_foo.
> >
> that seems to be right.
> No man if_ed(4) yust ed(4)...
No.
if_foo.c in /sys/modules/foo builds if_foo.ko.
This was discussed a year or so back; it's a compromise d
Since David's busy, I'm working on it now. Just some build issues to
be worked out since warnings were made fatal recently.
- Jordan
From: Matthew Jacob <[EMAIL PROTECTED]>
Subject: Re: chgrp broken on alpha systems
Date: Thu, 5 Jul 2001 14:17:51 -0700 (PDT)
>
> David claimed he would upgrade
On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
> Since David's busy, I'm working on it now. Just some build issues to
> be worked out since warnings were made fatal recently.
What problems? There shouldn't be any fatalities from warnings unless
people have marked something with
As of a month ago or so, there was some discussion that concluded it was
unsafe to enable softupdates on a root partition. Is it safe to go back in
the water there, now?
Cheers,
Ben
Benjamin P. Grubin [EMAIL PROTECTED]
PGP Fingerprint: EDE9 A88F 3BCC 514A F310 FEFB 71
In the last episode (Jul 05), Benjamin P. Grubin said:
> As of a month ago or so, there was some discussion that concluded it
> was unsafe to enable softupdates on a root partition. Is it safe to
> go back in the water there, now?
The 2 drawbacks with SU are
1 - You can't immediately reuse the
>From: "Benjamin P. Grubin" <[EMAIL PROTECTED]>
>Date: Thu, 5 Jul 2001 19:46:54 -0400
>As of a month ago or so, there was some discussion that concluded it was
>unsafe to enable softupdates on a root partition. Is it safe to go back in
>the water there, now?
Well, despite the warnings, I've bee
On Thu, Jul 05, 2001 at 02:17:51PM -0700, Matthew Jacob wrote:
> David claimed he would upgrade beast at some point- but he's pretty
> busy.
Acutally out of the state on a WRS forced "vacation". :-(
> 1. If I had the authority to do so, I'd drive over to Concord and do it.
> I can do that next
On Wed, Jul 04, 2001 at 08:53:59AM +0200, Dag-Erling Smorgrav wrote:
> > Not normal, except by dimwits who add WARNS?= 2 w/o checking.
>
> Now, would it really have been so hard to just send (or even commit) a
> patch that declares len as a size_t rather than an unsigned int,
> instead of calling
Well, unless implicit pointer-to-int conversions have suddenly become
fatal, it blew up on something that just got fixed (I went to commit
the fix and found that someone else had already done so in the last 12
hours). The world build has been restarted and is running again.
- Jordan
From: Kris
On 05-Jul-01 Kris Kennaway wrote:
> On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
>> Since David's busy, I'm working on it now. Just some build issues to
>> be worked out since warnings were made fatal recently.
>
> What problems? There shouldn't be any fatalities from warnin
On 06-Jul-01 Jordan Hubbard wrote:
> Well, unless implicit pointer-to-int conversions have suddenly become
> fatal, it blew up on something that just got fixed (I went to commit
> the fix and found that someone else had already done so in the last 12
> hours). The world build has been restarted
Jason Evans wrote:
> On Mon, Jul 02, 2001 at 02:16:16PM -0700, Julian Elischer wrote:
> >
> > Almost all of the current 'proc' pointers being passed around the system
> > in syscalls will be changed to the #4 item. In addition, most accesses to
> > curproc would point to a curthread (curr-#4) or
On Thu, Jul 05, 2001 at 10:12:50AM +0200, Michael Reifenberger wrote:
> Hi,
> it seems to me that most existing if_* modul-directories
> are named in an inconstant way.
> FE:
> if_ti.c -> /sys/modules/ti-> if_ti.ko
> if_fxp.c -> /sys/modules/fxp -> if_fxp.ko
> ...
> but
> ...
>
John Baldwin <[EMAIL PROTECTED]> writes:
>
> On 06-Jul-01 Jordan Hubbard wrote:
> > Well, unless implicit pointer-to-int conversions have suddenly become
> > fatal, it blew up on something that just got fixed (I went to commit
> > the fix and found that someone else had already done so in the las
On Thu, Jul 05, 2001 at 06:00:25PM -0700, John Baldwin wrote:
>
> On 05-Jul-01 Kris Kennaway wrote:
> > On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
> >> Since David's busy, I'm working on it now. Just some build issues to
> >> be worked out since warnings were made fatal rece
On Thu, Jul 05, 2001 at 06:54:45PM -0700, Dima Dorfman wrote:
> > Matt Jacob usually steps in and fixes breakages on the alpha. At the minimum,
> > people should be either testing the build on all archs, or asking for someone
> > else to review the patch on archs they don't have available (this
On 06-Jul-01 Dima Dorfman wrote:
>> In the WARNS= case, another
>> workable method would be to commit the warning fixes but don't commit the
>> actual WARNS= change until the build has been verified on all archs.
>
> This doesn't work. The point of WARNS, as I see it anyway, is not to
> scrub t
On Thu, Jul 05, 2001 at 05:38:31PM -0700, David O'Brien wrote:
> What is so hard with ``make -m /home/kris/mk''?
That's actually not one of the hoops you need to jump through on beast
-- I think I got someone to install the new mk files already. The
main hoops are related to stale /usr/include
On Thu, 5 Jul 2001, Michael Reifenberger wrote:
> Hi,
> it seems to me that most existing if_* modul-directories
> are named in an inconstant way.
> FE:
> if_ti.c -> /sys/modules/ti-> if_ti.ko
> if_fxp.c -> /sys/modules/fxp -> if_fxp.ko
> ...
> but
> ...
> if_ef.c -> /sys/modu
Yes, I've actually been massaging a few of those- glad somebody's on
it. I'll come on out to Concord if you you need a hand It's
sometimes hard to keep -current up on an alpha long enough for a
complete buildworld
On Thu, 5 Jul 2001, Jordan Hubbard wrote:
> Since David's busy, I'm work
On Thu, 5 Jul 2001, Kris Kennaway wrote:
> On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
> > Since David's busy, I'm working on it now. Just some build issues to
> > be worked out since warnings were made fatal recently.
>
> What problems? There shouldn't be any fatalities
Perhaps what we really need- and this is really a toolchain issues- is a
compiler that is just as stringent on i386 as on alpha?
I dunno- there used to be a flag to lint that would worn about
non-portable size casts. Is there a gcc flag that would cover most
of the heavy lifting for this on i386
On Thu, Jul 05, 2001 at 08:07:40PM -0700, Matthew Jacob wrote:
>
>
> On Thu, 5 Jul 2001, Kris Kennaway wrote:
>
> > On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
> > > Since David's busy, I'm working on it now. Just some build issues to
> > > be worked out since warnings were
On Thu, 5 Jul 2001, Kris Kennaway wrote:
> On Thu, Jul 05, 2001 at 08:07:40PM -0700, Matthew Jacob wrote:
> >
> >
> > On Thu, 5 Jul 2001, Kris Kennaway wrote:
> >
> > > On Thu, Jul 05, 2001 at 04:12:22PM -0700, Jordan Hubbard wrote:
> > > > Since David's busy, I'm working on it now. Just so
> > I have to laugh. Sorry if you don't that helps. S'long then. I've no
> > more time for the likes of you.
>
> *rolls eyes* Man, some people are hard to work in a team with.
You guys are still trying to pass this off as a team??
*boggle*
gh
(Yeah yeah, unproductive..but what part of this th
On Thu, 5 Jul 2001, GH wrote:
> > > I have to laugh. Sorry if you don't that helps. S'long then. I've no
> > > more time for the likes of you.
> >
> > *rolls eyes* Man, some people are hard to work in a team with.
>
> You guys are still trying to pass this off as a team??
> *boggle*
>
> gh
>Date: Thu, 5 Jul 2001 22:12:46 +0700 (NOVST)
>From: [EMAIL PROTECTED]
>>start_init: trying /sbin/init
>>DEPENDENCY NOTE: portmap will be enabled to support NFS
>>Entropy harvesting: interrupts ethernet point_to_point
>> Leaving the system alone, it will apparently sit th
> Actually, the growing realization (at least to me) that the problem
> probably cannot be solved except via software tools, unless the FreeBSD
> community gets more like the NetBSD community in terms of awareness-
> which can only happen if it happens.
>
> I don't know how you feel about it, but
In article <[EMAIL PROTECTED]>,
Maxim Sobolev <[EMAIL PROTECTED]> wrote:
>
> It turns that ld(1) in -current has another nasty bug. I noticed it when
> was doing an upgrade for the games/bomberinstinct port. Something is wrong
> with registering dependencies on shared libraries - following trace
On Thu, 5 Jul 2001, Dan Nelson wrote:
:In the last episode (Jul 05), Benjamin P. Grubin said:
:> As of a month ago or so, there was some discussion that concluded it
:> was unsafe to enable softupdates on a root partition. Is it safe to
:> go back in the water there, now?
:
:The 2 drawbacks with
In the last episode (Jul 06), David Scheidt said:
> On Thu, 5 Jul 2001, Dan Nelson wrote:
>
> :In the last episode (Jul 05), Benjamin P. Grubin said:
> :> As of a month ago or so, there was some discussion that concluded it
> :> was unsafe to enable softupdates on a root partition. Is it safe to
I saw something similar at usenix with my old, hacked kernel config
file, but not with GENERIC that I just booted.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Peter Wemm wrote:
>
> Jason Evans wrote:
> > On Mon, Jul 02, 2001 at 02:16:16PM -0700, Julian Elischer wrote:
[...]
> > I think there is a clear argument for #1 to be "struct proc". I don't much
> > care what #2, #3, and #4 are called.
> >
> > I am of the rather strong opinion that calling #3/#4
Hi,
It turns that ld(1) in -current has another nasty bug. I noticed it when
was doing an upgrade for the games/bomberinstinct port. Something is wrong
with registering dependencies on shared libraries - following trace shows
the problem (notice bogus crtn.o entry):
cc -pipe -O -mpreferred-stack
In message <20010705100122.N1134-10@nihil> Michael Reifenberger writes:
: Hi,
: it seems to me that most existing if_* modul-directories
: are named in an inconstant way.
: FE:
: if_ti.c -> /sys/modules/ti-> if_ti.ko
: if_fxp.c -> /sys/modules/fxp -> if_fxp.ko
: ...
: but
: ..
In message <[EMAIL PROTECTED]> Brooks Davis writes:
: They should have been if_* or possiably if/*, but since current plans
I think the current way that most of them are done (eg module/foo) is
right.
: are to take src/sys/modules out back and shoot it, there's probably no
: point in fixing the
52 matches
Mail list logo
