Would be nice if the pccard.conf.example had the D-Link DFE-650 in it!
For the hell of it, I tried the DE-660, no dice :(
Best regards,
Chris
_
DH/DSS Fingerprint = 8265 0BB8 2C7D A376 3CCD 6858 8630 0E47 194A 0
It seems Russell L. Carter wrote:
>
> Hi Soren,
>
> I am beginning to believe that the FIC mb is the problem. My
> IBM-DPTA-372050 is only half as fast (500MB bonnie)
> as on the P2B (~10MB/s vs. ~19MB/s). A Jan 11 kernel
> doesn't downgrade to PIO on the
> IBM-DTTA-371440 as fast as this eve
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: Well, I wasn't really trying to flame you, or anyone. It is frusterating
: to see how much time gets tied up in tracking down dodgy PCIC configs
: though. Solving that would probably free you up of several emails a
: week. If I start m
On Wed, 19 Jan 2000, Warner Losh wrote:
> I'd love to find a good solution to this problem. I'm glad your flame
> caught me at a time when my brain was up for trying to solve this
> silly problem.
Well, I wasn't really trying to flame you, or anyone. It is frusterating
to see how much time gets
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: Otherwise your timeout solution seems good. Are the valid IRQs dependent
: on the board integrator or on the chip used? Since we can identify the
: chips (well, it looks like we can) couldn't we maintain a 'quirk' table?
That I'm not s
It seems Valentin S. Chopov wrote:
>
> It seems that we need #if...#endif here, maybe
> something like that:
>
> ...
> #if NATAPICD > 0 || NATAPIFD > 0 || NATAPIST > 0
> /* then the atapi devices */
> for (ctlr=0; ctlr if (!atadevices[ctlr]) continue;
> if (atadevices[ct
On Wed, 19 Jan 2000, Warner Losh wrote:
> Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC
> part. If they are, then it works great. If they aren't, then we lose
> bigtime.
It seems to me that any IRQ that the PCIC can see will be usable for
assignment to a card no? Is the
Hard times for the box at home and freebsd-current.
there are of course some options to choose in the bios (which one would
be adequate?), but before it worked without the need to tweak the bios.
Btw. since this night i see the message from ata-all.c (it was too late
yesterday night to do more ..
Patrick Bihan-Faou writes :
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Hi,
>
> If we are changing the meaning of "USA_RESIDENT", could we replace it by
> something else completely. I know that the USA are the center of the
> universe ;-), but...
>
> It seems to me that a things pr
On Tue, 18 Jan 2000, Warner Losh wrote:
> Oops. Missed this part. The problem again is that the kernel doesn't
> know about this. At least it knows it only to a point. It knows
> which IRQs are in use, but it doesn't know if the pcic (or cardbus
> bridge in compat mode) can route to a given fr
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: pccardd shouldn't have to specify a list of IRQs to use; thats info the
: kernel knows about.
Oops. Missed this part. The problem again is that the kernel doesn't
know about this. At least it knows it only to a point. It knows
which
> The IRQ is useful to me at least, since the ISA/PCI irq distribution is
> rather hackish and non-trivial to get right at times.
Note that I'm not saying that IRQ is not useful - I'm just asking whether it's
important to see when bootverbose == 0.
To Unsubscribe: send mail to [EMAIL PROTECT
On Tue, 18 Jan 2000, FreeBSD mailing list wrote:
> speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref'
> /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings'
Please pay attention to the mailing list. I'm testing the fix for this now
with a make world of both
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: The pcic driver should be smart enough to find a free IRQ; in addition
: pccardd shouldn't have to specify a list of IRQs to use; thats info the
: kernel knows about.
Should be smart enough? How? There are a limited number of IRQs
avai
In message <[EMAIL PROTECTED]>, Matthew
Jacob writes:
>
>
>> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
>> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>>
>> Agreed. For a PCI card all I want to know is what i
On Tue, 18 Jan 2000, Warner Losh wrote:
> Also, you will likely need to add an IRQ to the pcic line in your
> kernel config.
The pcic driver should be smart enough to find a free IRQ; in addition
pccardd shouldn't have to specify a list of IRQs to use; thats info the
kernel knows about.
I'm ki
Kris Kennaway wrote:
>
> On Tue, 18 Jan 2000, Warner Losh wrote:
>
> > In message <[EMAIL PROTECTED]> Satoshi - Ports Wraith -
>Asami writes:
> > : Won't people get into legal trouble (technically) if they build the
> > : wrong version?
> >
> > RESIDENT=
> > CITIZEN=
>
> What about us dual cit
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Satoshi - Ports Wraith - Asami
>writes:
> : Won't people get into legal trouble (technically) if they build the
> : wrong version?
>
> RESIDENT=
> CITIZEN=
Is there an ISO code for Mars yet?
--
"Where am I, and what am I doing
In message <[EMAIL PROTECTED]> John Polstra writes:
: Details, please. If I had a nickel for every "CVSup problem" that
: turned out to be something else, I'd be a rich man today.
I was working on that
It was either one of two things.
My cvsup file at work didn't have a delete line like I
In article <[EMAIL PROTECTED]>,
Warner Losh <[EMAIL PROTECTED]> wrote:
>
> I did a make world Sunday and it worked. I did a makeworld today and
> it was busted. Turned out to be a cvsup problem that I owe jdp a
> message about.
Details, please. If I had a nickel for every "CVSup problem" tha
> %It seems Russell L. Carter wrote:
> %> %It seems Russell L. Carter wrote:
> %> %>
> %> %> I swapped out my motherboard and am seeing this now:
...
>
> )(*&$#%$# stupid magazine benchmarkers never actually test
> things like IO... gr
We in the computer hardware business have a bet
In message <[EMAIL PROTECTED]> Chuck Robey writes:
: Sure would be nice if some folks would start testing before
: committing. I'm starting to wonder how long it'll be before it builds
: again. I understand screwups (god know I better!) but if you don't test
: before commit, that's taking things
In message <[EMAIL PROTECTED]> Chris Piazza writes:
: I *thought* I noticed it was different. I actually find this pretty
: annoying because it wraps almost all of the lines and makes it difficult
: to read dmesg.
I don't mind them, but wouldn't object to a generic wrapping
mechanism.
Warner
In message <[EMAIL PROTECTED]> Edwin Culp writes:
: :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for
: D-Link(DE-66
: 0): Inappropriate ioctl for device
Make sure that your kernel and pccardd match. The binary api changes
from time to time in -curent. This is a sure symptom.
cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DRSAref
-I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o
crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o
openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa
%It seems Russell L. Carter wrote:
%> %It seems Russell L. Carter wrote:
%> %>
%> %> I swapped out my motherboard and am seeing this now:
%> %>
%> %> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
%> %> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
%> %> ad0: UDMA CRC WRITE ERROR blk# 1140495
Thank you very much. The include file was different and I copied it and
rebuilt pccardc and pccardd and think that will solve the problem.
Thanks,
ed
MIHIRA Yoshiro wrote:
> [EMAIL PROTECTED] wrote:
>
> >> I am running current as of yesterday. I have neglegently not been
> >> rebooting after
I copied the src/sys/pccard/cardinfo.h which was different from the one in
include. I remade pccardc and pccardd. I haven't tested it yet because I am
waiting for my "desperation" make world to finish in about 15 minutes, but I'm
confident that is the problem.
Thanks, I would not have found it
hi, there!
On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
> The equivalent to the old -a option is --binary-files=without-match.
> If you want this by default, you can hardcode it in GREP_OPTIONS
> environment variable.
I think there should be one-letter shorthand for this.
/fjoe
To Unsubscribe
On Sun, Jan 16, 2000 at 03:21:16PM +0100, F. Heinrichmeyer wrote:
>
>My parallel port zip-drive stopped working this weekend with the new ppc
>code. There is no printer attached:
Hmm, any chance to change parallel port bios setting on your MB?
>
>
>--
>Fritz Heinrichmeyer mailto:[EMAIL PROTECTE
[EMAIL PROTECTED] wrote:
>> I am running current as of yesterday. I have neglegently not been
>> rebooting after make world and making a new kernel. Yesterday I did
>> reboot and found that something has changed and my D-Link 660 and my
>> Viking Modem PCMCIA cards are no longer working.
>>
>>
From: Edwin Culp <[EMAIL PROTECTED]>
Subject: Re: Problems with PCMCIA Cards
Date: Tue, 18 Jan 2000 16:45:25 -0800
Message-ID: <[EMAIL PROTECTED]>
eculp> > On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote:
eculp> > > I am running current as of yesterday. I have neglegently not been
ec
On Tue, 18 Jan 2000, Garrett Wollman wrote:
> No, this is the same Garrett who persuaded you not to include the RSA
> code at all in the freefall repository so that I could continue to
> maintain a mirror without getting into trouble with the Technology
The upshot of all of which is that people
On Tue, 18 Jan 2000, David O'Brien wrote:
> On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > > was assigned. A single line should be suffient.
> >
> > Do you even need to know what IRQ it was assig
>
> What would be nice would be to have the normal version displayed and
> the verbose stuff go to a seperate buffer and logged seperatly..
>
> ie so you don't clutter your boot screen with junk, but if you have a
> problem you can get at the verbose info :)
>
> .. and no I don't have any patc
On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > was assigned. A single line should be suffient.
>
> Do you even need to know what IRQ it was assigned? It seems to me that IRQ,
With wacky PC hardwar
< said:
> Is this the same Garrett who persuaded me not to include the RSA code at
> all in the freefall repository so that people wouldn't get in trouble for
> simply posessing it? :)
No, this is the same Garrett who persuaded you not to include the RSA
code at all in the freefall repository so
Oscar,
Thanks a lot, but my kernel.conf has
device pcic0 isa?
Already.
Thanks,
ed
Oscar Bonilla wrote:
> On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote:
> > I am running current as of yesterday. I have neglegently not been
> > rebooting after make world and making a new kernel.
On 19-Jan-00 Matthew Jacob wrote:
> Do you even need to know what IRQ it was assigned? It seems to me
> that IRQ,
> like IO-PORT, is only needed if you're either interested in such
> stuff or to
> catch conflicts (both are under bootverbose)
What would be nice would be to have the normal ve
It seems that we need #if...#endif here, maybe
something like that:
...
#if NATAPICD > 0 || NATAPIFD > 0 || NATAPIST > 0
/* then the atapi devices */
for (ctlr=0; ctlrdevices &
ATA_ATAPI_MASTER)
atapi_attach(atadevices[ctlr],
ATA_MASTER);
if (atadevices[ctlr]->device
On Tue, 18 Jan 2000, David O'Brien wrote:
> I think this is the only way to properly handle it. As Garrett pointed
> out, some people in the USA actually do have a licence to use the "good"
> version of RSA.
Is this the same Garrett who persuaded me not to include the RSA code at
all in the fre
> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> was assigned. A single line should b
On Tue, Jan 18, 2000 at 10:26:12AM -0500, Patrick Bihan-Faou wrote:
> Then as part of the build process, automatically create specific variables
> for RSA or other stuff as they show up:
>
> CRYPTO_RSA="RSAref" or CRYPTO_RSA="rsa" or CRYPTO_RSA="none". This can be
> done by a little bit of shell
> In message <[EMAIL PROTECTED]> Brian Somers writes:
> : Where UP == OFF, from 1-8 I've got
> :
> : UP, UP, UP, UP, DOWN, UP, DOWN, DOWN
>
> OK. I've found out what the problem is, at least with the bog
> standard GENERIC. I'll see about finding some time to fix aha. Short
> answer is that a
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
Agreed. For a PCI card all I want to know is what it is, and what IRQ it
was assigned. A single line should be suffient.
On 18/01 20:03, Brad Knowles wrote:
> Russia and France both are highly crypto-unfriendly, in that you are
> not allowed to use any crypto whatsoever unless it has been explicitly
> approved by the government.
France changed their policy from zero-crypto to allowing 128-bits almost
exactly a yea
On 18/01 23:09, Jeroen Ruigrok/Asmodai wrote:
> >Given the Plug'n'Pray changes in -current, I pretty much expected to lose
> >AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to
> >probe the "magic" ports for the AWE32).
>
> AWE32 here, PnPBIOS to off, and added device
On Tue, Jan 18, 2000 at 02:12:02PM +0800, Peter Wemm wrote:
> .. and why is this a security hole? setresuid(geteuid(), geteuid(), geteuid())
> is equivalent to setuid(geteuid())..
Umm, maybe not the hole exactly, but difference between same area syscalls
implementation.
We define POSIX_APPENDIX
On Tue, 18 Jan 2000, Patrick Bihan-Faou wrote:
> cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src-freebsd-4.x/secure/usr.bin/opens
> sl -DRSAref -I/usr/obj/usr/src-freebsd-4.x/i386/usr/include -o openssl
> apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o
> enc.o errstr.o
On Tue, 18 Jan 2000, Kris Kennaway wrote:
> Fetching packages due to network topology is another idea I've wanted to
> implement for a while, although I was thinking of doing it dynamically by
> testing the available bandwidth to each of the hosts (and storing it in a
> database) and using them
> > I like to use BASH shell in my user account. how can i do this ? please
> > inform.
>
> Install bash (either from ports or a package).
>
> Use chsh to change the entry for Shell to /usr/local/bin/bash.
and before you ask why you cannot ftp to your machine, do not forget to a
From: "Jonathan M. Bresler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, January 18, 2000 3:07 AM
Subject: Re: ppp, incoming mail keeping the line up.
> >
> > I run user-ppp, and I have a mx-record for my system, so incoming mail =
> > goes directly to my s
On Tue, 18 Jan 2000, Taavi Talvik wrote:
> Maybe we should extend meaning of USA_RESIDENT or introduce new variable
> indicating contry. After doing netfork install, subsecuent fetces for
> ports/packages/distfiles from nearest
> ftp.xx.freebsd.org/cvsup.xx.freebsd.org is really handy. Specially
>
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
>
> I thought we printed out the port/mem stuff for ISA because it is
> usually jumpered by the admin, but for dynamic allocation
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
>
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
I *thought* I noticed it was different. I actually find this p
On Wed, 19 Jan 2000, Poul-Henning Kamp wrote:
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
Its consistant, but I need to unify all the resource printing stuff since
theres about
fxp0: port 0xc400-0xc43f mem
0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
Is this level of verbosity really helping anybody ?
I thought we printed out the port/mem stuff for ISA because it is
usually jumpered by the admin, but for dynamic allocation busses/devices
On Mon, Jan 17, 2000 at 11:46:23PM +0100, Jesper Skriver wrote:
> On Mon, Jan 17, 2000 at 05:00:14PM -0500, Christopher Masto wrote:
> > On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote:
> > > On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote:
> > > > In message <[EMAIL PRO
as of a cvsup from today, i just finished a buildworls and an
installworld, so it seems the errors on my system have gone away
Chuck Robey wrote:
>
> Sure would be nice if some folks would start testing before
> committing. I'm starting to wonder how long it'll be before it builds
> again. I u
-On [2118 04:02], Andy Sparrow ([EMAIL PROTECTED]) wrote:
>Given the Plug'n'Pray changes in -current, I pretty much expected to lose
>AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to
>probe the "magic" ports for t
In message <[EMAIL PROTECTED]> Brian Somers writes:
: Where UP == OFF, from 1-8 I've got
:
: UP, UP, UP, UP, DOWN, UP, DOWN, DOWN
OK. I've found out what the problem is, at least with the bog
standard GENERIC. I'll see about finding some time to fix aha. Short
answer is that aha is caching so
>Date: Sun, 16 Jan 2000 21:13:28 +0100
>From: "F. Heinrichmeyer" <[EMAIL PROTECTED]>
>
>my freebsd box goes down, something strange happens, when a ring signal
>is detected. I
>have apm disabled in the bios and no apm device in the config file.
>
>It is "alsmost a reset", like a short power failur
>
> Sure would be nice if some folks would start testing before
> committing. I'm starting to wonder how long it'll be before it builds
> again.
>
I had two problems building a kernel from 1/16/2000:
I had to create the directories:
/usr/share/examples/ses
On Tue, 18 Jan 2000, Jordan K. Hubbard wrote:
> > Not yet, but it should. If someone can help me out here it would be
> > greatly appreciated.
>
> "Setting it in sysinstall" is easy. Deciding where and how to set it
> in response to questions at certain stages of the installations(s)
> is more
Sure would be nice if some folks would start testing before
committing. I'm starting to wonder how long it'll be before it builds
again. I understand screwups (god know I better!) but if you don't test
before commit, that's taking things a step too far.
-
On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote:
> I am running current as of yesterday. I have neglegently not been
> rebooting after make world and making a new kernel. Yesterday I did
> reboot and found that something has changed and my D-Link 660 and my
> Viking Modem PCMCIA cards
At 9:58 AM -0800 2000/1/18, Kris Kennaway wrote:
> I don't know much about the restrictions of other countries. If the
> current crypto policies were a legal problem for someone else we can
> surely change them to suit, but I'd rather not complicate things even more
> than they are already wi
Hi,
this is probably not news, but here is what I get.
I tried with both USA_RESIDENT=YES and no USA_RESIDENT defined...
The code has been CVSuped on tuesday Jan 18 2000 around 2am EST.
cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src-freebsd-4.x/secure/usr.bin/opens
sl -DRSAref -I/usr/obj/usr/
On Tue, 18 Jan 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Satoshi - Ports Wraith - Asami
>writes:
> : Won't people get into legal trouble (technically) if they build the
> : wrong version?
>
> RESIDENT=
> CITIZEN=
What about us dual citizens? :-)
Kris
"How many roads must
> > If somebody _really_ want to ping forever, let them use -t0, and
> > defend the rest of us from our blunders of forgetting a ping, keeping
> > the line open infinitely.
>
> I use ping for precisely this purpose. Yes, I could change my setup,
> but so could you :-)
I used SunOS (and later Sol
I think the -a parameter to ping would be useful to you. It makes the pc
speaker emit a beep for every reply. If you have the speaker working and
are not hearing impaired, you will NOT forget! :)
On Tue, 18 Jan 2000, Leif Neland wrote:
> I've been hit by a "forgotten ping" again.
>
> I still
> Not yet, but it should. If someone can help me out here it would be
> greatly appreciated.
"Setting it in sysinstall" is easy. Deciding where and how to set it
in response to questions at certain stages of the installations(s)
is more the sticking point.
- Jordan
To Unsubscribe: send mail t
It seems Brian Somers wrote:
> Hi,
>
> I don't know if you'd class this as a bug report or more as an
> observation. I have a machine with the following:
bug :)
> ata-pci0: port 0xf000-0xf00f at device 15.0 on
>pci0
> ata-pci0: Busmastering DMA supported
> ata0 at 0x01f0 irq 14 on ata-pci0
Hi,
I don't know if you'd class this as a bug report or more as an
observation. I have a machine with the following:
ata-pci0: port 0xf000-0xf00f at device 15.0 on
pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
[.]
ad0: ATA-
I am running current as of yesterday. I have neglegently not been
rebooting after make world and making a new kernel. Yesterday I did
reboot and found that something has changed and my D-Link 660 and my
Viking Modem PCMCIA cards are no longer working.
:Jan 17 23:33:58 local-27 pccardd[46]: driv
In message <[EMAIL PROTECTED]> Garrett
Wollman writes:
: < said:
:
: > This is definitely a bad idea; IMHO we should only do this when the
: > resource is actually activated (and obviously free it when deactivated).
:
: Absolutely! As I keep trying to explain to people, that's why there
: *is*
It seems Russell L. Carter wrote:
>
> I swapped out my motherboard and am seeing this now:
>
> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
> ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT
On Mon, Jan 17, 2000 at 05:25:37PM -0500, Bush Doctor wrote:
> "make buildworld" fails with sources cvsup'd around 17:00 est ...
>
> whereintheworld.pl (thanxs Bill Fenner) shows ...
What does this Perl script do? :-)
--Will
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
In message <[EMAIL PROTECTED]> Brian Somers writes:
: UP, UP, UP, UP, DOWN, UP, DOWN, DOWN
:
: Needless to say (you wanna see the state of this place), I can't seem
: to find the manual at the moment :-/
OK. I'll take a look at it and see what's up. I even found my 1542CP
in the large mass of
In message <[EMAIL PROTECTED]> Kris Kennaway
writes:
: > In message <[EMAIL PROTECTED]> Satoshi - Ports Wraith -
:Asami writes:
: > : Won't people get into legal trouble (technically) if they build the
: > : wrong version?
: >
: > RESIDENT=
: > CITIZEN=
:
: What about us dual citizens? :-)
OK
In message <[EMAIL PROTECTED]> Satoshi - Ports Wraith - Asami
writes:
: Won't people get into legal trouble (technically) if they build the
: wrong version?
RESIDENT=
CITIZEN=
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I swapped out my motherboard and am seeing this now:
ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA
falling back to PI
On Tue, 18 Jan 2000, Patrick Bihan-Faou wrote:
> If we are changing the meaning of "USA_RESIDENT", could we replace it by
We're not. It's just that until now it hasn't really mattered if it
wasn't set (the cases where it did matter, like whether or not to fetch a
crypto port from a US site, it w
On Tue, 18 Jan 2000, Peter Wemm wrote:
> Yes, This should most definately have ${DESTDIR} for this sort of thing, but
> even then I'm not sure this is a good change.. We have got to find a better
> way than this.
I've said this a couple of times in private, but will repeat it again for
the list
On Tue, 18 Jan 2000, Sheldon Hearn wrote:
> Does sysinstall set this one? If not, it should. Then we can stop
> worrying about it. :-)
Not yet, but it should. If someone can help me out here it would be
greatly appreciated.
Kris
"How many roads must a man walk down, before you call him
On 18-Jan-00 Satoshi - Ports Wraith - Asami wrote:
> Won't people get into legal trouble (technically) if they build the
> wrong version?
As far as I understand things specifying USA_RESIDENT=yes when it is
not true is liable (technically) to get some US based ftp server operator in
trou
On Tue, 18 Jan 2000, Sheldon Hearn wrote:
> On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote:
>
> > +.if defined(WITH_RSA) && ${WITH_RSA} == YES
> > + /usr/bin/touch /etc/ssl/openssl_hasrsa
>
> Um, are you sure you want that hard path, /etc/ssl ? Shouldn't there be
> a ${DESTDIR} in the
Hi,
I checked the file RELNOTES.TXT for the latest snapshot
(4.0-2118-CURRENT). The following network cards from Intel are listed:
Intel EtherExpress 16
Intel EtherExpress Pro/10
Intel EtherExpress Pro/100B PCI
< Won't people get into legal trouble (technically) if they build the
> wrong version?
Depends on who they work for. Some people may work for organizations
which have licensing agreements in place to permit them to use RSA.
(This includes about 10,000 people who happen to work for the patent
ass
Hi is any oone else having trouble doing a make world? Completed reomved
/usr/obj and usr/src/ cvs'd twice and got the following error: (trimmed)
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:96:
print "FIX(numcodes)" > "codeftr"
awk:
/usr/src/
Hi,
If we are changing the meaning of "USA_RESIDENT", could we replace it by
something else completely. I know that the USA are the center of the
universe ;-), but...
It seems to me that a things progress, the crypto regulation gets more
complicated everyday. Why not have a "CRYPTO_COUNTRY" vari
< said:
> This is definitely a bad idea; IMHO we should only do this when the
> resource is actually activated (and obviously free it when deactivated).
Absolutely! As I keep trying to explain to people, that's why there
*is* a separate activate function (or one of the reasons, anyway).
-GAWo
On Tue, Jan 18, 2000 at 11:00:43AM -0500, Ben Rosengart wrote:
> On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
>
> > --binary-files='text' treats binary files as text
> > (equivalent to -a or --text).
>
> So "-a" now does the opposite of what it used to do?
>
Not exactly.
A stock grep 2.0
> It seems that texinfo is compiled as cross-tools for buildworld.
> But, is it really needed when -DNOINFO has been specified?
You stole my plan! :-)
Once the dust settles and the current crop of `make world' problems are
fixed, I want to commit a simular patch as I don't care for info files
an
On Tue, 18 Jan 2000, Frank Mayhar wrote:
> Interestingly, I rebuilt world with the latest pccardd changes and,
> suddenly, the 589D started working perfectly. Unfortunately, the
> 574BT doesn't work at all now. It appears to configure properly, but
> it doesn't transmit or receive.
Ok, I need t
On 18/01 12:05, Pascal Hofstee wrote:
> Yes .. i have noticed several occasions of mergemaster pointing out to me
> that a file from /usr/src/etc didn't exist in my own /etc tree yet.
And if you do a
mergemaster -v
it will tell you what exists in /etc, but not in /usr/src/etc. Very handy.
On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
> On Tue, Jan 18, 2000 at 11:47:27PM +1100, Bruce Evans wrote:
> > On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
> >
> How's that not a problem? The current Makefile.inc1 is written so,
> that bootstrap-tools are built with:
>
> BMAKE=${BMAKEENV} ${MAKE}
On Tue, Jan 18, 2000 at 11:47:27PM +1100, Bruce Evans wrote:
> On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
>
> > On Tue, Jan 18, 2000 at 12:31:18PM +0200, Sheldon Hearn wrote:
> > >
> > >
> > > On Tue, 18 Jan 2000 19:14:19 +0900, Munehiro Matsuda wrote:
> > >
> > > > It seems that texinfo is co
On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste <[EMAIL PROTECTED]>
wrote:
> I can say that I tried building the 3.9.17 with both official compiler
> in -current and also with gcc-devel, both built fine but didn't install.
> Seems like my fault, nothing else. Time to try again.
It seem
1 - 100 of 124 matches
Mail list logo
