On Mon, 08 May 2000 18:56:03 -0400, "Jeroen C. van Gelderen" wrote:
> Now it's a question of "the UNIX way" vs. convenience/userfriendlyness
> :-)
I don't agree. I think this is an issue of avoiding changes that
unnecessarily astonish existing users. If you can find ways to improve
MAKEDEV t
On Tue, 09 May 2000 10:26:05 +0200, Sheldon Hearn wrote:
> I don't agree. I think this is an issue of avoiding changes that
> unnecessarily astonish existing users. If you can find ways to improve
> MAKEDEV that don't inconvenience those already familiar with it, great.
> If your improvements
On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
> I ran MAKEDEV all, but the message still appear. The messages I found
> about this on the archives says to do a 'ls -l /dev | grep ^b', and
> to remake all devices listed, but there's no device listed when I'm
> doing the 'ls -l /dev | gr
On Mon, 08 May 2000 23:53:16 MST, Doug Barton wrote:
> > Eivind Eklund made a prototype some time back which addressed this issue -
> > you'd do well to take a look at that one first before reinventing the
> > wheel :)
>
> Point well taken. If anyone has references to this work, or an ea
About two days ago, I tested a machine with four IDE drives
each on its own cable as the master. All four drives were:
ad0: 29311MB [59554/16/63] at ata0-master using UDMA66
I used the motherboard controller to support two of the drives. It was a
atapci0: port 0xffa0-0xffaf at device 31.1 o
On Mon, 8 May 2000, Tim Vanderhoek wrote:
> On Mon, May 08, 2000 at 06:56:03PM -0400, Jeroen C. van Gelderen wrote:
> > >
> > > I don't buy it :-). This syntax is similar to a special case of the syntax
> > > of jot(1). It's better to use jot(1) directly, e.g.:
> > >
> > > MAKEDEV $(jot -
Appart from that, ipf does not load as a kld anymore. And probably, not
tried, the IPFILTER option in any kernel would break the build as well.
Nick
On Mon, 8 May 2000, Wes Morgan wrote:
> I sent a note to the committer on these last night. LINT must need some
> modification, because the error
On Mon, 8 May 2000, Warner Losh wrote:
> Leaving aside the 'r' question for the moment...
>
> Should that be sa or ast? sa is the scsi device for any tape device
> (formerly st or mt), while ast is for ide/atapi based tape drives.
It should be ssa and asa, of course :-).
> The wt and wst devi
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Jonathan Lemon <[EMAIL PROTECTED]> _crivait (wrote) :
>
> > jlemon 2000/05/05 20:31:10 PDT
> >
> > Modified files:
> > sys/netinet tcp.h tcp_input.c tcp_output.c
> > tcp_timer.c tcp_var.h
> >
On Tue, 9 May 2000, Sheldon Hearn wrote:
>
>
> On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
>
> > I ran MAKEDEV all, but the message still appear. The messages I found
> > about this on the archives says to do a 'ls -l /dev | grep ^b', and
> > to remake all devices listed, but there'
Errrmmm Really, did you check the archives for the issue?
There used to be a real long thread on why/why not sysV style init
scripts. It produced not one but several flamewars iirc 8-)
In short - if we change from the present scheme, we want something better
than just stop and restart ent
On Tue, May 09, 2000 at 08:54:50PM +1000, Bruce Evans wrote:
> wst and ast are weird names. Doesn't the "s" in them stand for "SCSI"
> and not "streaming", so wst is the so-called-Winchester (non-SCSI) SCSI
It does to me. But McKusick's mail I forwarded says "s" was for
"streaming".
--
-- Dav
On Mon, May 08, 2000 at 06:30:17PM -0400, Kenneth Wayne Culver wrote:
> Actually, it has to do with the pkg_ commands, which I believe are built
> when you make world...
yes.
> and aren't part of the ports,
And are only used for Ports. Thus their behavior defines the behavior of
the Ports Col
Doug Barton <[EMAIL PROTECTED]> wrote:
>
> Point well taken. If anyone has references to this work, or an easy
>introduction to netbsd's version I'd love to look at them.
There's useful stuff in the rc(8) and rcorder(8) manual pages, but I
can't find any more convenient copies of them other
On Mon, May 08, 2000 at 11:53:16PM -0700, Doug Barton wrote:
> Point well taken. If anyone has references to this work, or an easy
> introduction to netbsd's version I'd love to look at them. I've been
> hoping to carve out some time to work on this, but every time I talk
> about vacation, m
> >
> > Just curious, but wouldn't this be FreeSVR4??? :-)
>
> I'm going to assume that the smiley means you're joking, but I hope
> that we can stick to discussing this plan on its merits, rather than
> rejecting it out of hand because it's like something that someone else
> is doing.
>
>> > On Sun, 7 May 2000, Nick Hibma wrote:
>> >
>> > >
>> > > Is it only me that ever compiles LINT? The checksum changes went in a
>> > > few days ago.
>> > >
>> > > Please, people, when you move code around or change a function that is
>> > > used in more than a fixed set of files, compile LI
Will Andrews wrote:
>
> On Mon, May 08, 2000 at 11:53:16PM -0700, Doug Barton wrote:
> > Point well taken. If anyone has references to this work, or an easy
> > introduction to netbsd's version I'd love to look at them. I've been
> > hoping to carve out some time to work on this, but every
Kenneth Wayne Culver wrote:
> Yeah, I was just joking, I kinda like some things about SVR4, but I still
> think it would be nice to keep the option of using some of the regular rc
> scripts that we have now. Imagine the confusion of the people that have
> ONLY used FreeBSD when they go in and see
On Wed, May 10, 2000 at 01:49:51AM +0900, MIHIRA Yoshiro wrote:
> >> > On Sun, 7 May 2000, Nick Hibma wrote:
> >> >
> >> > >
> >> > > Is it only me that ever compiles LINT? The checksum changes went in a
> >> > > few days ago.
> >> > >
> >> > > Please, people, when you move code around or chang
On Tue, 9 May 2000, David O'Brien wrote:
>On Mon, May 08, 2000 at 06:30:17PM -0400, Kenneth Wayne Culver wrote:
>> Actually, it has to do with the pkg_ commands, which I believe are built
>> when you make world...
>
>yes.
>
>> and aren't part of the ports,
>
>And are only used for Ports. Thus t
On Tue, May 09, 2000 at 01:23:09PM -0400, Adam wrote:
> >And are only used for Ports. Thus their behavior defines the behavior of
> >the Ports Collection. Thus it is a Ports issue. IF the pkg_* utils were
> >ports, how would you install them??
>
> Am I missing something? I thought ports only
On Tue, May 09, 2000 at 12:12:44PM -0400, Kenneth Wayne Culver wrote:
> Yeah, I was just joking, I kinda like some things about SVR4, but I still
> think it would be nice to keep the option of using some of the regular rc
> scripts that we have now.
What I am prosing aguments what we have today (
< said:
> Packages (ie, those things that pkg_{create,add,delete,info} operate on
> are created with in /usr/ports.
Not necessarily, and certainly not in the very beginning. I remember
a number of times seeing a third-party software vendor who provided
their product in that form, just as many t
Did a cvsup on saturday, make world etc and now TCP/IP networking seems
to be broken. dmesg shows the devices, ifconfig configs everything
without
error, but cant ping, telnet, ssh etc off of the server. Even set up PPP
with the same results. Downside to this is that I cannot cvsup to
something
mo
On Tue, May 09, 2000 at 01:36:03PM -0400, Garrett Wollman wrote:
> Not necessarily, and certainly not in the very beginning. I remember
> a number of times seeing a third-party software vendor who provided
> their product in that form, just as many third-party vendors now ship
> *.rpm files (and
Update your source again. This has been fixed.
paul
Jason J. Horton ([EMAIL PROTECTED]) wrote:
> Did a cvsup on saturday, make world etc and now TCP/IP networking seems
> to be broken. dmesg shows the devices, ifconfig configs everything
> without
> error, but cant ping, telnet, ssh etc off of t
In message <[EMAIL PROTECTED]> Bruce Evans
writes:
: On Mon, 8 May 2000, Warner Losh wrote:
:
: > Leaving aside the 'r' question for the moment...
: >
: > Should that be sa or ast? sa is the scsi device for any tape device
: > (formerly st or mt), while ast is for ide/atapi based tape drives.
On Mon, 8 May 2000, Mike Pritchard wrote:
> On Mon, May 08, 2000 at 02:10:28AM -0400, Kenneth Wayne Culver wrote:
> > I have a suggestion for pkg_delete: Very often when I'm deleting a package
> > (such as kde, after testing the port) I want to delete that package, and
> > all it's dependancies;
On Tue, 9 May 2000, David O'Brien wrote:
>On Tue, May 09, 2000 at 01:23:09PM -0400, Adam wrote:
>> >And are only used for Ports. Thus their behavior defines the behavior of
>> >the Ports Collection. Thus it is a Ports issue. IF the pkg_* utils were
>> >ports, how would you install them??
>>
>
-On [2509 11:20], Alan Cox ([EMAIL PROTECTED]) wrote:
>In summary, same disks, three different controllers, problems only
>occur with the Highpoint controller. (I believe the Abit BP6 uses
>the Highpoint controller.)
It does.
It might be worthwhile to note that there are updates o
On Tue, May 09, 2000 at 03:24:25PM -0400, Adam wrote:
> I cant comment on the complexity of registering a port as an installed
> package because I havent read the code, but it doesnt look too complex
> according to whats in /var/db/pkg... perhaps more makefile things could
> be done to register a
Greg Lehey wrote:
>
> On Monday, 8 May 2000 at 9:57:54 +0200, [EMAIL PROTECTED] wrote:
> >> Not all non IBM disks has problems, that was not the message back
> >> then, at least not from me. What I said, and still says, is that
> >> Maxtor and WDC has a bad reputation on making drives that can'
>On Tue, May 09, 2000 at 03:24:25PM -0400, Adam wrote:
>> I cant comment on the complexity of registering a port as an installed
>> package because I havent read the code, but it doesnt look too complex
>> according to whats in /var/db/pkg... perhaps more makefile things could
>> be done to regist
>
> > Yeah, I was just joking, I kinda like some things about SVR4, but I still
> > think it would be nice to keep the option of using some of the regular rc
> > scripts that we have now. Imagine the confusion of the people that have
> > ONLY used FreeBSD when they go in and see rc.d and all it's
Yeah, but some ports and projects don't have the same beginning to their
names which prompted me to make my suggestion.
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 24767
Hi Y'll
A kernel source file that compiles flawlessly on RELEG_3,
gives (among many others, these warnings:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wm
issing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ans
i -nostdinc -I- -I. -I../
I just updated an i386 machine after a month to the latest 5.0-CURRENT,
and I now get some strange boot messages:
isa0: too many memory ranges
...
unknown0: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0
unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4
on isa0
unknown2: a
Alan Cox wrote:
>
> About two days ago, I tested a machine with four IDE drives
> each on its own cable as the master. All four drives were:
>
> ad0: 29311MB [59554/16/63] at ata0-master using UDMA66
>
> I used the motherboard controller to support two of the drives. It was a
>
> atapci0:
Hi Again,
Since you were so kind to me, I will impose another
one on you (the previous answers were _all_ correct! )
Given:
typedef struct junk {
...
} junk_t
volatile junk_t trash;
What I want to do is zero out trash.
bzero(trash, sizeof(junk_t));
produces a warning about loss of v
<
said:
> So does:
> bzero((void *)&trash, sizeof(junk_t));
> So, how do I make everyone happy?
Put a comment on that line indicating that a warning is expected.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The f
The only answer I've seen for this one is to kick, hard, whoever it was
that added -Wcast-qual to the kernel options. Or write your own,
suboptimal, bzero code.
> Hi Again,
>
> Since you were so kind to me, I will impose another
> one on you (the previous answers were _all_ correct! )
>
> G
On Tue, May 09, 2000 at 05:01:02PM -0400, Adam wrote:
> Since you claim superior knowledge about ports than me, I wont bother
> explaining it. I'm only trying to satisfy your original question.
>
> " IF the pkg_* utils were ports, how would you install them??"
I said that to make you thin
On Tue, May 09, 2000 at 04:27:10PM -0700, Mike Smith wrote:
> The only answer I've seen for this one is to kick, hard, whoever it was
> that added -Wcast-qual to the kernel options.
Or we should just delete it from the options.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to
> On Tue, May 09, 2000 at 04:27:10PM -0700, Mike Smith wrote:
> > The only answer I've seen for this one is to kick, hard, whoever it was
> > that added -Wcast-qual to the kernel options.
>
> Or we should just delete it from the options.
Ugh. I don't actually like that, because it serves a val
Mike Smith wrote:
>
> Ugh. I don't actually like that, because it serves a valid purpose.
> What irritates me mostly is just that there is no way of casting a
> volatile object into a non-volatile type, so you can't implement any sort
> of conditional volatility exclusion.
You can however use a
At 7:08 PM -0400 5/9/00, Simon Shapiro wrote:
>Given:
>
>typedef struct junk {
>...
>} junk_t
>
>volatile junk_t trash;
>
>What I want to do is zero out trash.
>
>bzero(trash, sizeof(junk_t));
>
>produces a warning about loss of volatility.
>So, how do I make everyone happy?
Write a 'bzer
Sorry to bother y'll, but;
Has anyone ever used that? I see no trace of any kernel
code calling it, and the at_shutdown code appears to be
gone.
BTW, for all it is worth, any caching controller not using
this is guaranteed to lose data.
that can range from 4MB to 256MB, all of which the kernel
> Sorry to bother y'll, but;
>
> Has anyone ever used that? I see no trace of any kernel
> code calling it, and the at_shutdown code appears to be
> gone.
It's still used in the shutdown code; it was meant to be available for
general use elsewhere, but I haven't seen anyone playing with it, so
On 10-May-00 Marcel Moolenaar wrote:
> Mike Smith wrote:
>>
>> Ugh. I don't actually like that, because it serves a valid purpose.
>> What irritates me mostly is just that there is no way of casting a
>> volatile object into a non-volatile type, so you can't implement any sort
>> of conditional
Correction to the below message;
Figured it out all by myself :-)
Thanx!
On 10-May-00 Simon Shapiro wrote:
> Sorry to bother y'll, but;
>
> Has anyone ever used that? I see no trace of any kernel
> code calling it, and the at_shutdown code appears to be
> gone.
>
> BTW, for all it is worth,
On 10-May-00 Mike Smith wrote:
>> Sorry to bother y'll, but;
>>
>> Has anyone ever used that? I see no trace of any kernel
>> code calling it, and the at_shutdown code appears to be
>> gone.
>
> It's still used in the shutdown code; it was meant to be available for
> general use elsewhere, bu
On Tue, 9 May 2000, David O'Brien wrote:
> On Mon, May 08, 2000 at 06:30:17PM -0400, Kenneth Wayne Culver wrote:
> > Actually, it has to do with the pkg_ commands, which I believe are built
> > when you make world...
>
> yes.
>
> > and aren't part of the ports,
>
> And are only used for Ports
On 09-May-00 Mike Smith wrote:
>> On Tue, May 09, 2000 at 04:27:10PM -0700, Mike Smith wrote:
>> > The only answer I've seen for this one is to kick, hard, whoever it was
>> > that added -Wcast-qual to the kernel options.
>>
>> Or we should just delete it from the options.
>
> Ugh. I don't ac
>
> On 10-May-00 Mike Smith wrote:
> >> Sorry to bother y'll, but;
> >>
> >> Has anyone ever used that? I see no trace of any kernel
> >> code calling it, and the at_shutdown code appears to be
> >> gone.
> >
> > It's still used in the shutdown code; it was meant to be available for
> > gener
Simon Shapiro wrote:
>
> On 10-May-00 Mike Smith wrote:
> >> Sorry to bother y'll, but;
> >>
> >> Has anyone ever used that? I see no trace of any kernel
> >> code calling it, and the at_shutdown code appears to be
> >> gone.
> >
> > It's still used in the shutdown code; it was meant to be ava
On Tuesday, 9 May 2000 at 4:14:01 -0500, Alan Cox wrote:
> About two days ago, I tested a machine with four IDE drives
> each on its own cable as the master. All four drives were:
>
> ad0: 29311MB [59554/16/63] at ata0-master using UDMA66
>
> I used the motherboard controller to support two of
Christian Weisgerber wrote:
>
> I just updated an i386 machine after a month to the latest 5.0-CURRENT,
> and I now get some strange boot messages:
>
> isa0: too many memory ranges
> ...
> unknown0: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0
> unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,
Narvi wrote:
>
> Errrmmm Really, did you check the archives for the issue?
>
> There used to be a real long thread on why/why not sysV style init
> scripts. It produced not one but several flamewars iirc 8-)
>
> In short - if we change from the present scheme, we want something better
> tha
59 matches
Mail list logo
