Re: gpg in KDE, passphrase window, p [ Giorgos Pallas <gpall@ccf.auth.gr> ]
Date: Tue, 28 Aug 2007 12:33:41 +0100 (BST)
From: "Richard Lyons" <richard@the-place.net>
To: "debian-user " <debian-user@lists.debian.org>
Subject: Re: smtp to bytemark.co.uk smarthost (was: using a remote IMAP
server and smarthost)
Message-ID: <57162.83.67.89.134.1188300821.squirrel@www.the-place.net>
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
On Mon, August 27, 2007 21:12, Steve Kemp wrote:
> On Mon Aug 27, 2007 at 15:27:55 +0100, Richard Lyons wrote:
>
>> > It might be time to contact bytemark's technical support.
>>
>> You are probably right. I'll give them a call.
>
> Agreed. Call us, or drop us a mail (!)
I did that, and here is their very reasonable reply:
| Hi Richard, I've currently no opinion on whether our servers
| should support the DSN extension or not. Currently they
| don't, and this is upsetting your chosen MTA which seems like
| odd / picky behaviour to me. I'd suggest swapping it for
| exim4 configured in forward-only mode which will do just as
| good a job.
It does, however, put me back where I started: trying to configure
exim4...
Hey ho.
--
richard
Date: Tue, 28 Aug 2007 13:41:41 +0100 (BST)
From: "Richard Lyons" <richard@the-place.net>
To: "debian-user " <debian-user@lists.debian.org>
Subject: Re: smtp to bytemark.co.uk smarthost (was: using a remote IMAP
server and smarthost)
Message-ID: <40232.83.67.89.134.1188304901.squirrel@www.the-place.net>
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
On Mon, August 27, 2007 10:44, Florian Kulzer wrote:
> On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
>> On Sun, August 26, 2007 22:53, Florian Kulzer wrote:
>>
[...]
>> > #-------------------------
>> > tls off
>> > host FULLY_QUALIFIED_DOMAIN_NAME_OR_IP_OF_SMARTHOST
>> > from YOUR_EMAIL_ADDRESS
>> > auth plain
>> > user YOUR_USERNAME
>> > password YOUR_PASSWORD
>> > #-------------------------
>>
>> Done that. Sending from the VM, now I get
>>
>> msmtp: the server does not support DSN
>> msmtp: could not send mail (account default from /home/richard/.msmtpr=
c)
[...]
> Maybe you need "dsn_notify never" and/or "dsn_return off". I am not sur=
e
> if this is really the reason for the failure or just a warning message.
Update:
These dsn settings do not help. It seems clear that msmtp expects a
DSN compliant server. Bytemark, the ISP, suggested configuring exim4
in forward-only mode, but I am not confident of my ability to get that
right, any more than I did with my previous attempt to configure exim4.
I decided to seek an alternative. esmtp and ssmtp seemed candidates,
but neither can be installed because
- ssmtp conflicts with exim4-config
- esmtp conflicts with exim4-daemon-light.
Can anybody suggest an alternative approach?
The only alternative I can see is to simply remove exim4 and install
several smaller packages that may be easier to configure, or to try with
the courier MTA in place of exim4 -- I already have courier IMAP. I
have no idea whether either of these will make anything easier.
--
richard
Date: Tue, 28 Aug 2007 13:04:57 +0000
From: "Douglas A. Tutty" <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: SATA vs PATA
Message-ID: <20070828130457.GB6357@titan.hooton>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Aug 28, 2007 at 09:26:45AM +0200, Dan H wrote:
> On Tue, 28 Aug 2007 01:41:38 +0000 "Douglas A. Tutty"
> <dtutty@porchlight.ca> wrote:
>
> > In any event, if you're choosing between PATA and SATA, go with SATA
>
> Thanks everybody. This is an easy decicion, seeing that opinions don't
> vary at all. One more question though: This mobo has 2 free SATA
> connections. If I get 2 identical disks, could I set them up as
> striped RAID without a dedicated controller, and could I expect a
> performance boost with a pretty low-end motherboard (I think it's a
> 2800MHz Sempron)?
>
You would use the Linux software raid. Ignore the fakeraid that the MB
calls raid.
For striping you have your choice between raid0 (which is a misnomer
since there is no redundancy) or straight LVM. Create a Volume Group,
make each drive a Physical Volume in that Volume Group, then create a
stripped LV. The advantage of this is that the striping is specific to
the LV and any free space can be used for something else. Also, the
drives don't have to be the same size. Obviously, any stripped volume
could not be bigger than the smaller drive unless you added a third
drive. You specify how may drives should contain stripes, you do not
specify which drives should contain stripes. There is a difference if
there are more than two drives (PVs) in a VG.
All we need now is for LVM to get mirrors and life will get simpler than
the existing md/lvm setup we have now.
Read the LVM-HOWTO in the doc-linux-html package, and of course all the
man pages. It seems complicated but it really is great.
Doug.
Date: Tue, 28 Aug 2007 12:58:58 +0000
From: "Douglas A. Tutty" <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: MSI nVidia NX7600GT-T2D256E
Message-ID: <20070828125858.GA6357@titan.hooton>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Aug 28, 2007 at 08:24:50AM +0100, Tim Day wrote:
> On Tue, 2007-08-28 at 02:17 +0000, Douglas A. Tutty wrote:
> > You mean that the system has totally hung and you can't ssh into it (its
> > not just the keyboard and display that's frozen)?
>
> Yes that's right. No ssh, no response to pings. System is completely
> unresponsive to anything but hard power down or reset button.
>
> > ...Remote-Serial-Console-HOWTO...
>
> Thanks that's exactly the info I was looking for. I have a serial cable
> somewhere (once networked an old 486 over it via PPP or SLIP or
> something 'cos I couldn't get hold of an ISA ethernet card). Will see
> if it yields any useful info next crash (although still no problems with
> the "nv" driver).
Something similar if you just want to caputure console messages: Use a
printer. I've never used a USB printer so I don't know if you can put
that on the kernel command line or if a usb printer will print
plain-text sent to it. However, a parallel printer will work.
Doug.
Date: Tue, 28 Aug 2007 15:17:41 +0200
From: Mirto Silvio Busico <mbusico@technip.com>
To: debian-user@lists.debian.org
Subject: zope2.10-sandbox doesn't configure in Lenny
Message-ID: <46D42075.6040001@technip.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Hi all,
I'm trying to install zope2.10-sandbox 2.10.4-2 on Lenny
When I try an apt-get install I see the error: "dzhandle make-instance:
service user must be specified as user:group" and no sandbox instance is
created.
What can I do?
Thanks
Mirto
P.S. here is the apt-get output:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
msb01:~# apt-get install zope2.10-sandbox
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso
Reading state information... Fatto
The following packages were automatically installed and are no longer
required:
apache-common libnss-ldap python2.5 python2.5-minimal
python-egenix-mxdatetime libpam-ldap python-egenix-mxtools
Use 'apt-get autoremove' to remove them.
Pacchetti suggeriti:
zope-book zope-devguide
I seguenti pacchetti NUOVI (NEW) saranno installati:
zope2.10-sandbox
0 aggiornati, 1 installati, 0 da rimuovere e 135 non aggiornati.
=C8 necessario prendere 0B/178kB di archivi.
Dopo l'estrazione, verranno occupati 311kB di spazio su disco.
Preconfigurazione dei pacchetti in corso
Selezionato il pacchetto zope2.10-sandbox, che non lo era.
(Lettura del database ... 239557 file e directory attualmente installati.)
Spacchetto zope2.10-sandbox (da .../zope2.10-sandbox=5F2.10.4-2=5Fall.deb) =
...
Configuro zope2.10-sandbox (2.10.4-2) ...
dzhandle make-instance: service user must be specified as user:group
msb01:~#
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
--=20
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F
Mirto Silvio Busico ICT Consultant
Tel. +39 333 4562651
=20
Date: Tue, 28 Aug 2007 09:18:37 -0500
From: Martin McCormick <martin@dc.cis.okstate.edu>
To: debian-user@lists.debian.org
Subject: All New rc2.d Scripts get Ignored. Debian from KNOPPIX
Message-Id: <200708281418.l7SEIbwf015631@dc.cis.okstate.edu>
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15629.1188310717.1@dc.cis.okstate.edu>
I installed the newest and probably last Oralux KNOPPIX
distribution from a live CD to the hard disk on a laptop and it
almost works right. I must not have the right magic touch
because I needed to add 2 more startup scripts in /etc/rc2.d in
order to start a software speech synthesizer and to start sshd
which I do want to enable on bootup for remote login capability.
Neither script starts on its own during the run-level 2 phase of
booting though all other scripts with higher as well as lower
sequence numbers do successfully start. The only thing these 2
starts have in common is that I put them there. One references
../init.d/ssh which was already sitting in /etc/init.d. I
figured the link wasn't there as a security measure because you
don't need sshd if you don't want remote logins from other
hosts.
The other references ../initd/speechd-up which starts
the software synthesizer.
Both scripts are executable and will start and run
perfectly after the system boots and one su's to root and
manually starts them, but they act as if they aren't even there
when they should be starting.
I even made a third script called got_this_far which
does absolutely nothing but echo a line to standard output. The
boot process misses that one also.
By testing the scripts, I call them the way init would
/etc/rc2.d/S20ssh start
That works every single time I call it manually.
Any suggestions on how to see inside the logic that is
keeping these 3 scripts from running?
Thank you.
Martin McCormick WB5AGZ Stillwater, OK
Systems Engineer
OSU Information Technology Department Network Operations Group
Date: Tue, 28 Aug 2007 14:23:27 +0000
From: "Douglas A. Tutty" <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: evince unable to open pdf
Message-ID: <20070828142327.GA7765@titan.hooton>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Hello,
I've recently reinstalled box running Etch amd64. However, evince no
longer works. It is my only gnome app; I don't usually have luck with
gnome but need it for this one application. When I ssh into the box
from a P-II with 64 MB ram, Kpdf keeps its image rendering in the
xserver which over-taxes the P-II whereas Evince keeps its memory to
itself, on the amd64.
Evince itself opens OK, but when I open the file dialog with its default
filter of "All Documents", it doesn't see any. If I remove the filter
to "All Files", it sees the pdfs but when I select one to open, it pops
up an error:
Unable to open document
Unhandled MIME type 'application/octet-stream'
When I click on help, it opens the help browser (I have yelp installed),
but instead of getting help, it in turn opens gvim with the XML source:
/usr/share/gnome/help/evince/C
I'm assuming that this is the same problem: the help browser doesn't
know how to handle its own XML help files so opens gvim.
Any ideas?
Thanks,
Doug.
Date: Tue, 28 Aug 2007 10:03:36 -0500
From: Owen Heisler <owenh000@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: smtp to bytemark.co.uk smarthost (was: using a remote IMAP
server and smarthost)
Message-ID: <20070828150336.GA5662@owenh.hopto.org>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy"
Content-Disposition: inline
--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, 2007.08.28 13:41, Richard Lyons wrote:
> On Mon, August 27, 2007 10:44, Florian Kulzer wrote:
> > On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
> >> Done that. Sending from the VM, now I get
> >>
> >> msmtp: the server does not support DSN
> >> msmtp: could not send mail (account default from /home/richard/.msmtpr=
c)
> [...]
> > Maybe you need "dsn_notify never" and/or "dsn_return off". I am not sure
> > if this is really the reason for the failure or just a warning message.
>=20
> Update:
>=20
> These dsn settings do not help. It seems clear that msmtp expects a
> DSN compliant server. Bytemark, the ISP, suggested configuring exim4
> in forward-only mode, but I am not confident of my ability to get that
> right, any more than I did with my previous attempt to configure exim4.
> I decided to seek an alternative. esmtp and ssmtp seemed candidates,
> but neither can be installed because
>=20
> - ssmtp conflicts with exim4-config
> - esmtp conflicts with exim4-daemon-light.
I haven't followed this thread at all so may be way off, but I just set up
msmtp with Mutt to forward to Gmail, and had some slight difficulty with DS=
N.
Gmail doesn't seem to support customization of DSN settings, so when I set
"dsn_notify failure,delay" and "dsn_return headers" Gmail complained. Then=
I
set them both to "off" which should work for a server that doesn't support =
DSN.
Gmail still complained. Then I realized that I had them set in Mutt as wel=
l.
After disabling them there, Gmail accepted mail.
So make sure that the DSN headers aren't getting added to mail somewhere al=
ong
the line.
--gBBFr7Ir9EOA20Yy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG1DlI9XC8Sh1vpNARAh3nAKCgO9CV8Hinv1Af0u+sfXHNG+obgACfZPWV
qaytyCXUx0usPk2azwR93xQ=
=Mb6T
-----END PGP SIGNATURE-----
--gBBFr7Ir9EOA20Yy--
Date: Tue, 28 Aug 2007 11:58:15 -0300
From: "Sergio Belkin" <sebelk@gmail.com>
To: debian-user@lists.debian.org
Subject: Howto enqueue with no sending in sendmail
Message-ID: <8c6f7f450708280758g5c34bbd4n52a4f3757a11003c@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Content-Disposition: inline
SGkgY29tbXVuaXR5LApJIGFtIHBlcmZvcm1pbmcgc29tZSB0ZXN0cyB3aXRoIHNlbmRtYWlsLiBJ
IGhhdmUgMiBxdWV1ZSBncm91cHMgZGVmaW5lZCBieSA6CgpRVUVVRV9HUk9VUChgb3V0c2lkZScs
YFA9L3Zhci9zcG9vbC9tcXVldWUvb3V0c2lkZSwgUj0wLCByPTEwIEk9Nm0nKWRubApRVUVVRV9H
Uk9VUChgbXF1ZXVlJyxgUGF0aD0vdmFyL3Nwb29sL21xdWV1ZSwgRj1mLCBSPTEwLCByPTEwMCwg
ST0xbScpZG5sCgpBbmQgZG9jdW1lbnRhdGlvbiBzYXlzCiJUaGUgbWF4aW11bSBudW1iZXIgb2Yg
cXVldWUgcnVubmVycyBmb3IgYW4gaW5kaXZpZHVhbCBxdWV1ZSBncm91cCBjYW4KYmUgY29udHJv
bGxlZCB2aWEKdGhlIFJ1bm5lcnMgb3B0aW9uLiBJZiBzZXQgdG8gMCwgZW50cmllcyBpbiB0aGUg
cXVldWUgd2lsbCBub3QgYmUKcHJvY2Vzc2VkLCB3aGljaCBpcyB1c2VmdWwgdG8gJydxdWFyLQph
bnRpbmUnJyBxdWV1ZSDvrIFsZXMuIFRoZSBudW1iZXIgb2YgcnVubmVycyBwZXIgcXVldWUgZ3Jv
dXAgbWF5IGFsc28gYmUKc2V0IHdpdGggdGhlIG9wdGlvbgpNYXhSdW5uZXJzUGVyUXVldWUsIHdo
aWNoIGFwcGxpZXMgdG8gcXVldWUgZ3JvdXBzIHRoYXQgaGF2ZSBubwppbmRpdmlkdWFsIGxpbWl0
LiBUaGF0IGlzLCB0aGUKZGVmYXVsdCB2YWx1ZSBmb3IgUnVubmVycyBpcyBNYXhSdW5uZXJzUGVy
UXVldWUgaWYgc2V0LCBvdGhlcndpc2UgMS4iCgpCdXQgSSBzZXQgdG8gIjAiIGBvdXRzaWRlJyBx
dWV1ZSBncm91cCBhbmQgaG93ZXZlciBzZW5kbWFpbCBrZWVwcyBvbgpzZW5kaW5nIG1haWwuCkkn
dmUgYWRkZWQgdG8gYWNjZXNzOgpRR1JQOndoYXRldmVyZG9tYWluLmNvbSAgICAgICAgICAgICAg
ICAgICAgICAgICAgb3V0c2lkZQoKSSB3YW50IHRvIG1haWxzIHNlbnQgdG8gd2hhdGV2ZXJkb21h
aW4uY29tIHN0YXkgaW4gZW5xdWV1ZWQgKGJlY2F1c2UKYXJlIG9ubHkgZm9yIHRlc3RpbmcgcHVy
cG9zZXMpCgpIb3cgY2FuIEkgZG8gdGhhdD8/ClRoYW5rcyBpbiBhZHZhbmNlIQotLSAKLS0KU2Vy
Z2lvIEJlbGtpbiAtCg==
Date: Tue, 28 Aug 2007 11:20:41 -0400
From: Rick Pasotto <rick@niof.net>
To: debian-user@lists.debian.org
Subject: package version numbers
Message-ID: <20070828152041.GY31411@niof.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Aptitude reports that for several packages:
Depends: libglib1.2 (>= 1.2.0) but it is not installable
however 'apt-cache policy libglib1.2' reports:
libglib1.2:
Installed: 1.2.10-17
Candidate: 1.2.10-17
Version table:
*** 1.2.10-17 0
100 /var/lib/dpkg/status
Isn't 1.2.10 >= 1.2.0?
--
"... the state ... is not armed with superior honesty, but
with superior physical strength." -- Henry David Thoreau
Rick Pasotto rick(at)niof.net http://www.niof.net
Date: Tue, 28 Aug 2007 16:06:10 +0100 (BST)
From: "Richard Thompson" <binary@freedom.prodigynetwork.co.uk>
To: debian-user@lists.debian.org
Subject: i686 Port
Message-ID: <1587.90.199.218.242.1188313570.squirrel@freedom.prodigynetwork.co.uk>
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
I was wondering why debian doesn't have a port of packages optimised for
i686, I realise they have support for i386, which obviously incudes
everything from an intel 386 to the latest and greatest intel and amd
processors (running in 32bit), ultimatley the i686 already has 'support'
however I just thought it would be great if a port was available where th=
e
packages had been compiled specifically for i686 as I have noticed that
when I use i686 optimised distro's such as arch, or even slackware there
is a noticable performance difference.
Richard Thompson
Date: Tue, 28 Aug 2007 12:33:24 -0300
From: "Sergio Belkin" <sebelk@gmail.com>
To: debian-user@lists.debian.org
Subject: Fwd: Howto enqueue with no sending in sendmail (SOLVED!)
Message-ID: <8c6f7f450708280833u315f80baoa8aa7c7ed6dc1db1@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Content-Disposition: inline
SSBhbnN3ZXIgbXlzZWxmOgoKSSd2ZSBhZGRlZCB0byBzZW5kbWFpbC5tYzoKZGVmaW5lKGBjb25m
Q09OX0VYUEVOU0lWRScsIGBUcnVlJykKZGVmaW5lKFNNVFBfTUFJTEVSX0ZMQUdTLCBlKQoKTm93
IGFsbCBtYWlsIHNlbnQgdG8gd2hhdGV2ZXJkb21haW4uY29tIGlzIGVucXVldWVkIGJ1dCBub3Qg
c2VudCA7KQoKTm90IGF0IGFsbCA7KQpTZXJnaW8KLS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2Fn
ZSAtLS0tLS0tLS0tCkZyb206IFNlcmdpbyBCZWxraW4gPHNlYmVsa0BnbWFpbC5jb20+CkRhdGU6
IDI4LWFnby0yMDA3IDExOjU4ClN1YmplY3Q6IEhvd3RvIGVucXVldWUgd2l0aCBubyBzZW5kaW5n
IGluIHNlbmRtYWlsClRvOiBkZWJpYW4tdXNlckBsaXN0cy5kZWJpYW4ub3JnCgoKSGkgY29tbXVu
aXR5LApJIGFtIHBlcmZvcm1pbmcgc29tZSB0ZXN0cyB3aXRoIHNlbmRtYWlsLiBJIGhhdmUgMiBx
dWV1ZSBncm91cHMgZGVmaW5lZCBieSA6CgpRVUVVRV9HUk9VUChgb3V0c2lkZScsYFA9L3Zhci9z
cG9vbC9tcXVldWUvb3V0c2lkZSwgUj0wLCByPTEwIEk9Nm0nKWRubApRVUVVRV9HUk9VUChgbXF1
ZXVlJyxgUGF0aD0vdmFyL3Nwb29sL21xdWV1ZSwgRj1mLCBSPTEwLCByPTEwMCwgST0xbScpZG5s
CgpBbmQgZG9jdW1lbnRhdGlvbiBzYXlzCiJUaGUgbWF4aW11bSBudW1iZXIgb2YgcXVldWUgcnVu
bmVycyBmb3IgYW4gaW5kaXZpZHVhbCBxdWV1ZSBncm91cCBjYW4KYmUgY29udHJvbGxlZCB2aWEK
dGhlIFJ1bm5lcnMgb3B0aW9uLiBJZiBzZXQgdG8gMCwgZW50cmllcyBpbiB0aGUgcXVldWUgd2ls
bCBub3QgYmUKcHJvY2Vzc2VkLCB3aGljaCBpcyB1c2VmdWwgdG8gJydxdWFyLQphbnRpbmUnJyBx
dWV1ZSDvrIFsZXMuIFRoZSBudW1iZXIgb2YgcnVubmVycyBwZXIgcXVldWUgZ3JvdXAgbWF5IGFs
c28gYmUKc2V0IHdpdGggdGhlIG9wdGlvbgpNYXhSdW5uZXJzUGVyUXVldWUsIHdoaWNoIGFwcGxp
ZXMgdG8gcXVldWUgZ3JvdXBzIHRoYXQgaGF2ZSBubwppbmRpdmlkdWFsIGxpbWl0LiBUaGF0IGlz
LCB0aGUKZGVmYXVsdCB2YWx1ZSBmb3IgUnVubmVycyBpcyBNYXhSdW5uZXJzUGVyUXVldWUgaWYg
c2V0LCBvdGhlcndpc2UgMS4iCgpCdXQgSSBzZXQgdG8gIjAiIGBvdXRzaWRlJyBxdWV1ZSBncm91
cCBhbmQgaG93ZXZlciBzZW5kbWFpbCBrZWVwcyBvbgpzZW5kaW5nIG1haWwuCkkndmUgYWRkZWQg
dG8gYWNjZXNzOgpRR1JQOndoYXRldmVyZG9tYWluLmNvbSAgICAgICAgICAgICAgICAgICAgICAg
ICAgb3V0c2lkZQoKSSB3YW50IHRvIG1haWxzIHNlbnQgdG8gd2hhdGV2ZXJkb21haW4uY29tIHN0
YXkgaW4gZW5xdWV1ZWQgKGJlY2F1c2UKYXJlIG9ubHkgZm9yIHRlc3RpbmcgcHVycG9zZXMpCgpI
b3cgY2FuIEkgZG8gdGhhdD8/ClRoYW5rcyBpbiBhZHZhbmNlIQotLQotLQpTZXJnaW8gQmVsa2lu
IC0KCgotLSAKLS0KU2VyZ2lvIEJlbGtpbiAtCg==
Date: Tue, 28 Aug 2007 08:35:42 -0700 (PDT)
From: Jeff D <fixedored@gmail.com>
To: debian user <debian-user@lists.debian.org>
Subject: Re: Ping my modem...
Message-ID: <Pine.LNX.4.62.0708280829540.19542@proto.technobounce.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 28 Aug 2007, Charlie wrote:
> On Tuesday 28 August 2007 14:50, Octavio Alvarez shared this with us all:
>> --} On Mon, 27 Aug 2007 21:42:41 -0700, Charlie <ariestao@clearmail.com.au>
>> --} wrote:
>> --}
>> --} >> --} > Is the following a normal reply from a satellite modem to
>> ping:- --} >> --} >
>> --} >> --} > ping: sendmsg: Operation not permitted
>> --} >> --} > ping: sendmsg: Operation not permitted
>> --} >> --} > ping: sendmsg: Operation not permitted
>> --} >> --} > ping: sendmsg: Operation not permitted
>> --} >> --} > ping: sendmsg: Operation not permitted
>> --}
>> --} Your iptables firewall is blocking ICMP.
>> --}
>
> I use the guarddog firewall and allowed ICMP - Redirect and ICMP - Source
> Quench on local and Internet DMZ and tried a combination of all and still get
> the same message.
>
> It must just be something otherwise I reckon, and will get round it
> eventually. I just thought that someone had come across this before.
>
> Thanks anyway for your help Octavio.
> Charlie
> --
ICMP redirect and source quench aren't what ping uses though, you need to
allow echo. Have a look at this doc, section 8.3:
http://newbiedoc.berlios.de/wiki/Setting_up_a_personal_firewall_on_Debian_using_Guarddog
That should get you going.
-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.
Date: Tue, 28 Aug 2007 11:35:09 -0400
From: "Francois Duranleau" <xiao.bai.xiong@gmail.com>
To: debian-user <debian-user@lists.debian.org>
Subject: Re: Cannot open root device "hda1" or unknown-block(0,0)
Message-ID: <8eb883950708280835p44b2ad3agfe84095d44944509@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/27/07, Francois Duranleau <xiao.bai.xiong@gmail.com> wrote:
> On 8/24/07, Bert Schulze <potassium.xyanide@googlemail.com> wrote:
> > Hi
> >
> > I took a look at your config and menu.lst
> > So whats missing seems to be an initrd image which holds all the
> > modules your kernel needs. Your config uses some of em. You should
> > build the initrd
> > mkinitramfs -o /boot/initrd.img-2.6.18 2.6.18
> > and
> > update-grub
>
> Success!!! After struggling with manual packages installation, I could run
> those commands and finally successfully reboot the computer in 2.6.18!
>
> One thing though, I had several messages about an '-F' invalid option when
> I ran 'mkinitramfs -o /boot/initrd.img-2.6.18 2.6.18', but everything seems
> okay this far.
>
> Thank you all for your help!
Argh! I cried out victory too soon... I was running a big update until
at one point
the root file system got remounted read-only. Its seems like the 2.6
kernel really
doesn't llike the CRC errors (see
http://lists.debian.org/debian-user/2007/08/msg00252.html). And then I had to
run a filesystem check and I lost many files, and now I can't boot the system.
I guess now there isn't much I can do but to maybe reinstall, or maybe I can try
to reinstall the core packages. Also, I guess I will have to live without DMA in
order to avoid the same situation later on.
--
Francois
Date: Tue, 28 Aug 2007 11:28:35 -0400
From: "Richard Carter" <carter.r.a.l@gmail.com>
To: "CLUG General" <clug-talk@clug.ca>,
"Linux questions" <forum@linuxquestions.org>,
debian-user@lists.debian.org
Subject: Shut down or leave on?
Message-ID: <92db4b30708280828l13fe12eeu703de66d132e63ec@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_56799_19592566.1188314915751"
------=_Part_56799_19592566.1188314915751
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi Folks,
Is it better to leave a system running all the time or is it better to shut
it down over night, on weekends, holidays etc?
In the past I have always shut my Debian system down over night etc for 3
reasons:
1) I put backups on my 80GB external HD which I usually leave shut down even
when I boot the rest of the system. It's about the same age as my internal
160GB HD so I hoped to reduce the probability of it failing at the same time
as the internal HD by starting it less often.
2) I hoped to reduce the probability of being hacked by shutting down,
although I do have a firewall installed.
3) I thought it was a waste of electricity, and money, to have a machine
running that wasn't being used.
But I notice that most backup utilities are designed to backup automatically
at the same time every day or week. That seems to assume that the system is
always running.
I'd appreciate your advice.
Robin Carter
------=_Part_56799_19592566.1188314915751
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi Folks,<br><br>Is it better to leave a system running all the time or is it better to shut it down over night, on weekends, holidays etc? <br><br>In the past I have always shut my Debian system down over night etc for 3 reasons:
<br><br>1) I put backups on my 80GB external HD which I usually leave shut down even when I boot the rest of the system. It's about the same age as my internal 160GB HD so I hoped to reduce the probability of it failing at the same time as the internal HD by starting it less often.
<br><br>2) I hoped to reduce the probability of being hacked by shutting down, although I do have a firewall installed. <br><br>3) I thought it was a waste of electricity, and money, to have a machine running that wasn't being used.
<br><br>But I notice that most backup utilities are designed to backup automatically at the same time every day or week. That seems to assume that the system is always running. <br><br>I'd appreciate your advice.<br>
<br>Robin Carter<br>
------=_Part_56799_19592566.1188314915751--
Date: Tue, 28 Aug 2007 18:51:18 +0300
From: Giorgos Pallas <gpall@ccf.auth.gr>
To: debian-user@lists.debian.org
Subject: Re: gpg in KDE, passphrase window, passphrase timeout (SOLVED)
Message-ID: <46D44476.6090703@ccf.auth.gr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Gilles Mocellin wrote:
> Le Monday 27 August 2007 20:06:54 Giorgos Pallas, vous avez =C3=A9crit =
:
> =20
>> I'm a little confused: I use gpg from the console and when asking for =
my
>> passphrase
>> , it raises a KDE window and prompts me to type it there. Why? I also
>> would like gpg to cache the passphrase for a certain period of time so=
>> that I don't have to type it again and again. Any ideas?
>>
>> G.
>> =20
>
> You certainly have gpg-agent installed and running.
> The configuration .gnupg/gpg-agent.conf tells which program to launch t=
o ask
> password.
> I have "pinentry-program /usr/bin/pinentry-qt" for a kde window.
> =20
Thanks for the answers guys, that was the answer to the question.
I set the the
default-cache-ttl xxx
max-cache-ttl xxx
options and all is fine now.
G.
End of debian-user-digest Digest V2007 Issue #2264
**************************************************
Received on Tue Aug 28 12:22:14 2007