Re: Procmail and smail
Hi, On Tue, Oct 27, 1998 at 11:13:48AM -, Moore, Paul wrote : > Hi, > I have smail and procmail installed, and I want to get them working > together. I am currently using a .forward file to push my mail through > procmail, but what I'd like is if smail used procmail directly as the > local delivery agent (when I used the SuSE distribution, with sendmail > and procmail, it did this). This would mean that any user with a > .procmailrc would automatically get mail processed via procmail, without > needing the extra .forward file. > > I've looked in the smail and procmail documentation, but I can't see > what I need to add to set this up. I guess I need some form of > transports file, but I can't find an example I can work from. For me, the following works well. But I changed it only a few days ago and it may be incorrect. I got it from some kind of procmail-doc (don't remember exactly) ---snip--- 'local' part of /etc/smail/transports local: driver=pipe, from, local, +inet, -uucp, return_path, unix_from_hack; cmd = "/usr/bin/procmail -d $($user$)", user=root ---snip--- Anyhow many users here recommend "exim". I'd like to know, what makes exim better before I try it, because smail works very well. Regards, Mika -- Mika Fischer <[EMAIL PROTECTED]>
Re: More than one question....
Hi, Vincent!
On Mon, Oct 26, 1998 at 11:08:40PM -0500, Vincent Rosso wrote :
> 4. Finally, how do I change the default resolution X windows starts up
> at? Right now it starts up at 1280x1024. It could be much worse, I
> guess, I could be starting at a resolution of 2 or something. But
> 1280x1024 on a 15 inch monitor is sorta high. I can switch it once I
> start up but then I have to reconfigure my monitor and the virtual
> desktop is still at 1280x1024.
Well, look at your /etc/X11/XF86Config.
There you'll find somthing like this:
--- snip ---
Section "Screen"
Driver "Accel"
Device "ELSA Winner 1000TRIO"
Monitor "My Monitor"
DefaultColorDepth 16
SubSection "Display"
Depth8
Modes"1024x768" "800x600"
Virtual 1024 768
ViewPort 0 0
EndSubSection
SubSection "Display"
Depth16
Modes"1024x768" "800x600"
Virtual 1024 768
ViewPort 0 0
EndSubSection
SubSection "Display"
Depth24
Modes"1024x768" "800x600"
Virtual 1024 768
ViewPort 0 0
EndSubSection
SubSection "Display"
Depth32
Modes"1024x768" "800x600"
Virtual 1024 768
ViewPort 0 0
EndSubSection
EndSection
--- snip ---
There are several 'screen'-sections.
Look at the 'Driver' line.
You have to edit the one of your X-Server. ('accel' in most cases)
The first resolution in each Modes line is the default mode.
Set this instead of "1280x1024" . to
"whateveryouwant" . "1280x1024"
X will then start up using the whateveryouwant-resolution.
The virtual resolution can be configured using the 'Virtual' line.
Set it to the same resolution as your physical if you don't want
virtual desktops (like me :-).
I hope this helps.
Best regards
Mika
--
Mika Fischer <[EMAIL PROTECTED]>
Re: /etc/init.d/isdnutils
Hi! On Fri, Oct 30, 1998 at 07:06:56AM +, Thomas Keusch wrote : > The only obvious "error" I get is this one when calling the script: > > Starting isdn services : isdnlogline0: Operation not supported by device > What might be causing the "Operation not supported by device" error? ISDNLOG tries to get its information out of the card with the ID 'line0'. That's OK, because it's the default ID for card-drivers compiled into the kernel. Nevertheless the default ID for module-drivers is 'HiSax'. > What should I have a look at? The solution is obvious: Make the card respond to the ID 'line0'. You can do this by adding 'id=line0' to your modprobe line (if you load the module by hand or in an rc-script - as it is recommended) or by putting this argument into conf.modules (if you let kerneld do the dirty work - not recommended). > The card is a Teles S0/16.3c1 PnP rev 1.1. I have that one too, and wasn't getting happy with it until I found kernel 2.0.36pre15. With this kernel-patch and the isdnutils included in hamm 2.0 I have solved all my problems (so far). Hope this helps. Mika -- Mika Fischer <[EMAIL PROTECTED]>
Emacs command line option
Hi! I've got a problem with Emacs. I want it to be started in auto-fill-mode. No problem so far. But I have to use an numeric argument with it. This is not possible with the '-f' CMD-line option. So how can I start Emacs in 'auto-fill-mode 70'? My e-mail client invokes emacs as the editor and so I want it to wrap lines at 70 Chars. At the moment I am breaking line manually :-( I hope someone can help me. Thanks in advance Mika -- Mika Fischer <[EMAIL PROTECTED]>
Re: Emacs command line option
On Fri, Oct 30, 1998, dpk wrote: > Create a ~/.emacs file with the following lines: > (setq default-major-mode 'text-mode) > (add-hook 'text-mode-hook 'auto-fill-mode 70) I tried it and it didn`t work. As I don't understand it I can't say why. (I'm using v20.2.2) The second point is that I don't want emacs to always use auto-fill-mode but only if it is invoked by mutt. But I noticed that the auto-fill-mode breaks always at 70 chars. Even if I try to override the value. Strange thing. > If you plan on using emacs a lot, I would install dotfile-emacs... It > is a good starting point to customizing emacs. Hope this helps! I'll try out it, but I think I will have to read the docs if I really want to understand Emacs (and I do). Is there somewhere some kind of 'Getting started with Emacs'-guide on the net? Regards Mika -- Mika Fischer <[EMAIL PROTECTED]>
Re: X: exec of /usr/bin/X11/ failed
Hi, Adam! On Thu, Nov 12, 1998 at 03:06:52PM -0900, Adam Shand wrote : > i while back upgraded all my x stuff and unfortunately timed it just as > the packages had been split up. i managed to figure out what was wrong > and patch things back together but now i'm getting this error when i tried > to change my xserver from s3v to svga. The first line of the file '/etc/X11/Xserver' tells X where to find the server. I think your line looks something like this: /usr/bin/X11/ set it to '/usr/bin/X11/XF86_S3V' after you hav installed the server and it should work. I have still got the 'old' X11 packages but I think it should work with the slink ones the same way. HTH Regards, Mika -- Mika Fischer <[EMAIL PROTECTED]>
Re: X: exec of /usr/bin/X11/ failed
Hi, Adam! On Sat, Nov 14, 1998 at 05:23:22PM -0900, Adam Shand wrote: > one question it appears that the debian setup > actually has a wrapper installed for security reasons so that you aren't > supposed to run them directly. > > do you know, is the Xserver file what the wrapper uses to determine what > to exec? or does this mean that i'm exec'ing the s3v server directly. I think what you search is /usr/doc/X11/README.Debain You can find there: * The X server to be used by default is not selected by changing a symlink. Instead a small wrapper program (/usr/X11R6/bin/X) reads a configuration file (/etc/X11/Xserver) to find out which server to run and who is allowed to run it. I hope this helps. Regards Mika -- Mika Fischer <[EMAIL PROTECTED]>
Re: emu10k1 WILL NOT load!
Hello! * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-06-29 14:02]: > Hello debian-user, this is my first submission and is unfortunately due to the > My sound card is a Creative SoundBlaster Audigy MP3 and so the corresponding > driver should be emu10k1. I am running a 2.4.9 kernel and have tried compiling > the driver module directly into the kernel with no luck. So I currently have > the driver compiled as a separate loadable module, however no matter what I try, > I can not get it to load. Me guess is that your kernel is just too old. I'd try upgrading to 2.4.18 which is available for woody as a security update. So you might want to upgrade for security reasons as well... > siva:~# modprobe -v emu10k1 > /sbin/insmod /lib/modules/2.4.9/kernel/drivers/sound/emu10k1/emu10k1.o > Using /lib/modules/2.4.9/kernel/drivers/sound/emu10k1/emu10k1.o > Symbol version prefix '' > /lib/modules/2.4.9/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such > device > Hint: insmod errors can be caused by incorrect module parameters, including > invalid IO or IRQ parameters > /lib/modules/2.4.9/kernel/drivers/sound/emu10k1/emu10k1.o: insmod > /lib/modules/2.4.9/kernel/drivers/sound/emu10k1/emu10k1.o failed > /lib/modules/2.4.9/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed Normally this works out of the box. I'd go for the newer kernel. Cheers, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: run-parts bug (maybe)
Hi, David! * David <[EMAIL PROTECTED]> [2003-06-30 06:45]: > After running various tests - even editing a copy of the file to where > it only contained "#!/bin/bash" I finally renamed the file substituting > a dash for each dot and bingo! it worked.. > > It seems that run-parts (at least mine (v 1.15 ) ignores any file with a > dot in the name.. That's a feature nor a bug. :) See also the manpage: If the --lsbsysinit option is not given then the names must consist entirely of upper and lower case letters, digits, underscores, and hyphens. > Is this a bug or something about my particular system? Apparently the > maintainer of the kernel-patch package expected it to work, because the > name of the file to be run was debian-2.4.21. If there is a scribt that should be executed but isn't because it has .'s in the name, then that's a bug in kernel-patch (kernel-*package* or what?). Cheers, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: run-parts bug (maybe)
Hi, David! * David <[EMAIL PROTECTED]> [2003-07-01 16:09]: > [EMAIL PROTECTED]:~$ ls -l /usr/src/kernel-patches/all/apply/ > total 4 > lrwxrwxrwx1 dlb dlb13 Jun 28 20:40 debian-2-4-21 -> > debian-2.4.21* > -rwxrwxr-x1 root src 689 Jun 28 08:36 debian-2.4.21* This file comes from kernel-patch-debian-2.4.21. File a bug against this package saying that kernel-package uses run-parts, which doesn't pick up files with dots in the filename. Cheers, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automount
Hi! * JZidar <[EMAIL PROTECTED]> [2003-07-01 19:13]: > Is there an app or trick that would enable to just pop a cd or floppy in the > drive and use it without the need for mount and unmount every time? Can be > this built-in in the kernel? If you know how to patch compile a kernel you should go for supermount. Grab the patch from http://supermount-ng.sourceforge.net/, patch the kernel, compile supermount in :) Then put something similar to this in your /etc/fstab: /mnt/cdrom /mnt/cdrom supermount fs=iso9660,dev=/dev/sr1 0 0 Supermount mounts the CD as soon as you access it (I think) and unmounts it when you press the eject button of the drive... HTH, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Forcing installation over unmet dependencies
Hi, Morten! * Morten Eriksen <[EMAIL PROTECTED]> [2003-07-01 23:46]: > How can I force apt-get to ignore the unmet dependency, or otherwise > get the libqt3-dev package installed? for a permanent solution you want the package equivs. I don't know how to use it though, sorry... HTH, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Newbie Question
* Abrasive <[EMAIL PROTECTED]> [2003-07-01 23:27]: > I'd like to download all the necessary files to upgrade the kernel from 2.2.x to a > 2.4.x > kernel. But, I don't know which files to download, and I have no idea how to upgrade > the kernel the 'Debian Way' Get one of the kernel-image packages here: http://security.debian.org/pool/updates/main/k/kernel-image-2.4.18-1-i386/ if in doubt take: http://security.debian.org/pool/updates/main/k/kernel-image-2.4.18-1-i386/kernel-image-2.4.18-1-386_2.4.18-8_i386.deb and install it with: dpkg -i kernel-image-2.4.18-1-386_2.4.18-8_i386.deb Normally the postinstall script should configure LILO automagically but chacking the lilo config before rebooting can't hurt :) HTH, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 4.3
Hi, Joeri! * Joeri De Backer <[EMAIL PROTECTED]> [2003-07-01 21:20]: > Is there anybody who can tell me if it's possible to install > XFree86 version 4.3? If so: how? :-) If you're using sid: http://penguinppc.org/~daniels/ For woody, i don't know... HTH, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Turn on DMA on boot
Hi, Dan! * Dan Collis Puro <[EMAIL PROTECTED]> [2003-07-02 20:36]: > Anyway: What would be the most "Debian" way to turn on DMA (essentially > run "hdparm -d1 /dev/hda") on boot? I could (probably) add something in > /etc/rc2.d, but that just seems dirty. apt-get install hwtools read /usr/share/doc/hwtools/* vi /etc/init.d/hwtools HTH, Mika -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
