Re: SSH: does it require portmapper and what hostname is it looking for?
On Wed, Feb 18, 2004 at 10:24:44AM -0700, Monique Y. Herman wrote: On 2004-02-18, Anthony Campbell penned: I'm trying to run ssh between two computers but I get: connect to host port 22: Connection refused. I have portmapper turned off for security, but is it essential for ssh? I don't know about this one, but I don't think so? Also, what is the hostname I have to supply? The FQDN seems to be acampbell.org.uk but this is the same for both computers, which doesn't seem to be right. Two machines should not resolve to the same FQDN. -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] SSH doesn't require portmap. It uses a fixed well-known port. You might not have sshd running on the destination machine. You could use ps ax to find out. If it's running, and the machines can ping each other, the next thing to try is telnet destination ssh If a server answers, then you're reaching it, so the next place to look for the answer is in the sshd config file. That's /etc/ssh/sshd_config. There's some on-system documentation, and a comprehensive book published by O'Reilly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why Linux, Why Debian
On Fri, Feb 20, 2004 at 06:34:25AM +1100, bob parker wrote: On Fri, 13 Feb 2004 10:09, Manoj Srivastava wrote: Hi, 9) Does the gentoo configurability deliver significantly better performance? Is the added step of compilation too much of an inconvenience? By compiling all applications with optimisations for your processor, you can have your machine do nothing between keystrokes and/or mouse clicks a whole lot faster than it otherwise would. Naturally you want time critical code such as the kernel optimised but there is no need to use gentoo for that. I'm just getting started with Gentoo, and haven't made it all the way through installation yet. So this is tentative. But, there are a lot of CPU hogs in GNU/Linux besides the kernel. Some browsers take the other side of forever to start up, especially on an older machine whose RAM space is merely huge, rather than inconceivable. OpenOffice.org is notoriously slow. So you probably don't want to build everything for your machine, but there are quite a few candidates for local compilation. Of course, you can install from pre-built packages first, which is what I'm trying to do, and then selectively compile the ones that look worth optimizing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCL only printer
On Thu, Feb 19, 2004 at 02:20:28PM -0800, Paul Yeatman wrote: Hi, I recently inherited an HP Deskjet 932C printer. Apparently this only uses the PCL printer language. As I need to be able to print postscript for this to be of much use to me, I've been struggling to make this happen. I'm running stable Debian using lprng and ifhp as printer software. According to ifhp documentation, I need to us ghostscript to convert a postscript to (I suppose) PCL so that it can be printed on a printer like mine. Ultimately, this can be setup in the ifhp config file but I'm trying to successfully show that I can do this with ghostscript, 'gs', alone first. I ran for years and years with a PCL printer under lpd. So it's definitely possible. I haven't configured it under Debian, though. I did it with printtool, both under Red Hat 6.2 and Libranet 2.0 through 2.7. I was never able to get it to work under CUPS, not because it was PCL, but because its parallel interface was receive-only and it couldn't report identification and status back to the host's parallel port. As far as I could tell, the only file that needed to be configured after installing lpd was /etc/printcap. Unfortunately, there's some stuff in there that isn't well-documented, so I had to let printtool do the job. You could probably download it from Red Hat, or there might even be a .deb for all I know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge installer: unsure what images needed
There's a new sarge installer??? Can anybody tell me where it resides? Is there documentation with it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: recommended reading?
C'mon, guys, quit snarling at each other. The only dumb question is the one you don't ask. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating a hardware Firewall
On Thu, Feb 12, 2004 at 11:49:54AM -0500, Bojan Baros wrote: Hello. I am looking into creating a firewall for my home network. So far I have a simple Internet router (Netgear) that protects my win and deb boxes, but I would like to replace it with something more substantial. I did the job with Libranet 2.7 on an old Pentium 133 with 3 network boards. Firestarter did the best job of creating an iptables script. I did a little hand-hacking on the script afterward to convert it from 2 networks to 3, so both internal networks are masqueraded to the external network. I can send you a copy if you want. Besides firewalling, the box is also the network print server and a primary master name server for the local hosts and a caching name server for the Internet. It's also set up as a local mail server, but that's not in use yet. Most of the time I administer it with ssh from my main workstation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Floppy installer fails to load modules
Thanks, guys for all the clues so far. Looks like the next step is to spend tomorrow evening reading the docs you suggested, then build an install kernel on one of my working machines. I have Libranet 2.7 and 2.8.1 on everything, and a bare Debian 3.0 on one machine's /dev/sdb. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Old x486 as thin client
On Sat, Feb 07, 2004 at 11:04:56AM -0800, Paul Johnson wrote: I have always wanted to do this. How do you have the 486s run an X server without an OS? Or do they get a base Debian install? You need at least a minimum OS installed to provide an infrastructure for X. A light X client is one way you could do it. On the other hand, I run a 486 as my main Linux workstation -- not that I plan to continue too much longer. There's plenty of software that delivers decent performance on it; for instance, I'm replying to you with Mutt in an xterm. On the other hand, for a major pig like Mozilla, you need at least a Pentium 2 to deliver adequate response. Don't be afraid to try a few things and see what suits your workload. You might end up deciding to set up different machines with different configurations. One thing about old gear is, it's cheap, and you can afford to have some extra boxes around to experiment on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Floppy installer fails to load modules
On Sun, Feb 08, 2004 at 04:15:07PM -0500, David Clymer wrote: This sounds like a problem with the installation instructions. Has anybody successfully done an install from floppies on a system that needs modules to be loaded? Do I need to build a custom kernel and install that on a rescue floppy? I've tried before and had similar problems with loading modules from floppies. I would suggest 2 things: 1. try a different install kernel (type F3 at the CD boot prompt) 2. build a custom kernel and copy it over linux.bin on the boot floppy most likely, if you are going to be booting off a SCSI controller for which the install kernel doesnt have a driver compiled in, you are going to have problems, and will have to compile a custom kernel. The load modules from floppy option often isnt really useful - loading modules usually can be put off until after you've got a base debian install and can more easily configure your system to support whatever hardware you like. The manuals and some of the messages from the installer differ on that point. The key observation seems to be that the installer insists on laying out partitions before it even attempts to get further installation software from either the CD or the net, and it also needs to load modules to use the network boards. That being the case, it needs modules right then, and the floppies are the only place it could get them. So it looks like there's a fatal bug associated with loading modules from floppies, and therefore a custom kernel is necessary. That's a real drag. This is going to be a major chore to figure out, because there's no cut-and-drived procedure to follow. I'll give F3 a shot, though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: recommended reading?
I took a run down to the bookstore tonight to look at Debian GNU/Linux Bible, on the strength of the recommendation on this thread. I found it rather dated, and I didn't think it went into as much useful detail as Debian GNU/Linux 2.1 Unleashed. Admittedly, that's dated too, but I didn't find anything on Debian that's newer. The Linux Administration Handbook has quite a bit on Debian, though, and it's a lot more recent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Floppy installer fails to load modules
Didn't find anything about this in the archives. I want to install Woody or Sarge on two older machines that have SCSI CD-ROMs and SCSI hard disks. Neither can boot from a CD. I've always booted installation programs from floppies in the past. I downloaded the boot floppy set and wrote them out according to the instructions in Installing Debian GNU/Linux 3.0 for Intel x86. I've read the manual pretty thoroughly. I checked each floppy against the downloaded image with cmp. None had errors. After the rescue and root floppies read in, I got a message saying that no hard disks were recognized. (The same thing occurs with my Ethernet boards; they need to have modules loaded before they can be recognized.) Then I select Load modules from floppies. That fails with a message saying that it was unable to mount the driver floppy. If I try to mount any of them on a machine that has Linux running, it asks me to specify the filesystem type. All reasonable guesses fail -- it ain't msdos, ext2, or ext3. This sounds like a problem with the installation instructions. Has anybody successfully done an install from floppies on a system that needs modules to be loaded? Do I need to build a custom kernel and install that on a rescue floppy? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
