-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I sometimes receive double-posts, but it is only when my address is placed in
the To: or CC: fields. My mail reader indicates this by placing a C in the
message listing if I am in CC ant a T if I am in To. So far, this is the only
time when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just read the guidelines at
http://people.cornell.edu/pages/kk288/du-guidelines.html
and have one question. I understand the general concept of inline posting,
which is what you are advocating in this document, (not to be confused with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Let me try a couple of possible replacements for the dynamic MMap error
message. Maybe one of these will more clearly state the error without being too
verbose:
Allowed cache too small.
Allowed cache too small; please (reconfigure|resize).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh no! I meant to send this to the list. I need to check my fields better. It
seems when I hit reply on debian-user, it sends to the person who sent the
message instead of sending it back to the list like most lists do. I usually
catch it, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow. Now I broke the thread. Damn I'm good! ;-(
Lorenzo
- --
- -BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d- s:+ a- C+++ UL P+ L+++ E- W++ N o K- w---
O M V- PS+++ PE Y+ PGP++ t++ 5+ X+ R tv-- b++ DI-- D+
G e* h r+++ y+++
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Sher's comments on Re: Ubunto vs. Debian were as follows:
# Please use the same thread. Please do not open different threads for the
# same topic that is still active. Your reply could as well go into the
# thread titled Debian or Ubuntu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can run a perl script from a cron job just like any other program. As the
user whose home directory the file is in:
crontab -e
and in the file put
0,30 * * * * ~/doc/id.pl
Note that the /home/user part can be replaced with ~ just like in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reply- debian-user@lists.debian.org
In-Reply-To: [EMAIL PROTECTED]
OS: Debian GNU/Linux Unstable (Sid)
Linux-Kernel: 2.6.11-1-k7
Linux-User: 346322 (http://counter.li.org)
Martin Kenneth Lopez's comments on Sound Configuration were as follows:
# I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
# Preparing to replace udev 0.056-3
# (using .../archives/udev_0.062-4_i386.deb) ...
# udev requires a kernel = 2.6.12, upgrade aborted.
rant
This is a classic example of probably the only thing I dislike about Debian.
The latest version of udev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
kamaraju kusumanchi's comments on Re: failing to upgrade udev were as follows:
# In such a case, you should use stable distribution. Unstable is not for
# everyone. It is useless to complain about instability of unstable.
# Unstable is meant just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sarge and stable currently refer to the same Debian branch in the official
Debian mirrors. However, when Etch becomes stable, stable will refer to Etch
rather than Sarge and sarge will still refer to Sarge, which will then be
considered old-stable.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Scott's comments on Re: xorg in sid were as follows:
# Don't I need xserver-xorg which is dependent on xserver-common
# 6.8.2.dfsg.1-1 and therefore not installable?
Mine did install and it shows that the correct xserver-common is installed.
I am able to switch to any virtual console I want with ctrl-alt-functionkey.
I am using the latest Sid as of yesterday on i386, complete with xserver-xorg.
Lorenzo
--
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d- s:+ a- C+++ UL P+ L+++ E- W++ N o K- w---
O M V- PS+++ PE Y+ PGP++ t++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am running orville-write on my Debian Sid system, which, as far as I can tell,
is the only package that provides /usr/bin/write. Every day, I get an email
from Cron which presents the output of chkrootkit. It shows me a list of files
and also a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Scott's comments on xorg in sid were as follows:
# I see that some xorg packages are now in sid. Are there enough packages
# to switch from xfree86? Are there any problems?
My aptitude removed xfree86 and replaced it with xorg. I have had no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lale's comments on [SOLVED] Re: Cannot burn audio tracks with cdrecord
were as follows:
# If I use disk at once
# $ cdrecord -eject -v -dao speed=16 -pad -audio dev=ATA:1,0,0 *.wav
# I get a disc not recognised by audio equipment.
#
snip
#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure how the = signs got into my message. I don't use MS products, and
in fact, refuse to use Windows, and I am using a plain-text editor to compose my
mail. The = signs almost look like some kind of margin bell or something turned
on either
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Clive Menzies's comments on Re: sarge or etch? were as follows:
# You, Carl, are an experienced Debian user; would you really suggest a
# newcomer to debian, install from etch?
PersonalOpinion
I feel that since sarge is stable and only about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
roberto's comments on mc confusion were as follows:
# what is M-Tab M-Enter C-Enter and so-on...
M-Tab, or Alt-Tab is the mc equivalent to the Tab key in the shell. It does
command-line completion.
M-Enter, or Alt-Enter puts the currently selected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen R Laniel's comments on Re: OT (and Flamebait): Top-Posting were as
follows:
# On Thu, Jul 07, 2005 at 02:52:41PM -0500, Kent West wrote:
# message
# messageWereReplyingTo
# This is some stuff that a guy wrote
#
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen R Laniel's comments on Re: OT (and Flamebait): Top-Posting were as
follows:
# I've had similar ideas recently about using XML for conf
# files in /etc, but that would take a bit of elaboration.
# I'll save that for another time.
Wow! A good
I'm not sure about the recovery data, but p7zip will handle multivolume archives
and has a superior compression ratio to rar. Plus it is GPL.
Lorenzo
--
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d- s:+ a- C+++ UL P+ L+++ E- W++ N o K- w---
O M V- PS+++ PE Y+ PGP++ t++ 5+ X+ R tv--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just installed Sarge on my laptop and upgraded to Sid with kernel
2.6.11-1-686.
I installed the latest versions of linux-sound-base, alsa-base, libasound2 and
alsa-utils and ran alsaconf. Everything worked fine until I rebooted, when the
mixer
23 matches
Mail list logo