00:00:00 --- log: started forth/01.10.26 00:44:20 --- quit: aaronl (Read error to aaronl[vitelus.com]: EOF from client) 00:54:41 --- quit: MrReach (Read error to MrReach[209.181.43.190]: Connection reset by peer) 09:19:21 --- join: tcn (tcn@bespin.org) joined #forth 09:19:53 --- quit: tcn ([BX] The Spice Girls use BitchX (instead of underwear and talent)) 12:00:51 --- join: Guest (Guest@pc58-239.lib.ucalgary.ca) joined #forth 12:01:12 --- nick: Guest -> blak 12:01:48 --- quit: blak (Leaving) 12:51:07 --- join: futhin (kla@h24-66-209-114.cg.shawcable.net) joined #forth 12:52:15 --- join: Speuler (ls@d77243.upc-d.chello.nl) joined #forth 12:52:21 g'day 12:52:36 good day 12:52:39 how's it going? 12:52:42 hi futhin 12:52:47 not so bad at all 12:52:54 weekend mood 12:52:54 how is the internet cafe going? 12:53:01 just sitting here 12:53:21 heh 12:53:23 same 12:53:24 still looking for a reasonable bootp client 12:53:40 found an eprom programmer 12:53:51 hmm? bootp for what purpose? 12:53:52 need a ne2k bootrom image 12:54:12 to boot workstations from net 12:54:22 from bootp server 12:54:47 why would you want to do that? to keep the workstatsions consistent and the same across all workstations? 12:54:52 floppy might do for the moment too, but can't decide which client program 12:55:01 single floppy linux f.e. 12:55:10 f.e? 12:55:14 to get rid of the harddisks 12:55:17 for example 12:55:23 hmm 12:55:42 i looked at some but can't make up my mind 12:56:02 so you want the bootp client for the internet cafe? 12:56:52 the owner wants to replace the existing pcs against diskless x terminals 12:57:25 Linu Router Project looks dead 12:57:40 i heard and read about linux for terminal project 12:57:52 why not get dumb terminals or "x terminals" and have a server and a backup server? 12:58:06 and there are some more single floppy linux distrib 12:58:29 but i don't know which one i can just stick on a floppy, to negotatiate boot with the bootp server 12:58:42 do you know ? 12:59:12 umm.. well it depends on the boot client itself? 12:59:16 that's exactly the plan (x terminals) 12:59:20 no. 12:59:27 that's just for testing 12:59:44 i don't want to put much effort into choosing 12:59:50 will the single floppy linux distro have enough memory on disk to put all the boot stuff on it? 13:00:00 think so 13:00:20 may be formatted to 1722 k too 13:00:45 there probably is already a boot disk with all the bootp stuff on it.. 13:00:52 i've set up diskless boot at home but that's years ago 13:01:05 exactly that disk is what i'm looking for ... 13:01:13 but too much choice 13:01:23 don't want to try them all out 13:01:34 heh 13:01:41 what are the choices? 13:02:02 or give me a site with all the choices or something 13:02:17 pcoket linux 13:02:21 pocket linux 13:02:22 lrp 13:02:31 lft 13:02:37 bwimage 13:02:44 etherboot 13:02:45 netboot 13:02:59 what's wrong with netboot? 13:03:00 "image2.50" 13:03:18 i don't know whether there's anything wrong with it 13:03:42 i think i would have to get the cwyrn.. drivers from a simtel archive 13:03:45 sounds like msdos 13:03:51 i've heard of netboot before.. it's a solid brandname :P 13:03:56 er.. 13:04:03 "it's a brandname" drop the solid 13:04:10 or do i confuse packages ? 13:04:12 what's lft ? 13:04:20 lts 13:04:22 netboot is probably msdos simtel i think 13:04:37 lts? long name? 13:04:56 linux terminal s.... 13:05:04 hm 13:05:08 s shouldn't stand for server 13:05:26 or maybe it is, and there's the client image ready to run too 13:05:33 what's wrong with lrp? 13:05:38 no idea 13:05:44 what is wrong with it ? 13:05:57 nothing.. you said it looks dead, but does that matter? :) 13:06:03 my home setup used to boot some dos thing 13:06:19 possibly the crywnd 13:06:35 together with something else which i forgot 13:06:50 well i'm sorry, i can't help you out much 13:06:56 as long it tries to negotiate bootp it would be fine 13:06:57 haven't really done much with bootp 13:07:21 how mud going ? 13:07:24 i'd probably go with lrp because it seems the most professional.. 13:07:31 mud isn't really going :( 13:07:41 because i'm lazy 13:07:49 good advice i hope because i'll check it out 13:07:51 and because i can't figure out how to do sockets in gforth 13:08:13 do you know how to do sockets in gforth? :) 13:08:24 i wish i could tell you. never used gforth socket support 13:08:39 should resemble opening files 13:08:44 hmm 13:09:01 it's weird, i did a grep for "ports" and "socket" in the documentation.. came up with nothing 13:09:17 and i looked thru the documentation.. 13:09:48 but i've hooked gforth on a port once, as server 13:09:54 and connected with telnet 13:10:12 only, i didn't use gforth facilities to do that 13:10:18 instead i used netcat 13:10:54 or was it the fromport toport (linux utilities) 13:10:56 ? 13:11:05 heh 13:11:09 hmm 13:12:04 netcat -p -l | gforth or something like that 13:12:35 and how did i get the output out again ? 13:12:58 VERY maybe twas 13:13:55 netcat -p -l | gforth | netcat -p 13:14:15 and maybe the -t option for answering telnet negotiation 13:14:33 not very efficient way i suppose 13:15:09 hmmmmmm.. so how does gforth send output and input to the users?? 13:15:20 (and get input) 13:15:54 through standard i/o which was redirected from/to socket with that util 13:16:59 netcat -p -l listens to a port, and send what it receives to standard out 13:17:25 can use it to watch netbus or back orifice and the like 13:17:48 can this method be used to handle multiple users?? how? 13:18:22 i don't think so 13:19:32 LTSP linux terminal server project 13:19:44 argh 13:19:51 seems like a bit of a hack 13:19:56 LTSP is a hack :P 13:20:02 hmm 13:22:09 the mud itself should be doing the sockets stuff shouldn't it ? :) 13:23:21 etherboot "needs a bootstrap loader, usually in EPROM on network card, or on a floppy" ... 13:23:28 yes it should 13:23:49 so do i (bootstrap loader need) 13:24:07 although the concept of netcating stuff is interesting.. 13:24:19 "also see here, and the LTSP" ... 13:24:36 making it easy to put anything up onto the internet is cool if done properly 13:25:16 no need for program. write a server as script :) 13:25:37 heh 13:25:38 yeah 13:26:01 netboot "uses standard msdos packet driver" 13:26:08 heh 13:26:25 crynwr 13:27:08 netboot contains sources and executable for bootrom 13:28:07 i might burn those into a 2764 or 128 if those are still available 13:28:57 could i put lilo on a floppy, and load the netboot image with it ?? 13:29:21 figure i could try out 13:29:33 or syslinux 13:30:37 "bootrom can be copied to a floppy and started from it upon boot" 13:31:01 two versions. one eprom image, one msdos .com 13:31:21 shit, i don't have msdos here ... 13:33:01 heh 13:33:13 "need a packet driver". again. 13:33:31 i just want an image which i can dd to floppy ... 13:35:15 i don't get it. if one can put an image into a network card, to boot, what do i need a packet driver for if booting from floppy, and run it from there ?? 13:35:44 i don't need one if i write an image to rom 13:36:08 and it is both just the same code . 13:36:12 more or less 13:39:55 i'll go on looking for a suitable linux bootdisk. 13:40:10 i'll be gone, changing machines 13:40:49 l8er 13:41:02 --- quit: Speuler (Speuler) 14:03:16 --- quit: futhin () 14:52:52 --- join: edrx (edrx@200.240.18.105) joined #forth 15:11:08 --- quit: edrx ([x]chat) 16:58:48 --- join: edrx (edrx@200.240.18.111) joined #forth 17:21:08 --- quit: edrx ([x]chat) 17:38:27 --- join: edrx (edrx@200.240.18.95) joined #forth 18:06:50 --- join: futhin (kla@h24-66-209-114.cg.shawcable.net) joined #forth 18:07:51 howdy edrx 18:07:58 hi futhin 18:08:00 are you familiar with gforth? 18:10:23 do you know how to do sockets in gforth? 18:13:50 no, I've used gforth too little 18:16:44 have you coded in forth? 18:16:54 i haven't really coded in forth yet.. but have you? 18:21:33 yes, but not much in the last years... recently I've been usign ideas from Forth and coding Forth-like languages, but not written real Forth code 18:29:56 --- join: aaronl (aaronl@vitelus.com) joined #forth 18:37:45 --- quit: edrx ([x]chat) 18:43:08 --- part: aaronl left #forth 19:17:12 --- join: aum (aum@210-54-227-86.adsl.xtra.co.nz) joined #forth 19:19:57 --- quit: aum () 19:20:12 --- join: aum (aum@210-54-227-86.adsl.xtra.co.nz) joined #forth 19:24:52 --- quit: aum (Ping timeout for aum[210-54-227-86.adsl.xtra.co.nz]) 20:16:35 --- join: edrx (edrx@200.240.18.82) joined #forth 20:28:54 --- quit: futhin (lala) 21:04:34 --- quit: edrx ([x]chat) 21:55:28 --- join: futhin (kla@h24-66-209-114.cg.shawcable.net) joined #forth 22:01:31 --- mode: ChanServ set mode: +o futhin 22:01:47 --- mode: futhin set mode: +nt 22:06:25 --- quit: futhin () 22:42:15 --- join: I440r (mark4@A010-0105.BLMG.splitrock.net) joined #forth 22:42:15 --- mode: ChanServ set mode: +o I440r 23:16:56 --- join: aaronl (aaronl@vitelus.com) joined #forth 23:17:16 --- part: aaronl left #forth 23:59:59 --- log: ended forth/01.10.26