Re: sendmail 8.10
On Sun, 12 Mar 2000, Chris Knight wrote: > Are there any plans by the FreeBSD team to add sendmail 8.10 to > FreeBSD-4.0, or is the sendmail release too late for this to happen? > TIA for any info. I would say with release being a couple of days away it's too late. We've already delayed enough already, IMO. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
On Sat, 11 Mar 2000, Kris Kennaway wrote:
> the fix isn't immediately obvious to me - make world doesn't seem to run a
> full 'make includes' prior to doing the perl thing (it just does 'make
Well, that was probably the stupidest thing I've said all day (I say the
fix isn't obvious and then proceed to give a fix). i.e. explicitly running
'${MAKE} -f Makefile.inc1 includes' in the reinstall: target of
Makefile.inc1 would solve the problem, but there's probably a better way.
Kris
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
sendmail 8.10
Howdy, Are there any plans by the FreeBSD team to add sendmail 8.10 to FreeBSD-4.0, or is the sendmail release too late for this to happen? TIA for any info. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
On Fri, 10 Mar 2000, John Polstra wrote: > This is still broken. I ran into it when upgrading a Feb. 29 -current > system to today's -current. I didn't use make -j and I didn't take > any shortcuts. Okay, the problem is indeed caused by the fact that there's a dangling symlink from des.h to openssl/des.h, which at the point of perlifying the headers hasn't yet been installed in /usr/include (along with a lot of other headers). It only affects upgrades from within a certain window, and the fix isn't immediately obvious to me - make world doesn't seem to run a full 'make includes' prior to doing the perl thing (it just does 'make install' in include/), and the openssl headers are only installed later in the installworld. Running a "make -k installworld; make installworld", or "make includes; make installworld" will fix this - perhaps we can look at it again after release. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OpenSSH/RSAREF patch to detect long keys
RSAREF can't handle RSA keys longer than 1024 bits (and we're not allowed
to fix it so that it can, by the terms of the RSAREF license). This is a
problem for OpenSSH, because it can't be used to interoperate with
servers (or clients) which use long keys. Currently it gives a very
non-helpful error message:
rsa_private_encrypt() failed.
The attached patch detects when it is failing because it's being used with
RSAREF and a long key, and returns the error:
rsa_private_encrypt() failed: RSAREF cannot handle keys larger than 1024 bits.
It does this by adding a RSA_libversion() function to the librsausa and
librsaintl libraries so libcrypto users can work out which version they
are actually using (I tried to do this with just an "int RSA_libversion",
but I was having problems getting the symbol to be found at link time).
I've tested it through a make world and with sshd servers that have large
and small keys - I haven't tested it for international OpenSSH users. The
patch takes the openssh/rsa.c file off the vendor branch. There's also a
new file added, crypto/openssl/crypto/rsa/rsa_intlstubs.c.
I'd like to get this committed for 4.0 if I have some more positive
feedback from people.
Kris
Index: crypto/openssh/rsa.c
===
RCS file: /home/ncvs/src/crypto/openssh/rsa.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 rsa.c
--- crypto/openssh/rsa.c2000/02/24 14:29:45 1.1.1.1
+++ crypto/openssh/rsa.c2000/03/12 03:19:52
@@ -125,7 +125,10 @@
if ((len = RSA_public_encrypt(ilen, inbuf, outbuf, key,
RSA_PKCS1_PADDING)) <= 0)
- fatal("rsa_public_encrypt() failed");
+ if (BN_num_bits(key->n) > 1024 && RSA_libversion() == RSALIB_RSAREF)
+ fatal("rsa_private_encrypt() failed: RSAREF cannot handle keys larger
+than 1024 bits.");
+ else
+ fatal("rsa_private_encrypt() failed.");
BN_bin2bn(outbuf, len, out);
@@ -150,7 +153,10 @@
if ((len = RSA_private_decrypt(ilen, inbuf, outbuf, key,
RSA_PKCS1_PADDING)) <= 0)
- fatal("rsa_private_decrypt() failed");
+ if (BN_num_bits(key->n) > 1024 && RSA_libversion() == RSALIB_RSAREF)
+ fatal("rsa_private_decrypt() failed: RSAREF cannot handle keys larger
+than 1024 bits.");
+ else
+ fatal("rsa_private_decrypt() failed.");
BN_bin2bn(outbuf, len, out);
Index: crypto/openssl/crypto/rsa/rsa.h
===
RCS file: /home/ncvs/src/crypto/openssl/crypto/rsa/rsa.h,v
retrieving revision 1.2
diff -u -r1.2 rsa.h
--- crypto/openssl/crypto/rsa/rsa.h 2000/02/26 13:13:02 1.2
+++ crypto/openssl/crypto/rsa/rsa.h 2000/03/12 03:02:07
@@ -244,6 +244,8 @@
int RSA_set_ex_data(RSA *r,int idx,char *arg);
char *RSA_get_ex_data(RSA *r, int idx);
+int RSA_libversion();
+
/* BEGIN ERROR CODES */
/* The following lines are auto generated by the script mkerr.pl. Any changes
* made after this point may be overwritten when the script is next run.
@@ -307,6 +309,9 @@
#define RSA_R_UNKNOWN_ALGORITHM_TYPE117
#define RSA_R_UNKNOWN_PADDING_TYPE 118
#define RSA_R_WRONG_SIGNATURE_LENGTH119
+
+#define RSALIB_OPENSSL 1
+#define RSALIB_RSAREF 2
#ifdef __cplusplus
}
Index: crypto/openssl/crypto/rsa/rsa_stubs.c
===
RCS file: /home/ncvs/src/crypto/openssl/crypto/rsa/rsa_stubs.c,v
retrieving revision 1.4
diff -u -r1.4 rsa_stubs.c
--- crypto/openssl/crypto/rsa/rsa_stubs.c 2000/03/02 06:21:02 1.4
+++ crypto/openssl/crypto/rsa/rsa_stubs.c 2000/03/12 03:03:13
@@ -87,6 +87,16 @@
}
__weak_reference(ERR_load_RSA_strings_stub, ERR_load_RSA_strings);
+int
+RSA_libversion_stub(void)
+{
+static void (*sym)(void);
+
+if (sym || (sym = getsym("RSA_libversion")))
+ sym();
+}
+__weak_reference(RSA_libversion_stub, RSA_libversion);
+
#else /* !PIC */
/* Sigh, just get your own libs, ld(1) doesn't deal with weaks here */
Index: crypto/openssl/rsaref/rsaref_stubs.c
===
RCS file: /home/ncvs/src/crypto/openssl/rsaref/rsaref_stubs.c,v
retrieving revision 1.5
diff -u -r1.5 rsaref_stubs.c
--- crypto/openssl/rsaref/rsaref_stubs.c2000/03/02 06:21:02 1.5
+++ crypto/openssl/rsaref/rsaref_stubs.c2000/03/12 03:10:46
@@ -40,6 +40,7 @@
#ifndef NO_RSA
#include
+#include
#define VERBOSE_STUBS /* undef if you don't want missing rsaref reported */
@@ -164,6 +165,12 @@
return 0;
}
__weak_reference(R_RandomUpdate_stub, R_RandomUpdate);
+
+int
+RSA_libversion()
+{
+ return RSALIB_RSAREF;
+}
#else /* !PIC */
Index: secure//lib/librsaintl/Makefile
===
RCS file: /home/ncvs/src/
Re: XFree86-4 can't start
On Sun, Mar 12, 2000 at 02:30:46AM +, Cliff Rowley wrote: > Two things, I know it's silly, but I might as well ask: > > 1) Did you install XFree86 4 over an old XFree86? If so, did you ask it > specifically to make and install aout libraries (re: __Xglobal_lock) - the > aout libraries arent built by default. Yes - I installed it over an existing and running 3.9.17. But this itself was installed over an older version so the aout libs I was using might be older. Yes - I build with aout libs - and I checked that they are installed. I asume if I had keeped my old it would still working... > 2) Are you using a completely new XFree86 configuration file? The > configuration has changed since 3.x Yes - The configuration has even changed from 3.9.17 slightly :( > I realise they are silly points, but easy mistakes to make nonetheless. Of course. But the mouse_dev.o was definitely not build - the directory even contained no Makefile. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 mouse?
Ted Sikora wrote: > > My problem is a little different. XFree86-4.0 loads > fine looks great but the mouse does not work. There > are no errors. I tried PS/2 , serial, etc same with > them all. The pointer appears then moves to the upper > right and dissappers. I tried moving it...Mouse1, etc. > but nothing Any ideas? > > Note:XF86Config works well but > XFree86 -configure gives a bad config > Got it working. The new config takes a bit getting used to. The default xf86config generated script puts all devices at 1 as in "Mouse 1". When I changed the mouse to "0 "and set it at auto it worked. All others I left at "1". XFree86 -configure sets all at "0" but leaves a bit of info out rendering it useless without editing. It leaves the screen modes out. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
John Polstra wrote: > > In article <[EMAIL PROTECTED]>, > Paul Richards <[EMAIL PROTECTED]> wrote: > > > > I think we need a MAX_UID and a MAX_GID to perform checks like this. > > Anyone got any objections to adding them to /usr/include/limits.h ? > > They must not go into . That header file is defined by > the ANSI/ISO C standard. The standard doesn't permit polluting the > namespace with extra stuff. Umm, ok. I don't think our limits.h actually has anything in it that meets the ANSI/ISO standard, every line is ifdef'd :-) Where would be a better place for constants like this? Are expressions like ((uid_t)0-1) portable/safe ? Maybe that's a better way of approaching this. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM deltas
On Sat, 11 Mar 2000 [EMAIL PROTECTED] wrote: > The latest CTM delta for -CURRENT on ftp.freebsd.org is 4257 (March > 6). Because all of the mirrors for CTM are in countries other than the US, > would there be any differences between the deltas they have and the ones > that ftp.freebsd.org should have? (I don't understand this crypto thing > all too well.) Also, is there some reason that CTM deltas aren't on the > FTP servers? The deltas stop at 4257 on one of the mirrors in Taiwan too, > and I can't contact either of the other two Taiwanese mirrors or the South > African mirror listed on http://www.freebsd.org/handbook/mirrors-ctm.html > (the one in Germany is fine, and has all the deltas through 4265 at this > point). So many points to address here ... 1) please, bring ctm problems to the attention of [EMAIL PROTECTED] If you think they are general in nature, you can use ctm-announce, which is a public list. Don't use current, they're mostly uninterested in CTM stuff. 2) Archive site has changed, try ftp.freesoftware.com. You *should* have read that on logging into ftp.freebsd.org. 3) I don't see the numbers you see. On current, the latest delta is cvs-cur.6161.gz. I checked the src-3 one also, in case you maybe meant that, it's also a long way off of 4257. I think you must have your numbers messed up; please recheck them. 4) As long as you're not talking about Mark Murray's CTM of int'l crypto, there's only *one* source of ctm deltas, and I'm it. They are all now signed with GNU's gpg, and any you get are identically the same. Doesn't matter where you pick them up from. Most folks get them from the mailing lists from [EMAIL PROTECTED] 5) Just checked with the new ftp site; ftp.freesoftware.com isn't correctly mirroring ctm deltas. The other sites are OK. I'll get right on that, thanks for pointing me at it. The last ctm delta that ftp.freesoftware.com has is a week or two old: cvs-cur.6147.gz. Any more questions, send them to [EMAIL PROTECTED], not this list. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
I haven't tried xfce, but I had some problems running Enlightenment 16.3,
all related to shared memory. I disabled shared pixmaps in my Imlib
configuration and that got rid of the random crashing, but is again not a
very optimal solution :) I'm guessing it's a problem with the current GTK
version and X4.
Try starting xfce with "--no-xshm" and/or "--no-shm" and see if the
problem clears up.
Michael L. Imamura
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: [EMAIL PROTECTED]
On Sat, 11 Mar 2000, Doug Barton wrote:
> "Michael L. Imamura" wrote:
> >
> > I was able to get it working through a small patch to the
> > scripts/configure file. Probably not the most optimal solution, but it
> > works until the port is updated:
> >
> > --- configure Fri Mar 10 19:20:34 2000
> > +++ configure.2 Sat Mar 11 18:19:55 2000
> > @@ -197,7 +197,7 @@
> >echo "#define BuildXInputExt NO" >> $F
> > else
> >echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
> > -mutouch spaceorb wacom" >> $F
> > +mutouch spaceorb wacom mouse" >> $F
> > # XXX broken in 3.9.18
> > # if [ X${MACHINE} != X"alpha" ]; then
> > #echo "#define JoystickSupport YES" >> $F
>
> that got me to the point where I could start X, but xfce won't start. I
> get the following errors:
>
> Gdk-ERROR **: BadAccess (attempt to access private resource denied)
> serial 63 error_code 10 request_code 141 minor_code 1
> Gdk-ERROR **: BadShmSeg (invalid shared segment parameter)
> serial 64 error_code 143 request_code 141 minor_code 5
>
> I have shared memory compiled into my kernel, not sure what this could
> be if it's not an X 4 problem. xfwm does start though, odd.
>
> Doug
> --
> "Welcome to the desert of the real."
>
> - Laurence Fishburne as Morpheus, "The Matrix"
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
Hi, > So my IPv4 address is 24.113.130.83 that in IPv6 would be > 2002:240:113:130:083 ?? No, no, because IPv6 address is printed in hex format each 2bytes separated by collon, so the 1st 6bytes will be, 2002:1871:8253: and if printed in full 16bytes, 2002:1871:8253:-::::/64 is the prefixes you can use in your site. You can assign each prefixes, 2002:1871:8253:::, 2002:1871:8253:0001::, 2002:1871:8253:::,,,etc, onto your site's subnets. I just imported a man for "stf" interfaces into src/share/man/man4. So if you update it, then I think you can also refer "man 4 stf". Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAX_UID ?
In article <[EMAIL PROTECTED]>, Paul Richards <[EMAIL PROTECTED]> wrote: > > I think we need a MAX_UID and a MAX_GID to perform checks like this. > Anyone got any objections to adding them to /usr/include/limits.h ? They must not go into . That header file is defined by the ANSI/ISO C standard. The standard doesn't permit polluting the namespace with extra stuff. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CTM deltas
The latest CTM delta for -CURRENT on ftp.freebsd.org is 4257 (March 6). Because all of the mirrors for CTM are in countries other than the US, would there be any differences between the deltas they have and the ones that ftp.freebsd.org should have? (I don't understand this crypto thing all too well.) Also, is there some reason that CTM deltas aren't on the FTP servers? The deltas stop at 4257 on one of the mirrors in Taiwan too, and I can't contact either of the other two Taiwanese mirrors or the South African mirror listed on http://www.freebsd.org/handbook/mirrors-ctm.html (the one in Germany is fine, and has all the deltas through 4265 at this point). -Charon [EMAIL PROTECTED] http://www.seektruth.org/ "Duty-free Mega-mart, port Brasta, Alpha Centauri. Be like the twenty-second elephant with heated value in space - Bark!" -Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
"Michael L. Imamura" wrote:
>
> I was able to get it working through a small patch to the
> scripts/configure file. Probably not the most optimal solution, but it
> works until the port is updated:
>
> --- configure Fri Mar 10 19:20:34 2000
> +++ configure.2 Sat Mar 11 18:19:55 2000
> @@ -197,7 +197,7 @@
>echo "#define BuildXInputExt NO" >> $F
> else
>echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
> -mutouch spaceorb wacom" >> $F
> +mutouch spaceorb wacom mouse" >> $F
> # XXX broken in 3.9.18
> # if [ X${MACHINE} != X"alpha" ]; then
> #echo "#define JoystickSupport YES" >> $F
that got me to the point where I could start X, but xfce won't start. I
get the following errors:
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
serial 63 error_code 10 request_code 141 minor_code 1
Gdk-ERROR **: BadShmSeg (invalid shared segment parameter)
serial 64 error_code 143 request_code 141 minor_code 5
I have shared memory compiled into my kernel, not sure what this could
be if it's not an X 4 problem. xfwm does start though, odd.
Doug
--
"Welcome to the desert of the real."
- Laurence Fishburne as Morpheus, "The Matrix"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: RC3: problems with SSH
On Sat, 11 Mar 2000, Mathew Kanner wrote: > Finally a benefit to living in Canada! Anyway, I made the > port in /usr/ports/security/rsaref. My mistake was thinking that it > would look at my make.conf and get the right one. Sorry about that. You shouldn't need/use rsaref. Use the librsaintl port instead. > Also, just now when I look at the handbook, it appears to be chapter > 7.5. Grr, better update all the error messages :-( Thanks.. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with PnP (related to sio?)?
On Sat, Mar 11, 2000 at 06:44:32PM -0500, Eric D. Futch wrote: > Ugh... nevermind. Getting rid of the PNPBIOS option from the kernel > config got rid of all the unknown strangeness, Argh!, yes , that was it, PNPBIOS not ``device pnp0''. Close though, only 3 letters out :) -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:[EMAIL PROTECTED] http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with PnP (related to sio?)?
On Sat, Mar 11, 2000 at 05:27:33PM -0500, Eric D. Futch wrote: > # cat QUAKE | grep ^device | grep pnp > # > > Attached is my kernel config. > Hmm, I saw exactly the same thing when I moved to -current and I was certain that it was pnp0 that caused it, obviously not. Sorry for wasting your time. > -- > Eric Futch New York Connect.Net, Ltd. > [EMAIL PROTECTED] Technical Support Staff > http://www.nyct.net (212) 293-2620 > "Bringing New York The Internet Access It Deserves" > > > On Sat, 11 Mar 2000, Mark Ovens wrote: > > >Remove the line > > > >device pnp0 > > > >from the kernel config file and re-build. > > > > > > > > > >-- > > Microsoft: Where do you want to go today? > > Linux: Where do you want to go tomorrow? > > BSD: Are you guys coming, or what? > > -Poster at LinuxWorld 2000 > > > > FreeBSD - The Power To Serve http://www.freebsd.org > > My Webpage http://ukug.uk.freebsd.org/~mark/ > >mailto:[EMAIL PROTECTED] http://www.radan.com > > > machine i386 > #cpu I386_CPU > #cpu I486_CPU > #cpu I586_CPU > cpu I686_CPU > ident QuakeStation > maxusers 128 > > #makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols > > #options MATH_EMULATE#Support for x87 emulation > options INET#InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT#FFS usable as root device [keep this!] > #options MFS #Memory Filesystem > #options MD_ROOT #MD is a potential root device > options NFS #Network Filesystem > #options NFS_ROOT#NFS usable as root device, NFS required > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > #options CD9660_ROOT #CD-ROM usable as root, CD9660 required > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > #options SCSI_DELAY=15000#Delay (in ms) before probing SCSI > options UCONSOLE#Allow users to grab the console > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B#Posix P1003_1B real-time extentions > options _KPOSIX_PRIORITY_SCHEDULING > options ICMP_BANDLIM#Rate limit bad replies > > # To make an SMP kernel, the next two are needed > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > # Optionally these may need tweaked, (defaults shown): > #options NCPU=2 # number of CPUs > #options NBUS=4 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24# number of INTs > > deviceisa > deviceeisa > devicepci > > # Floppy drives > devicefdc0at isa? port IO_FD1 irq 6 drq 2 > devicefd0 at fdc0 drive 0 > devicefd1 at fdc0 drive 1 > > # ATA and ATAPI devices > deviceata0at isa? port IO_WD1 irq 14 > deviceata1at isa? port IO_WD2 irq 15 > deviceata > deviceatadisk # ATA disk drives > deviceatapicd # ATAPI CDROM drives > deviceatapifd # ATAPI floppy drives > deviceatapist # ATAPI tape drives > options ATA_STATIC_ID #Static device numbering > #options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices > > # SCSI Controllers > #device ahb # EISA AHA1742 family > deviceahc # AHA2940 and onboard AIC7xxx devices > #device amd # AMD 53C974 (Teckram DC-390(T)) > #device dpt # DPT Smartcache - See LINT for options! > #device isp # Qlogic family > #device ncr # NCR/Symbios Logic > #device sym # NCR/Symbios Logic (newer chipsets) > > #device adv0at isa? > #device adw > #device bt0 at isa? > #device aha0at isa? > #device
RC3: burncd/ata problems
I've got a new machine that I was testing FreeBSD out on. I had large problems with promise ata controller and fujistsu drives, a red-herring on the promise site was that they can't run ata66. Turns out that the last pci slot on the a-bit BE6-II doesn't work regularly when the on-board udma66 controller is enabled. Problem #1, the CD-R on this system doesn't recongize on the on board udma66 port but does on the promise PCI card. However, it shows up in the bios scan both ways. Problem #2, burncd failed with some (not verbatim) 'wrote -1 of n'. I'm remote from the machine now so I can't reproduce the error output that burncd did. The dmesg that follows has the some of the errors. I'll provide more info if needed. --Mat Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-2307-CURRENT #0: Wed Mar 8 00:14:33 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387f9ff real memory = 536870912 (524288K bytes) avail memory = 517152768 (505032K bytes) Preloaded elf kernel "kernel" at 0xc03be000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 9 chip1: port 0x5000-0x500f at device 7.3 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x9400-0x947f mem 0xe706-0xe706007f irq 9 at device 11.0 on pci0 xl0: Ethernet address: 00:50:da:d6:6a:d0 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: supplying EUI64: 00:50:da:ff:fe:d6:6a:d0 atapci1: port 0xa800-0xa83f,0xa400-0xa403,0xa000-0xa007,0x9c00-0x9c03,0x9800-0x9807 mem 0xe704-0xe705 irq 11 at device 13.0 on pci0 ata2: at 0x9800 on atapci1 ata3: at 0xa000 on atapci1 atapci2: port 0xbc00-0xbc3f,0xb800-0xb803,0xb400-0xb407,0xb000-0xb003,0xac00-0xac07 mem 0xe702-0xe703 irq 5 at device 15.0 on pci0 ata4: at 0xac00 on atapci2 ata5: at 0xb400 on atapci2 atapci3: port 0xd000-0xd03f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 mem 0xe700-0xe701 irq 10 at device 17.0 on pci0 ata6: at 0xc000 on atapci3 atapci4: port 0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 11 at device 19.0 on pci0 atapci5: port 0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 11 at device 19.1 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ata6-slave: ata_command: timeout waiting for intr ata6-slave: identify failed ad0: 26063MB [52953/16/63] at ata0-master using UDMA33 ad4: 26063MB [52953/16/63] at ata2-master using UDMA33 ad6: 26063MB [52953/16/63] at ata3-master using UDMA33 ad8: 26063MB [52953/16/63] at ata4-master using UDMA33 ad10: 26063MB [52953/16/63] at ata5-master using UDMA33 acd0: CDROM at ata1-master using PIO4 acd1: CD-RW at ata6-master using PIO4 Mounting root from ufs:/dev/ad0s1a vinum: loaded vinum: reading configuration from /dev/ad8s1e vinum: updating configuration from /dev/ad10s1e vinum: updating configuration from /dev/ad4s1e vinum: updating configuration from /dev/ad6s1e xl0: starting DAD for fe80:0001::0250:daff:fed6:6ad0 xl0: DAD complete for fe80:0001::0250:daff:fed6:6ad0 - no duplicates found cd9660: Joliet Extension acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: WRITE_BIG - ILLEGAL REQUEST asc=2c ascq=00 error=04 acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=0
Re: RC3: problems with SSH
[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: Kris Kennaway's message [Re: RC3: problems with SSH] as of Sat, Mar 1 1, 2000 at 05:10:07PM -0800 Organization: SOCS, McGill University, Montreal, CANADA Status: RO Content-Length: 815 Lines: 21 On Mar 11, Kris Kennaway wrote: > On Sat, 11 Mar 2000, Mathew Kanner wrote: > > > debug: Received server public key (1152 bits) and host key (1024 bits). > > > rsa_public_encrypt() failed > > Are you using rsaref? rsaref can't handle keys longer than 1024 bits and > we're not allowed to fix it so it can by the terms of the rsaref license. > Since you're in Canada, you don't need rsaref and should be using the > international version of openssl. See chapter 6.5 in the handbook for a > longer description of the state of play. Finally a benefit to living in Canada! Anyway, I made the port in /usr/ports/security/rsaref. My mistake was thinking that it would look at my make.conf and get the right one. Sorry about that. Also, just now when I look at the handbook, it appears to be chapter 7.5. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kdm display manager working anywhere with current?
"F. Heinrichmeyer" <[EMAIL PROTECTED]> writes: > I found no way to get kdm to work, it dumps core in a qt string find > routine. wdm works kind of (the window manager menu is buggy but > repairable). I had the same problem. Someone else reported here that it works if you compile kdm without optimisation, and that fixed it for me. Now why does it work for some folk and not others? Simon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
On Sat, 11 Mar 2000, Ryan Thompson wrote: > The old 2-button 9-pin $5 serial Dexxa mice were really fun.. I used > to buy the OEMs in bulk. They were a comfy little mouse, but, shine > direct sunlight on them and the optical disc motion sensors wouldn't > work. The cheap, thin plastic casing allowed light to shine through > and confuse the eye. The 3 button Dexxas were nice too; all you had to do was get a real metal ball for them and they worked until the cord broke internally. Wish I could buy a few dozen for a dollar each. :/ -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3: problems with SSH
On Sat, 11 Mar 2000, Kris Kennaway wrote: > I consider this a bug in openssh that it doesn't realise that it's using > rsaref and give a helpful error message when it gets a key that is too > long. I'm also working on a patch to do just this..give me a few minutes :-) Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3: problems with SSH
On Sat, 11 Mar 2000, Jordan K. Hubbard wrote: > > Are you using rsaref? rsaref can't handle keys longer than 1024 bits and > > we're not allowed to fix it so it can by the terms of the rsaref license. > > Since you're in Canada, you don't need rsaref and should be using the > > international version of openssl. See chapter 6.5 in the handbook for a > > longer description of the state of play. > > Can't he also just install the rsaintl package? That's what I meant by 'international version of openssl' since the rsaintl library is what makes it 'intl' :-) Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3: problems with SSH
> Are you using rsaref? rsaref can't handle keys longer than 1024 bits and > we're not allowed to fix it so it can by the terms of the rsaref license. > Since you're in Canada, you don't need rsaref and should be using the > international version of openssl. See chapter 6.5 in the handbook for a > longer description of the state of play. Can't he also just install the rsaintl package? - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3: problems with SSH
On Sat, 11 Mar 2000, Mathew Kanner wrote: > debug: Received server public key (1152 bits) and host key (1024 bits). > rsa_public_encrypt() failed Are you using rsaref? rsaref can't handle keys longer than 1024 bits and we're not allowed to fix it so it can by the terms of the rsaref license. Since you're in Canada, you don't need rsaref and should be using the international version of openssl. See chapter 6.5 in the handbook for a longer description of the state of play. > debug: Received server public key (768 bits) and host key (1023 bits). Since this one succeeded, it strongly suggests thats the problem. I consider this a bug in openssh that it doesn't realise that it's using rsaref and give a helpful error message when it gets a key that is too long. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3: problems with SSH
My colleague found these problems on a machine freshly installed with RC3. The machines on the other end are mix of sunos 2.5,6,7 on sparcs. Please flame me if this has already been discused. Script started on Sun Mar 12 00:55:40 2000 bash-2.03$ slogin -v XXX SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. debug: Reading configuration data /etc/ssh/ssh_config debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to XXX.CS.McGill.CA [132.206.51.205] port 22. debug: Allocated local port 978. debug: Connection established. debug: Remote protocol version 1.5, remote software version 1.2.26 debug: Waiting for server public key. debug: Received server public key (1152 bits) and host key (1024 bits). The authenticity of host 'XXX.cs.mcgill.ca' can't be established. Key fingerprint is 1024 a4:5d:e5:6d:1b:a3:71:31:31:eb:cf:09:45:a1:97:3b. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'XXX.cs.mcgill.ca' to the list of known hosts. rsa_public_encrypt() failed debug: Calling cleanup 0x8052d0c(0x0) bash-2.03$ slogin -v ni ova SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. debug: Reading configuration data /etc/ssh/ssh_config debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to YYY.CS.McGill.CA [132.206.51.245] port 22. debug: Allocated local port 977. debug: Connection established. debug: Remote protocol version 1.5, remote software version 1.2.26 debug: Waiting for server public key. debug: Received server public key (1152 bits) and host key (1024 bits). The authenticity of host 'YYY.cs.mcgill.ca' can't be established. Key fingerprint is 1024 ab:33:ca:d0:51:4c:fa:26:1d:d4:ed:c0:72:b0:e4:bc. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'YYY.cs.mcgill.ca' to the list of known hosts. rsa_public_encrypt() failed debug: Calling cleanup 0x8052d0c(0x0) bash-2.03$ slogin -v Z SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. debug: Reading configuration data /etc/ssh/ssh_config debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to ZZZ.CS.McGill.CA [132.206.2.5] port 22. debug: Allocated local port 976. debug: Connection established. debug: Remote protocol version 1.5, remote software version 1.2.17 debug: Waiting for server public key. Warning: Server lies about size of server host key: actual size is 1023 bits vs. announced 1024. Warning: This may be due to an old implementation of ssh. debug: Received server public key (768 bits) and host key (1023 bits). debug: Host 'ZZZ.cs.mcgill.ca' is known and matches the host key. debug: Encryption type: 3des debug: Sent encrypted session key. debug: Installing crc compensation attack detector. debug: Received encrypted confirmation. debug: Remote: Server does not permit empty password login. debug: Trying rhosts or /etc/hosts.equiv with RSA host authentication. debug: Server refused our rhosts authentication or host key. debug: Trying RSA authentication with key '[EMAIL PROTECTED]' debug: Server refused our key. debug: Doing password authentication. [EMAIL PROTECTED]'s password: debug: Requesting pty. debug: Requesting shell. debug: Entering interactive session. Last login: Sat Mar 11 19:55:07 2000 from .cs.m Sun Microsystems Inc. SunOS 5.7 Generic October 1998 Path now includes local/scripts Z/scripts ucb openwin Library path includes /usr/ucblib rvplayer Whoa, I know vim bash-2.03$ logout Connection to ZZZ.CS.McGill.CA closed. debug: Transferred: stdin 1, stdout 266, stderr 48 bytes in 1.0 seconds debug: Bytes per second: stdin 1.0, stdout 254.7, stderr 46.0 debug: Exit status 0 bash-2.03$ exit --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
"Jeffrey J. Mountin" wrote: > You could say I reserve the right shoot myself in foot by swapping keyboards. I think you've made it really clear with all of your many posts that you want this option. On the other hand, some of us think it's worthwhile to warn people that swapping keyboards and/or mice while the system is on could cause them problems. There is no reason that the two goals can't coexist, so why are you still posting? Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
>> For NetBSD-current, I'll bring in cleaner 6to4 code (since netbsd is >> not that close to the deadline). >> please wait for a while... >This is what I expected. I was just messing around some and was pleased >that it didn't panic my machine. Thanks. BTW, please be sure to read this before you configure 6to4 interface. I recommend you to run configured tunnels. (I missed the i-d cutoff date...) http://playground.iijlab.net/i-d/draft-itojun-ipv6-transition-abuse-00.txt itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
> Nawfal M Rouyan writes:
> Hi,
> I've installed XFree86 version 4 trough the ports
> collection
> but it won't start and I think it is because of the
> missing mouse module. Since I'm using lynx, I can't
> attached the /var/log/XFree86.0.log file for your
> reference. I can only paste the error I found in the
Yes, the mouse drive was not built :-(. TRy again with the following
patch to scripts/configure
Jean-Marc
Index: scripts/configure
===
RCS file: /home/ncvs/ports/x11/XFree86-4/scripts/configure,v
retrieving revision 1.58
diff -u -r1.58 configure
--- scripts/configure 2000/03/11 00:20:34 1.58
+++ scripts/configure 2000/03/12 00:23:57
@@ -196,7 +196,7 @@
echo "#undef BuildXInputExt" >> $F
echo "#define BuildXInputExt NO" >> $F
else
- echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
+ echo "#define XInputDrivers mouse dynapro elo2300 elographics magellan microtouch \
mutouch spaceorb wacom" >> $F
# XXX broken in 3.9.18
# if [ X${MACHINE} != X"alpha" ]; then
--
Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
So my IPv4 address is 24.113.130.83 that in IPv6 would be 2002:240:113:130:083 ?? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with PnP (related to sio?)?
Ugh... nevermind. Getting rid of the PNPBIOS option from the kernel
config got rid of all the unknown strangeness, although I still can't
explain it. The signal 11's only hit kdm, so I'm assuming that's a
different problem. Can someone commit the PnP magic for this modem or
should I just send-pr?
--
Eric Futch New York Connect.Net, Ltd.
[EMAIL PROTECTED] Technical Support Staff
http://www.nyct.net (212) 293-2620
"Bringing New York The Internet Access It Deserves"
Index: src/sys/isa/sio.c
===
RCS file: /home/ncvs/src/sys/isa/sio.c,v
retrieving revision 1.291
diff -u -r1.291 sio.c
--- src/sys/isa/sio.c 2000/03/11 20:22:09 1.291
+++ src/sys/isa/sio.c 2000/03/11 23:42:56
@@ -548,6 +548,7 @@
{0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */
{0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */
/* Devices that do not have a compatid */
+ {0x12206804, NULL}, /* ACH2012 - 5634BTS 56K Video Ready Modem */
{0x7602a904, NULL}, /* AEI0276 - 56K v.90 Fax Modem (LKT) */
{0x7905, NULL}, /* AKY - 56K Plug&Play Modem */
{0x01405407, NULL}, /* AZT4001 - AZT3000 PnP SOUND DEVICE, MODEM */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
MAX_UID ?
The fix I applied to pwd_mkdb is an improvement over what was there
before i.e. nothing, but is a poor solution at the moment since it won't
work correctly on the alpha.
The following code snippet is OK on the i386 but on the alpha ULONG_MAX
is 64 bits and so is a totally wrong constant to check a max uid
against.
id = strtoul(p, (char **)NULL, 10);
if (errno == ERANGE) {
warnx("%s > max uid value (%lu)", p, ULONG_MAX);
return (0)
}
I think we need a MAX_UID and a MAX_GID to perform checks like this.
Anyone got any objections to adding them to /usr/include/limits.h ?
Paul.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
I was able to get it working through a small patch to the
scripts/configure file. Probably not the most optimal solution, but it
works until the port is updated:
--- configure Fri Mar 10 19:20:34 2000
+++ configure.2 Sat Mar 11 18:19:55 2000
@@ -197,7 +197,7 @@
echo "#define BuildXInputExt NO" >> $F
else
echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
-mutouch spaceorb wacom" >> $F
+mutouch spaceorb wacom mouse" >> $F
# XXX broken in 3.9.18
# if [ X${MACHINE} != X"alpha" ]; then
#echo "#define JoystickSupport YES" >> $F
Michael L. Imamura
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: [EMAIL PROTECTED]
On Sat, 11 Mar 2000, Nawfal M. Rouyan wrote:
> Hi,
> I've installed XFree86 version 4 trough the ports
> collection
> but it won't start and I think it is because of the
> missing mouse module. Since I'm using lynx, I can't
> attached the /var/log/XFree86.0.log file for your
> reference. I can only paste the error I found in the
> file.
> .
> (II) LoadModule: "mouse"
> (WW) Warning, couldn't open module mouse
> (II) UnloadModule: "mouse"
> (EE) Failed to load module "mouse" (module does not
> exist, 0)
> .
> (EE) No Input driver matching `mouse'
> (II) Keyboard "Keyboard1" handled by legacy driver
> (WW) No core pointer registered
> No core pointer
> Fatal server error:
> failed to initialize core devices
>
> I'm using NVidia RIVA 128ZX with 8MB RAM and the X
> server
> detects it successfully. Any suggestions to solve my problems?
> __
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[andreas@klemm.gtn.com: -current install on Laptop, panic: resource_list_alloc: resource entry is busy]
Send one copy to -current, just for the case, that Soren is currently not available and somebody other could help. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 5.2.0 and songs from our band -> http://www.freebsd.org/~andreas Hi Søren, I have a problem to install a self created FreeBSD 4.0-SNAP-2311 on my LAPTOP: The last things I see on screen pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x3f4-0x3f7,0x374-0x377,0x1f4-0x1f7,0x174-0x177 at device 1.1 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy Uptime: 0s Automatic reboot in 15 seconds . Is that info o.k. for you or do you need something from boot_verbose ? Currently I have FreeBSD 3.4 installed onto it, since 4.x didn't run. So I would have the possibility to build 4.0 and boot test kernels onto it... This boot was from the boot floppy of the SNAP. Would you have time and interest to make it run ? Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
At 05:43 AM 3/11/00 -0800, David O'Brien wrote: >On Fri, Mar 10, 2000 at 07:45:33PM -0600, Jeffrey J. Mountin wrote: > > > > Hopefully that "yet" will be "never" so one can boot sans keyboard and > > later hook one up if need be. > >For me it cannot come soon enough. *FINALLY* the PC toy will act like a >real Unix computer. This is the behavior of all Sun's, DEC Alpha, >DECstations, etc... Gads! Now it a matter of what's "real" or not. I'd prefer the behaviour to be configurable and *not* push what I expect it do on everyone or what other systems do. And yes I am familiar with their behaviour. You could say I reserve the right shoot myself in foot by swapping keyboards. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ad0: WRITE command timeout - resetting
Hi, I've updated my desktop system to -CURRENT (my laptop runs ok since few months) : download and install the bin distrib, reboot then cvsup and make world, new kernel and mergemaster. All seems ok _except_ one thing : sometimes, my box seems to be slw and freezed, the reason is explaining in the following lines (from /var/log/messages) : Mar 11 23:05:57 titine /kernel: ad0: WRITE command timeout - resetting Mar 11 23:05:57 titine /kernel: ata0: resetting devices .. done Mar 11 23:06:07 titine /kernel: ad0: WRITE command timeout - resetting Mar 11 23:06:08 titine /kernel: ata0: resetting devices .. done Mar 11 23:06:18 titine /kernel: ad0: WRITE command timeout - resetting Mar 11 23:06:18 titine /kernel: ata0: resetting devices .. done Mar 11 23:08:23 titine /kernel: ad0: WRITE command timeout - resetting Mar 11 23:08:23 titine /kernel: ata0: resetting devices .. done Before updating, the wd driver never send me such things so i suspect my problem comes from ata driver... Here are the relevant lines of my kernel conf file : =-=-=-=-=-=-= device isa device eisa device pci device ata device atadisk device atapicd device atapifd options ATA_STATIC_ID =-=-=-=-=-=-=- Here are the boot messages : =-=-=-=-=-=-=- pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe800-0xe80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 (...) unknown0: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 ad0: 1222MB [2484/16/63] at ata0-master using WDMA2 ad1: 2445MB [4969/16/63] at ata0-slave using WDMA2 acd0: CDROM at ata1-master using PIO4 =-=-=-=-=-=-=- % /sbin/mount /dev/ad0s2a on / (ufs, local, soft-updates, writes: sync 118 async 870, reads: sync 1804 async 115) /dev/ad0s1 on /usr/home (ufs, local, soft-updates, writes: sync 43 async 250, reads: sync 146 async 28) /dev/ad1s4 on /usr/local (ufs, local, soft-updates, writes: sync 44 async 242, reads: sync 1020 async 162) /dev/ad0s3 on /usr/src (ufs, local, soft-updates, writes: sync 2 async 8, reads: sync 15 async 3) procfs on /proc (procfs, local) /dev/acd0c on /cdrom (cd9660, local, read-only, reads: sync 2 async 0) * $FreeBSD: src/sys/dev/ata/ata-all.c,v 1.50 2000/02/27 12:41:07 sos Exp $ Any ideas ? Thanks in advance, -- - Éric Jacoboni « No sport, cigars! » (W. Churchill) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with PnP (related to sio?)?
# cat QUAKE | grep ^device | grep pnp # Attached is my kernel config. -- Eric Futch New York Connect.Net, Ltd. [EMAIL PROTECTED] Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Sat, 11 Mar 2000, Mark Ovens wrote: >Remove the line > >device pnp0 > >from the kernel config file and re-build. > > > > >-- > Microsoft: Where do you want to go today? > Linux: Where do you want to go tomorrow? > BSD: Are you guys coming, or what? > -Poster at LinuxWorld 2000 > > FreeBSD - The Power To Serve http://www.freebsd.org > My Webpage http://ukug.uk.freebsd.org/~mark/ >mailto:[EMAIL PROTECTED] http://www.radan.com > machine i386 #cpuI386_CPU #cpuI486_CPU #cpuI586_CPU cpu I686_CPU ident QuakeStation maxusers128 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] #optionsMFS #Memory Filesystem #optionsMD_ROOT #MD is a potential root device options NFS #Network Filesystem #optionsNFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #optionsCD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #optionsSCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #optionsNCPU=2 # number of CPUs #optionsNBUS=4 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs device isa device eisa device pci # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #device adv0at isa? #device adw #device bt0 at isa? #device aha0at isa? #device aic0at isa? # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) # RAID controllers #device amr # AMI MegaRAID #device mlx #
Re: [20000307-SNAP] /etc/make.conf USA_RESIDENT and international crypto distribution
That was fixed days ago - get a more recent snap. :)
> Hi.
>
> I'm testing 2307-SNAP and I found that USA_RESIDENT is set to YES
> even if I installed from CD-ROMs with crypto distribution compiled
> from international crypto sources.
>
> How about adding something like following patch to sysinstall?
> (this patch has not tested yet)
>
> Index: dist.c
> ===
> RCS file: /home/ncvs/src/release/sysinstall/dist.c,v
> retrieving revision 1.174
> diff -u -r1.174 dist.c
> --- dist.c2000/03/08 14:54:19 1.174
> +++ dist.c2000/03/11 20:49:57
> @@ -393,14 +393,22 @@
> "DES-based passwords on other Unix systems. There will also
be some\n"
> "differences in the type of RSA code you use.\n\n"
> "Please do NOT choose Yes at this point if you are outside th
e\n"
> - "United States and Canada and are installing from a U.S. FTP
server.\n"
> + "United States and Canada and are installing from a U.S. FTP
server\n"
> + "or CDROM with international crypto distribution.\n"
> "Instead, install everything but the crypto bits from the U.S
. site\n"
> "and then switch to an international FTP server to install cr
ypto on\n"
> "a second pass with the Custom Installation option.")) {
> if (!dmenuOpenSimple(&MenuCRYPTODistributions, FALSE))
> i = DITEM_FAILURE;
> - else
> - USAResident = TRUE;
> + else {
> + if (!msgYesNo("Are you living in the United States or Canada?\n"
> + "(If you are not living in other countries and \n"
> + " installing from international CDROM, please\n"
> + " choose \"NO\")"))
> + USAResident = TRUE;
> + else
> + USAResident = FALSE;
> + }
> }
> else
> USAResident = FALSE;
>
> --
> ---
> Tatsumi Hosokawa
> [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
4.0-RC3 problems with sysinstall!!
I decided to grab the iso of 4.0-RC3 and do some installation testing, since problems have plagued the previous releases and I wanted to do my part to make sure that doesn't happen with 4.0. :-) Initial installation from the ISO went flawlessly. My problems are ocurring while using the post-install configure of sysinstall to add some packages (Configure/Packages). When attempting to install a package via FTP using a HTTP proxy (Squid to be exact), I found two problems. One is a minor problem, and the other is rather large, but they could be related. The minor problem is that the dialog box asking you for the address of the proxy server says the default port is 3128, but when I leave the port out, it initially tries port 21 instead. If I immediately select "Packages" again to make another attempt, it then correctly tries 3128, but says it still can't connect. Now here's the big problem... If I try selecting "Packages" a third time, I get a coredump (signal 11) and the terminal is screwed. No keyboard input works except Ctrl-C, which gives me successive prompts as if I were hitting the Enter key instead. Going to another terminal and killing csh on the offending terminal gives me a login prompt back. This is quite reproducible, since I've tried about 10 times with the same result. The only difference is that if I specify the correct port the first time, I get an immediate coredump instead of an error that it can't find the proxy server. Interestingly enough, after I run sysinstall a few times reproducing this, entering the proxy server address _without_ the port results in an immediate coredump as if I had entered the correct port the first time. No successive invocations of sysinstall show the initial behavior. Logging out and back in or using a fresh terminal doesn't change anything. Rebooting the system causes it to show the initial behavior again. That is particularly weird, since I don't see any weird environment variables or tempfiles laying around that would cause sysinstall to "keep state" like that. *boggle* Just as a datapoint, here is what is showing up in the Squid proxy logs each time I try this: 952812287.997 3 192.168.4.159 NONE/400 1100 GET / - NONE/- - -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 mouse?
On Sat, Mar 11, 2000 at 04:10:26PM -0500, Ted Sikora wrote: > My problem is a little different. XFree86-4.0 loads > fine looks great but the mouse does not work. There > are no errors. I tried PS/2 , serial, etc same with > them all. The pointer appears then moves to the upper > right and dissappers. I tried moving it...Mouse1, etc. > but nothing Any ideas? Yeah, I have it working under -CURRENT: XFree86 Version 4.0 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 8 March 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 4.0-CURRENT i386 [ELF] [snip] (==) Mouse1: Protocol: "Auto" (**) Mouse1: Core Pointer (==) Mouse1: Buttons: 3 Relevant config in XF86Config: Identifier "Mouse1" Driver "mouse" Option "Device" "/dev/sysmouse" If you don't specify a protocol, XF86-4 will auto-probe the device and should pick it up no problem. This particular problem is mentioned in the documentation for XFree86 4.0 by the way, as well as how to resolve it. I should also note I didn't build mine from the ports (the port wasn't available when I built it) but from the raw source. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mylex Support
Not very helpful at this point; what I need is the time to attempt to reproduce your situation. To be quite honest, since none of the BIOS, RedHat nor FreeBSD can agree over the actual reported size of the array coming from these controllers of yours, I'm rather inclined to think that there's an external factor affecting things. > OK. How about if I put the controller in a spare PC, stick a -current on there, and >give you telnet access? > Hopefully it _is_ just something stupid I'm doing, but at least that will cure my >problem. > If it's not, it may be a problem for others as well. > > Lawrence > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SB AWE64 in -CURRENT
Ok, I'm giving serious thought to ditching the Debian installation on this drive and go with FreeBSD. I run FreeBSD on this machine already, but on a smaller drive. Debian and Linux have been routinely irritating me. I'm used to the traditional set of Unix tools, and the traditional command line options. Linux utils are close, but most seem to have weird little quirks to them to their traditional counterparts. I run 4-CURRENT on my network server here also. Does 4-CURRENT have drivers for the SB64 AWE synth? I have the regular PCM stuff going pretty well already... Sorry to ask here, but the LINT file isn't much help and the sound driver documentation is slightly out of date. -- Cheers, Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird problems with PnP (related to sio?)?
On Sat, Mar 11, 2000 at 03:30:33PM -0500, Eric D. Futch wrote:
> I'm having some weird problems with PnP, I guess. I have a "SmartLink 56K
> Voice Fax Modem" that I just stuck into the computer. Before I added the
> PnP magic to src/sys/isa/sio.c, in the kernel messages just said unknown
> for it, which is what I expected. So at that point I had three unkowns,
> one for , and then that modem.
>
> The src/sys/isa/sio.c magic for this modem looks like this:
> {0x12206804, NULL}, /* ACH2012 - 5634BTS 56K Video Ready Modem */
>
> Now that I have that in there, after building/installing a fresh kernel,
> it gets attached to the sio driver but I'm getting these other lines of
> unknown stuff that seems to be causing problems with memory. Random things
> die on signal 11 now, like kdm.
>
> >From dmesg:
> sio2: <5634BTS 56K Video Ready Modem> at port 0x3e8-0x3ef irq 10 on isa0
> sio2: type 16550A
> unknown2: at port 0x20-0x21,0xa0-0xa1,0x4d0-0x4d1 irq 2 on isa0
> unknown3: at port
>0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde,0x40b,0x410-0x43f,0x481-0x483,0x487,0x489-0x48c,0x4d6
> drq 4 on isa0
> unknown4: at port 0x40-0x43 irq 0 on isa0
> unknown5: at port 0x70-0x71 irq 8 on isa0
> unknown: can't assign resources
[snip]
Remove the line
device pnp0
from the kernel config file and re-build.
--
Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
BSD: Are you guys coming, or what?
-Poster at LinuxWorld 2000
FreeBSD - The Power To Serve http://www.freebsd.org
My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:[EMAIL PROTECTED] http://www.radan.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
On Sat, 11 Mar 2000, in a never-ending search for enlightenment, Ryan Thompson wrote: > Jeffrey J. Mountin wrote to Ryan Thompson: > > > At 09:19 PM 3/10/00 -0600, Ryan Thompson wrote: > > >Me as well...For at least a decade. I used to do it manually all the > > >time, but had occasional glitches with funny scan codes and indicator > > >statuses. With a mid-range priced switch, though, I have had no problems > > >whatsoever. > > > > The only glitches I ever see are with a mouse. Tap me on the shoulder > > while my hand is on the mouse and it will seize. For my use at home there > > isn't a need for a switch. Could use one at times, but it's simple enough > > to swap around at need. > > The old 2-button 9-pin $5 serial Dexxa mice were really fun.. I used to > buy the OEMs in bulk. They were a comfy little mouse, but, shine direct > sunlight on them and the optical disc motion sensors wouldn't work. The > cheap, thin plastic casing allowed light to shine through and confuse the > eye. > > -- > Ryan Thompson <[EMAIL PROTECTED]> > Systems Administrator, Accounts > Phone: +1 (306) 664-1161 A sun-powered mouseneat! > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
> I believe I'm looking for a public IPv6 address to use for testing > purposes. So where/what addresses can I use is my question. > then how I intergrate that into my setup. > > Hope that makes the question more clearer. > Thanks OK, then I think you should try 6to4 addr. The format is like below. 2002your IPv4 addr site prefix interface ID 2byte 4byte2byte 8byte You need to choose one of your own IPv4 addr which is reachable from internet. Site prefix part is 2byte. This means you can have 65535 IPv6 subnets. If your IPv4 address is 1.2.3.4, then your IPv6 address blocks will be, 2002:0102:0304:-::/64 Then you can assign each IPv6 prefix to each of your subnets, like prefix ed0 2002:0102:0304::: prefix ed1 2002:0102:0304:0001:: etc... And you need to setup 6to4 outer interface on the router which is reachable form internet. That is just committed yesterday, so you need to cvs update your source, and rebuild your kernel. The necessary procedure is below. (I suppose your IPv4 addr is 1.2.3.4) gifconfig stf0 1.2.3.4 255.255.255.255 ifconfig stf0 inet6 2002:0102:0304::1 -prefix 16 I think you should setup ip6fw entries for "stf0" interface for security reasons. About more details for 6to4, please check draft-ietf-ngtrans-6to4-0x.txt Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86-4 mouse?
My problem is a little different. XFree86-4.0 loads fine looks great but the mouse does not work. There are no errors. I tried PS/2 , serial, etc same with them all. The pointer appears then moves to the upper right and dissappers. I tried moving it...Mouse1, etc. but nothing Any ideas? Note:XF86Config works well but XFree86 -configure gives a bad config Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
I believe I'm looking for a public IPv6 address to use for testing purposes. So where/what addresses can I use is my question. then how I intergrate that into my setup. Hope that makes the question more clearer. Thanks On Sat, 11 Mar 2000, Shaun (UNIX) wrote: > Ok, now I would like to get some good info on IPv6 and how it is > structured. Mainly looking for how it works in regards to setting up IP's > and how the IP formatting works. Eg. IPv4 has special blocks of IPs that > are only used for internal networks with there own subnet masks etc. > That kind of info. > > Thanks > Shaun > > On Sat, 11 Mar 2000, Yoshinobu Inoue wrote: > > > > How/Where is the setup for the IPv6? > > > > > > Shaun > > > > If you have recent tree or Freebsd4.0 RC3, then there will be > > IPv6 specific configuration examples in /etc/defaults/rc.conf. > > The lines which start from "ipv6_..." are them. > > > > At least you need to set ipv6_enable to YES. > > You need to add the follwing line into /etc/rc.conf. > > > > ipv6_enable="YES" > > > > If you want to use your machine as IPv6 router, then you need > > to assigne your interfaces IPv6 prefix (like IPv4 subnet). > > Typical configurations will be, > > > > ipv6_gateway_enable="YES"# Set to YES if this host will be a gateway. > > ipv6_router_enable="YES" # Set to YES to enable an IPv6 routing daemon. > > ipv6_router_flags="-l"# Flags to IPv6 routing daemon. > > > > Also, if your router has ed0 and ep0, and you want to assigne > > IPv6 site local prefixes fec0:::0001::/64 and > > fec0:::0003::/64, then following additions will be enough. > > > > ipv6_network_interfaces="ed0 ep0" > > ipv6_prefix_ed0=fec0:::0001 > > ipv6_prefix_ep0=fec0:::0003 > > > > > > Cheers, > > Yoshinobu Inoue > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[20000307-SNAP] /etc/make.conf USA_RESIDENT and international crypto distribution
Hi.
I'm testing 2307-SNAP and I found that USA_RESIDENT is set to YES
even if I installed from CD-ROMs with crypto distribution compiled
from international crypto sources.
How about adding something like following patch to sysinstall?
(this patch has not tested yet)
Index: dist.c
===
RCS file: /home/ncvs/src/release/sysinstall/dist.c,v
retrieving revision 1.174
diff -u -r1.174 dist.c
--- dist.c 2000/03/08 14:54:19 1.174
+++ dist.c 2000/03/11 20:49:57
@@ -393,14 +393,22 @@
"DES-based passwords on other Unix systems. There will also be
some\n"
"differences in the type of RSA code you use.\n\n"
"Please do NOT choose Yes at this point if you are outside the\n"
- "United States and Canada and are installing from a U.S. FTP
server.\n"
+ "United States and Canada and are installing from a U.S. FTP
+server\n"
+ "or CDROM with international crypto distribution.\n"
"Instead, install everything but the crypto bits from the U.S.
site\n"
"and then switch to an international FTP server to install crypto
on\n"
"a second pass with the Custom Installation option.")) {
if (!dmenuOpenSimple(&MenuCRYPTODistributions, FALSE))
i = DITEM_FAILURE;
- else
- USAResident = TRUE;
+ else {
+ if (!msgYesNo("Are you living in the United States or Canada?\n"
+ "(If you are not living in other countries and \n"
+ " installing from international CDROM, please\n"
+ " choose \"NO\")"))
+ USAResident = TRUE;
+ else
+ USAResident = FALSE;
+ }
}
else
USAResident = FALSE;
--
---
Tatsumi Hosokawa
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
On Sat, Mar 11, 2000 at 12:24:10PM -0800, Nawfal M. Rouyan wrote: > Hi, > I've installed XFree86 version 4 trough the ports > collection > but it won't start and I think it is because of the > missing mouse module. Since I'm using lynx, I can't > attached the /var/log/XFree86.0.log file for your > reference. I can only paste the error I found in the > file. > . > (II) LoadModule: "mouse" > (WW) Warning, couldn't open module mouse > (II) UnloadModule: "mouse" > (EE) Failed to load module "mouse" (module does not > exist, 0) > . > (EE) No Input driver matching `mouse' > (II) Keyboard "Keyboard1" handled by legacy driver > (WW) No core pointer registered > No core pointer > Fatal server error: > failed to initialize core devices I fall into the same... with 3.9.17 everything was fine/ It seems that mouse_drv.o is not build automaticaly at least with the port. If I buld it myself it's working. I also got other problems with /usr/X11R6 linked to /vol/X11R6 which is automounted. Some of the build softlinks getting make install to fail. It was the link to /usr/X11R6/lib/X11/app-defaults. I put schg on /usr/X11R6/lib/X11 and installed with make -i. Netscape is also a problem: bash-2.03$ netscape ld.so failed: Undefined symbol "__Xglobal_lock" in navigator-4.7.bin:/usr/X11R6/lib/aout/libXext.so.6.3 -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
Ok, now I would like to get some good info on IPv6 and how it is structured. Mainly looking for how it works in regards to setting up IP's and how the IP formatting works. Eg. IPv4 has special blocks of IPs that are only used for internal networks with there own subnet masks etc. That kind of info. Thanks Shaun On Sat, 11 Mar 2000, Yoshinobu Inoue wrote: > > How/Where is the setup for the IPv6? > > > > Shaun > > If you have recent tree or Freebsd4.0 RC3, then there will be > IPv6 specific configuration examples in /etc/defaults/rc.conf. > The lines which start from "ipv6_..." are them. > > At least you need to set ipv6_enable to YES. > You need to add the follwing line into /etc/rc.conf. > > ipv6_enable="YES" > > If you want to use your machine as IPv6 router, then you need > to assigne your interfaces IPv6 prefix (like IPv4 subnet). > Typical configurations will be, > > ipv6_gateway_enable="YES"# Set to YES if this host will be a gateway. > ipv6_router_enable="YES" # Set to YES to enable an IPv6 routing daemon. > ipv6_router_flags="-l"# Flags to IPv6 routing daemon. > > Also, if your router has ed0 and ep0, and you want to assigne > IPv6 site local prefixes fec0:::0001::/64 and > fec0:::0003::/64, then following additions will be enough. > > ipv6_network_interfaces="ed0 ep0" > ipv6_prefix_ed0=fec0:::0001 > ipv6_prefix_ep0=fec0:::0003 > > > Cheers, > Yoshinobu Inoue > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weird problems with PnP (related to sio?)?
I'm having some weird problems with PnP, I guess. I have a "SmartLink 56K
Voice Fax Modem" that I just stuck into the computer. Before I added the
PnP magic to src/sys/isa/sio.c, in the kernel messages just said unknown
for it, which is what I expected. So at that point I had three unkowns,
one for , and then that modem.
The src/sys/isa/sio.c magic for this modem looks like this:
{0x12206804, NULL}, /* ACH2012 - 5634BTS 56K Video Ready Modem */
Now that I have that in there, after building/installing a fresh kernel,
it gets attached to the sio driver but I'm getting these other lines of
unknown stuff that seems to be causing problems with memory. Random things
die on signal 11 now, like kdm.
>From dmesg:
sio2: <5634BTS 56K Video Ready Modem> at port 0x3e8-0x3ef irq 10 on isa0
sio2: type 16550A
unknown2: at port 0x20-0x21,0xa0-0xa1,0x4d0-0x4d1 irq 2 on isa0
unknown3: at port
0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde,0x40b,0x410-0x43f,0x481-0x483,0x487,0x489-0x48c,0x4d6
drq 4 on isa0
unknown4: at port 0x40-0x43 irq 0 on isa0
unknown5: at port 0x70-0x71 irq 8 on isa0
unknown: can't assign resources
unknown6: at port 0xf0-0xff irq 13 on isa0
unknown: can't assign resources
unknown: can't assign resources
unknown7: at iomem
0xe8000-0xf,0-0x9,0x10-0x7ff,0xffe8-0x,0xfec0-0xfec08fff
on isa0
unknown8: at port 0xcf8-0xcff on isa0
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown9: at port 0x78-0x7f,0x2e-0x2f on isa0
unknown10: at port 0x290-0x297 on isa0
Strange things from running kdm:
/kernel: pid 567 (kdm), uid 0: exited on signal 11 (core dumped)
kdm[563]: Unknown session exit code 35584 from process 567
Of course all of this worked beautifully before I stuck the modem in and
put in the PnP magic for it. Output of pnpinfo and full dmesg provided as
attachments. I can provide the boot -v output as well if anyone really
wants it. Feel free to pass the point hat if I missed anything obvious.
--
Eric Futch New York Connect.Net, Ltd.
[EMAIL PROTECTED] Technical Support Staff
http://www.nyct.net (212) 293-2620
"Bringing New York The Internet Access It Deserves"
Checking for Plug-n-Play devices...
Card assigned CSN #1
Vendor ID CSC0b36 (0x360b630e), Serial Number 0x
PnP Version 1.0, Vendor Version 1
Device Description: CS4236 Audio
Logical Device ID: CSC 0x630e #0
Device Description: WSS/SB
TAG Start DF
Good Configuration
DMA: channel(s) 1
8-bit, not a bus master, count by byte, , Type A
DMA: channel(s) 0 3
8-bit, not a bus master, count by byte, , Type A
IRQ: 5 - only one type (true/edge)
I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4
[16-bit addr]
I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4
[16-bit addr]
I/O Range 0x220 .. 0x220, alignment 0x20, len 0x10
[16-bit addr]
TAG Start DF
Acceptable Configuration
DMA: channel(s) 1 3
8-bit, not a bus master, count by byte, , Type A
DMA: channel(s) 0 1 3
8-bit, not a bus master, count by byte, , Type A
IRQ: 5 7 9 11 12 15 - only one type (true/edge)
I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4
[16-bit addr]
I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4
[16-bit addr]
I/O Range 0x220 .. 0x260, alignment 0x20, len 0x10
[16-bit addr]
TAG Start DF
Sub-optimal Configuration
DMA: channel(s) 0 1 3
8-bit, not a bus master, count by byte, , Type A
IRQ: 5 7 9 11 12 15 - only one type (true/edge)
I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4
[16-bit addr]
I/O Range 0x388 .. 0x3f8, alignment 0x8, len 0x4
[16-bit addr]
I/O Range 0x220 .. 0x300, alignment 0x20, len 0x10
[16-bit addr]
TAG End DF
Logical Device ID: CSC0001 0x0100630e #1
Device Description: GAME
TAG Start DF
Good Configuration
I/O Range 0x200 .. 0x200, alignment 0x8, len 0x8
[16-bit addr]
TAG Start DF
Acceptable Configuration
I/O Range 0x208 .. 0x208, alignment 0x8, len 0x8
[16-bit addr]
TAG End DF
Logical Device ID: CSC0010 0x1000630e #2
Device Description: CTRL
I/O Range 0x120 .. 0xff8, alignment 0x8, len 0x8
[16-bit addr]
Logical Device ID: CSC0003 0x0300630e #3
Device Description: MPU
TAG Start DF
Good Configuration
IRQ: 9 - only one type (true/edge)
I/O Range 0x330 .. 0x330, alignment 0x8, len 0x2
[16-bit addr]
TAG Start DF
Acceptable Configuration
IRQ: 9 11 12 15 - only one type (true/edge)
I/O Range 0x300 .. 0x3f8, alignment 0x8, len 0x2
[16-bit addr]
TAG End DF
End Tag
Successfully got 44 resources, 4 logical fdevs
-- card select # 0x0001
CSN CSC0b36 (0x360b630e), Serial Number 0x
Logical device #0
IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534
XFree86-4 can't start
Hi, I've installed XFree86 version 4 trough the ports collection but it won't start and I think it is because of the missing mouse module. Since I'm using lynx, I can't attached the /var/log/XFree86.0.log file for your reference. I can only paste the error I found in the file. . (II) LoadModule: "mouse" (WW) Warning, couldn't open module mouse (II) UnloadModule: "mouse" (EE) Failed to load module "mouse" (module does not exist, 0) . (EE) No Input driver matching `mouse' (II) Keyboard "Keyboard1" handled by legacy driver (WW) No core pointer registered No core pointer Fatal server error: failed to initialize core devices I'm using NVidia RIVA 128ZX with 8MB RAM and the X server detects it successfully. Any suggestions to solve my problems? __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
Jeffrey J. Mountin wrote to Ryan Thompson: > At 09:19 PM 3/10/00 -0600, Ryan Thompson wrote: > >Me as well...For at least a decade. I used to do it manually all the > >time, but had occasional glitches with funny scan codes and indicator > >statuses. With a mid-range priced switch, though, I have had no problems > >whatsoever. > > The only glitches I ever see are with a mouse. Tap me on the shoulder > while my hand is on the mouse and it will seize. For my use at home there > isn't a need for a switch. Could use one at times, but it's simple enough > to swap around at need. The old 2-button 9-pin $5 serial Dexxa mice were really fun.. I used to buy the OEMs in bulk. They were a comfy little mouse, but, shine direct sunlight on them and the optical disc motion sensors wouldn't work. The cheap, thin plastic casing allowed light to shine through and confuse the eye. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: netstat output for inet6
> > And sorry, it is not added to netstat man yet. > > I see you've just commited a change there, but I think it needs adding to > the usage message as well: > > ben@platinum:~$ netstat -\? > netstat: illegal option -- ? > usage: netstat [-Aan] [-f address_family] [-M core] [-N system] >netstat [-abdghimnrs] [-f address_family] [-M core] [-N system] >netstat [-bdn] [-I interface] [-M core] [-N system] [-w wait] >netstat [-M core] [-N system] [-p protocol] I see. I'll try to request permission to fix it. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: netstat output for inet6
Yoshinobu Inoue wrote: > Please add "-l" flag. ah.. thanks. > And sorry, it is not added to netstat man yet. I see you've just commited a change there, but I think it needs adding to the usage message as well: ben@platinum:~$ netstat -\? netstat: illegal option -- ? usage: netstat [-Aan] [-f address_family] [-M core] [-N system] netstat [-abdghimnrs] [-f address_family] [-M core] [-N system] netstat [-bdn] [-I interface] [-M core] [-N system] [-w wait] netstat [-M core] [-N system] [-p protocol] -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
Ryan Thompson wrote: > > I'm not sure, that's why I asked the list :-) Really, what I was asking > is if there is a better way to detect a serial console.. Rather than the > current logic of "If there is no keyboard, there must be a serial > console". I can think of N reasons why a box would have no keyboard > attached, besides having a serial console. You can force loader on this matter. Man loader(8) and loader.conf(5). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI Modems
In message <[EMAIL PROTECTED]> Kent Hauser writes: : I of course did this because "device_set_unit" didn't link. : : Any suggestions? Yes. I forgot to include this in my original patch. Grab a new copy. I've updated the patch to include this. Sorry for any trouble this cuased. http://people.freebsd.org/~imp/sio-current-pci-patch Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
>I applied a variant of your patch to my NetBSD/i386 -currentish box that >also uses the KAME stack and was able to ping6 your 6to4 address. For NetBSD-current, I'll bring in cleaner 6to4 code (since netbsd is not that close to the deadline). please wait for a while... itojun This is what I expected. I was just messing around some and was pleased that it didn't panic my machine. Brad Spencer - [EMAIL PROTECTED] http://anduin.eldar.org [finger [EMAIL PROTECTED] for PGP public key] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with Linksys NIC and the new dc driver.
On Fri, Mar 10, 2000 at 06:13:14PM +, [EMAIL PROTECTED] wrote: > I am currently experiencing problems with the 0307 -CURRENT snapshot, and > the dc driver. I previously have had no problems with the pn driver I had [snip] Yes, I'm using a LinkSys card with -CURRENT: dc0: port 0xd400-0xd4ff mem 0xea00-0xeaff irq 11 at device 13.0 on pci0 dc0: Ethernet address: 00:a0:cc:32:9a:d8 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto It's a LNE100TX v2.0 10/100 PCI NIC. However, under 3.x it used the mx* driver, not pn* (this particular card anyways) Relevant kernel config options: device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes pseudo-device ether # Ethernet support Hope that helps some. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unexplained network outages
I have a win98 box connected to a 4.0-current box via an ethernet connection. The connection will go dead after about 20 minutes. I'm unable to ping the win98 box and cannot ping the FreeBSD box from the win98 box. No error/console messages. I can bring it back to life by doing an ifconfig dc1 down/up, then pinging the win98 box. Has anyone experienced this behavior? The strange thing is that the network never goes down if I run tcpdump in promiscuous mode on the interface - it's a workaround, but I don't like it. Any ideas would be greatly appreciated. Here's the output from ifconfig and dmesg: dc1: flags=8943 mtu 1500 inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 ether 00:80:c6:f9:70:ec media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX none dc1: port 0xec00-0xecff mem 0xebfbff00-0xebfb irq 10 at device 5.0 on pci0 dc1: Ethernet address: 00:80:c6:f9:70:ec miibus1: on dc1 dcphy1: on miibus1 dcphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED] Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ida driver in -current and eisa bus attachment
> > Compaq claimed that the documentation necessary to do this was available, > > but it's not. I've tried to contact the individual that I spoke to about > > this, but he's not returning email or phone calls. 8( > > I've tried this internally in Compaq and the answer is quite clear IMO: > "The config interface is Compaq IP. No, you cannot get the spec". > > So... unless someone changes their minds in Houston this is the outcome > I'm afraid. So we will have to wait then... Thanks Ales To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: netstat output for inet6
Hi, > On Sat, 11 Mar 2000 12:44:57 + > Ben Smithurst <[EMAIL PROTECTED]> said: ben> Is there any way to see the full IPv6 address with netstat? I just see: Try do with -l option. ume@peace:263# netstat -anl -f inet6 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp6 0 20 2001:200:301:0:200:f8ff:fe05:3eae.22 2001:200:301:0:200:f4ff:fe5e:7147.1022ESTABLISHED -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: netstat output for inet6
> Is there any way to see the full IPv6 address with netstat? I just see: > > ben@strontium:~$ netstat -an -f inet6 > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address(state) > tcp6 0 0 2002:d4e4:e0d:0:.989 2002:d4e4:e0d:0:.22ESTABLISHED > ... Please add "-l" flag. And sorry, it is not added to netstat man yet. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
On Fri, Mar 10, 2000 at 07:45:33PM -0600, Jeffrey J. Mountin wrote: > > Hopefully that "yet" will be "never" so one can boot sans keyboard and > later hook one up if need be. For me it cannot come soon enough. *FINALLY* the PC toy will act like a real Unix computer. This is the behavior of all Sun's, DEC Alpha, DECstations, etc... -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
netstat output for inet6
Is there any way to see the full IPv6 address with netstat? I just see: ben@strontium:~$ netstat -an -f inet6 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp6 0 0 2002:d4e4:e0d:0:.989 2002:d4e4:e0d:0:.22ESTABLISHED ... Perhaps there's some flag I missed. If there is no way, there should be; perhaps a -W flag for wider output for IPv6 addresses? I'll try this myself if people think it would be a good idea, or have any better ideas, but it may be too much for me. :-) -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mylex Support
OK. How about if I put the controller in a spare PC, stick a -current on there, and give you telnet access? Hopefully it _is_ just something stupid I'm doing, but at least that will cure my problem. If it's not, it may be a problem for others as well. Lawrence To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
On Fri, Mar 10, 2000 at 10:48:22AM -0800, Mike Smith wrote: > > Hi Jonathan, > > > > > Note that I just committed some more changes to the IDA driver to > > > 4.0-RC yesterday. The changes are: > > > > > > - support for EISA controllers (untested) > > > - support for newer S2400 controllers (untested) > > > - addition of IDA to the GENERIC kernel > > > - support for installing directly onto the RAID array. > > > > Are there any plans to add some utility to configure (or reconfigure) the > > array under FreeBSD??? > > Compaq claimed that the documentation necessary to do this was available, > but it's not. I've tried to contact the individual that I spoke to about > this, but he's not returning email or phone calls. 8( I've tried this internally in Compaq and the answer is quite clear IMO: "The config interface is Compaq IP. No, you cannot get the spec". So... unless someone changes their minds in Houston this is the outcome I'm afraid. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Commit candidate: libRSAglue patches
Here are the patches which seem to fix the libRSAglue upgrade problems
people had been seeing when upgrading from trees built in a certain time
window. I've tested these on both an older system which was breaking and a
current one with no ill effects - nor should there be any since libRSAglue
is an empty stub library thesedays.
Kris
Index: usr.sbin/ppp/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/ppp/Makefile,v
retrieving revision 1.72
diff -u -r1.72 Makefile
--- usr.sbin/ppp/Makefile 2000/03/09 06:29:02 1.72
+++ usr.sbin/ppp/Makefile 2000/03/11 02:23:24
@@ -39,10 +39,6 @@
SRCS+= chap_ms.c
LDADD+= -lcrypto
DPADD+= ${LIBCRYPTO}
-.if defined(RSAREF) && ${RSAREF} == YES
-LDADD+=-lRSAglue
-DPADD+= ${LIBRSAGLUE}
-.endif
.endif
.if defined(NORADIUS)
Index: usr.sbin/pppd/Makefile
===
RCS file: /home/ncvs/src/usr.sbin/pppd/Makefile,v
retrieving revision 1.18
diff -u -r1.18 Makefile
--- usr.sbin/pppd/Makefile 2000/03/09 06:29:05 1.18
+++ usr.sbin/pppd/Makefile 2000/03/11 02:23:27
@@ -34,10 +34,6 @@
SRCS+= chap_ms.c
LDADD+=-lcrypto
DPADD+=${LIBCRYPTO}
-.if defined(RSAREF) && ${RSAREF} == YES
-LDADD+=-lRSAglue
-DPADD+= ${LIBRSAGLUE}
-.endif
.endif
.if defined(RELEASE_CRUNCH)
Index: kerberosIV/Makefile.inc
===
RCS file: /home/ncvs/src/kerberosIV/Makefile.inc,v
retrieving revision 1.7
diff -u -r1.7 Makefile.inc
--- kerberosIV/Makefile.inc 2000/02/24 20:56:39 1.7
+++ kerberosIV/Makefile.inc 2000/03/11 01:13:01
@@ -71,10 +71,6 @@
CFLAGS+= -I${.CURDIR}/../../include -Wall -DHAVE_CONFIG_H \
-I${INCLUDEOBJDIR} -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\"
-.if defined(RSAREF) && ${RSAREF} == YES
-LDADD+=-lRSAglue
-DPADD+= ${LIBRSAGLUE}
-.endif
protos.h: ${KRB4DIR}/include/protos.H
ln -sf ${.ALLSRC} ${.TARGET}
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
>I applied a variant of your patch to my NetBSD/i386 -currentish box that >also uses the KAME stack and was able to ping6 your 6to4 address. For NetBSD-current, I'll bring in cleaner 6to4 code (since netbsd is not that close to the deadline). please wait for a while... itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
>> And here is the patches. > >The last patches should work but I found a improvement related >to coexistence with gif, so this is the updated patches. > > I applied a variant of your patch to my NetBSD/i386 -currentish box that > also uses the KAME stack and was able to ping6 your 6to4 address. That is fine. :-) However, my patches are temporal hack for FreeBSD4.0. KAME code is changing tunnel interface implementations more generally, so I think different fixes and support for 6to4 will be introduced eventually. Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6 setup...
> How/Where is the setup for the IPv6? > > Shaun If you have recent tree or Freebsd4.0 RC3, then there will be IPv6 specific configuration examples in /etc/defaults/rc.conf. The lines which start from "ipv6_..." are them. At least you need to set ipv6_enable to YES. You need to add the follwing line into /etc/rc.conf. ipv6_enable="YES" If you want to use your machine as IPv6 router, then you need to assigne your interfaces IPv6 prefix (like IPv4 subnet). Typical configurations will be, ipv6_gateway_enable="YES"# Set to YES if this host will be a gateway. ipv6_router_enable="YES" # Set to YES to enable an IPv6 routing daemon. ipv6_router_flags="-l"# Flags to IPv6 routing daemon. Also, if your router has ed0 and ep0, and you want to assigne IPv6 site local prefixes fec0:::0001::/64 and fec0:::0003::/64, then following additions will be enough. ipv6_network_interfaces="ed0 ep0" ipv6_prefix_ed0=fec0:::0001 ipv6_prefix_ep0=fec0:::0003 Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
