Re: Porting YTalk to Windows
Steve McIntyre <[EMAIL PROTECTED]> writes: > >In article <[EMAIL PROTECTED]> you write: >> >>I am interested in porting YTalk to Windows. This has probably been done >>before. Do you know where I can find information about this. > >Hi, I'm the ytalk maintainer. Unfortunately I don't know of any efforts to >port it to windows, but I must admit that I haven't really looked. My >first (obvious) suggestion would be to talk to the upstream maintainer, >Roger Espel Llima <[EMAIL PROTECTED]>. He's definitely >approachable... > Wintalk is effectively a ytalk port for Windows. >From http://www.thoughtcraft.com/elf/wintalk/wintalk.html "Wintalk is an implementation of the UNIX talk protocols for Microsoft Windows 3.1 and above, written by Glen Daniels." It isn't DFSG free though - there is a "free beer" version and a "Pro" version you have to pay for. Chris
Re: dselect question
Shaleh <[EMAIL PROTECTED]> writes: > >I wanted to use dselect because it could show me dependencies and >suggestions, before it tried to install them. I grabbed a few packages >and it turned out they had some dependencies I did not expect. So I had >a half installed package left behind. Thought dselect might have helped >here. Is there a way to find this out ahead of time? > I've done this, though as I'm not on my debian system, and it is a little while since I've used dselect, so I may not be quite accurate. Within "access methods", you select the main, contrib, non-free sections. You can also select a local archive as well, and get dselect to automatically generate a packages file for it. In case it makes a difference, I NFS mounted a debian mirror (local to my university), and told dselect to use a mounted filesystem (ie I didn't get dselect to do the NFS mounting for me). I then had a directory (/root/debian-local I think) which contained various local packages. I'm not sure whether this will work for the FTP access method. Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: [INSTALL]:novice questions
Rick Jones <[EMAIL PROTECTED]> writes: > > On Sat, 26 Apr 1997, Pavel Galynin wrote: > > > 5. Could you give me some pointers to info about building a kernel with > > custom drivers, lilo config etc., all the novice questions, so that I > > could RTFM and not bother people on the list with stupid questions. >From http://www.debian.org/docs.html there is a list of lots of useful documentation. I'd suggest there is a good place to start looking. For compiling a kernel, the Kernel-Howto is where you should start, and this is available from http://www.li.org/Resources/HOWTO/Kernel-HOWTO.html The below advice however is a summary of how to compile a kernel. > > Get the kernel source pkg. Do make config (line oriented) or make > menuconfig (fair menu with help) or make xconfig (GUI menu needs X). > > After you select all the drivers etc.. you want save and type the > following at the console prompt: > > make dep ; make clean ; make zlilo > > and if you have modules > > make modules ; make module_install That should be "make modules_install" (the original author confirms it as a typo). N.b If "make xconfig" gives an error telling you that it can't connect to the display, then you need to do something like the following to give the root account access to the cookies needed to display on your X session: 1) use X as root or 2) slogin -l root localhost (requires the ssh package from the non-us mirror, but works from an xterm) 3) cd ~root ln -s ~username/.Xauthority . (this needs to be done as root, and means that root's Xauthority file is a symbolic link to yours - nb replace username by your username. Hope this helps. Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Newby: dselect failure
George Bonser <[EMAIL PROTECTED]> writes: > > > One trick that I have learned is to SELECT NOTHING the first time you run > dselect, simply let it install the PRESELECTED things only. THEN run > dselect again and choose your other software. > > The original problem was problems with installing the quota package. I'd suggest trying dselect again, but without selecting quota. If that fails to work, or there are lots of problems then the advice above is worth following. When the other packages are installed, try quota again. In either case it is probably worth submitting a bug report - I've checked, and there is only one bug against quota, and it wouldn't have caused your problem. See http://www.debian.org/Bugs/Reporting.html for details on how to submit a bug. The problems occur because packages sometimes depend on other packages being installed. They shouldn't do this (in most cases), but the problems are sometimes difficult to spot. An alternative solution may be to try the packages in frozen - though this includes the same version of quota. Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Package configuration philosophy
In article <[EMAIL PROTECTED]> you write: > >On Tue, 25 Feb 1997, Yoav Cohen-Sivan wrote: > >> X is pretty bare in Debian after install, too - if you just "startx" >> you get a simple xterm with no default menus, no menued way of running >> another xterm, heck not even a FvwmModule running on screen with xload >> and xclock in it. > >what are you talking about? > >debian has a 'menu' package which all other packages can use to register >themselves with - menus for fvwm, fvwm95 and other are auto-generated >from this information. It was written in such a way that it is easy to >add support for a new window manager or text-mode menu program whenever >needed. > >Not all packages are using menu yet, but most are. I'm not sure about the situation in unstable, but in stable neither the menu package, or fvwm2 seem to provide /etc/menu-methods/fvwm2. This file is available in /usr/doc/menu/examples. Because of this, the menu is not updated by default. Is this the case in unstable or should I report it as a bug? Having copied the example file over, the result is excellent and should be a selling point for Debian. Well done. > >it seems to me that your complaints have less to do with omissions in >debian than with lack of understanding/knowledge on your part. What you >want (and more!) is already in debian. > Sometimes, Debian hides its light under a bushel. There was a suggestion recently of producing an equivalent of the "Tips on Startup" available from win95. If this is going ahead, perhaps one of the tips could be "You can add user menu entries - for details see ..." Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
KEYBOARD PROBLEMS!
Content-Type: text/plain; charset="us-ascii" > Dear Sir/Madam, > > I recently decided to venture into Linux-Land, and downloaded all the = > necessary files from your sites. All the procedures involving rawrite2.0 = > worked fine. I inserted the Rescue disk, and Linux booted. It analysed = > my system, chugging along merrily until.. it reached the monitor display = > choice screen. > > This screen appears (in mono) with the cursor flashing under . = > However, I cannot do anything from here. No keyboard commands, = > RETURN/ENTER or arrow movements are carried out. It just sits there, = > taunting me. Arrggh! Is there anything I am doing wrong? The Recue disk = > is fine - clean and error free. My machine is: > > A custom built P5-200Mhz Intel Pentium comprising: > > 32MB EDO RAM > 2.1GB E-IDE (Mode 4) HDD > 500MB E-IDE (Mode 4) HDD > 200MB Partioned drive, run from d:\ > 8xPanasonic CD-ROM > Sony 3.5" FDD > Diamond Stealth 3D-2000 (S3) Videocard +2MB VRAM > 15" Goldstar SVGA monitor. > Cherry Keyboard (Win95) > > I would dearly appreciate a reply - otherwise Linux is no more! > > Yours sincerely, > > Chris Walker > [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Errors with Ethernet module installation...
Tim Sailer wrote: > > In your email to me, Bill Vinson, you wrote: > > > > I just decided to reinstall so I would have the chance to install modules > > to work with the SN2000CT ethernet card. It says it is 100% NE2000 > > Ethernet compatible and when I opted to install the NE2000 module I got the > > following error: > > > > nc.c: module autoprobing not allowed. Append "io=0xNNN" value(s). > > Initialization of ne failed > > > > Installation failed. > > > > What does this mean? I'm pretty sure the card is set in the 16-bit slot > > firmly. Did I get a useless ethernet card? Is there a good way to test if > > it is in fact available? No, the card probably isn't causing this problem, you need to tell it where to find the card. > > I think 0x320 it the 'standard' spot the ne2k cards live. At the prompt > for additional command line options (or what ever it is), add > "io=0x320" and see if that works > In my /etc/conf.modules I have: options ne io=0x340 irq=10 which indicates that my card is at io address 0x340 and irq10. You probably need to insert this line into yours as well, or specify it on the command line when you call depmod. You can use the io=0xNNN to get it to autoprobe, apparently, I read this somewhere when I was trying to do understand modules, but can't give you a precise reference. It was probably in one of the files in /usr/doc/modules, the modules howto or /usr/src/linux/Documentation An alternative is to build the driver into the kernel, when it will autoprobe and find out the correct addresses. The kernel prints up this info when it boots (I think), enabling you to find out the the io address and irq if you don't know them. Sorry I can't point you to an exact reference, but I hope this helps. Chris, -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: better fonts?
David Puryear wrote: > > Hi all, > > I was looking at some postscript files and quality was not very good. Is > there different fonts I can get that would produce better output in X > and especially ghostscript? If so, where and how. > The Alladin version of ghostscript (version 4) has much better fonts than previous versions - at least that's what they say, I havn't compared them myself. You need to install the version of gsfonts in unstable to use it. The packages are: non-free/binary-i386/gs_4.01-4.deb unstable/binary-i386/text/gsfonts_4.01-2.deb You can probably install just the fonts and use it with your present version of ghostscript. I don't know if this will improve output in X - I suspect not. Hope this helps. Chris -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: 1.1 Beta Install (11 June 1996 disks)
Andy Dougherty wrote: > > I tried a fresh install of 1.1 Beta using the 11 June 1996 disks. > > The installation disks worked quite well, including modules configuration. > The core dump in configuring the net/ modules is indeed gone. My > /etc/modules file is also now properly populated with the modules I selected. > Good job. Thanks. > > My remaining complaints are two-fold: > > 1. My PS/2 mouse no longer works. I'll try to track this down today. Try compiling the kernel with PS/2 mouse support in the kernel, rather than as a module. I can't use the kernel-image-1.99.7 for this reason, as lack of mouse support seems to cause X to hang the computer. I've reported this (Bug#3265), and if you can throw more light on it, I'm sure it would be welcome. I'm beginning to wonder whether this problem is a kernel bug. Chris
Re: Loading X Windows
Buddha Buck wrote: > > > > > > Is it possible to start an X session from the shell? > > > > yes. type "startx" at the command line, as any user, and the machine is > > transformed. you can end with alt-ctl-backspace. > > > > > Also, does X allow multiple sessions at once? > > > > what do you mean by this. you can have multiple windows open. type > > "xterm &" to launch an extra xterm, for example. Or you can log in from > > another x-capable machine and open windows. > > > Or, if you are desparate and foolish enough (and have a lot of memory), > you -can- run multiple X servers on different virtual consoles. I've > done this in the past. I don't recommend it. > The command I use to do this is: X :1.0 -query For even more replace :1.0 with :2.0 etc. I've used it occasionally so that I can don't have to reconfigure my machine (which boots into X) to run an X session on a remote machine as well as a session on my local machine. I hope this helps. Chris
Re: Imake problems.
Christian Hudon wrote: > > On Mon, 20 May 1996, Dale Scheetz wrote: > > > I find the fracturing of packages into runtime and development sometimes > > doesn't make any sense. In this case, why is imake and xmkmf supplied in > > xbase, but the configuration files they need to run properly in the xdevel > > package. Shouldn't they all be in the same place? It would certainly make > > using and finding them more straight forward. > > Agreed. IMHO imake and xmkmf should be together with their config files... > i.e in the xdevel package. > > 1. They're only used when compiling x binaries. > > 2. Getting a 'xmkmf: file not found' will probably get users thinking "I > need an x development package". Getting a failed xmkmf run will most > probably get the users thinking 'bug!'. > I agree with 2. I think I was rather confused and required advice on what to do when xmkmf wouldn't work. It certainly got a Slackware using friend thinking Debian was broken. Your comment is slightly misleading however. I assume you mean "bash: xmkmf: command not found". When I ran into this problem xmkmf ran for a while and then stopped with the error "xmkmf: file not found" IIRC. There may be good reasons to do it the way it is done at present of course. Chris Chris
Re: which..
[EMAIL PROTECTED] wrote: > > Is the command "which" available in any of the debian releases? > I haven't seen it yet in 0.93R6 though I don't have everything > installed so I may have missed it. > > Cheers! > Richard.. Here's a simple shell script I've installed in /usr/local/bin to perform the same task (thanks Jon). I'm afraid I don't know if it will be in Version 1.1. #!/bin/sh type -p $* Chris
