Re: Sox - no more play?
On Fri, 4 Apr 1997, Jim wrote: The sound tool, sox, used to have a 'play' symlink that no longer works. So.. how on earth do we get sox 12.12 to play (.au) files? Simply cat'ing them to /dev/dsp sounds terrible! :-) Try catting to /dev/audio, it does the ulaw decoding by default. Jason
Re: Sox - no more play?
The sound tool, sox, used to have a 'play' symlink that no longer works. So.. how on earth do we get sox 12.12 to play (.au) files? Simply cat'ing them to /dev/dsp sounds terrible! :-) You could do something like this: sox -t au sound.au -t sbdsp /dev/dsp
inetd dying
Hello, Recently my inetd daemon has been dying leaving no traces. Any ideas on this ? Thanks much, Lennard
Re: ppp loopback
[EMAIL PROTECTED] writes: [snip] But .. it doesn't start ip-up properly, since ip-up does the following: [snip] # routing route del default route add default dev ppp0 # send mail echo 'doing putmail' /dev/console $EXECDIR/putmail # get mail echo 'doing getmail' /dev/console $EXECDIR/getmail [snip] and I get messages from the echo lines, but I don't get any mail popped or sent. Strange is, if I run ip-up by hand, it behaves properly. Do putmail and getmail rely on any settings of uid? Slackware 3.0's pppd ran ip-up (for me) with euid=root, uid=carey. Debian's pppd runs ip-up with euid=root, uid=root. I'm using the gid=carey to work out who invoked pppd. Also, in debian pppd I have to set default route by hand, since pppd informs me that he refuses to substitute my default route (usually to eth0) to ppp0 I'm using defaultroute in options file, but this doesn't help. Are you sure the previous default route is right? For example, at work we use 192.168.17.* and 192.168.18.* subnets, where 192.168.17.200 aka 192.168.18.200 is the router. My machine is 192.168.17.11, so I can access the first subnet OK with route add -net 192.168.17.0. To access the second I could route add default 192.168.17.200 (I think), but the better solution is route add -net 192.168.18.0 gw 192.168.17.200. The best solution is to start routed -q which updates my machine from the router's periodic broadcasts. I think I should put some stuff in /etc/gateways in case someone else's machine starts broadcasting bogus routes though. -- Carey Evans * [EMAIL PROTECTED] Double, double, toil and trouble, / Fire burn and cauldron bubble.
unsbuscribe
unsbuscribe ---BeginMessage--- unsbuscribe -- +=++=+ || || ByoungLae Kim, || || _\\|//_ || Seoul National University, || || //.'.\\ || School of Electrical Engineering. || || q - p || http://laplace.snu.ac.kr/~pos7hink. || || oOo-(__O__)-oOo || [EMAIL PROTECTED] || || || Think positively and good. || +=++=+ ---End Message---
Re: lilo.conf--vga=ask doesn't; APM
Hello Douglas and Carey, On 03-Apr-97, Douglas L Stewart wrote On 4 Apr 1997, Carey Evans wrote: APM support can be in a 2.0.27 kernel if it's compiled in. Recompiling your kernel isn't too bad, if you make sure you have all the information about all your hardware and use make menuconfig or make xconfig. make-kpkg is supposed to make it easier too, although I haven't used it. If your current setup works, you don't need to know anything about your hardware. Just keep hitting enter when running make config until near the end when it comes to APM. Just turn it on and keep hitting enter, then Thank you for your suggestions about recompiling the kernel to include APM support. Could I ask you a follow-up question to your messages? I have tried running 'make config', 'make menuconfig' and 'make xconfig', but I always get the same error, No rule to make target 'config'. Running 'make -p' shows no entries under the Make data base, which I suspect is related to the error message. I hope this isn't an utterly ignorant question--I am trying to read as fast as I can, but Unix just seems to be getting bigger and more complex at an equal or greater rate. ;-) Cheers, Nikolaj -- Nikolaj Richers, North York, Canada, [EMAIL PROTECTED]
Re: lilo.conf--vga=ask doesn't; APM
-BEGIN PGP SIGNED MESSAGE- This may be a stupid question, but, are you typing make *config in the /usr/src/linux directory? It doesn't work in any other directory. If you are then you should replace your kernel source files because somthin aint right. On 05-Apr-97 Nikolaj Richers wrote: Hello Douglas and Carey, On 03-Apr-97, Douglas L Stewart wrote On 4 Apr 1997, Carey Evans wrote: APM support can be in a 2.0.27 kernel if it's compiled in. Recompiling your kernel isn't too bad, if you make sure you have all the information about all your hardware and use make menuconfig or make xconfig. make-kpkg is supposed to make it easier too, although I haven't used it. If your current setup works, you don't need to know anything about your hardware. Just keep hitting enter when running make config until near the end when it comes to APM. Just turn it on and keep hitting enter, then Thank you for your suggestions about recompiling the kernel to include APM support. Could I ask you a follow-up question to your messages? I have tried running 'make config', 'make menuconfig' and 'make xconfig', but I always get the same error, No rule to make target 'config'. Running 'make -p' shows no entries under the Make data base, which I suspect is related to the error message. I hope this isn't an utterly ignorant question--I am trying to read as fast as I can, but Unix just seems to be getting bigger and more complex at an equal or greater rate. ;-) Cheers, Nikolaj -- Nikolaj Richers, North York, Canada, [EMAIL PROTECTED] Have a good one. - -- Rick Jones E-Mail: Rick [EMAIL PROTECTED] Date: 05-Apr-97 Time: 09:22:54 - -- -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBM0ZgSwi+Ph+i3TgpAQFrmgQAvmNl6LQjcbdpALJezRAzE6mtGcC8h/vz JsP6RvUHq0i/kHpivpRAbDoTXuFQMqZJUHKoPJ2dD/yq19R4Ka8IAo0pzmj3OoTt vMhmHtzr150YAX+O3f2QAPRVtSwIgQwvmszGMsH0NbTIwfTKA0/EFPkMp3idT3K7 9BFEvZxip9M= =zEX0 -END PGP SIGNATURE-
syslogd will not start
For some reason syslogd refuses to start in the /etc/init.d/sysklogd file. The docs say to use a -n command line argument if starting syslogd from the inits, but at bootup I see the message -n unknown option and it still doesn't start. I can start it manually just fine, but that is a pain. I did nothing special to this system, so I assume others must have had this happen, too. What is the secret? Here are the lines in my /etc/init.d/sysklogd file: SYSLOGD= # Use KLOGD=-k /boot/System.map-2.0 to specify System.map # KLOGD= case $1 in start) echo -n Starting system log daemon: syslogd start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- $SYSLOGD -- Ken Gaugler N6OSK Santa Clara, California email: [EMAIL PROTECTED] URL: http://www.wco.com/~keng The life of a Repo Man is always INTENSE...
Re: syslogd will not start
On Sat, 5 Apr 1997, Ken Gaugler wrote: For some reason syslogd refuses to start in the /etc/init.d/sysklogd file. The docs say to use a -n command line argument if starting syslogd from the inits, but at bootup I see the message -n unknown option and it still doesn't start. Here are the lines in my /etc/init.d/sysklogd file: SYSLOGD= # Use KLOGD=-k /boot/System.map-2.0 to specify System.map # KLOGD= case $1 in start) echo -n Starting system log daemon: syslogd start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- $SYSLOGD Here's mine. I didn't ch9ange mine either! case $1 in start) echo -n Starting system log daemon: syslogd start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD ...RickM...
Re: syslogd will not start
On Sat, 5 Apr 1997, Rick Macdonald wrote: Here's mine. I didn't change mine either! case $1 in start) echo -n Starting system log daemon: syslogd start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds when syslogd starts. It didn't used to. I'm running from unstable. Anybody know what it's doing? ...RickM...
Re: Safer package installation
In message [EMAIL PROTECTED] you wrote: ... If we use the /usr/packages/* method, though, we can separate installation into two steps. The maintainer supplies normal install scripts that handles everything under /usr/packages/package-name/. It runs as, say, user tool, group bin. After that's finished, a separate, *standard*, Debian-provided script runs (as root) that sets up the symlinks, and changes the ownership of /usr/packages/package-name to, e.g., bin:bin. (Or root:root, or package:dialout,dip, or whatever is needed.) Aint that simple -- the standard debian-provided script released yesterday has to know how to handle a new package I will release tomorrow. So we need to wait for the new version of the script, then ppl can install my new package, report bugs, then I release a new version, then we wait for the new version of the script etc. Multiply by slightly more than 1000, which is the current number of debian packages. Ok, the alternative is that the script uses the information provided inside the package, which is precisely what we have now and the only benefits of your scheme is a different (read non-standard) directory structure and heaps of symlinks -- waste of [nowadays cheap] disk space, possibility of symlinks pointing to unmounted filesystems, [ add more here ] ... And don't tell me I can't exploit the script to screw up people's systems: it has to modify at least /etc, in addition to changing symlinks (unless of course we move all the configuration files from /etc -- nice thing about standards is that we don't have to follow them.) Aieee, /vmlinuz is a symlink pointing to /usr/kernel-image/vmlinuz, but /usr is not mounted! Not a good day to die! ... Yes, there are exceptions. Indeed. Eg. all packages that have system-wide config files have them in /etc. ... Dselect and dpkg can be set to prompt, This package requires a script to run as user root. Do you want to [e]xamine the script, [r]un it, or [a]bort installation? Read: do you want to suspend dselect, su to root and continue? Do you want to suspend dselect, login as root, install and configure su and then continue? Do you want to do all of the above, go learn Perl, examine the script and _then continue? Oh [EMAIL PROTECTED], why didn't I run dselect as root in the first place? Where's my nearest RedHat mirror? ... This does require revision of dpkg, dselect, and the .deb format. And in the end, we will still rely on the very same thing -- that people involved didn't insert malicious code in the package, and that bugs will be soon found by us users, and promptly corrected. Your scheme simply removes debian package maintainers from the list of people involved. Since I kinda trust them (have since .93R6), I don't think it's worth the hassle. Regards -- Dimitri reply to emaziuk at curtin.edu.au --- Avoid reality at all costs.
Re: ppp loopback
[EMAIL PROTECTED] writes: [snip] But .. it doesn't start ip-up properly, since ip-up does the following: [snip] and I get messages from the echo lines, but I don't get any mail popped or sent. Strange is, if I run ip-up by hand, it behaves properly. Do putmail and getmail rely on any settings of uid? Slackware 3.0's I don't know. Maybe. putmail simply checks if there are files in /var/spool/mqueue and if so starts sendmail on the queue. getmail starts popclient with appropriate parameters, and the filters received mail with awk. I'll check on this, but id doesn't work with root either. I also have to say that only getmail is not working .. mail get sent. So probably it's a problem with popclient (which is newer than Slack and has some differencies in options .. and is obsolete, substituted by .. fetchmail? that was alos substituted by .. don't remember .. I'll try qpopper and see how it behaves. pppd ran ip-up (for me) with euid=root, uid=carey. Debian's pppd runs ip-up with euid=root, uid=root. I'm using the gid=carey to work out who invoked pppd. Also, in debian pppd I have to set default route by hand, since pppd informs me that he refuses to substitute my default route (usually to eth0) to ppp0 I'm using defaultroute in options file, but this doesn't help. Are you sure the previous default route is right? For example, at Well. I'm almost sure here (but could be wrong anyway). My LAN is made up of two PCs, rarely up together (it's my home LAN). So default route is usually thru eth0, like this: (route -n) Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface a.b.c.0 0.0.0.0 255.255.255.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 05 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 01 eth0 This is how both Slack and Debian (with /etc/init.d/network) set it up. When I call my ISP, I want my default route to be thru it: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface a.b.c.0 0.0.0.0 255.255.255.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 05 lo 0.0.0.0 my.isp.addr 255.255.255.0 U 0 01 ppp0 that's it. When I hang up, it has to revert to prior setup. With Slack that happened simply using defaultroute in /etc/ppp/options. The best solution is to start routed -q which updates my machine You probably have real networks, so you have real routers and gateways. I think mine would be a little up-on-steroids home LAN if I used routed. from the router's periodic broadcasts. I think I should put some stuff in /etc/gateways in case someone else's machine starts broadcasting bogus routes though. Thanks for your suggestions, -- |||| ||| Marco Frattola Microsoft is not the answer ||`..'|| |||... Piacenza, ItalyMicrosoft is the question ||| ||| |||''[EMAIL PROTECTED]No is the answer ||| ||| ||| www.enjoy.it/users/~mk/index.html Live Linux, live free!
Re: syslogd will not start
[EMAIL PROTECTED] wrote: For some reason syslogd refuses to start in the /etc/init.d/sysklogd file. The docs say to use a -n command line argument if starting syslogd from the inits, but at bootup I see the message -n unknown option and it still doesn't start. because, written as it is shown below, you're passing -n to start-stop-daemon, not to syslogd (I discovered this with another daemon, but think it is valid to syslogd too) I can start it manually just fine, but that is a pain. I did nothing special to this system, so I assume others must have had this happen, too. start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- $SYSLOGD try this start-stop-daemon --start --quiet --exec /sbin/syslogd -- -n $SYSLOGD HTH -- |||| ||| Marco Frattola Microsoft is not the answer ||`..'|| |||... Piacenza, ItalyMicrosoft is the question ||| ||| |||''[EMAIL PROTECTED]No is the answer ||| ||| ||| www.enjoy.it/users/~mk/index.html Live Linux, live free! Nope. This hoses my system completely. These boot messages print: syslog: /dev/xconsole: Interrupted system call syslogd: unknown priority name ..] syslogd: unknown priority name and then hangs. Thanks anyway! -- Ken Gaugler N6OSK Santa Clara, California email: [EMAIL PROTECTED] URL: http://www.wco.com/~keng The life of a Repo Man is always INTENSE...
Re: syslogd will not start
On Apr 5, Rick Macdonald wrote On Sat, 5 Apr 1997, Rick Macdonald wrote: Here's mine. I didn't change mine either! case $1 in start) echo -n Starting system log daemon: syslogd start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds when syslogd starts. It didn't used to. I'm running from unstable. Anybody know what it's doing? It's just sleeping ;-) Seems to be a quick and dirty hack which came from the upstream source to solve problems with bash2.0. Hopefully it will be solved more cleanly in the near future. Greetings, Christian -- Christian Meder, email: [EMAIL PROTECTED] What's the railroad to me ? I never go to see Where it ends. It fills a few hollows, And makes banks for the swallows, It sets the sand a-blowing, And the blackberries a-growing. (Henry David Thoreau)
Re: syslogd will not start
Ken Gaugler writes: For some reason syslogd refuses to start in the /etc/init.d/sysklogd file. The docs say to use a -n command line argument if starting syslogd from the inits, but at bootup I see the message -n unknown option and it still doesn't start. because, written as it is shown below, you're passing -n to start-stop-daemon, not to syslogd (I discovered this with another daemon, but think it is valid to syslogd too) I can start it manually just fine, but that is a pain. I did nothing special to this system, so I assume others must have had this happen, too. start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- $SYSLOGD This actually means that -n is an argument to start-stop-daemon start-stop-daemon --start --quiet --exec /sbin/syslogd -- -n $SYSLOGD Now it's an argument for /sbin/syslogd. but please read the manual again to find yout what -n does. IT TURNS OFF AUTO-BACKGROUNDING. This means that YOUR SYSTEM WILL WAIT UNTIL SYSLOGD DIES - which won't be the case for sure. Nope. This hoses my system completely. These boot messages print: Sure! RTFM syslog: /dev/xconsole: Interrupted system call syslogd: unknown priority name ..] syslogd: unknown priority name and then hangs. Please check your /etc/syslog.conf file. This mistake sounds very strange to me. Joey -- / Martin Schulze * Debian GNU/Linux Developer * [EMAIL PROTECTED] / / http://www.debian.org/ http://home.pages.de/~joey/
xdm?
Hello, When ever I boot up linux xdm starts before i log in. After login i try to run xwindows but it tells me that it is already running. Can someone tell me which file loads the xdm and how do i disable it? I have tried the SVGA and VGA servers but i get the same results. I just installed them (at sepearate times) and neither of them have ever worked. The error says i can't make a connection. Thank you Chris [EMAIL PROTECTED]
MC broken?
Today, I upgraded MC to version 3.5.17 from the unstable tree, and so far, I have been unable to get the new version to run. It prints two blank lines and then hangs, and I have to kill it from another terminal to get my prompt back. I have tried using different terminal definitions, turning off mouse support, turning off color, to no avail. There does not seem to be any debug feature for MC. On a side note, I have noticed that with newer versions of MC, the file 10 appears in my home directory with the name of that directory. I assume this is some way of keeping track of the last current directory or something, but this does not work anyway, and it is annoying (a misconfiguration, I'm sure.. but where?) I do not use MC incredibly often, but there are places where it comes in handy, especially for large-scale file actions.. so I would appreciate it if someone could help me with this. Thanks, David Benjamin [EMAIL PROTECTED]
Re: xdm?
Chris writes: When ever I boot up linux xdm starts before i log in. After login i try to run xwindows but it tells me that it is already running. Can someone tell me which file loads the xdm and how do i disable it? Try the following dpkg --configure xbase This might let you re-configure your X11 system and at the end you should be queried if you want to start XDM at bootup. If this doesn't work then replace xbase with your installed xserver package. And if even that fails then take a look at the files in /etc/X11. In one of it there's an option which tells the system to fire up an xdm. [ I haven't proved the above methods, they just came to my mind. So don't blame me if it doesn't work. ] Joey -- / Martin Schulze * Debian GNU/Linux Developer * [EMAIL PROTECTED] / / http://www.debian.org/ http://home.pages.de/~joey/
Re: Postgres95 - missing library
Sorry, but I didn't found the POSTGRES95 package in the unstable tree - do you know where it hides ? --- On Sun, 30 Mar 1997 08:22:20 +0100 Oliver Elphick olly@lfix.co.uk wrote: In message [EMAIL PROTECTED], writes: Hi there, I've recently downloaded the latest stable POSTGRES95 package and installed it (Debian 1.2; kernel - 2.0.27). Apparently I'm missing a package, as postmaster keeps on complaining: can't load library 'libbsd.so.1.0.0. I will appreciate advise as to the whereabouts of the above mentioned librar y. Get the latest postgres from unstable: the missing library is a bug in the stable version. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://homepages.enterprise.net/olly -End of Original Message- - Matiss Horodishtiano P.O.Box 1175, Kfar-Saba 44111, ISRAEL Phone: 972-9-7650177 Fax:972-9-7661463 E-mail: [EMAIL PROTECTED] -
Re: MC broken?
On Sat, 5 Apr 1997, David/Bill Benjamin wrote: Today, I upgraded MC to version 3.5.17 from the unstable tree, and so far, I have been unable to get the new version to run. It prints two blank lines and then hangs, and I have to kill it from another terminal to get my prompt back. I have tried using different terminal definitions, turning off mouse support, turning off color, to no avail. There does not seem to be any debug feature for MC. On a side note, I have noticed that with newer versions of MC, the file 10 appears in my home directory with the name of that directory. I assume this is some way of keeping track of the last current directory or something, but this does not work anyway, and it is annoying (a misconfiguration, I'm sure.. but where?) I do not use MC incredibly often, but there are places where it comes in handy, especially for large-scale file actions.. so I would appreciate it if someone could help me with this. Thanks, David Benjamin [EMAIL PROTECTED] I'm running it on 2 systems. Check that you dependencies are up to date: libgpm1 libc5 ncurses-base Get them also from unstable if necessary. Paul Wade - Greenbush Technologies Corporation http://www.greenbush.com/cds.html Linux CD's sent worldwide
Re: MC broken?
I can't help you with the *.deb package nor 3.5.17, but I've used 3.5.18 for some time without any problems -- compiled from upstream sources and installed in /usr/local. It creates mc.hot, mc.hot.bak and mc.ini in my ~ -- no 10. FWIW I just finished compiling 3.5.22. -- Dimitri (emaziuk at curtin.edu.au) -- Entia non sunt multiplicanda praeter necessitatem
Re: MC broken?
On Sat, 5 Apr 1997, David/Bill Benjamin wrote: Today, I upgraded MC to version 3.5.17 from the unstable tree, and so far, I have been unable to get the new version to run. Could it be trying to use your old .mc.ini files? It acted very strangely here until I deleted them and created new ones. -!-
Bo has been Frozen -- Beta Test
I'm not sure if this was announced before, so... * * * * * * * * * * * * * Bo has now been officially frozen! If you'd like to start upgrading to the packages in that distribution, please do. We can use all the testing we can get. People who can do from-scratch installs are also needed. If you would like to be an official tester, please contact Dale Scheetz [EMAIL PROTECTED]. * * * * * * * * * * * * * Brian ( [EMAIL PROTECTED] ) --- measure with micrometer, mark with chalk, cut with axe, hope like hell
