Fools Day Joke ?
There is some strangenes in date on file ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.5198.gz -r--r--r- 1 603 207 49741 apr 1 1998 cvs-cur.5198.gz N.Dudorov To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
On Thu, 01 Apr 1999 00:48:50 EST, Rod Taylor wrote:
Just out of curiosity, why are there games included in the FreeBSD
source tree?
Politics and hysterical raisins. If you don't want the gamey games,
apply the diffs below to your source.
Caio,
Sheldon.
Index: Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.65
diff -u -d -r1.65 Makefile.inc1
--- Makefile.inc1 1999/03/01 01:09:06 1.65
+++ Makefile.inc1 1999/03/01 09:26:18
@@ -828,9 +828,6 @@
.endif
.for d in \
bin/sh \
- ${_adventure} \
- ${_hack}\
- ${_phantasia} \
gnu/usr.bin/cc/cc_tools \
lib/libmytinfo \
${_linux} \
Index: games/Makefile
===
RCS file: /home/ncvs/src/games/Makefile,v
retrieving revision 1.15
diff -u -d -r1.15 Makefile
--- Makefile1998/08/30 20:58:16 1.15
+++ Makefile1999/03/02 14:57:30
@@ -2,44 +2,19 @@
# $Id: Makefile,v 1.15 1998/08/30 20:58:16 gpalmer Exp $
# XXX missing: chess ching monop [copyright]
-SUBDIR= adventure \
- arithmetic \
- atc \
- backgammon \
- battlestar \
+SUBDIR= \
bcd \
- bs \
caesar \
- canfield \
- cribbage \
- dm \
factor \
- fish \
fortune \
grdc \
- hack \
- hangman \
- larn \
- mille \
morse \
number \
- phantasia \
- piano \
pig \
pom \
ppt \
primes \
- quiz \
- rain \
random \
- robots \
- rogue \
- sail \
- snake \
- trek \
- wargames \
- worm \
- worms \
- wump
+ \
.include bsd.subdir.mk
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Games
On 1 Apr, Daniel C. Sobral wrote: Well, first of all, .profile, .cshrc and signature scripts are broken in the absense of fortune. If I remember correctly .cshrc contains [ -x /usr/games/fortune ] ... so this shouldn't be an issue. BTW.: My /usr/games contains nothing (3.1-Stable install, cvsup to current and make world with NOGAMES=YES). The only thing I've noticed is: hack istn't there anymore, but thats expected. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
* From: Jordan K. Hubbard j...@zippy.cdrom.com * * Committing /var/db/pkg to mtree was fine, it probably should have been * there to begin with. Sticking things into it outside of pkg_add, * however, is evil. pkg_add owns this directory and every time we've * tried to go behind its back, so to speak, we've been raped for it. * The whole mess with XFree68 was a total nightmare and is what happens * when changes like this are made without really thinking things out. The name of the directory where it resides doesn't matter. It's not a package file so the situation is totally different from XFree86. (The only reason pkg_info was affected was because I blindly assumed it will ignore non-directories in /var/db/pkg.) I can easily move it out of /var/db/pkg to some other place. * No more kludges, please. I'm not changing sysinstall and make world * shouldn't be writing into /var/db/pkg either. If you've found it * necessasry to do this, then you've made a mistake just as you did * with XFree86 and need to think about the problem again. The same situation arises whether the version info is in /var/db/pkg or /some/other/place. It has been pointed out many times in the past that we need something to ensure bsd.port.mk can synchronize itself with the rest of the system (simply because there are too many people who cvsup one without the other). The question is, can I ask you to make sysinstall write some kind of version info that can be used by bsd.port.mk to identify the age of the system? The problem is real, we've been bitten too many times in the past (haven't you seen all the where's fetch -A? and other more subtle breakages that are caused by ports and system mismatch), and I can solve it with or without your help. It will just be so much easier if you can help me out a little. -W To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
Alexander Leidinger wrote: On 1 Apr, Daniel C. Sobral wrote: Well, first of all, .profile, .cshrc and signature scripts are broken in the absense of fortune. If I remember correctly .cshrc contains [ -x /usr/games/fortune ] ... so this shouldn't be an issue. Well, some people seem to be able to survive without fortune, but that's probably the exception to the rule... :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
[ Yes, I'm sticking my nose in where it probably doesn't belong and should get chopped off for it. It's a hobby ;] On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me that Satoshi - the Wraith - Asami remarked The same situation arises whether the version info is in /var/db/pkg or /some/other/place. It has been pointed out many times in the past that we need something to ensure bsd.port.mk can synchronize itself with the rest of the system (simply because there are too many people who cvsup one without the other). The question is, can I ask you to make sysinstall write some kind of version info that can be used by bsd.port.mk to identify the age of the system? This would require a little more work on the 'back' side, but what would be so hard about just checking $Id$ strings around the .mk files? If not for the revision, at least for the date. The problem is real, we've been bitten too many times in the past (haven't you seen all the where's fetch -A? and other more subtle Well, certainly, it's not always feasible, but I never understood this one in particular. It always seemed like a PERFECT candidate for an OSVERSION (or whatever) bump; certainly the 3.1+ only, since pre-3.1 didn't have the -A (3.1 didn't either, but that would cut out all the complaints from pre-3.1'ers). --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fulle...@futuresouth.com fulle...@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | The only reason I'm burning my candle at both ends, | *is because I haven't figured out how to light the* | middle yet | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Games
-Original Message- From: Daniel C. Sobral [SMTP:d...@newsguy.com] Sent: Thursday, April 01, 1999 1:14 PM To: Alexander Leidinger Cc: curr...@freebsd.org; tr49...@rcc.on.ca Subject: Re: Games Alexander Leidinger wrote: On 1 Apr, Daniel C. Sobral wrote: Well, first of all, .profile, .cshrc and signature scripts are broken in the absense of fortune. If I remember correctly .cshrc contains [ -x /usr/games/fortune ] ... so this shouldn't be an issue. Well, some people seem to be able to survive without fortune, but that's probably the exception to the rule... :-) [ML] Oh, I can live without fortune(6), but pom(6) was invaluable in software malfunction diagnosis: luser: My program fails when I do this or that. me: types pom No wonder, the moon is 73% full. /Marino -- Daniel C. Sobral (8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: booting systems with lots of memory
Mike Smith m...@smith.net.au wrote: Tony Finch d...@dotat.at wrote: [serial console problems] We suspect a BIOS that's being too damn clever for its own good. That sounds about right. If your BIOS on the Intel box is set for a serial console, you could try poking it again to make sure that it's set for 9600 bps and that the various 'magic' options relating to remote health monitoring are all off. That did turn out to be the problem. The memory has finally followed the box from here to the Docklands and we now have a machine with the following dmesg. We'll be trying it out under load in the near future. Tony. -- f.a.n.finch d...@dotat.at f...@demon.net Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #25: Mon Mar 29 14:38:45 BST 1999 r...@discord.news.demon.net:/usr/src/sys/compile/NCRXEON Timecounter i8254 frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = GenuineIntel Id = 0x653 Stepping=3 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,b24 real memory = 3221225472 (3145728K bytes) avail memory = 3133857792 (3060408K bytes) Programming 64 pins in IOAPIC #0 IOAPIC #0 intpint 38 - irq 17 IOAPIC #0 intpint 40 - irq 18 IOAPIC #0 intpint 41 - irq 15 IOAPIC #0 intpint 42 - irq 10 IOAPIC #0 intpint 44 - irq 7 IOAPIC #0 intpint 48 - irq 11 IOAPIC #0 intpint 49 - irq 16 IOAPIC #0 intpint 58 - irq 14 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 cpu2 (AP): apic id: 1, version: 0x00040011, at 0xfee0 cpu3 (AP): apic id: 2, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 4, version: 0x003f0013, at 0xfec1 Preloaded elf kernel kernel at 0xc02ea000. Probing for devices on PCI bus 0: ahc0: Adaptec aic7880 Ultra SCSI adapter rev 0x01 int a irq 14 on pci0.10.0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: Cirrus Logic GD5446 SVGA controller rev 0x00 int a irq 11 on pci0.12.0 chip0: Intel 82371AB PCI to ISA bridge rev 0x02 on pci0.15.0 No driver for device 0x71118086 at pci0:15:1 No driver for device 0x71128086 at pci0:15:2 chip1: Intel 82371AB Power management controller rev 0x02 on pci0.15.3 chip2: Intel 82451NX Memory and I/O Controller rev 0x03 on pci0.16.0 chip3: Intel 82454NX PCI Expander Bridge rev 0x02 on pci0.18.0 chip4: Intel 82454NX PCI Expander Bridge rev 0x02 on pci0.19.0 chip5: Intel 82454NX PCI Expander Bridge rev 0x02 on pci0.20.0 Probing for devices on PCI bus 1: ahc1: Adaptec 2940 Ultra SCSI adapter rev 0x00 int a irq 17 on pci1.4.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: Intel EtherExpress Pro 10/100B Ethernet rev 0x04 int a irq 18 on pci1.5.0 fxp0: Ethernet address 00:a0:c9:a4:85:bd chip6: DEC 21152 PCI-PCI bridge rev 0x03 on pci1.6.0 fpa0: Digital DEFPA PCI FDDI Controller rev 0x01 int a irq 7 on pci1.7.0 fpa0: DEC DEFPA PCI FDDI SAS Controller fpa0: FDDI address 00:00:f8:c9:91:56, FW=3.10, HW=0, SMT V7.2 fpa0: FDDI Port = S (PMD = Unshielded Twisted Pair) No driver for device 0x123d8086 at pci1:9:0 Probing for devices on PCI bus 2: de0: Digital 21140A Fast Ethernet rev 0x22 int a irq 10 on pci2.4.0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de0: address 00:e0:29:26:53:71 de1: Digital 21140A Fast Ethernet rev 0x22 int a irq 15 on pci2.5.0 de1: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de1: address 00:e0:29:26:53:70 Probing for devices on PCI bus 3: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, unlimited logging Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! de0: enabling 10baseT port de1: autosense failed: cable problem? pass2 at ahc0 bus 0 target 6 lun 0 pass2: ESG-SHV SCA HSBP M4 0.62 Fixed Processor SCSI-2 device pass2: 3.300MB/s transfers pass5 at ahc1 bus 0 target 6 lun 0 pass5: ESG-SHV SCA HSBP M4 0.62 Fixed Processor SCSI-2 device pass5: 3.300MB/s transfers da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST39102LC 0005 Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) da2 at ahc1 bus
Re: /var/db/pkg/.mkversion
* From: Matthew D. Fuller fulle...@futuresouth.com * [ Yes, I'm sticking my nose in where it probably doesn't belong and * should get chopped off for it. It's a hobby ;] Don't worry, I enjoy chopping off noses. :) * On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me * that Satoshi - the Wraith - Asami remarked What birdie? * This would require a little more work on the 'back' side, but what would * be so hard about just checking $Id$ strings around the .mk files? If * not for the revision, at least for the date. Which .mk files? Note that it's not bsd.port.mk's version we need -- we already have that. We need something on the system to compare against. * Well, certainly, it's not always feasible, but I never understood this * one in particular. It always seemed like a PERFECT candidate for an * OSVERSION (or whatever) bump; certainly the 3.1+ only, since pre-3.1 * didn't have the -A (3.1 didn't either, but that would cut out all the * complaints from pre-3.1'ers). That only works if the user recompiled the kernel, since that's where we're getting it from. (Or we can get it from sys/param.h but bsd.port.mk is not a compiler.) -W To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
I have to agree that the problem is real. However, let me point out that a one identifier solution is very short sided. There are two distinct environments to be considered. The HOST environment and the TARGET environment. For convience, we should also consider a TOOLSET environment which is a cross between the two. Just as it is wrong to use compiler variables like, __FreeBSD__ to control target compilations (except as a default), it is also wrong to do so for the ports. The group has come around to the idea that the files in /usr/include represent the HOST and not the TARGET. I suggest that you dig out my old proposal for tagging the HOST in /usr/include. The natural tag for the TARGET would be in /usr/src/include. However, I can see some problems with this for the ports tree. The more general mechanism allows us to register capabilities. (Shades of some commercial OS'es) However, we may not want to do things in such a unified manner :-) On Thu, 1 Apr 1999, Satoshi - the Wraith - Asami wrote: It has been pointed out many times in the past that we need something to ensure bsd.port.mk can synchronize itself with the rest of the system The question is, can I ask you to make sysinstall write some kind of version info that can be used by bsd.port.mk to identify the age of the system? The problem is real, we've been bitten too many times in the past (haven't you seen all the where's fetch -A? and other more subtle breakages that are caused by ports and system mismatch) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, 1 Apr 1999, Richard Wackerbarth wrote: I have to agree that the problem is real. However, let me point out that a one identifier solution is very short sided. There are two distinct environments to be considered. The HOST environment and the TARGET environment. For convience, we should also consider a TOOLSET environment which is a cross between the two. Just as it is wrong to use compiler variables like, __FreeBSD__ to control target compilations (except as a default), it is also wrong to do so for the ports. The group has come around to the idea that the files in /usr/include represent the HOST and not the TARGET. I suggest that you dig out my old proposal for tagging the HOST in /usr/include. The natural tag for the TARGET would be in /usr/src/include. However, I can see some problems with this for the ports tree. Richard, don't forget that having /usr/src isn't required to build ports. It seems a pretty draconian requirement to add. This is ports we're talking about, and nearly all of ports cannot build (as they are now) in cross-hosted environments. There's 2000 ports to consider, and the fix has to go in soon, not something for 2001. I would not be against changes in strategy for the longer run (and your ideas have merit for that view) but we need a short term fix here. +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make world fail with ctm src-cur.3809
Hello, I tried to update my system with ctm upto src-cur.3809 and found the following error. Can anyone help ? thanks. Clarence === Error === In file included from /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc:24: /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include/posix.h:25: osfcn.h: No such file or directory /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc: In function `void ewrite(const char *)': /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc:30: warning: implicit declaration of function `int write(...)' *** Error code 1 Stop. === Error === To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
* From: Richard Wackerbarth r...@dataplex.net * I have to agree that the problem is real. * However, let me point out that a one identifier solution is * very short sided. sighted : * There are two distinct environments to be considered. * The HOST environment and the TARGET environment. * For convience, we should also consider a TOOLSET * environment which is a cross between the two. (Rolling my eyes.) This issue has nothing to do with hosts and targets. The ports tree has never supported building ports on a system with a version other than the one that is going to run it. (And we don't intend to start doing it any time soon either, sorry. ;) -W To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Thu, Apr 01, 1999 at 11:55:23AM +0900, Daniel C. Sobral wrote: Brian Beattie wrote: writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. Once aic6[23]60 is working, the PCMCIA stuff is easily done. However, the sad fact is that the development is less than active on this driver. It is a fact, sad? Im not sure. except for the pccard stuff there is much better stuff than the 6x60 based hardware. But there are *no* alternatives for notebooks, except parallel port SCSI. This isn't true. The 3.0 version of Newtek's Bus Toaster uses a Symbios 53C500 chip. I think Newtek still makes them... Granted, we don't have a driver for that controller either, but the programming manual is readily available from LSI Logic. Seems to me that NetBSD has a driver for it, based on a Linux driver. (Been a while since I looked into it, so I may be misremembering.) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
latest bsd.port.mk and FETCH_CMD
With the latest changes to the bsd.port.mk, my local setting (in /etc/make.conf) of: FETCH_CMD=/usr/local/bin/runsocks /usr/bin/fetch -p is ignored. It uses the default /usr/bin/fetch, which does nto work for me... My setup worked fine back on Sunday, when I built the last port... -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, 1 Apr 1999, Chuck Robey wrote: On Thu, 1 Apr 1999, Richard Wackerbarth wrote: The natural tag for the TARGET would be in /usr/src/include. However, I can see some problems with this for the ports tree. Richard, don't forget that having /usr/src isn't required to build ports. I don't think that I did forget. I explicitly reference that situation. The real solution (re the TARGET) has to depend on something that the USER sets for a particular run. As such, it should be an environment variable which defaults to the HOST value. At the same time, the ports have to consider the purpose for which they need the identification. For example, fetch -A is a HOST/TOOLSET situation. But selecting the set of sysctls to compile into the code is a TARGET question. Nobody said cross compilation is easy :-) The simple solution for ports may be to build 3.1 packages on 3.1 machines and 4.0 packages only on 4.0 systems. In that case, TARGET == HOST and things are much easier. I still see nothing wrong with /usr/include for a place to store a tag about the HOST. Alternately, the traditional place would be /etc. The format of the tag should be considered. IMHO, it is best if we can have one knob which works for make, sh, and cc. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: latest bsd.port.mk and FETCH_CMD
* From: Mikhail Teterin m...@kot.ne.mediaone.net * With the latest changes to the bsd.port.mk, my local setting (in * /etc/make.conf) of: * FETCH_CMD=/usr/local/bin/runsocks /usr/bin/fetch -p * is ignored. It uses the default /usr/bin/fetch, which does nto work * for me... That's weird. The only change around that area was to add a comment. FETCH_CMD is still defined with a ?=, so your make.conf should take precedence. -W To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
In message 19990401052839.d11...@futuresouth.com, Matthew D. Fuller wrote: } [ Yes, I'm sticking my nose in where it probably doesn't belong and } should get chopped off for it. It's a hobby ;] } } On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me } that Satoshi - the Wraith - Asami remarked } } The same situation arises whether the version info is in /var/db/pkg } or /some/other/place. It has been pointed out many times in the past } that we need something to ensure bsd.port.mk can synchronize itself } with the rest of the system (simply because there are too many people } who cvsup one without the other). } } The question is, can I ask you to make sysinstall write some kind of } version info that can be used by bsd.port.mk to identify the age of } the system? } } This would require a little more work on the 'back' side, but what would } be so hard about just checking $Id$ strings around the .mk files? If } not for the revision, at least for the date. I think that's asking for trouble - it'll lose if someone keeps their .mk files in their own RCS (I do this for some files; admittedly not for the .mk files, but I could see someone doing that). -- Jon Hamilton hamil...@pobox.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, 1 Apr 1999, Satoshi - the Wraith - Asami wrote: * From: Richard Wackerbarth r...@dataplex.net * very short sided. sighted : Yes, a slight transfer error between my brain and 'sendmail'. * There are two distinct environments to be considered. * The HOST environment and the TARGET environment. This issue has nothing to do with hosts and targets. The ports tree has never supported building ports on a system with a version other than the one that is going to run it. (And we don't intend to start doing it any time soon either, sorry. ;) I recognize that. However, I bring it up because there are a number of programmers who still fail to recognize the distinction. I hope that we can get the rest (non-ports) of the build system into shape. Any solution for the ports should be one that also works elsewhere. As a result, I would hate to see yet another inadequate mechanism become entrenched. I don't think that ports ever stands a real chance in making it to cross compilation because too many of the components rely on autoconf style configuration. This often trys to decide which representation to use by trial and error. It is virtually impossible for you to police all those ports authors and have them maintain cross-compile compliance. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
On Thu, 1 Apr 1999, Rod Taylor wrote: Just out of curiosity, why are there games included in the FreeBSD source tree? For a group of people that was so worried about including dhcp because it's extra code, don't you think it's time to make those games into ports only? I say this under the assumption that they're not required for FreeBSD to function. (Not like IE for windows ;) As far as I am concerned, things like fortune, pom, pig and banner have been included with BSD-ish systems for ages... Tradition... I wouldn't feel the same if I didn't get my fortune every login. also, don't you have the option to not have the games? -Jason J. Horton ja...@intercom.com Senior Network Systems Engineer Intercom Online Inc. 212.378.2202 | http://www.intercom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
On Thu, 01 Apr 1999 10:43:51 EST, Jason J. Horton wrote: also, don't you have the option to not have the games? The problem with NOGAMES is that it strips things that some people consider useful. The diffs I posted earlier today (same subject line) rip out the games and leave behind the utilities, where words in quotes are subjective matters, and hence not worth discussing. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
Steven Plite wrote: But there are *no* alternatives for notebooks, except parallel port SCSI. This isn't true. The 3.0 version of Newtek's Bus Toaster uses a Symbios 53C500 chip. I think Newtek still makes them... I meant that there are no alternatives available in 3.x. Granted, we don't have a driver for that controller either, but the programming manual is readily available from LSI Logic. Seems to me that NetBSD has a driver for it, based on a Linux driver. (Been a while since I looked into it, so I may be misremembering.) It seems programming manuals for the AIC 6[23]60 are also available, and there is even a FreeBSD driver for it... :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
Sheldon Hearn wrote: On Thu, 01 Apr 1999 10:43:51 EST, Jason J. Horton wrote: also, don't you have the option to not have the games? The problem with NOGAMES is that it strips things that some people consider useful. The diffs I posted earlier today (same subject line) rip out the games and leave behind the utilities, where words in quotes are subjective matters, and hence not worth discussing. You stripped DM, which has it's uses. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, 1 Apr 1999, Richard Wackerbarth wrote: Richard, don't forget that having /usr/src isn't required to build ports. I don't think that I did forget. I explicitly reference that situation. The real solution (re the TARGET) has to depend on something that the USER sets for a particular run. As such, it should be an environment variable which defaults to the HOST value. At the same time, the ports have to consider the purpose for which they need the identification. For example, fetch -A is a HOST/TOOLSET situation. But selecting the set of sysctls to compile into the code is a TARGET question. Nobody said cross compilation is easy :-) Well, seeing as FreeBSD doesn't have control over the software involved, and nearly all the software involved is broken for the kind of portability you're talking about, this seems unreasonable. It's one thing for ports to adapt a particular piece of software to run on FreeBSD hosts, it's quite a different thing to make it cross-build, any to any. That would convert doing a port from being a reasonably short job, to being (for each port) a major rewrite project. Seeing the extreme fluidity of many ports, and the large number of ports, this sounds like a very unreal expectation. Your statement Nobody said cross compilation is easy :-), well, the work involved is huge, and the demand ... huh, you're the ONLY one to demand it. OK, maybe even demand is wrong, but you get the idea, that it's a lot of work for something that isn't seen as necessary. If you were talking about the FreeBSD sources themselves, everything I said is out the window, because we *do* have total control of those, and the change rate is under our purview. For ports, with that outside our control, and no established need, it seems excessive. Go adapt one of the gnome things, see how long it takes you to do *one* port with the features you seem to be requiring. If it's less than what I envision, perhaps you're getting what you want over badly, and seeing a port done as you want would be instructive to the rest of us. I think you're going to spend a *lot* of time doing that one port. +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
On 01-Apr-99 Sheldon Hearn wrote: On Thu, 01 Apr 1999 10:43:51 EST, Jason J. Horton wrote: also, don't you have the option to not have the games? The problem with NOGAMES is that it strips things that some people consider useful. The diffs I posted earlier today (same subject line) rip out the games and leave behind the utilities, where words in quotes are subjective matters, and hence not worth discussing. They aren't exactly huge either, my /usr/obj/usr/src/games only has 4 Meg in it, and that's including all the object files in addition to the executables. Ciao, Sheldon. --- John Baldwin jobal...@vt.edu -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Power Users Use the Power to Serve! - http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, 1 Apr 1999, Chuck Robey wrote: On Thu, 1 Apr 1999, Richard Wackerbarth wrote: Your statement Nobody said cross compilation is easy :-) By this smiley, I mean to infer that it is far from easy. you're the ONLY one to demand it. OK, maybe even demand is wrong If you were talking about the FreeBSD sources themselves, everything I said is out the window, because we *do* have total control I think that you have missed the entire point of what I am advocating. Within the ports Makefiles (and .mk), we DO have control. We SHOULD make certain that we do NOT REPEAT the past errors of using the wrong parameter when we CAN do it correctly. IOW, don't box the future development in by building a mechanism which works ONLY if HOST == TARGET. Provide a mechanism which can provide TARGET independent from HOST, but defaulting to the same value. In the code which we write for the FreeBSD tree, including /usr/ports, use the correct context. I ask this because the mechanism for ports SHOULD be the same mechanism that is used for OS builds. In the realm of OS building, I think that we are making progress toward cross build capability. I would hate to see this thing for ports be a step backward. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Adaptec 3950U2B Ver 2.11.0
Our hardware vendor, in an effort to save us PCI slot space, fitted us with a new 3950U2B instead of the old 3940 (no longer in production!) cards we were used to. All documents on FreeBSD.org say that FreeBSD 3.1 supports this card. However, /stand/sysinstall refuses to see it when I try to mount drives on the card. What's the status of the 3950U2B CAM driver? -- andy edmond After trying 3.1-REL, 3.1-STABLE and 3.0-REL it still won't see the second scsi card. I've built it with 3.1-REL on just the 4gb drive and will poke around in the mail lists and kernal configs to see if I can find a magic switch. sshd is running on it if you want to take a crack at it. The card is an Adaptec 3950U2B Ver 2.11.0 and is set for 80Mby transfer with 2 18Gby drives. The transfer of the Frontier feed to f0/0/0 took only about 3 minutes. The graphs show longer because I did the mrtg config changes after a smoke. It's 5:00AM now, I'm going home to get some more sleep and will be in this afternoon. -Joe *--* | Joe Hamelin |j...@nethead.comhttp://www.nethead.com | | Seattle WA USA | Without love in the dream it will never come true. | *--* -- Andrew N. EdmondS E X Chief Executive Officer presid...@sextracker.com T R A C K E R http://www.sextracker.com -- GET PAID BY SEXTRACKER!WINDOWS 95/98/NT STATISTICS http://moneytree.sextracker.com/ http://executive.sextracker.com/ BANNER EXCHANGE RANKS! DOWNLOAD SUPERBROWSER TODAY! http://stx.sextracker.com/ http://superbrowser.sextracker.com/ FREE CHAT FOR YOUR ADULT WEBSITE http://chatnet.sextracker.com/ FREE WEB HOSTING TODAY! http://www.sexspaces.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Dates off by 1 year (was: Fools Day Joke ?)
In article abypp0t...@itfs.nsk.su, Nickolay Dudorov n...@itfs.nsk.su wrote: There is some strangenes in date on file ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.5198.gz -r--r--r- 1 603 207 49741 apr 1 1998 cvs-cur.5198.gz I changed the subject because I think this may actually be a real bug somewhere. I happened to notice 2 days ago that some of the files in etinc's download area had dates exactly one year too old in this same way. I mentioned it to Dennis there, and he told me that the files had been created by a 2.2.7 machine onto a directory mounted via NFS from a 3.1 machine. The dates are set correctly on both machines, but the problem is reproduceable there. I haven't been able to duplicate it myself, but I suspect that it's a real bug. If anybody else is seeing similar problems, please speak up. And no, this message is not an April Fools joke. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: I think this entire thing is a massive botch and needs to be removed as a bad idea ASAP. I think that's jumping to conclusions a little too quickly. Jordan, we are eliminating a LOT more future PRs and FAQs by using this method. A few permission and installation oversights (no software can ever be tested on every possible instance.) should not constitute removal of the whole idea. - bill fumerola - bi...@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfume...@computerhorizons.com - bi...@freebsd.org - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dates off by 1 year (was: Fools Day Joke ?)
In the last episode (Apr 01), John Polstra said: In article abypp0t...@itfs.nsk.su, Nickolay Dudorov n...@itfs.nsk.su wrote: There is some strangenes in date on file ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.5198.gz -r--r--r- 1 603 207 49741 apr 1 1998 cvs-cur.5198.gz I changed the subject because I think this may actually be a real bug somewhere. I happened to notice 2 days ago that some of the files in etinc's download area had dates exactly one year too old in this same way. I mentioned it to Dennis there, and he told me that the files had been created by a 2.2.7 machine onto a directory mounted via NFS from a 3.1 machine. The dates are set correctly on both machines, but the problem is reproduceable there. I haven't been able to duplicate it myself, but I suspect that it's a real bug. If anybody else is seeing similar problems, please speak up. I've seen this too, on other FTP servers. I doubt it's an NFS problem, since there is no reason for NFS to add/subtract exactly one year from the date. FTP, on the other hand, doesn't have a standard way of passing a date to the client (MDTM isn't always implemented). I can imagine an FTP client (especially NcFTP which parses the LIST command itself) getting confused about a file that was created a couple hours in the future , due to the fact that FTP servers work in the local timezone, but FTP client's cant easily determine the timezone of the server. aha! I just tested this, with stock 3.1 /usr/bin/ftp and with NcFTP3.0b18. I touched a file with a date four hours into the future, connected to my FTP server, and tried to list it: ftp dir asdf 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. -rw-rw-r-- 1 dan 1000 0 Apr 1 22:00 asdf 226 Transfer complete. ftp ncftp /pub dir asdf -rw-rw-r-- 1 dan 10000 Apr 1 1998 asdf ncftp /pub So I'd say it's a bug in NcFTP's date parser. I'm willing to bet that Nickolay is also using NcFTP, since the 'group' column in his 'ls' output is right-justified, just like my ncftp output sample :) -Dan Nelson dnel...@emsphone.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dates off by 1 year (was: Fools Day Joke ?)
Dan Nelson wrote: I've seen this too, on other FTP servers. I doubt it's an NFS problem, since there is no reason for NFS to add/subtract exactly one year from the date. ... So I'd say it's a bug in NcFTP's date parser. Bingo! It looks like you're right. I noticed that the file's time was later than the current time, too (disregarding the year). I'm willing to bet that Nickolay is also using NcFTP I don't doubt that. But for me it happened using Netscape. Thanks for solving this mystery! John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
On Thu, 1 Apr 1999, Rod Taylor wrote: Just out of curiosity, why are there games included in the FreeBSD source tree? For a group of people that was so worried about including dhcp because it's extra code, don't you think it's time to make those games into ports only? I say this under the assumption that they're not required for FreeBSD to function. (Not like IE for windows ;) As far as I am concerned, things like fortune, pom, pig and banner have been included with BSD-ish systems for ages... Tradition... I wouldn't feel the same if I didn't get my fortune every login. also, don't you have the option to not have the games? It's not just a matter of turning them off though. A few of the games in the distro are trademark infringements. While the product I'm developing that uses FreeBSD doesn't have the games installed, it brought up the comment from our lawyers What else are they infringing on that we *are* using? (see trek, mille, boggle, tetris, wargames) Kevin To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Adaptec 3950U2B Ver 2.11.0
Andrew N. Edmond (Nero) wrote... Our hardware vendor, in an effort to save us PCI slot space, fitted us with a new 3950U2B instead of the old 3940 (no longer in production!) cards we were used to. All documents on FreeBSD.org say that FreeBSD 3.1 supports this card. However, /stand/sysinstall refuses to see it when I try to mount drives on the card. What's the status of the 3950U2B CAM driver? Well, the 3950 *is* supported, if you get one of the newer 3.1-STABLE or 4.0-CURRENT snapshots. I know this for a fact, since Justin used my 3950U2 to get things working a couple of weeks ago: ahc0: Adaptec 3950U2 Ultra2 SCSI adapter rev 0x00 int a irq 12 on pci0.10.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: Adaptec 3950U2 Ultra2 SCSI adapter rev 0x00 int a irq 12 on pci0.10.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs He checked support for that card into -stable on March 22nd/23rd, in revision 1.5.2.3 of sys/pci/ahc_pci.c, and revision 1.16.2.4 of sys/dev/aic7xxx/aic7xxx.c. The reason that the 3.1 release notes say that the 3950 is supported is that Justin has a prerelease 3950 board that works just fine. But, as it turns out, they changed the PCI ID and some of the features for the real 3950, so the kernel wouldn't recognize it. (for instance, his prerelease board has external SRAM, but my production 3950U2 does not) Anyway, you should be able to get things working if you get one of the post-March 23rd snapshots from here: ftp://releng3.FreeBSD.ORG/pub/FreeBSD/snapshots/i386 The board seems to work fine for me, but I've only got 4 narrow 2gig Seagate Hawks on it, so I'm hardly pushing it. After trying 3.1-REL, 3.1-STABLE and 3.0-REL it still won't see the second scsi card. I've built it with 3.1-REL on just the 4gb drive and will poke around in the mail lists and kernal configs to see if I can find a magic switch. sshd is running on it if you want to take a crack at it. The card is an Adaptec 3950U2B Ver 2.11.0 and is set for 80Mby transfer with 2 18Gby drives. The transfer of the Frontier feed to f0/0/0 took only about 3 minutes. The graphs show longer because I did the mrtg config changes after a smoke. It's 5:00AM now, I'm going home to get some more sleep and will be in this afternoon. Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
:It's not just a matter of turning them off though. A few of the games in the :distro are trademark infringements. While the product I'm developing that :uses FreeBSD doesn't have the games installed, it brought up the comment :from our lawyers What else are they infringing on that we *are* using? : :(see trek, mille, boggle, tetris, wargames) : :Kevin Tetris hasn't been in the distribution for a while. Your lawyers need a dose of reality if they think the existance of the other games in a distribution could ever come back to haunt you or your company. Tell them to screw their heads on straight and try again. If your really worried, just delete them. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Games
:It's not just a matter of turning them off though. A few of the games in the :distro are trademark infringements. While the product I'm developing that :uses FreeBSD doesn't have the games installed, it brought up the comment :from our lawyers What else are they infringing on that we *are* using? : :(see trek, mille, boggle, tetris, wargames) : :Kevin Tetris hasn't been in the distribution for a while. Oops, i did an 'ls /usr/games' on a machine that's been around since 2.2.2. Ok, forget tetris. Your lawyers need a dose of reality if they think the existance of the other games in a distribution could ever come back to haunt you or your company. Tell them to screw their heads on straight and try again. If your really worried, just delete them. That wasn't really the issue though. It's that FreeBSD is infringing on trademarks in the games distribution, so what's to make them think that the vm system isn't an infringement? (i.e. They're the type of people who don't care about trademarks/copyrights. How can we trust this code?) It also probably doesn't help things that i'm working for a video game company. /usr/games is deleted here, anyway. :) Kevin To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
WORM CAM CD
Has the worm driver been taken out of current? If so does the CAM CD driver handle ATAPI CD-Rs or what is the new way of doing it? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
On Mon, Mar 29, 1999 at 06:34:27AM -0500, Brian Feldman wrote: Doc is a nice format, but it's not hypertext. Check out ports/palm/pilot_makedoc TealDoc's version supports graphics and links. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 1998 www.anime-expo.org/ # Redline Games www.redlinegames.com/ # Cal-Animage Epsilon www.best.com/~nugundam/epsilon/ # EX: The Online World of Anime Manga www.ex.org/ / To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
On Thu, 1 Apr 1999, Joseph T. Lee wrote: On Mon, Mar 29, 1999 at 06:34:27AM -0500, Brian Feldman wrote: Doc is a nice format, but it's not hypertext. Check out ports/palm/pilot_makedoc TealDoc's version supports graphics and links. Is it a published format, though? I know TealDoc is $$$, but the format must be open for it to be worth it to us Palm users. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 1998 www.anime-expo.org/ # Redline Games www.redlinegames.com/ # Cal-Animage Epsilon www.best.com/~nugundam/epsilon/ # EX: The Online World of Anime Manga www.ex.org/ / To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: WORM CAM CD
Smelly Pooh wrote... Has the worm driver been taken out of current? Yes. You have to use cdrecord now for SCSI CD burners. If so does the CAM CD driver handle ATAPI CD-Rs or what is the new way of doing it? No, you need to use the IDE/ATAPI CDROM driver. wormcontrol will talk to that driver. Ask Soren Schmidt s...@freebsd.org if you want more information on it.. Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, Apr 01, 1999 at 02:22:57PM -0500, Bill Fumerola wrote: On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: I think this entire thing is a massive botch and needs to be removed as a bad idea ASAP. I think that's jumping to conclusions a little too quickly. Jordan, we are eliminating a LOT more future PRs and FAQs by using this method. A few permission and installation oversights (no software can ever be tested on every possible instance.) should not constitute removal of the whole idea. At minimum, the implementation is off... What /var/db/pkg/.mkversion is tracking w/ the current implementation it the date of the last _installation_ of the make files... Wouldn't just a MKPKG_VERSION=xxyyzz inside of the relevant make file work easier? What's _really_ trying to be accomplished w/ .mkversion? Tracking the version/date of the make binary, of the full set of share/mk files, of just the ports related makefiles? William R. Somsky wrsom...@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
netscape: no recognized font
% netscape no recognized font charsets! 3.1-stable as of today navigator 4.5 freshly installed randy To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
