Re: 2.2.0 kernel broke sound

1999-01-28 Thread Miller Paul
On Thu, 28 Jan 1999, Matt Garman wrote: > > Before upgrading to kernel 2.2.0, I had sound working perfectly. I > have a SoundBlaster AWE 32 plug'n'play (ISA). With my 2.0.x kernels, > I used isapnp, then loaded sound as a module (automatically by > kerneld). > > With the 2.2.0 kernel, I've tri

Re: Logging bootup sequence

1998-12-03 Thread Miller Paul
On Wed, 2 Dec 1998 [EMAIL PROTECTED] wrote: > As a new Debian user, I'd kind of like to see what Linux is doing when it > boots up. Is there a way to log the boot up sequence (before the syslog takes > over) so I can peruse it? Unforunately, the Pause key doesn't seem to work... > I'm booting fro

Re: About network daemons in a multi homed workstation

1998-12-01 Thread Miller Paul
On Tue, 1 Dec 1998 [EMAIL PROTECTED] wrote: > The interfaces are well configured; I can ping on any of them, I have a > custom client/server application running on the second interface and the > routed daemon is aware of the third one. But still NFS, telnet and ftp don't > work. > > The /etc/h

Re: /etc/host.deny and co

1998-10-27 Thread Miller Paul
On Tue, 27 Oct 1998, Linh Dang wrote: > I want to deny telnet, ftp and smtp connection from ANY other sites. > But I want to accept http connection, pull down pop3, imap and > send out mail (smtp). > > How do I setup /etc/host.deny, /etc/host.allow and CO. I will RTFM > but since security is so i

Characters Disappearing on virtual consoles

1998-10-27 Thread Miller Paul
This problem is not like a messed up terminal after 'catting' a binary file. What I see is the bitmaps of characters not being fully displayedin my virtual consoles. At first everything is OK, but I leave the terminal unattended for say about 20 minutes, I see the bad bitmapped characters. This doe

Re: IP Firewalling/Forwarding baffles me

1998-09-17 Thread Miller Paul
On Tue, 15 Sep 1998, Kendall P. Bullen wrote: > The protected machine is running Solaris 2.5.1 (possible to be > upgraded to 2.6). It has another 'private' IP address, 192.168.2.2. > (Using those private network numbers seemed like a good idea for > security reasons.) It can ping the IP address