Actually, dpkg-scanpackages is deprecated in woody. There is an
apt-foo program that does the same, is faster and more configurable.
Ah, 'apt-ftparchive', it seems. Thanks for the tip.
A deprecation note in dpkg-scanpage's man page would be nice, though..
- Jarno
--
To UNSUBSCRIBE, email to
Actually, dpkg-scanpackages is deprecated in woody. There is an
apt-foo program that does the same, is faster and more configurable.
Ah, 'apt-ftparchive', it seems. Thanks for the tip.
A deprecation note in dpkg-scanpage's man page would be nice, though..
- Jarno
apt-get to install new packages. If anyone could direct me to some docs
describing this I would be most grateful.
The commands you'll have to use are 'dpkg-scanpackages' and
'dpkg-scansources'. I don't remember the details, but it's really not too
complicated. Just read the man pages and try
apt-get to install new packages. If anyone could direct me to some docs
describing this I would be most grateful.
The commands you'll have to use are 'dpkg-scanpackages' and
'dpkg-scansources'. I don't remember the details, but it's really not too
complicated. Just read the man pages and try
Does anyone know any way to make this more difficult without introducing
a remote host? Are there, for example, any Linux kernel options for
device access passwords or such?
Maybe removing the appropriate /dev/hd* entries after backup, and
recreating them just before backup with mknod.
Ingenious. :b
Does it work reliably with devfs? (So that devices don't magically
reappear after deletion, for example)?
I can hear sarcasm in your words,
Not at all - except towards my own stupidity for not even thinking of such a
simple solution. :)
The follow-up question was just
We're using rsync to mirror a hot drive in our main server to a cold drive
(one that is only mounted when backing up, and is briefly mounted read only
for per file restoration).
...which reminds me of a related problem of mine. On my own system, I'm using
a fixed spare IDE hard drive for
Does anyone know any way to make this more difficult without introducing
a remote host? Are there, for example, any Linux kernel options for
device access passwords or such?
Maybe removing the appropriate /dev/hd* entries after backup, and
recreating them just before backup with mknod.
Ingenious. :b
Does it work reliably with devfs? (So that devices don't magically
reappear after deletion, for example)?
I can hear sarcasm in your words,
Not at all - except towards my own stupidity for not even thinking of such a
simple solution. :)
The follow-up question was just
You either need to compile/get a kernel with the required SCSI drivers
built in, or get the module for it.
A module probably won't do if the root file system (/) is on a SCSI driver. I
think you will have to compile the driver statically into the kernel.
- Jarno
/etc/default/maildelivery
[...]
Any packages treating with system mailbox handling, should use the
first word in the first line of this file, to determine how to
configure themselves.
Sounds very good, but are you sure this is feasible enough to implement?
It would probably be quite easy
People still use pine? Where do you get deb's for that, or at least
installer deb's. Last time I looked they apeared gone for good. I have one
user who want's his pine fix bad, and I've been fobbing him of with it's
no-longer available, use mutt.
The Pine license prohibits distribution in
Hi,
I get daily error from exim (and some other packages, but mainly exim):
/bin/sh: root: command not found
/etc/cron.daily/exim:
failed to open database lock file /var/spool/exim/db/retry.lockfile:
Permission denied (euid=1000 egid=50)
failed to open database lock file
Hi,
I get daily error from exim (and some other packages, but mainly exim):
/bin/sh: root: command not found
/etc/cron.daily/exim:
failed to open database lock file /var/spool/exim/db/retry.lockfile:
Permission denied (euid=1000 egid=50)
failed to open database lock file
Hi,
I'm building a set of scripts to archive email messages in a custom way.
Do you know of any better shell tools for extracting from, cc, subject etc.
from the headers than procmail/formail?
The problems with them are that if there are non-ASCII characters in the
subject, I get a still
Do you know of any better shell tools for extracting from, cc, subject
etc. from the headers than procmail/formail?
How about Python and its RFC822 modules?
Thanks, Python did it easily after getting comfortable with the language and
libraries (never really used Python before). I used the
Hi,
Is there any comprehensive maildir-howto around?
All I can find is some bits and pieces on how to setup some individual
programs to support it. None of them tell, for example, what to do with
'login', environment variables, 'mail', .forward etc. It doesn't help much to
know how to get
and Pine (obviously, since I've built it myself) still use
/var/spool/mail.
- Jarno
On Sunday 17. Februaryta 2002 00:55, Jarno Elonen wrote:
I have a small problem with ipop3d.
After a recent system update, ipop3d stopped moving users' mail from
/var/spool/mail to mbox. Now both 'mail
and Pine (obviously, since I've built it myself) still use
/var/spool/mail.
- Jarno
On Sunday 17. Februaryta 2002 00:55, Jarno Elonen wrote:
I have a small problem with ipop3d.
After a recent system update, ipop3d stopped moving users' mail from
/var/spool/mail to mbox. Now both 'mail' command
No concrete solution to the problem, but did you notice that the default
location for the mailboxes has changed from /var/spool/mail to /var/mail?
Huh? At least exim's fresh configuration file still says:
file = /var/spool/mail/${local_part}
Try stracing the ipop3d process and look what
No concrete solution to the problem, but did you notice that the default
location for the mailboxes has changed from /var/spool/mail to /var/mail?
Huh? At least exim's fresh configuration file still says:
file = /var/spool/mail/${local_part}
Try stracing the ipop3d process and look what
Hi,
I have a small problem with ipop3d.
After a recent system update, ipop3d stopped moving users' mail from
/var/spool/mail to mbox. Now both 'mail' command and pop3 clients show empty
mailbox even if exim has in fact pumped /var/spool/mail full of new messages.
I previously had ipop3d with
Hi,
I have a small problem with ipop3d.
After a recent system update, ipop3d stopped moving users' mail from
/var/spool/mail to mbox. Now both 'mail' command and pop3 clients show empty
mailbox even if exim has in fact pumped /var/spool/mail full of new messages.
I previously had ipop3d with
23 matches
Mail list logo
