REMOVE!!!
At 12:04 AM 9/16/98 -0000, you wrote:
>debian-user-digest Digest Volume 98 : Issue 953
>
>Today's Topics:
> dilad still not working [ TheKman <nfn11988@naples.net> ]
> Re: [Fwd: colors in xwindows] [ Tom Malloy <tjm1@thorn.net> ]
> Linux for Disabled -- Contact sought [ (Ted Harding) <Ted.Harding@nessie.m ]
> Weird fonts problem in X [ nebu@shaw.wave.ca ]
> Re: Linux for Disabled -- Contact so [ George Bonser <grep@shorelink.com> ]
> Help with new install [ Ken Archer <karcher@idworld.net> ]
> Re: Question about videocard [ antispam@feverish.demon.co.uk (Robe ]
> Re: Hamm [ Bob Nielsen <nielsen@primenet.com> ]
> Re: XRINGD AGAIN [ Lazar Fleysher <fleysher@chudo.lanl ]
> GGI [ Panajotis Karajannis <panos@di.uoa. ]
> XEmacs novice customisation [ David Warnock <david@sundayta.co.uk ]
> Re: XEmacs novice customisation [ Matt Garman <garman@crh3019.urh.uiu ]
>Date: Tue, 15 Sep 1998 14:36:48 -0400
>From: TheKman <nfn11988@naples.net>
>To: Debian User List <debian-user@lists.debian.org>,
> Diald User List <linux-diald@vger.rutgers.edu>
>Subject: dilad still not working
>Message-ID: <[🔎] 35FEB3C0.81076C08@naples.net>
>Content-Type: multipart/mixed; boundary="------------4C34CC7C548E013B2485B451"
>
>Well I have been following everyone advice and I am pretty close to
>getting diald to work. What happens now is it dials, gets connected,
>sits there for about 30 seconds then disconnects.
>
>I can connect to the Internet if diald is not loaded by using pon.
>
>I have attached my /etc/diald/diald.options /etc/diald/standard.filter
>/etc/chatscripts/provider files and the last couple of entries in the
>/var/log/ppp.log and /var/log/diald.log files.
>
>I didn't have a standard.filter file after installing the Debian package
>for diald so I copied the standard.filter file from my other Debian 1.3
>box. I am running Debian 2.0 kernel 2.0.34.
>
>--
>Thanks,
>Keith
>http://www.naples.net/~nfn11988
>Debian GNU/Linux# /etc/diald/diald.options
>#
># $Id: diald.options,v 1.8 1996/12/08 20:33:01 gv Exp $
>#
># Sample diald.options -- works for PPP links and fixed IP
>#
># Edit to match your set up.
>#
>
># This is the port the modem is connected to.
># *** MODIFY to match your set up ***
># See the file /usr/doc/diald/debian.device.gz for discussion about
># the use of /dev/ttyS? instead of /dev/cua?.
>device /dev/ttyS0
>
># diald log file: do not change.
>accounting-log /var/log/diald.log
>
># diald monitoring pipe: do not change.
>fifo /var/run/diald.fifo
>
># This turns on full debugging.
>#debug 31
>debug 77
>
># We have PPP
>mode ppp
>
># Specifies dynamic IP address assignment
>dynamic
>
># IP number for deselby.xs4all.nl
>local 172.16.1.1
># IP number for the provider's machine. This is different each time we connect.
># This is not a problem, but it'll make the routine table look funny.
>remote 172.16.1.4
>
># If the connection gets broken from the ISP, redial only
># if there's outgoing traffic from our side.
>#two-way
>
># When the link's up, change routes to point to the real link
># instead of the proxy.
>#reroute
>
># diald should set a default route to the proxy SLIP link.
>defaultroute
>
># These two scripts must be executable.
>ip-up /etc/diald/ip-up
>ip-down /etc/diald/ip-down
>
># Scripts used to bring up/shut down the serial line.
>connect "/usr/sbin/chat -v -f /etc/chatscripts/provider"
>disconnect "/etc/ppp/ppp-disconnect"
>
># Do UUCP locking.
>lock
>
># We connect through a modem.
>modem
>crtscts
>
># Local tweaking
>#connect-timeout 90
>#dial-fail-limit 2
>#died-retry-count 0
>
># Dutch PTT timetable: same charge for 2.5 (peak) 5 (night) minutes.
>impulse 330,30
>restrict * * * * *
>#impulse 130,20
>
>include /etc/diald/standard.filter
>
>ABORT BUSY
>ABORT "NO CARRIER"
>ABORT VOICE
>ABORT "NO DIALTONE"
>ABORT "NO ANSWER"
>"" ATZ
>OK ATDT4359240
>CONNECT \d\c
># This is a pretty complicated set of filter rules.
># (These are the rules I use myself.)
>#
># I've divided the rules up into four sections.
># TCP packets, UDP packets, ICMP packets and a general catch all rule
># at the end.
>
>
>#------------------------------------------------------------------------------
># Rules for TCP packets.
>#------------------------------------------------------------------------------
># General comments on the rule set:
>#
># In general we would like to treat only data on a TCP link as signficant
># for timeouts. Therefore, we try to ignore packets with no data.
># Since the shortest possible set of headers in a TCP/IP packet is 40 bytes.
># Any packet with length 40 must have no data riding in it.
># We may miss some empty packets this way (optional routing information
># and other extras may be present in the IP header), but we should get
># most of them. Note that we don't want to filter out packets with
># tcp.live clear, since we use them later to speedup disconnects
># on some TCP links.
>#
># We also want to make sure WWW packets live even if the TCP socket
># is shut down. We do this because WWW doesn't keep connections open
># once the data has been transfered, and it would be annoying to have the link
># keep bouncing up and down every time you get a document.
>#
># Outside of WWW the most common use of TCP is for long lived connections,
># that once they are gone mean we no longer need the network connection.
># We don't neccessarily want to wait 10 minutes for the connection
># to go down when we don't have any telnet's or rlogin's running,
># so we want to speed up the timeout on TCP connections that have
># shutdown. We do this by catching packets that do not have the live flag set.
>
># --- start of rule set proper ---
>
># When initiating a connection we only give the link 15 seconds initially.
># The idea here is to deal with possibility that the network on the opposite
># end of the connection is unreachable. In this case you don't really
># want to give the link 10 minutes up time. With the rule below
># we only give the link 15 seconds initially. If the network is reachable
># then we will normally get a response that actually contains some
># data within 15 seconds. If this causes problems because you have a slow
># response time at some site you want to regularly access, you can either
># increase the timeout or remove this rule.
>accept tcp 15 tcp.syn
>
># Keep named xfers from holding the link up
>ignore tcp tcp.dest=tcp.domain
>ignore tcp tcp.source=tcp.domain
>
># (Ack! SCO telnet starts by sending empty SYNs and only opens the
># connection if it gets a response. Sheesh..)
>accept tcp 5 ip.tot_len=40,tcp.syn
>
># keep empty packets from holding the link up (other than empty SYN packets)
>ignore tcp ip.tot_len=40,tcp.live
>
># make sure http transfers hold the link for 2 minutes, even after they end.
># NOTE: Your /etc/services may not define the tcp service www, in which
># case you should comment out the following two lines or get a more
># up to date /etc/services file. See the FAQ for information on obtaining
># a new /etc/services file.
>accept tcp 120 tcp.dest=tcp.www
>accept tcp 120 tcp.source=tcp.www
>
># Once the link is no longer live, we try to shut down the connection
># quickly. Note that if the link is already down, a state change
># will not bring it back up.
>keepup tcp 5 !tcp.live
>ignore tcp !tcp.live
>
># an ftp-data or ftp connection can be expected to show reasonably frequent
># traffic.
>accept tcp 120 tcp.dest=tcp.ftp
>accept tcp 120 tcp.source=tcp.ftp
>
>#NOTE: ftp-data is not defined in the /etc/services file provided with
># the latest versions of NETKIT, so I've got this commented out here.
># If you want to define it add the following line to your /etc/services:
># ftp-data 20/tcp
># and uncomment the following two rules.
>#accept tcp 120 tcp.dest=tcp.ftp-data
>#accept tcp 120 tcp.source=tcp.ftp-data
>
># If we don't catch it above, give the link 10 minutes up time.
>accept tcp 600 any
>
># Rules for UDP packets
>#
># We time out domain requests right away, we just want them to bring
># the link up, not keep it around for very long.
># This is because the network will usually come up on a call
># from the resolver library (unless you have all your commonly
># used addresses in /etc/hosts, in which case you will discover
># other problems.)
># Note that you should not make the timeout shorter than the time you
># might expect your DNS server to take to respond. Otherwise
># when the initial link gets established there might be a delay
># greater than this between the initial series of packets before
># any packets that keep the link up longer pass over the link.
>
># Don't bring the link up for rwho.
>ignore udp udp.dest=udp.who
>ignore udp udp.source=udp.who
># Don't bring the link up for RIP.
>ignore udp udp.dest=udp.route
>ignore udp udp.source=udp.route
># Don't bring the link up for NTP or timed.
>ignore udp udp.dest=udp.ntp
>ignore udp udp.source=udp.ntp
>ignore udp udp.dest=udp.timed
>ignore udp udp.source=udp.timed
># Don't bring up on domain name requests between two running nameds.
>ignore udp udp.dest=udp.domain,udp.source=udp.domain
># Bring up the network whenever we make a domain request from someplace
># other than named.
>accept udp 30 udp.dest=udp.domain
>accept udp 30 udp.source=udp.domain
># Do the same for netbios-ns broadcasts
># NOTE: your /etc/services file may not define the netbios-ns service
># in which case you should comment out the next three lines.
>ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns
>accept udp 30 udp.dest=udp.netbios-ns
>accept udp 30 udp.source=udp.netbios-ns
># keep routed and gated transfers from holding the link up
>ignore udp tcp.dest=udp.route
>ignore udp tcp.source=udp.route
># Anything else gest 2 minutes.
>accept udp 120 any
>
># Catch any packets that we didn't catch above and give the connection
># 30 seconds of live time.
>accept any 30 any
>Tue Sep 15 14:12:35 1998 EDT: Calling site 172.16.1.4.
>Tue Sep 15 14:13:21 1998 EDT: Disconnected. Call duration 46 seconds.
> IP transmitted 840 bytes and received 0 bytes.
>Tue Sep 15 14:16:25 1998 EDT: Calling site 172.16.1.4.
>Tue Sep 15 14:16:26 1998 EDT: Disconnected. Call duration 1 seconds.
> IP transmitted 84 bytes and received 0 bytes.
>Tue Sep 15 14:16:58 1998 EDT: Calling site 172.16.1.4.
>Tue Sep 15 14:16:59 1998 EDT: Disconnected. Call duration 1 seconds.
> IP transmitted 0 bytes and received 0 bytes.
>Tue Sep 15 14:17:30 1998 EDT: Calling site 172.16.1.4.
>Tue Sep 15 14:17:31 1998 EDT: Disconnected. Call duration 1 seconds.
> IP transmitted 84 bytes and received 0 bytes.
>Tue Sep 15 14:18:03 1998 EDT: Calling site 172.16.1.4.
>Tue Sep 15 14:18:04 1998 EDT: Disconnected. Call duration 1 seconds.
> IP transmitted 0 bytes and received 0 bytes.
>
>
>Sep 15 14:17:30 monster1 chat[184]: abort on (BUSY)
>Sep 15 14:17:30 monster1 chat[184]: abort on (NO CARRIER)
>Sep 15 14:17:30 monster1 chat[184]: abort on (VOICE)
>Sep 15 14:17:30 monster1 chat[184]: abort on (NO DIALTONE)
>Sep 15 14:17:30 monster1 chat[184]: abort on (NO ANSWER)
>Sep 15 14:17:30 monster1 chat[184]: send (ATZ^M)
>Sep 15 14:17:30 monster1 chat[184]: expect (OK)
>Sep 15 14:17:30 monster1 chat[184]: ATZ^M^M
>Sep 15 14:17:30 monster1 chat[184]: OK
>Sep 15 14:17:30 monster1 chat[184]: -- got it
>Sep 15 14:17:30 monster1 chat[184]: send (ATDT4359240^M)
>Sep 15 14:17:30 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:30 monster1 diald[126]: Adding connection 0x805e2f8 @
905883450 - timeout 30
>Sep 15 14:17:30 monster1 chat[184]: expect (CONNECT)
>Sep 15 14:17:31 monster1 diald[126]: Running connect (pid = 185).
>Sep 15 14:17:31 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:31 monster1 diald[126]: Adding connection 0x805e2f8 @
905883451 - timeout 30
>Sep 15 14:17:31 monster1 diald[126]: SIGCHLD[6]: pid 185 dial, status 32512
>Sep 15 14:17:31 monster1 diald[126]: Connect script failed.
>Sep 15 14:17:31 monster1 diald[126]: Closing modem line.
>Sep 15 14:17:32 monster1 chat[184]: 359240^M^M
>Sep 15 14:17:32 monster1 chat[184]: NO CARRIER
>Sep 15 14:17:32 monster1 chat[184]: -- failed
>Sep 15 14:17:32 monster1 chat[184]: Failed (NO CARRIER)
>Sep 15 14:17:32 monster1 pppd[183]: Connect script failed
>Sep 15 14:17:32 monster1 diald[126]: Delaying 30 seconds before clear to dial.
>Sep 15 14:17:32 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:32 monster1 diald[126]: Adding connection 0x805e2f8 @
905883452 - timeout 30
>Sep 15 14:17:33 monster1 pppd[183]: Exit.
>Sep 15 14:17:33 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:33 monster1 diald[126]: Adding connection 0x805e2f8 @
905883453 - timeout 30
>Sep 15 14:17:35 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:35 monster1 diald[126]: Adding connection 0x805e2f8 @
905883455 - timeout 30
>Sep 15 14:17:36 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:36 monster1 diald[126]: Adding connection 0x805e2f8 @
905883456 - timeout 30
>Sep 15 14:17:37 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:37 monster1 diald[126]: Adding connection 0x805e2f8 @
905883457 - timeout 30
>Sep 15 14:17:39 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:39 monster1 diald[126]: Adding connection 0x805e2f8 @
905883459 - timeout 30
>Sep 15 14:17:40 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:40 monster1 diald[126]: Adding connection 0x805e2f8 @
905883460 - timeout 30
>Sep 15 14:17:41 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:41 monster1 diald[126]: Adding connection 0x805e2f8 @
905883461 - timeout 30
>Sep 15 14:17:42 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:42 monster1 diald[126]: Adding connection 0x805e2f8 @
905883462 - timeout 30
>Sep 15 14:17:43 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:43 monster1 diald[126]: Adding connection 0x805e2f8 @
905883463 - timeout 30
>Sep 15 14:17:44 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:44 monster1 diald[126]: Adding connection 0x805e2f8 @
905883464 - timeout 30
>Sep 15 14:17:45 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:45 monster1 diald[126]: Adding connection 0x805e2f8 @
905883465 - timeout 30
>Sep 15 14:17:46 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:46 monster1 diald[126]: Adding connection 0x805e2f8 @
905883466 - timeout 30
>Sep 15 14:17:47 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:47 monster1 diald[126]: Adding connection 0x805e2f8 @
905883467 - timeout 30
>Sep 15 14:17:48 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:17:48 monster1 diald[126]: Adding connection 0x805e2f8 @
905883468 - timeout 30
>Sep 15 14:18:03 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:18:03 monster1 diald[126]: Adding connection 0x805e2f8 @
905883483 - timeout 30
>Sep 15 14:18:04 monster1 diald[126]: Running connect (pid = 190).
>Sep 15 14:18:04 monster1 diald[126]: SIGCHLD[7]: pid 190 dial, status 32512
>Sep 15 14:18:04 monster1 diald[126]: Connect script failed.
>Sep 15 14:18:04 monster1 diald[126]: Closing modem line.
>Sep 15 14:18:05 monster1 diald[126]: Delaying 30 seconds before clear to dial.
>Sep 15 14:18:05 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:18:05 monster1 diald[126]: Adding connection 0x805e2f8 @
905883485 - timeout 30
>Sep 15 14:18:05 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:18:05 monster1 diald[126]: Adding connection 0x805e2f8 @
905883485 - timeout 30
>Sep 15 14:18:06 monster1 diald[126]: filter accepted rule 31 proto 1 len 84
packet 172.16.1.1,0 => 199.233.75.16,0
>Sep 15 14:18:06 monster1 diald[126]: Adding connection 0x805e2f8 @
905883486 - timeout 30
>Sep 15 14:18:36 monster1 diald[126]: Deleting connection 0x805e2f8 @ 905883516
>
>
>
>
>
>
>
>
>
>
>
>
>Date: Tue, 15 Sep 1998 18:49:47 -0400
>From: Tom Malloy <tjm1@thorn.net>
>To: Dan@thorn.net, Hrabarchuk@thorn.net
>CC: "debian-user@lists.debian.org" <debian-user@lists.debian.org>
>Subject: Re: [Fwd: colors in xwindows]
>Message-ID: <[🔎] 35FEEF0B.CCB48F91@thorn.net>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Dan Hrabarchuk wrote:
>>
>> What driver are you using?
>>
>
>xserver-svga 3.3.2.3a-1
>Date: Tue, 15 Sep 1998 23:40:40 +0100 (BST)
>From: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
>To: debian-user@lists.debian.org, linux-list@ssc.com
>Subject: Linux for Disabled -- Contact sought
>Message-ID: <[🔎] XFMail.980915234040.Ted.Harding@nessie.mcc.ac.uk>
>Content-Type: text/plain; charset=iso-8859-1
>Content-Transfer-Encoding: 8bit
>
>Hi Folks,
>
>A few years back there was a guy (in the US) active on some of the Linux
>lists who was developing linux applications for the disabled.
>
>He set up his own list, as I recall, and disappeared from general view.
>It's some time since I lost track of him and no longer have any pointers.
>
>I would now like to get in touch with him, and would welcome any
>information which would lead me to him (private reply or to the list, as
>you please).
>
>With thanks,
>Ted.
>
>--------------------------------------------------------------------
>E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
>Date: 15-Sep-98 Time: 23:40:40
>--------------------------------------------------------------------
>Date: Tue, 15 Sep 1998 22:45:30 +0000
>From: nebu@shaw.wave.ca
>To: debian-user@lists.debian.org
>Subject: Weird fonts problem in X
>Message-ID: <[🔎] 35FEEE0A.1F73190C@shaw.wave.ca>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>My problem has just got massively weird after installing more programs.
>
>I get messages that seem to indicate some fonts are missing, but I can't
>figure out how to fix it. If anyone has a clue please tell me!
>
>Here's what Netscape says when it tries to run:
>Warning: Cannot convert string
>"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
>
>Gimp says:
>**WARNING **: file gdkfont.c: line 115 (gdk_font_ref): "font != NULL"
>and it does not run.
>
>I have fntbase, fnt75, fnt100, fntscl all installed.
>
>Any clues?
>
>Thanks in abundance
>Date: Tue, 15 Sep 1998 15:54:26 -0700 (PDT)
>From: George Bonser <grep@shorelink.com>
>To: Ted.Harding@nessie.mcc.ac.uk
>cc: debian-user@lists.debian.org, linux-list@ssc.com
>Subject: Re: Linux for Disabled -- Contact sought
>Message-ID: <[🔎] Pine.LNX.3.96.980915155235.13253F-100000@calvin.shorelink.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>I know of blinux for the visually impared. I do not have the website handy
>but you can find it from www.linux.org I think. That site might have other
>links to Linux for the disabled.
>
>On Tue, 15 Sep 1998 Ted.Harding@nessie.mcc.ac.uk wrote:
>
>> Hi Folks,
>>
>> A few years back there was a guy (in the US) active on some of the Linux
>> lists who was developing linux applications for the disabled.
>>
>> He set up his own list, as I recall, and disappeared from general view.
>> It's some time since I lost track of him and no longer have any pointers.
>>
>> I would now like to get in touch with him, and would welcome any
>> information which would lead me to him (private reply or to the list, as
>> you please).
>>
>> With thanks,
>> Ted.
>>
>> --------------------------------------------------------------------
>> E-Mail: (Ted Harding) <Ted.Harding@nessie.mcc.ac.uk>
>> Date: 15-Sep-98 Time: 23:40:40
>> --------------------------------------------------------------------
>>
>>
>> --
>> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org <
/dev/null
>>
>>
>>
>
>George Bonser
>
>The Linux "We're never going out of business" sale at an FTP site near you!
>Date: Tue, 15 Sep 1998 17:52:38 -0500
>From: Ken Archer <karcher@idworld.net>
>To: debian-user@lists.debian.org
>Subject: Help with new install
>Message-ID: <[🔎] 35FEEFB6.B2581B86@idworld.net>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Just installed a 8.4 gig hd and set it up for a triple-boot with Suse
>5.2, RedHat 5.1 and Debian 2.0. Installed Suse and set up the
>partitions for the other OS's. Red Hat refuses to go to the partition
>screen saying something about "not enough resources." I was able to
>format the partitions for Debian with the Debian install program, but
>when I went to the "install programs" screen it keeps jumping back to
>the main menu screen. The three root directories are all within the
>first 528 meg. I am going to go home tonight and keep trying, but I
>could sure use some experienced help on this one.
>Date: Tue, 15 Sep 1998 18:35:53 GMT
>From: antispam@feverish.demon.co.uk (Robert Wilderspin)
>To: debian-user@lists.debian.org
>Subject: Re: Question about videocard
>Message-ID: <[🔎] 35feb34a.2007782@mailtraq.feverish.demon.co.uk>
>
>On 15 Sep 98 08:20:13 GMT, tgakem@sg10.chem.tue.nl wrote:
>
>>I've got a Diamond Viper 330 AGP running the X window system just fine
>>on a debian 2.0 box. I don't know about svga, I haven't tried that yet.
>
>I have, and it does, if you update to the latest version in slink.
>
>
>Rob Wilderspin
>--
>"But I need it to crash once every few days -
>reboots are the only chance I get to sleep..."
>----------------------= (send replies to rob@)
>Date: Tue, 15 Sep 1998 16:01:08 -0700 (MST)
>From: Bob Nielsen <nielsen@primenet.com>
>To: Dan Hrabarchuk <danh@firstwest.com>
>cc: debian-user@lists.debian.org
>Subject: Re: Hamm
>Message-ID: <[🔎] Pine.LNX.3.96.980915154459.644A-100000@nielsen.tus.primenet.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>On Tue, 15 Sep 1998, Dan Hrabarchuk wrote:
>
>> I relativley new to Debian. I did my first Debian install a week ago, After
>> 4 years of slackware, and a brief stint with RedHat
>
>Welcome!
>
>>
>> <rant>
>> (I asked three email support questions like, why doesn't g++ wok with full
>> error messages etc. All answers "this is not an installation issue". g++ not
>> installling is not an istalation issue !?)
>> </rant>
>
>Yes, that is a frequent complaint about Red Hat. Their "official"
>support is limited to installation problems only. However, they do have a
>mailing list for post-installation support, etc., which I found to be
>quite helpful in my pre-Debian days.
>
>>
>> anyway, I was just wondering what Hamm is, and just to say "THANK YOU FOR
>> DEBIAN!!!".
>
>It is a codename for the current (2.0) version of Debian. This name and
>the others which have been used (buzz, rexx, bo, slink) came from the
>names of characters in the movie "Toy Story". The next version slink is
>currently in the unstable tree.
>
>----
>Bob Nielsen Internet: nielsen@primenet.com
>Tucson, AZ AMPRnet: w6swe@w6swe.ampr.org
>DM42nh http://www.primenet.com/~nielsen
>Date: Tue, 15 Sep 1998 16:55:56 -0700 (PDT)
>From: Lazar Fleysher <fleysher@chudo.lanl.gov>
>To: Jason Kennedy <jason@vnakc.com>
>cc: Debian User <debian-user@lists.debian.org>
>Subject: Re: XRINGD AGAIN
>Message-ID: <[🔎] Pine.SGI.3.93.980915165008.295A-100000@chudo.lanl.gov>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>Hi
>
>I have only one line in my xringd.conf
>
>R 10-15 R 30 : /usr/bin/pon
>
>If I add -m /dev/ttyS1
>
>the xringd starts to complain that the file does not exist
>
>By default it should use /dev/modem
>
>so I've made dev/ modem point to /dev/ttyS1
>
>but it does not help either...
>
>Oh and yes, please send me your config file (although, honestly, I do not
>know how it might help)
>
>
>On Tue, 15 Sep 1998, Jason Kennedy wrote:
>
>>
>>
>> Hey I use xringd
>> I use wvdial to dial into my ISP
>> So in the xringd.conf I have execute "wvdial" when it gets two
>> rings with none after it for 30 seconds
>> I can send you my xringd.conf is you want
>>
>>
>Date: Wed, 16 Sep 1998 02:20:49 +0300
>From: Panajotis Karajannis <panos@di.uoa.gr>
>To: debian-user@lists.debian.org
>Subject: GGI
>Message-ID: <[🔎] 19980916022049.A582@di.uoa.gr>
>Content-Type: text/plain; charset=us-ascii
>
>Hi
>
>I saw in slink many GGI libs with various targets.I wonder if there is a GGI
>ready kernel witch I can use, because it is impossible to build one myself.I
>always get errors at compile time.
>Also I saw hurd binaries and I am very happy about this because the hurd looks
>very promising (see www.debian.org and www.fig.org).
>What Is your opinion about this OS, his future and his relationship with
>Debian ?
>Date: Mon, 14 Sep 1998 23:28:27 +0000
>From: David Warnock <david@sundayta.co.uk>
>To: Debian Users Mailing List <debian-user@lists.debian.org>
>Subject: XEmacs novice customisation
>Message-ID: <[🔎] 35FDA69B.902F478C@sundayta.co.uk>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Hi,
>
>I am attempting to work with XEmacs, so far I can't say I am
>particularly enjoying the experience ;-)
>
>There are some things I really miss and one is the ability to select
>text using the shift key combined with any cursor movement. From the
>latest FAQ where it talks about windows versions it mentions a package
>called pending-delete.
>
>I have found /usr/lib/xemacs-20.4/lisp/pending-del.elc on my Debian 2.0
>system.
>
>Is this something that would make shift and cursors movement select
>text? If so how do I install it?
>
>Another thing I really miss is the effective use of the mouse for
>selecting text. With 3 buttons I would love to have something line
>
> button1 + drag = select text from start to current point
> button2 + drag = select rectangle of text from start to current
>point
>
>I can't get used to a mouse button causing a paste at the text cursor.
>
>Finally I would like to disable all the cursor movement by Control + a
>letter as the cursor keys work fine. That would allow me C-x, C-c and
>C-v for my cut copy and paste which are so convenient.
>
>Any suggestions.
>
>Thanks
>
>Dave
>Date: Tue, 15 Sep 1998 18:53:00 -0500
>From: Matt Garman <garman@crh3019.urh.uiuc.edu>
>To: David Warnock <david@sundayta.co.uk>,
> Debian User's List <debian-user@lists.debian.org>
>Subject: Re: XEmacs novice customisation
>Message-ID: <[🔎] 19980915185300.B31132@crh3019.urh.uiuc.edu>
>Content-Type: text/plain; charset=us-ascii
>
>On Mon, Sep 14, 1998 at 11:28:27PM +0000, David Warnock wrote:
>> There are some things I really miss and one is the ability to select
>> text using the shift key combined with any cursor movement. From the
>> latest FAQ where it talks about windows versions it mentions a package
>> called pending-delete.
>
>The emacs family of text editors has DOS/Windows-like cut and paste,
>but they're often referred to by different names, and implemented
>differently. I don't know how you customize (x)emacs to do what you
>want, but, in a nutshell, here's cut'n'paste with (x)emacs:
>
>CTRL-Space "sets the mark." That is, from the point where you pressed
>CTRL-Space to wherever you move the cursor, that region is what you
>can manipulate (as you would a region highlighted with Shift-arrows
>under DOS). And xemacs should highlight this for you, too.
>
>CTRL-w will cut the highlighted region. If I wanted to cut my
>paragraph above, I would move the cursor to the "C" in the first
>sentence, press CTRL-Space to set the mark. Next, I'd move the cursor
>to the empty line between paragraphs and press CTRL-w; the text would
>be cut out.
>
>If I pressed CTRL-y immediately after that, I would paste what I just
>cut; that is, the paragraph would return. CTRL-y is the paste
>command.
>
>If I just wanted to copy a region, but not cut it (i.e. saving it for
>later pasting, maybe with source code), Then instead of using CTRL-w,
>I would use META-w. (Or press Esc, release, then press w; OR,
>Alt-w).
>
>> button1 + drag = select text from start to current point
>> button2 + drag = select rectangle of text from start to current
>> point
>
>Well... I find mouse cut'n'paste with Unix easier than windows. If I
>wanted to select the quoted text above, I would use mouse button1 (my
>left-most button), press it, and drag the mouse over the text I
>wanted. Upon releasing the mouse button, the region should remain
>highlighted.
>
>Now I can move the cursor to wherever I want to paste this text, and
>press mouse button 2 (my middle button, of three).
>
>I don't know if this is the default behavior -- I have the gpm package
>installed, and that may be what does this for me. (On the other hand,
>I compiled xemacs 20 withOUT gpm support, and this still works...
><shrug>).
>
>One final note, though: if you use xemacs version 20.4 on the console
>(i.e. not in X), then Ctrl-Z (to suspend) will not work, and you'll
>basically freeze you're terminal. This is a bug with gpm. I compiled
>my own xemacs 20.4 to work around this.
>
>Good luck!
>
Reply to: