rare invitation
http://members.madasafish.com/~lukefictitious/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: path_mtu_discovery
-Original Message- From: Crist J. Clark [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 06, 2002 02:39 To: Leo Bicknell Cc: Rogier R. Mulhuijzen; [EMAIL PROTECTED] Subject: Re: path_mtu_discovery [snip] I'd support it if anyone actually has any credible evidence that such attacks have ever occured. Or if there is are plausible ways to attack that don't require someone to sniff and inject into a connection in which the victim is participating (if you can do that, you can do much worse). The original message of the old thread mentioned: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=4186+0+archive/2001/freebsd-sec urity/20010715.freebsd-security Darren Reed's post to BugTraq implied, IIRC, that an attacker can kill (or slow down) a server if he requests a large file with low MSS. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Should pam_ssh and xdm work?
Hi,
I have my xdm+pam_ssh running as I expected, with following patch
applied to xdm:
Index: programs/xdm/session.c
===
RCS file: /export/cvsup-xfree86/cvs/xc/programs/xdm/session.c,v
retrieving revision 3.33
diff -u -r3.33 session.c
--- programs/xdm/session.c 14 Dec 2001 20:01:23 - 3.33
+++ programs/xdm/session.c 15 Dec 2001 12:35:52 -
@@ -534,6 +534,7 @@
intpid;
#ifdef HAS_SETUSERCONTEXT
struct passwd* pwd;
+extern char **environ;
#endif
#ifdef USE_PAM
pam_handle_t *pamh = thepamh();
@@ -613,6 +614,8 @@
* Set the user's credentials: uid, gid, groups,
* environment variables, resource limits, and umask.
*/
+/* destroy user environment before calling setusercontext */
+ environ = verify-userEnviron;
pwd = getpwnam(name);
if (pwd)
{
@@ -622,6 +625,7 @@
errno);
return (0);
}
+verify-userEnviron = environ;
endpwent();
}
else
The diff is against the head of XFree86 CVS tree.
I hope it works for you.
--
さねを (SANETO Takanori) // [趣味] 本業をすること //
・・・・・・・・・・・・・・・・・ //Bonjour Chapeau //
URL:mailto:[EMAIL PROTECTED] // [本業] 趣味に走ること //
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Tell gcc I have a i686
On 06-Jan-02 Stephen Montgomery-Smith wrote: Matthew D. Fuller wrote: On Fri, Jan 04, 2002 at 12:02:03PM -0600 I heard the voice of Stephen Montgomery-Smith, and lo! it spake thus: I want to create a Makefile for a C program that includes some Pentium II specific inline assembler code. How do I tell the compiler whether we are compiling on a i686? Dunno, how well will your Pentium II specific inline assembler code run on my Pentium Pro? You know, I have no idea. It is someone elses code. These are the instructions. Can anyone tell me? movl 32(%0),%1\n adcl %1,32(%0)\n Also, from this discussion, what I have decided to do is provide it as an option for the user to add by editing the Makefile - not to do it automatically. These instructions are 386 instructions. What we need to see are the contraints (the stuff after the actual instructions with colons in them) to see if it is somehow using Pentium Pro+ specific registers. And actually, just for the record, a PPro is a 686. :) It claims to be family 6 via cpuid at least. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tell gcc I have a i686
John Baldwin wrote: You know, I have no idea. It is someone elses code. These are the instructions. Can anyone tell me? movl 32(%0),%1\n adcl %1,32(%0)\n Also, from this discussion, what I have decided to do is provide it as an option for the user to add by editing the Makefile - not to do it automatically. These instructions are 386 instructions. What we need to see are the contraints (the stuff after the actual instructions with colons in them) to see if it is somehow using Pentium Pro+ specific registers. And actually, just for the record, a PPro is a 686. :) OK, this is it in context: register Word32 *_x = x; register int _a = 0; asm(xorl %1,%1\n /* clear C */ movl 124(%0),%1\n adcl %1,124(%0)\n : : r (_x), r (_a) ); -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tell gcc I have a i686
On 07-Jan-02 Stephen Montgomery-Smith wrote: John Baldwin wrote: You know, I have no idea. It is someone elses code. These are the instructions. Can anyone tell me? movl 32(%0),%1\n adcl %1,32(%0)\n Also, from this discussion, what I have decided to do is provide it as an option for the user to add by editing the Makefile - not to do it automatically. These instructions are 386 instructions. What we need to see are the contraints (the stuff after the actual instructions with colons in them) to see if it is somehow using Pentium Pro+ specific registers. And actually, just for the record, a PPro is a 686. :) OK, this is it in context: register Word32 *_x = x; register int _a = 0; asm(xorl %1,%1\n /* clear C */ movl 124(%0),%1\n adcl %1,124(%0)\n : : r (_x), r (_a) ); Looks like rather silly code to double the value at x + 124. I say silly casue it clears carry and then does a addcl. However, since CF is zero, this is the same as doing an addl. Since it is just doubling the value, a shl would make more sense (and only be 1 instruction.) -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tell gcc I have a i686
John Baldwin wrote: On 07-Jan-02 Stephen Montgomery-Smith wrote: John Baldwin wrote: You know, I have no idea. It is someone elses code. These are the instructions. Can anyone tell me? movl 32(%0),%1\n adcl %1,32(%0)\n Also, from this discussion, what I have decided to do is provide it as an option for the user to add by editing the Makefile - not to do it automatically. These instructions are 386 instructions. What we need to see are the contraints (the stuff after the actual instructions with colons in them) to see if it is somehow using Pentium Pro+ specific registers. And actually, just for the record, a PPro is a 686. :) OK, this is it in context: register Word32 *_x = x; register int _a = 0; asm(xorl %1,%1\n /* clear C */ movl 124(%0),%1\n adcl %1,124(%0)\n : : r (_x), r (_a) ); Looks like rather silly code to double the value at x + 124. I say silly casue it clears carry and then does a addcl. However, since CF is zero, this is the same as doing an addl. Since it is just doubling the value, a shl would make more sense (and only be 1 instruction.) More likely I am butchering the code by trying to only give you part of it. The whole code is designed to take N 32 bit words and do a left shift on it: register Word32 *_x = x; register int _a = 0; asm(xorl %1,%1\n /* clear C */ movl (%0),%1\n adcl %1,(%0)\n #if (N = 2) movl 4(%0),%1\n adcl %1,4(%0)\n #endif #if (N = 3) movl 8(%0),%1\n adcl %1,8(%0)\n #endif #if (N = 4) movl 12(%0),%1\n adcl %1,12(%0)\n #endif #if (N = 5) movl 16(%0),%1\n adcl %1,16(%0)\n #endif #if (N = 6) movl 20(%0),%1\n adcl %1,20(%0)\n #endif #if (N = 7) movl 24(%0),%1\n adcl %1,24(%0)\n #endif #if (N = 8) movl 28(%0),%1\n adcl %1,28(%0)\n #endif #if (N = 9) movl 32(%0),%1\n adcl %1,32(%0)\n #endif #if (N = 10) movl 36(%0),%1\n adcl %1,36(%0)\n #endif #if (N = 11) movl 40(%0),%1\n adcl %1,40(%0)\n #endif #if (N = 12) movl 44(%0),%1\n adcl %1,44(%0)\n #endif #if (N = 13) movl 48(%0),%1\n adcl %1,48(%0)\n #endif #if (N = 14) movl 52(%0),%1\n adcl %1,52(%0)\n #endif #if (N = 15) movl 56(%0),%1\n adcl %1,56(%0)\n #endif #if (N = 16) movl 60(%0),%1\n adcl %1,60(%0)\n #endif #if (N = 17) movl 64(%0),%1\n adcl %1,64(%0)\n #endif #if (N = 18) movl 68(%0),%1\n adcl %1,68(%0)\n #endif #if (N = 19) movl 72(%0),%1\n adcl %1,72(%0)\n #endif #if (N = 20) movl 76(%0),%1\n adcl %1,76(%0)\n #endif #if (N = 21) movl 80(%0),%1\n adcl %1,80(%0)\n #endif #if (N = 22) movl 84(%0),%1\n adcl %1,84(%0)\n #endif #if (N = 23) movl 88(%0),%1\n adcl %1,88(%0)\n #endif #if (N = 24) movl 92(%0),%1\n adcl %1,92(%0)\n #endif #if (N = 25) movl 96(%0),%1\n adcl %1,96(%0)\n #endif #if (N = 26) movl 100(%0),%1\n adcl %1,100(%0)\n #endif #if (N = 27) movl 104(%0),%1\n adcl %1,104(%0)\n #endif #if (N = 28) movl 108(%0),%1\n adcl %1,108(%0)\n #endif #if (N = 29) movl 112(%0),%1\n adcl %1,112(%0)\n #endif #if (N = 30) movl 116(%0),%1\n adcl %1,116(%0)\n #endif #if (N = 31) movl 120(%0),%1\n adcl %1,120(%0)\n #endif #if (N = 32) movl 124(%0),%1\n adcl %1,124(%0)\n #endif : : r (_x), r (_a) ); -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tell gcc I have a i686
On 07-Jan-02 Stephen Montgomery-Smith wrote: John Baldwin wrote: On 07-Jan-02 Stephen Montgomery-Smith wrote: John Baldwin wrote: You know, I have no idea. It is someone elses code. These are the instructions. Can anyone tell me? movl 32(%0),%1\n adcl %1,32(%0)\n Also, from this discussion, what I have decided to do is provide it as an option for the user to add by editing the Makefile - not to do it automatically. These instructions are 386 instructions. What we need to see are the contraints (the stuff after the actual instructions with colons in them) to see if it is somehow using Pentium Pro+ specific registers. And actually, just for the record, a PPro is a 686. :) OK, this is it in context: register Word32 *_x = x; register int _a = 0; asm(xorl %1,%1\n /* clear C */ movl 124(%0),%1\n adcl %1,124(%0)\n : : r (_x), r (_a) ); Looks like rather silly code to double the value at x + 124. I say silly casue it clears carry and then does a addcl. However, since CF is zero, this is the same as doing an addl. Since it is just doubling the value, a shl would make more sense (and only be 1 instruction.) More likely I am butchering the code by trying to only give you part of it. The whole code is designed to take N 32 bit words and do a left shift on it: Ok. This isn't 686 specific at all. However, one optimization might be to get rid of the xorl, and use 'addl' for the first instruction instead of adcl. Anyways, If I were you, I would do it via a series of rcl (rotate through carry left, it shits in the carry flag instead of 0), thus I would do: shl (%0),1\n #if (N = 2) rcl 4(%0),1\n #endif etc. using a single rcl for the rest of the shifts. Using multiple instructions might be useful if you did multiple loads to different destination registers by interleaving movl's and adcl's, and alternating temporary registers to try and use the multiple pipelines on Pentiums and better. Then again, these instructions might not work well for that. *shrug* Or perhaps if it uses suitable temporary registers, this might be doing all the loads in one pipeline and the adcl's in the others to get a jumpstart on each mov. I dunno. :-P -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tell gcc I have a i686
On 07-Jan-02 John Baldwin wrote: Ok. This isn't 686 specific at all. However, one optimization might be to get rid of the xorl, and use 'addl' for the first instruction instead of adcl. Anyways, If I were you, I would do it via a series of rcl (rotate through carry left, it shits in the carry flag instead of 0), thus I would do: Erm, it shifts in the carry flag. CPU's usually don't go around abusing their flags like that. :-P -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Oh my god, Google has a USENET archive going back to 1981!
Oh my god. I don't even *remember* writing this one! This was when I was 18. Google's archive isn't complete but they've done an incredible job getting as much as they have. Pet, C64, DMail, Shell (for the amiga), backup/restore utilities, dme, dterm, AmigaUUCP, DICE, etc. It's all there in bits and pieces, complete with my trademark spelling errors. -Matt :Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP :Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA :From: [EMAIL PROTECTED] (The Sherif Matt D.) :Newsgroups: net.micro.cbm :Subject: Misc. Discussion 1541/2031/4040/2040 :Message-ID: [EMAIL PROTECTED] :Date: Sat, 29-Dec-84 16:29:38 EST :Article-I.D.: ucbvax.3957 :Posted: Sat Dec 29 16:29:38 1984 :Date-Received: Sat, 29-Dec-84 20:04:09 EST :Distribution: net :Organization: University of California at Berkeley :Lines: 73 : : : :Let me tell you a story about these drives. The first, the 2040, is a :duel drive whos age is beyond counting. At one point commodore decided :that the 2040 format was creating errors (It had one extra sector on :several tracks). So, they modified the format slightly by taking out that :sector. That is why the OLD 2040 has more storage than the NEW 1541/2031/ :4040. Now, Commodore tells us that the 1541, 2031, and 4040 have the same :disk format. Bryce pointed out to me one day as we were muling over the :hundreds of errors (not to mention the bad programming style) of the 1541 :DOS, that the 4040 uses a different spacing between sectors. Oh JUST GREAT... :I suggest that to keep read errors at a minimum, you not write on a disk :using a 1541 that was formatted on a 4040. : :Guess what! Commodore did not write a new DOS for the 1541 or the 2031. :In fact, the used the 4040's DOS and attempted to take out all the references :to the second drive. Well, they just didn't get them all and that is why :you get that DRIVE NOT READY error sometimes. Their @replace bug was a :classic, and that was one of the first thing Bryce fixed in his 1541 FLASH. : :But the story does not end there. Word has it that two people worked on :the original DOS for the 1541/2031/4040/2040. One wrote the drive interface, :and one wrote the communications protocal. Word also has it that the two :hardly confered with each other at all... Hence the slowness of drive. : :You have to be an expert on 6502 to be able to understand the drive's DOS, :considering how lousy the guy programmed it. Why commodore used a modem- :speed interface with an intelligent disk drive I could not guess. : :I myself am a PET person. The best transfer speed I've been able to come :up with a PET 2031 has been 53KBytes/sec ... With sector loading, I've :been able to get a skew factor of 3 and a 130 block load in 6.5 sec. Bryce :has been able to turn the rinky-dink serial interface into exactly the same :speed... Were both stuck on the skew factor. I think that's pretty good :considering the controller Commodore used for the disk (It consists of a :micro-processor, 2K RAM, 16K ROM, and 2 6522's. None of these, by the way, :are dedicated as a floppy controller). : :And now we come to the (quote unquote) Build in RS-232C. The C64 does it all :in software, and the outputs are +5/GND rather than standard -12/12V. Baud :rates below 2400 work fine. Anything after that will not work well unless :you do it by hand. Commodore has this nack of putting everything on the :interrupt, you see; They put the disk-controller of the 1541... on the :interrupt. I'm not kidding, to request a sector you wrote some crap into :some memory and had to wait for a timer interupt to occur before the :interrupt service routine would catch it and get/write the sector. In :anycase, I'm getting off the subject; Commodore has the modem on the :interrupt. So as long as you don't use the disk drive or printer, you :can use the modem. You can either recieve or transmit (but not both at :the same time). In other words, commodore blew it again in terms of the :C64. : : :You might ask if there is anything good about the commodore 64. Well, the :graphics are good and the sound is fantastic. Don't let anyone tell you :the sound is the pits... I've heard very un-computer like voice synthesis :using only that single solitary SID. The graphics are good, considering :that the C64 is only a small home computer. I particulary like the raster :interrupt which makes it all worth while. You probably have heard that at :any time the graphics chip can take 40cc from the processor. Well, using :the raster interrupt, Bryce was able to sync the two and to a VERY FAST :trasfer over the original serial lines sync'd with the drive to within :3cc (On my PET, I used to use a single sync signal to sync the block transfers, :Giving me a 32KByte/sec ifc with 8cc tolerances. Bryce suggested a double :sync to sync the sync, so to speak, which is why I can do 56KBytes/sec over
IPSEC with Cisco VPN 3000?
Has anybody successfully set up IPSEC between a FreeBSD box (I am using 4.3-STABLE) and a Cisco VPN 3000 concentrator? The Cisco wants a group name and group password, and I can't tell how this maps to the racoon implementation of IKE keys. Thanks. -Guy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Tell gcc I have a i686
On Fri, Jan 04, 2002 at 12:02:03PM -0600 I heard the voice of Stephen Montgomery-Smith, and lo! it spake thus: I want to create a Makefile for a C program that includes some Pentium II specific inline assembler code. How do I tell the compiler whether we are compiling on a i686? [lots of snippage] Did this original question ever get answered? I think what you need is just -mcpu=i686 on the (g)cc command line. Or, given that other discussion seemed to indicate that a 686 isn't needed for these instructions, -mcpu=pentiumpro should do it. If there's any chance the code needs to run on older CPUs, go for the lower setting, as I believe this option affects the overall codegen and optimization. -- Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
On 2002-01-07 13:28 -0800, Matthew Dillon [EMAIL PROTECTED] wrote: Oh my god. I don't even *remember* writing this one! This was when I was 18. Google's archive isn't complete but they've done an incredible job getting as much as they have. Yes, Google is indeed great. Now everyone can go back and find my first USENET posting, which was to alt.life.sucks. Sigh. :) Greg -- Gregory S. Sutter My reality check just bounced. mailto:[EMAIL PROTECTED] http://www.zer0.org/~gsutter/ hkp://wwwkeys.pgp.net/0x845DFEDD msg30772/pgp0.pgp Description: PGP signature
Re: IPSEC with Cisco VPN 3000?
Hi Has anybody successfully set up IPSEC between a FreeBSD box (I am using 4.3-STABLE) and a Cisco VPN 3000 concentrator? The Cisco wants a group name and group password, and I can't tell how this maps to the racoon implementation of IKE keys. They have a linux client available for download if you have CCO access (and access to download 3DES software from them). That might give you some answers. Not sure if you can connect as a vpngroup member without their client. http://www.cisco.com/warp/public/707/index.shtml#vpn3000 might be worth a read, with the index at http://www.cisco.com/warp/public/707/index.shtml. Regards --Rob To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: Oh my god, Google has a USENET archive going back to 1981!
Oooohh!! Those model numbers bring back memories!! I remember drooling over the first Commodore Pet (the one with the rectangular keyboard) in one of the many computer shops that were springing up at the time. If anyone's interested, I've got a 2nd edition of Nick Hampshire's 'The Pet Revealed' --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.313 / Virus Database: 174 - Release Date: 02/01/02 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: path_mtu_discovery
On Mon, Jan 07, 2002 at 01:57:26PM +0200, Yonatan Bokovza wrote: -Original Message- From: Crist J. Clark [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 06, 2002 02:39 To: Leo Bicknell Cc: Rogier R. Mulhuijzen; [EMAIL PROTECTED] Subject: Re: path_mtu_discovery [snip] I'd support it if anyone actually has any credible evidence that such attacks have ever occured. Or if there is are plausible ways to attack that don't require someone to sniff and inject into a connection in which the victim is participating (if you can do that, you can do much worse). The original message of the old thread mentioned: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=4186+0+archive/2001/freebsd-sec urity/20010715.freebsd-security Darren Reed's post to BugTraq implied, IIRC, that an attacker can kill (or slow down) a server if he requests a large file with low MSS. I took part in that discussion and there was no mention of real exploits. And TCP MSS is not the same thing as the PMTU (though they can be related). As I pointed out in that thread, there are much more devistating TCP attacks to worry about that are still threats like Daytona attacks. -- It's always funny until someone gets hurt. Then it's hilarious. Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Issues with /stand sysinstall
Tried -questions, no response. Verified issue on 4.5 PRERELEASE. Going to /usr/src/release/sysinstall and doing make all make install builds a sysinstall which seems not to include the functionality needed to run as /stand/sh, /stand/fsck and friends. What is the correct way to build and install all of /stand? /\/\ \/\/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: Issues with /stand sysinstall
On 07-Jan-02 Michael R. Wayne wrote: Tried -questions, no response. Verified issue on 4.5 PRERELEASE. Going to /usr/src/release/sysinstall and doing make all make install builds a sysinstall which seems not to include the functionality needed to run as /stand/sh, /stand/fsck and friends. What is the correct way to build and install all of /stand? As part of the release process. It's a bit tricky. :) In current sysinstall has moved to src/usr.sbin/sysinstall and lives in /usr/sbin/sysinstall since it's just another program. /stand is basically copied off the boot floppy or CD during the installation process. It's meant to basically be a safety net in case you hose your filesystem so badly you don't have /bin/sh, etc. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
Danny Horne wrote: Oooohh!! Those model numbers bring back memories!! I remember drooling over the first Commodore Pet (the one with the rectangular keyboard) in one of the many computer shops that were springing up at the time. Drool away, buddy! Here's mine, and it still works (chicklet keyboard, built in cassette drive, metal filing cabinet company case,40 character BW monitor, and all): PET 2001-8 SN: 0031620 I have some of the original flyers for the PET and CBM boxes, as well as the yellow folded 4 page 8x11 BASIC Reference sheet, too... Space Invaders Anyone? 8-) 8-) If anyone's interested, I've got a 2nd edition of Nick Hampshire's 'The Pet Revealed' Now that's tempting -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
On Mon, Jan 07, 2002 at 04:26:54PM -0800, Terry Lambert wrote: Danny Horne wrote: Oooohh!! Those model numbers bring back memories!! I remember drooling over the first Commodore Pet (the one with the rectangular keyboard) in one of the many computer shops that were springing up at the time. Drool away, buddy! Here's mine, and it still works (chicklet keyboard, built in cassette drive, metal filing cabinet company case,40 character BW monitor, and all): PET 2001-8 SN: 0031620 I have some of the original flyers for the PET and CBM boxes, as well as the yellow folded 4 page 8x11 BASIC Reference sheet, too... Space Invaders Anyone? 8-) 8-) If anyone's interested, I've got a 2nd edition of Nick Hampshire's 'The Pet Revealed' Now that's tempting Heh. And 386's seem ancient to me. I really *was* born 10 years too late. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
On Mon, 7 Jan 2002, Terry Lambert wrote: Space Invaders Anyone? 8-) 8-) Does that just have LAN support, or does it support internet play too? I forgot when they made that transition... Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
In a message dated 01/07/2002 7:32:36 PM Eastern Standard Time, [EMAIL PROTECTED] writes: Drool away, buddy! Here's mine, and it still works (chicklet keyboard, built in cassette drive, metal filing cabinet company case,40 character BW monitor, and all): PET 2001-8 SN: 0031620 I have some of the original flyers for the PET and CBM boxes, as well as the yellow folded 4 page 8x11 BASIC Reference sheet, too... Space Invaders Anyone? 8-) 8-) Think they have the code to the C64 supermon assembler? I spend 3 evenings poking it in from Compute! and now I can't find the cassette anywhere. db To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
[moved to -chat] On Monday, 7 January 2002 at 21:21:54 -0500, [EMAIL PROTECTED] wrote: In a message dated 01/07/2002 7:32:36 PM Eastern Standard Time, [EMAIL PROTECTED] writes: Drool away, buddy! Here's mine, and it still works (chicklet keyboard, built in cassette drive, metal filing cabinet company case,40 character BW monitor, and all): PET 2001-8 SN: 0031620 I have some of the original flyers for the PET and CBM boxes, as well as the yellow folded 4 page 8x11 BASIC Reference sheet, too... Space Invaders Anyone? 8-) 8-) Think they have the code to the C64 supermon assembler? I spend 3 evenings poking it in from Compute! and now I can't find the cassette anywhere. Why not search for it? I got 35 hits on +c64 +supermon. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
Does that just have LAN support, or does it support internet play too? I forgot when they made that transition... If it even has LAN support, you should be able to play it over the internet. Just get creative with vtun, tap and ng_bridge =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
sound files
anyone knows how to get free sound files or record sound in FreeBSD? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
On Mon, Jan 07, 2002 at 01:45:23PM -0800, Gregory Sutter wrote: On 2002-01-07 13:28 -0800, Matthew Dillon [EMAIL PROTECTED] wrote: Oh my god. I don't even *remember* writing this one! This was when I was 18. Google's archive isn't complete but they've done an incredible job getting as much as they have. Yes, Google is indeed great. Now everyone can go back and find my first USENET posting, which was to alt.life.sucks. Sigh. :) Yea, but aren't you STILL posting to alt.life.sucks? I'v move on to alt.freebsd.rocks.microsoft.sucks ;-) Josef -- Josef Grosch | Another day closer to a | FreeBSD 4.4 [EMAIL PROTECTED] | Micro$oft free world | www.bafug.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
[EMAIL PROTECTED] wrote: Think they have the code to the C64 supermon assembler? I spend 3 evenings poking it in from Compute! and now I can't find the cassette anywhere. I have that somewhere. I also have the Compute! with it in it. 8-). If you want to download it, you can get it from here: http://www.ffd2.com/fridge/programs/supermon.s I also have Aztec C for the C64. I'd give you a copy, but that would violate the license, since mine's paid for... 8^p. http://www.ffd2.com/fridge/ Is a pretty good C64 resource... see also: http://www.funet.fi/pub/cbm/ ...it has all the Waterloo stuff, among other things (schematics, ROM firmware images, etc.). BASIC, FORTAN, Pascal, APL, COBOL... 8-) 8-) -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
In article [EMAIL PROTECTED], Danny Horne [EMAIL PROTECTED] writes Oooohh!! Those model numbers bring back memories!! I remember drooling over the first Commodore Pet (the one with the rectangular keyboard) in one of the many computer shops that were springing up at the time. When my school bought its 3016 (1980?) it was a revelation. I had seen the big orange ICL mainframe where my dad worked, a room full of big cabinets and whirring disks tapes, but this was a computer on a desk! If anyone's interested, I've got a 2nd edition of Nick Hampshire's 'The Pet Revealed' That, and Zaks' book on programming the 6502, certainly fuelled my enthusiasm and many hours with a switch connected to the NMI line and the MLM. I'm still fascinated by computer schematics, and dabbling with the hardware. ;-) Thankfully Google is missing many of my early postings. Tony To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
In message: [EMAIL PROTECTED] Josef Grosch [EMAIL PROTECTED] writes: : Yea, but aren't you STILL posting to alt.life.sucks? I'v move on to : alt.freebsd.rocks.microsoft.sucks /me does all his popsting in alt.freebsd.daemon.daemon.daemon these days. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
On Mon, Jan 07, 2002 at 06:52:52PM +, Mike Silbersack wrote: On Mon, 7 Jan 2002, Terry Lambert wrote: Space Invaders Anyone? 8-) 8-) Does that just have LAN support, or does it support internet play too? I Internet?? UUCP dialup please ;-) ..!mcvax!philapd!wilko :-) I just found out that my first posting in Oct 89 is about the GNU project. Go figure. In those days I built my own SWTPc/09 clone system, running TSC FLEX and later TSC UniFlex. I still have it! Started off with 2 floppys, later grew a Miniscribe 3012, 10Mb @ 155ms average access time. 1Mbyte RAM. Motorola 6809 at 2 MHz. 2 years ago it still ran (OK, it blew a electrolytic cap in the HD power supply but that was an easy fix). 8) W/ -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
