On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
> atapci0: port 0xe000-0xe00f at device 7.1 on
> pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> ...
> isic0: Error allocating io at 0x160 for Teles S0/16.3!
>
> While I was able to use the Teles again by changing i
Jose Gabriel Marcelino wrote:
> This obviously conflicts with the secondary IDE controller which lies at
> 0x170, however this has not been a problem till this day and no driver
> complained about this. Now, with the newer kernel I get this:
>
> atapci0: port 0xe000-0xe00f at device 7.1 on
> pc
Chris> It doesn't need kernel support to build with ipv6 support.
Chris> Trying to use the ipv6 support without it in the kernel is the
Chris> only problem.
dgilbert> Well... ruby refuses to build with IPv6 if it's not enabled and mtr
dgilbert> dies with a "cannot open socket".
dgilbert> In esce
>On -current my VGA card is being used as a CGA card. It is correctly
>recognized as a VGA:
>
>vga-pci0: mem 0xf800-0xfbff irq 11 at d
>evice 15.0 on pci0
The above message simply means that a PCI card classified as VGA is
found. This does not necessarily means that the card can be use
Hello,
I dont't know if this is some HW problem, but after the last update system
became unbootable if I load modules by /boot/loader rather them kldload.
> sos 2000/02/18 12:57:33 PST
>
> Modified files:
> sys/alpha/includemd_var.h
> sys/alpha/pcipcibus.c
>
Doug Rabson wrote:
> > atapci0: port 0xe000-0xe00f at device 7.1 on
> > pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: at 0x170 irq 15 on atapci0
> > ...
> > isic0: Error allocating io at 0x160 for Teles S0/16.3!
> >
> > While I was able to use the Teles again by changing it's default IO p
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
> Doug Rabson wrote:
>
> > > atapci0: port 0xe000-0xe00f at device 7.1 on
> > > pci0
> > > ata0: at 0x1f0 irq 14 on atapci0
> > > ata1: at 0x170 irq 15 on atapci0
> > > ...
> > > isic0: Error allocating io at 0x160 for Teles S0/16.3!
> > >
> > > W
Say I do something like
find /cdrom
is the HD light supposed to be blinking as if the hard drives are being
accessed? I did the above command (note that it doesn't involve finding
files on the hard drives at all), and basically the HD light and the cdrom
activity light were flashing tog
> In FreeBSD's case, however, the conservative approach has landed us in
> "no man's land", where openssl can neither be wholly justified or
> dismissed, and I think that's a fundamental issue which needs to be
> addressed. I've seen Kris's arguments about how integrating openssl
> is a useful fi
Christian Weisgerber wrote:
>
> binary installation:
> - before: user needs to install openssl port
> - now:user needs to install openssl package
Where is the openssl package, and what it is called?
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
> Given that we can't import rsaref into FreeBSD and we can't depend on it
> as a port, that about rules out any options for installing from
> sysinstall. The remaining possibility is what we have now, namely manual
> installation of the package post-installation, which is documented in the
> hand
In message <[EMAIL PROTECTED]>, "Jordan K. Hubbard" writes:
>Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out
>at this point. The situation with RSA makes this far more problematic
>than I think anyone first thought, and I've seen a lot of breakage so
>far for what appears t
On Sun, 20 Feb 2000, Jordan K. Hubbard wrote:
> Well, I guess I'll be less frantic about this when I see the ports
> infrastructure working properly with this - having openssh fail
> came as a rude shock. :)
See Jim Bloom's patch of earlier this evening.
> I'm also assuming that if I have opens
> On Sun, 20 Feb 2000, Jordan K. Hubbard wrote:
>
> > Well, I guess I'll be less frantic about this when I see the ports
> > infrastructure working properly with this - having openssh fail
> > came as a rude shock. :)
>
> See Jim Bloom's patch of earlier this evening.
Sorry, I'm the release eng
On Sun, 20 Feb 2000, Jordan K. Hubbard wrote:
> > See Jim Bloom's patch of earlier this evening.
>
> Sorry, I'm the release engineer - I only "see" something as fixed when
> it's actually committed to the tree and in my current build. :)
Well, I'm not allowed to commit to that file :) I also ha
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
>
>
> Hi,
>
> Apart from the more recently broken ATA stuff I started getting the
> following (cosmetic only really, but it leaves me wondering..) in kernels
> compiled around the 12th this month. This machine really just has one pci
> bus (th
Omachonu Ogali <[EMAIL PROTECTED]> writes:
> ===> lib/libcom_err/doc
> install-info --quiet --defsection="Programming & development tools." --defentry="*
>libcom_err: (com_err).A Common Error Description Library for UNIX."
>com_err.info /usr/share/info/dir
> install-info: unrecognize
> On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
>
> > Doug Rabson wrote:
> >
> > > > atapci0: port 0xe000-0xe00f at device 7.1 on
> > > > pci0
> > > > ata0: at 0x1f0 irq 14 on atapci0
> > > > ata1: at 0x170 irq 15 on atapci0
> > > > ...
> > > > isic0: Error allocating io at 0x160 for Teles S0/
It seems Donn Miller wrote:
> Say I do something like
>
> find /cdrom
>
> is the HD light supposed to be blinking as if the hard drives are being
> accessed? I did the above command (note that it doesn't involve finding
> files on the hard drives at all), and basically the HD light and th
> > So you are saying that what we really have here is a simple i/o conflict
> > and possibly the ISDN card can be reconfigured to use a non-conflicting
> > address? If so, then everything is working correctly and the resource
> > manager has pointed a possible hardware problem :-).
>
> So it wo
> > > > atapci0: port 0xe000-0xe00f at device 7.1 on
> > > > pci0
> > > > ata0: at 0x1f0 irq 14 on atapci0
> > > > ata1: at 0x170 irq 15 on atapci0
> > > > ...
> > > > isic0: Error allocating io at 0x160 for Teles S0/16.3!
> > > >
> > > > While I was able to use the Teles again by changing it's
Brian Somers wrote:
> > So you are saying that what we really have here is a simple i/o conflict
> > and possibly the ISDN card can be reconfigured to use a non-conflicting
> > address? If so, then everything is working correctly and the resource
> > manager has pointed a possible hardware proble
On Fri, 18 Feb 2000, Ruslan Ermilov wrote:
> Hi!
>
> Why then it works on 3.4-STABLE (booting without loader(8) and
> having kvm(3) programs like pstat(8) and top(1) working).
> What makes a difference here?
RCS file: /home/ncvs/src/lib/libkvm/kvm_file.c,v
Working file: kvm_file.c
head: 1.10
..
Kai Großjohann wrote:
> Omachonu Ogali <[EMAIL PROTECTED]> writes:
>
>> ===> lib/libcom_err/doc
>> install-info --quiet --defsection="Programming & development tools."
>--defentry="* libcom_err: (com_err).A Common Error Description Library for
>UNIX." com_err.info /usr/share/info/di
> The BIOS setup menu usually has an entry to specify the type of the
> installed video card. If this item is set to CGA, the BIOS and the
> vga driver will initialize the card, even if it is a VGA, as the CGA
> card. Are you sure that this doesn't happen to be the case with
> your system?
My B
Kris Kennaway wrote:
>
> Except it's not just this release, it's "for the life of the 4.x branch"
> given the rules of what should get put into -stable. I really don't want
> to have to wait another year or more for 5.0-RELEASE before we can start
> making use of crypto in the recommended version
> In case there is is already an IDE controller allocated at 0x170 and a
> Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so.
This is a PnP card, right? So what does the PnP info say about needed
memory ranges?
> So where is the bug ?
Depends. If the drivers allocation is co
>From the keyboard of Martin Husemann:
> > In case there is is already an IDE controller allocated at 0x170 and a
> > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so.
>
> This is a PnP card, right?
No.
hellmuth
--
Hellmuth MichaelisTel
Today Kris Kennaway wrote:
> > I'm also assuming that if I have openssl installed via the base system
> > and USA_RESIDENT=YES in /etc/make.conf, going off to make openssh will
> > cause it to build rsaref on my behalf just like it used to? I'd hate
> > to have something become manual which was
> Depends. If the drivers allocation is coherent with the vendors description
> in the PnP configuration data, it's a newbus error (it shouldn't try to
> allocate the card there in the first place). If the PnP info differs from
> the drivers view of the card, it's either the vendors fault for pro
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
>
> A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC
> chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b,
> the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73.
But in the case of the teles16.3, it does
> But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in
> the HSCX or ISAC: the ASIC on the card has 'folded' the address space so
> that the fifo appears at an address 3 bytes after the last register (0x3e
> with the current scheme - see tels0163_read_fifo()).
Ah, then the dri
Andrew Gordon wrote:
> On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
> >
> > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC
> > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b,
> > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73.
>
> But i
At 17:19 -0700 19/2/00, Kenneth D. Merry wrote:
>On Sat, Feb 19, 2000 at 19:28:23 +, Bob Bishop wrote:
>> Hi,
>>
>> cdrecord, freshly built on last night's -current:
>
>Freshly built? That's cdrecord 1.8a21, which is several versions old. I
>think you should be using cdrecord 1.8 release fro
First, no I haven't been reading the big ATA problem thread. I should be
*ponders switching to digest list ;) *
This has been the case over three buildworlds in the past three days.
Is it a general problem that audio CD's fail to play in a dvd drive (or
cd drive, for that matter ;) via cdcontro
On Sat, Feb 19, 2000 at 11:41:22PM -0800, Kris Kennaway wrote:
> Given that we can't import rsaref into FreeBSD and we can't depend on it
> as a port, that about rules out any options for installing from
> sysinstall.
How does OpenBSD deal with it? Why is it so easy for them?
--
-- David([
On Sun, Feb 20, 2000 at 01:12:48PM -0800, David O'Brien wrote:
> How does OpenBSD deal with it? Why is it so easy for them?
Their main repositories lie in Canada and not the United States of
Anti-encryption? :-)
--
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+
On Sun, Feb 20, 2000 at 12:52:49AM -0800, Kris Kennaway wrote:
> No, because openssl is compiled differently if rsaref is present or not -
> it's not just a matter of dropping in librsaref.so (we can't always just
> build the version with RSAref stubs because it references symbols in
> librsaref a
On Sat, Feb 19, 2000 at 07:46:50PM -0800, Kris Kennaway wrote:
>
> Having _a_ general-purpose cryptography toolkit in the base system allows
> us to add in all sorts of cool things to FreeBSD (https support for fetch,
> openssh, random cryptographic enhancements elsewhere).
Which OpenBSD has don
> How does OpenBSD deal with it? Why is it so easy for them?
It isn't. Go look for yourself.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, Feb 19, 2000 at 08:27:48PM -0800, Kris Kennaway wrote:
> > How does OpenBSD do it? Cant we do what they do?
>
> They do a worse job than us is the short answer.
That is not a very helpful answer. Care to provide details?
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail
On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote:
>
> 1. They're in Canada
What does that buy them? They have the same restrictions on rsaref since
it originated from the USA.
> 2. What they do appears to be kind of icky, e.g. it requires more
>"hand work" than I think the
> On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote:
> >
> > 1. They're in Canada
>
> What does that buy them? They have the same restrictions on rsaref since
> it originated from the USA.
I don't believe they're under the same legal gun when it comes to the
patent issues. Thi
On Sat, Feb 19, 2000 at 06:19:17PM +0900, Yoshinobu Inoue wrote:
> EPSV is just enhanced version of PASV, and I think it needs to
> check same kind of errors. Maybe same check as getreply() in
> ftp/ftp.c will be necessary. About the spec, please check RFC2428.
>
> But the problem is that the err
On Fri, Feb 18, 2000 at 08:31:06PM -0800, Matthew Dillon wrote:
>
> I wound up having to rm -rf /compat/linux and /usr/compat/linux and
> then doing the make install, which worked. It created /usr/compat/linux
> and didn't seem to care that no /compat/linux existed. However,
> o
On Fri, Feb 18, 2000 at 01:18:48PM -0800, Kris Kennaway wrote:
> > Nope -- my make was in the top level /usr/src tree, in the form of ``make
> > -j 3 all''.
>
> You need to make depend first..perhaps the makefile could be improved
You should not need to. If it is required you have a broken Make
> The /compat symlink should just die. compat bits should not be on the
> root partition, so why are we pretending? /usr/compat should be the only
> supported place. Peroid.
You miss the point entirely. Compat bits aren't intended for the root
partition, they're intended for wherever you happ
On Sun, Feb 20, 2000 at 01:37:01PM -0800, Andrey A. Chernov wrote:
> I don't look at the code deeply yet, but it looks from
> your words that EPSV command must be issued _only_ if ftp called
> as pftp or 'passive' command given or FTP_PASIVE_MODE
> env. variable is set and must be not issued in no
On Sun, Feb 20, 2000 at 01:32:22PM -0800, Jordan K. Hubbard wrote:
> > > 1. They're in Canada
> >
> > What does that buy them? They have the same restrictions on rsaref since
> > it originated from the USA.
>
> I don't believe they're under the same legal gun when it comes to the
> patent issue
On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote:
> P.S. /usr/local/etc/shells anyone? :)
I second this. As there becomes more ports around, this would simplify
the job of ports since we would now modify a ${PREFIX}-based file
instead of /etc/shells.
--
Will Andrews <[EMAIL PRO
On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote:
>
> You miss the point entirely.
Possibly.
> For others that's anywhere but since /usr is a comparatively small,
> read-only partition which they share amongst multiple boxes and they
> want the compat stuff to go in /usr/local/
Jordan, please approve this patch.
It seems not good to have FTP_PASSIVE_MODE On as default while ftp program
itself have it Off by default. Lets either change ftp program defaults to
Passive On or login.conf defaults to Passive Off. I prefer second variant:
--- login.conf.bak Wed Sep 15 04
On Sun, 20 Feb 2000, David O'Brien wrote:
> On Fri, Feb 18, 2000 at 01:18:48PM -0800, Kris Kennaway wrote:
> > > Nope -- my make was in the top level /usr/src tree, in the form of ``make
> > > -j 3 all''.
> >
> > You need to make depend first..perhaps the makefile could be improved
>
> You shou
On Sun, 20 Feb 2000, David O'Brien wrote:
> > 2. What they do appears to be kind of icky, e.g. it requires more
> >"hand work" than I think the average FreeBSD user would be willing
> >to accept
>
> By handwork you man building, or installing? When I put OpenBSD 2.6 on
> my sparc5, I di
On Sun, 20 Feb 2000, David O'Brien wrote:
> On Sun, Feb 20, 2000 at 12:52:49AM -0800, Kris Kennaway wrote:
> > No, because openssl is compiled differently if rsaref is present or not -
> > it's not just a matter of dropping in librsaref.so (we can't always just
> > build the version with RSAref s
On Sun, Feb 20, 2000 at 02:14:21PM -0800, Kris Kennaway wrote:
> stand by my comment that 'make depend' is needed generally, though -
> things often fail elsewhere in the tree (e.g. gcc, perl)
Yes, give a log. Look at all the gunk in
src/gnu/usr.bin/cc/cc_tools/Makefile to keep a `make depend' f
On Mon, Feb 21, 2000 at 01:14:04AM +0300, Andrey A. Chernov wrote:
>
> It seems not good to have FTP_PASSIVE_MODE On as default while ftp program
> itself have it Off by default.
Agreed.
> Lets either change ftp program defaults to Passive On or login.conf
/usr/bin/ftp should default to Passiv
On Sun, 20 Feb 2000, Jonathan Smith wrote:
> Is it a general problem that audio CD's fail to play in a dvd drive (or
> cd drive, for that matter ;) via cdcontrol as of the past few days and/or
> dvd's not being accessed properly, ie. with DeCSS? Cdcontrol would not
> eject, but would close until
> Jordan, please approve this patch.
>
> It seems not good to have FTP_PASSIVE_MODE On as default while ftp program
> itself have it Off by default. Lets either change ftp program defaults to
> Passive On or login.conf defaults to Passive Off. I prefer second variant:
Um, the point of turning FT
On Sun, Feb 20, 2000 at 01:56:06PM -0800, Andrey A. Chernov wrote:
> Sorry, this place (EPSV == PASV) is right excepting proxy mode is not covered by
> EPSV (see PASV usage for proxy).
Another error is that
static int try_epsv = 1;
is set globally for all connections made by ftp
instead
[ Sent to -current and -ports, followups set to -current ]
Here's another trivial patch that people might like to comment on before I
commit it. I'm doing more and more FreeBSD installs recently at various
client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of
those standard
At 10:17 PM 2/19/00 -0800, Kris Kennaway wrote:
>This doesn't help. The RSA source not being there isn't the problem, the
>problem is that there are two different binary versions depending on how
>you build it (with rsaref or not). Source code builds aren't a problem,
>they already work fine, it's
On Sun, 20 Feb 2000 09:15:41 GMT, Nik Clayton wrote:
> Here's another trivial patch that people might like to comment on before I
> commit it. I'm doing more and more FreeBSD installs recently at various
> client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.conf is just one of
> those stan
I used to have an Adaptec 2940UW in this machine, but I now have a:
sym0: <895> port 0xd800-0xd8ff mem 0xefffe000-0xefffefff,0xef00-0xefff irq 11
at device 13.0 on pci0
sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking
This attaches:
sa0 at sym0 bus 0 target 3 lun 0
sa0: Removab
Please review this patch. It fix all problems I mention.
--- ftp.c.old Sun Feb 20 23:30:29 2000
+++ ftp.c Mon Feb 21 02:21:01 2000
@@ -1173,8 +1173,6 @@
#endif
if (passivemode) {
- static int try_epsv = 1;
-
data_addr = myctladdr;
d
On Sun, 20 Feb 2000 14:31:43 PST, Kris Kennaway wrote:
> I've not been able to play audio CDs ever since switching to the new ATA
> drivers. Soren tells me there are two different ways to encode commands to
> the drive, and no easy way to tell which one the drive expects :-(
Welcome to it. Th
David O'Brien <[EMAIL PROTECTED]> wrote:
> How does OpenBSD deal with it? Why is it so easy for them?
0. RSA situation
In the USA, the RSA algorithm(!) is patented by RSA Inc. It doesn't
matter where the actual code is from, any use of RSA needs permission
by the patent holder. RSA Inc. provid
> "Christian" == Christian Weisgerber <[EMAIL PROTECTED]> writes:
Christian> Commercial users need to get
Christian> an explicit license from RSA Inc., which from what I
Christian> hear you can't get in practice.
Correct. The only option for commercial software (in the US) is to
On 20-Feb-00 kibbet wrote:
> Hey all,
>
> I got this error, and the 2205 entry in UPDATING didn't seem to cover
> enough for me, I was comming from a clean bin install of 3.2.
>
> UPDATING - 2205 entry;
>
> make buildworld
> make installworld Thi
David O'Brien <[EMAIL PROTECTED]> wrote:
> While I don't know is how OpenBSD builds the two sets of bits, I do know
> how easy it was for me as a user to install 2.6 and get a RSA enabled
> crypto lib.
Alas, if I understand Jordan correctly, he objects exactly to this
additional installation st
Jeffrey J. Mountin <[EMAIL PROTECTED]> wrote:
> My big question is - Do we really want to force a 'make world' on the those
> that want RSA support in openssl?
We don't want to and WE DON'T DO.
> That would be ugly, when before it was simply the matter of building only
> two ports.
binary inst
> Thanks for the reply.
>
> > Date: Wed, 16 Feb 2000 01:16:25 -0700
> > From: Warner Losh <[EMAIL PROTECTED]>
> >
> > In message <[EMAIL PROTECTED]> Thomas Dean writes:
> > : What change to ppp did I miss?
> >
> > There were some quoting and comment recognition changes at one
> > point...
> >
Vladimir Kushnir wrote:
>
> Hello,
> I dont't know if this is some HW problem, but after the last update system
> became unbootable if I load modules by /boot/loader rather them kldload.
That seems to be a bug -- I'd just load the modules via /etc/rc.conf for
now. Other people have reported p
Nik Clayton wrote:
>
> [ Sent to -current and -ports, followups set to -current ]
>
> Here's another trivial patch that people might like to comment on before I
> commit it. I'm doing more and more FreeBSD installs recently at various
> client sites, and adding "FETCH_BEFORE_ARGS=-p" to make.co
> 0. RSA situation
> [ a very nice point-for-point analysis of the situation elided ]
Christian,
Thank you for this summary; it helps a lot to have all the relevant
information presented in one place like this. Now we can begin
cutting to the heart of this matter, which I'll do in the form of
e
On 20-Feb-00 Ben Smithurst wrote:
> Kai Großjohann wrote:
>
>> Omachonu Ogali <[EMAIL PROTECTED]> writes:
>>
>>> ===> lib/libcom_err/doc
>>> install-info --quiet --defsection="Programming & development tools."
>--defentry="* libcom_err:
>>> (com_err).A Common Error Description Librar
unsubscribe freebsd-current
__
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
OK, I've dinked around with this some more and I think I might have at
least a partial solution to this whole mess (it still doesn't make
openssl actually useful to us, it just makes it less annoying :).
First, apply the following patch:
Index: Makefile
==
> Please review this patch. It fix all problems I mention.
Thanks, as far as I reviewed and actually confirmed, your
patches solved every problem. :-)
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
According to Yoshinobu Inoue:
> So now I think of following things.
>
> -Adopt the format below now, and never change it again
>before 4.0 release.
>
> addr%scope
We're getting close to the release so I'd go that way.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PR
On 2000-Feb-21 13:09:21 +1100, "Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote:
> Simply swapping one openssl library for another ...
> If we're going to go with that level of packaging granularity
>then openssl belongs as a package and should not be part of the
>bindist, end of story
This sounds
The latest commit of /sys/i386/i386/machdep.c breaks the kernel build:
cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../.
> Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out
> at this point. The situation with RSA makes this far more problematic
> than I think anyone first thought, and I've seen a lot of breakage so
> far for what appears to be comparatively little gain over what we had
> before
On Sun, 20 Feb 2000 23:48:01 -0500,
Ray Kohler <[EMAIL PROTECTED]> said:
Ray> cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls
Ray> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
Ray> -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
Ray> -nostdinc -
:On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote:
:> P.S. /usr/local/etc/shells anyone? :)
:
:I second this. As there becomes more ports around, this would simplify
:the job of ports since we would now modify a ${PREFIX}-based file
:instead of /etc/shells.
:
:--
:Will Andrews <[
On Mon, Feb 21, 2000 at 02:00:42PM +0900, Seigo Tanimura wrote:
> On Sun, 20 Feb 2000 23:48:01 -0500,
> Ray Kohler <[EMAIL PROTECTED]> said:
>
> Ray> cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls
> Ray> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> Ray> -Wpo
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: I believe setting MEM_ASSIGNED is the proper fix and attached is the
: one line patch.
This looks goo.d
: PS: anybody know why cardaddr is set to 16k?
No. I have no clue Maybe a kludge left over from an old card?
Warner
To Unsu
* From: Nik Clayton <[EMAIL PROTECTED]>
* [ Sent to -current and -ports, followups set to -current ]
(Your Followups-to: didn't survive someone's MTA, so replying to
-current manually.)
* Here's another trivial patch that people might like to comment on before I
* commit it. I'm doing more
On Sun, 20 Feb 2000, David O'Brien wrote:
> The /compat symlink should just die. compat bits should not be on the
> root partition, so why are we pretending? /usr/compat should be the only
> supported place. Peroid.
/compat is often a symlink or mount point, and "/" is a better place for
such
On Sun, 20 Feb 2000, David O'Brien wrote:
> On Sun, Feb 20, 2000 at 02:14:21PM -0800, Kris Kennaway wrote:
> > stand by my comment that 'make depend' is needed generally, though -
> > things often fail elsewhere in the tree (e.g. gcc, perl)
Only in broken makefiles. I once fixed all makefiles u
On Sun, 20 Feb 2000, Jeffrey J. Mountin wrote:
> Considering that building and installing world takes quite a while, it
> would be nice to have a simple way, so wonder if a simple 'make all
> install' in secure/usr.bin/openssl will do it for everything that depends
> on openssl. Chapter 6.5 of t
On 21 Feb 00, at 15:23, Daniel C. Sobral wrote:
> Christian Weisgerber wrote:
> >
> > binary installation:
> > - before: user needs to install openssl port
> > - now:user needs to install openssl package
>
> Where is the openssl package, and what it is called?
security/openssl
--
Dan Langi
92 matches
Mail list logo
