Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 1888
Today's Topics:
Re: rock solid [ "Cybe R. Wizard" ]
Re: grub assist needed [ Steve Kemp ]
kile [ Art Edwards ]
OT: knoppix memtest powers off after [ Kent West ]
Re: Continuing saga of xorg restarts [ Andrew Sackville-West ]
Re: restarting pump (DHCP) automatic [ bob@proulx.com (Bob Proulx) ]
Re: restarting pump (DHCP) automatic [ bob@proulx.com (Bob Proulx) ]
Re: OT: knoppix memtest powers off a [ bob@proulx.com (Bob Proulx) ]
Re: [SOLVED] Re: Importing mencoder [ bob@proulx.com (Bob Proulx) ]
Date: Tue, 3 Jul 2007 13:25:07 -0500
From: "Cybe R. Wizard" <cyber_wizard@mindspring.com>
To: debian-user@lists.debian.org
Subject: Re: rock solid
Message-ID: <20070703132507.2d7445ca@WizardsTower>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Andrew Sackville-West <andrew@farwestbilliards.com> said:
> Its memory-bound and I don't any spare...
^
have
Cybe R. Wizard
--
When Windows are opened the bugs come in.
Winduhs
Date: Tue, 3 Jul 2007 20:58:30 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: backports
Message-ID: <20070703185830.GB7632@localhost>
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jul 03, 2007 at 09:55:20 +0100, Chris Lale wrote:
[...]
> It seems that this is an outstanding debian-keyring bug dating from 16 Fe=
b 2005:
> #295527 "horribly outdated"[1].
>=20
> A bug reply mentions a local updated, unofficial version by Roland Stigge:
> debian-keyring_2006.10.11_all.deb[2] dated 11-Oct-2006. I downloaded and
> extracted it using your previous method:
>=20
> $ mkdir tempdir
> $ dpkg-deb -X debian-backports-keyring_2007.06.10_all.deb tempdir/
> $ mv tempdir/usr/share/keyrings/debian-backports-keyring.gpg .
> $ rm -rf tempdir/
>=20
> Then I checked for 4B2B2B9E and got a match!
>=20
> $ gpg --no-default-keyring --keyring ~/downloads/debs/debian-keyring.gpg
> --check-sig 4B2B2B9E
> gpg: checking the trustdb
> gpg: public key 3C093EEF is 29789 seconds newer than the signature
I don't see this when I do the same. 8 hours difference; a timezone
configuration problem, maybe?
> gpg: public key of ultimately trusted key ECB41FF5 not found
The "ultimately trusted" key should be your own. Did you experiment with
gpg in the past and generate a key (pair) which you deleted again?
> gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
> gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
> pub 1024D/4B2B2B9E 2004-06-20
> uid Daniel Baumann
> [...]
> sig!3 307D56ED 2004-09-18 No=E8l K=F6the
> sig!3 9B7C328D 2005-03-30 Luk Claes
> sig!3 4B2B2B9E 2004-06-20 Daniel Baumann
> sig!3 4B2B2B9E 2004-06-20 Daniel Baumann
> [...]
> 1 bad signature
> 535 signatures not checked due to missing keys
>=20
> How well do you think I can trust this debian-keyring_2006.10.11_all.deb =
package?
It certainly increases trust if a key(ring) checks out from many
different sources. However, I think that the most important thing is
being able to verify signatures with the keys from the debian-keyring
package.
=20
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D295527
> [2] http://people.debian.org/~stigge/packages/
--=20
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Date: Tue, 03 Jul 2007 15:43:42 -0400
From: Frank McCormick <fmccormick@videotron.ca>
To: debian-user@lists.debian.org
Subject: Re: aptitude "initialising package status" takes _really_ long
Message-id: <20070703154342.d09e8fda.fmccormick@videotron.ca>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
On Tue, 03 Jul 2007 11:17:04 -0700
Alan Ianson <agianson@gmail.com> wrote:
> > > at the start of aptitude and after every action you have took,
> > > aptitude has to initialise its package status. This is the same
> > > step as "loading cache". Yesterday I have updated aptitude to .
> > > Since then this step takes _really_ long. Lets say 40s. I am on
> > > sid. There is no output it any loggs
>
> >
> > I have the same problem (also running sid). There is a bugreport by
> > me relating to this behaviour.
>
> I get the same thing on my amd64 box, on my laptop it takes about
> forever.. :) I saw on the bts that it is caused by some new feature
> of apt, tags or something.
> I suspect it will be fixed soon.
I thought I was all alone :) On my 2.6 ghz dual-core, Aptitude
keep-all took more than an hour. I gave up and killed it !!
--
Change the world one loan at a time - visit Kiva.org to find out how
Date: Tue, 03 Jul 2007 13:07:06 -0700
From: tony mollica <tjm3@threedogs.net>
To: debian-user@lists.debian.org
Subject: grub assist needed
Message-ID: <468AAC6A.3010609@threedogs.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hello. Looking for a grub assist to make my system boot the way I would
like, hopefully without making the system un-bootable as a result.
I have a nicely working system booting from a SATA drive with two kernels
onboard, one generic and one k7 kernels. The system config is one SATA
drive, one IDE dvd burner on the one and only onboard IDE channel and
an additional Silcon Image 680a IDE card (working properly but no drive
on either channel). The si680a is wired to a removeable tray that I would
like to be able to change drives. The system was originally loaded without
this drive in the bay and so grub knows nothing about it. If I shutdown and
reboot with the removeable drive (ide) in the bay it obviously changes the
drive designations as the si680a drive is recognized first, no boot sector
is found on this drive and errors and no boot occurs.
I would like to be able to boot the system automagically whether or not
the removeable drive is loaded it the bay but I'm at a loss for how to do
this safely. There is no BIOS setting to help decide which drive is first,
second or otherwise. I find no options for the si680a driver that would
delay or change the order of the drive recognition. I need a way to always
have it boot from the same drive no matter what other disks loaded on
the IDE channels.
Any suggestions?
thanks,
--
-----------------
tony
tjm3@threedogs.net
Date: Tue, 3 Jul 2007 21:35:14 +0100
From: Steve Kemp <skx@debian.org>
To: tony mollica <tjm3@threedogs.net>
Cc: debian-user@lists.debian.org
Subject: Re: grub assist needed
Message-ID: <20070703203514.GB27066@steve.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue Jul 03, 2007 at 13:07:06 -0700, tony mollica wrote:
> Hello. Looking for a grub assist to make my system boot the way I would
> like, hopefully without making the system un-bootable as a result.
:)
> There is no BIOS setting to help decide which drive is first,
> second or otherwise. I find no options for the si680a driver that would
> delay or change the order of the drive recognition. I need a way to always
> have it boot from the same drive no matter what other disks loaded on
> the IDE channels.
Have you considered using filesystem labels? Something like
root=LABEL=root
> Any suggestions?
There is a brief introduction here:
http://www.debian-administration.org/articles/522
Steve
--
# Commercial Debian GNU/Linux Support
http://www.linux-administration.org/
Date: Tue, 03 Jul 2007 15:06:36 -0600
From: Art Edwards <edwardsa@afrl.kirtland.af.mil>
To: debian-user@lists.debian.org, debian-devel@lists.debian.org
Subject: kile
Message-ID: <200707032102.l63L2ZKC002357@bell.kirtland.af.mil>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In testing, kile has been removed. It appears that texlive is undergoing
a reorganization. As a result, kile's dependencies are at odds with the
new organization. When will kile be returned to the distribution?
--
Arthur H. Edwards
Senior Research Physicist
Air Force Research Laboratory
AFRL/VSSE
Bldg. 914
3550 Aberdeen Ave. SE
KAFB, NM 87117-5776
(505) 853-6042 (O)
(505) 463-6722 (C)
(505) 846-2290 (F)
Date: Tue, 3 Jul 2007 14:11:26 -0700
From: Steve Langasek <vorlon@debian.org>
To: debian-devel@lists.debian.org, debian-user@lists.debian.org
Subject: Re: kile
Message-ID: <20070703211126.GF5925@dario.dodds.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Jul 03, 2007 at 03:06:36PM -0600, Art Edwards wrote:
> In testing, kile has been removed.
That doesn't appear to be the case.
> It appears that texlive is undergoing a reorganization. As a result,
> kile's dependencies are at odds with the new organization.
I don't see this in any version of kile in etch/lenny/sid.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon(at)debian.org http://www.debian.org/
Date: Tue, 03 Jul 2007 16:56:27 -0500
From: Kent West <westk@acu.edu>
To: debian users <debian-user@lists.debian.org>
Subject: OT: knoppix memtest powers off after 35 mins
Message-id: <468AC60B.5040204@acu.edu>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
OT for Debian, but you folks are knowledgeable ...
Running memtest86 from a Knoppix LiveCD on an HP pavilion ze4400 laptop.
No errors, but the laptop powers off consistently after about 35 minutes
of testing.
The laptop does not power off when sitting at the Knoppix prompt (I
enter some random character or two to prevent time-out default boot),
nor does it power off after 35 minutes at the Windows (yech!) login
prompt or within Knoppix when it's running from the LiveCD.
I've not seen any odd behaviour when running Knoppix, and very limited
oddness when running Windows (yet a couple of small things - easily
attributable to Windows flakiness); the guy who owns the laptop says it
has frozen on him a few times and wouldn't power up once until left
alone a couple of hours.
After spending a couple of days with the laptop, my gut instinct is that
the hardware is fine, but this consistent auto-poweroff 35 minutes into
a memtest86 run (with default parameters) raises a yellow flag in my brain.
Anyone have any knowledge if maybe memtest86 might be triggering a
shut-down code, or if it's running into a bad memory cell?
Thanks!
--
Kent
Date: Tue, 3 Jul 2007 15:26:29 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: Re: Continuing saga of xorg restarts
Message-ID: <20070703222629.GG12665@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="+Pu8h6CsJtbukPM9"
Content-Disposition: inline
--+Pu8h6CsJtbukPM9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jul 03, 2007 at 12:39:05PM -0400, Carl Fink wrote:
> On Tue, Jul 03, 2007 at 08:29:40AM -0700, Andrew Sackville-West wrote:
> [much snipping]
>=20
> > I've seen some xorg crashes lately too... mostly caused by mplayer,
> > but not reliably. I'll grab my backtrace too.=20
>=20
> > contact the xorg team (Debian X strike force?) and see what they
> > say...
>=20
> I'll wait until you have a backtrace and we can give them more information
> in a single package. Meanwhile I'll try booting Knoppix tonight and see =
if
> I get X crashes there. (I want to eliminate the possibility of hardware
> failures.)
here's mine:
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591]
1: /lib/i686/cmov/libc.so.6 [0xb7ddce08]
2: /usr/bin/X11/X [0x80ddae5]
3: /usr/bin/X11/X(miHandleValidateExposures+0x78) [0x813b828]
4: /usr/bin/X11/X(miMoveWindow+0x290) [0x813c1a0]
5: /usr/bin/X11/X(ConfigureWindow+0x6b7) [0x807c517]
6: /usr/bin/X11/X(ProcConfigureWindow+0xa1) [0x808e4c1]
7: /usr/bin/X11/X(PanoramiXConfigureWindow+0x1a6) [0x8150c86]
8: /usr/bin/X11/X [0x8154a21]
9: /usr/bin/X11/X(Dispatch+0x19f) [0x808ed3f]
10: /usr/bin/X11/X(main+0x495) [0x8076e85]
11: /lib/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7dc8ebc]
12: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e5) [0x80761a1]
Fatal server error:
Caught signal 11. Server aborting
but that is induced by a very specific situation: dragging an active
mplayer window from my left-hand screen to my right hand-screen (which
gives me a blank mplayer frame) and then dragging it back. crashes
every time.=20
I tried to induce the crash by iterating through a bunch of avi's with
mplayer, but it wouldn't go in the time allotted. i'll try again
later.=20
hth
A
--+Pu8h6CsJtbukPM9
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)
iD8DBQFGis0UaIeIEqwil4YRAidVAKDaWPySXm5dgMJRLDAc3FWzrkzRYgCbBtqf
OtHF53BWbsu3DBRbsSCRi1U=
=oNX0
-----END PGP SIGNATURE-----
--+Pu8h6CsJtbukPM9--
Date: Tue, 03 Jul 2007 15:54:20 -0700
From: Bob McGowan <bob_mcgowan@symantec.com>
To: debian-user@lists.debian.org
Subject: Re: Importing mencoder into a bash script
Message-ID: <468AD39C.4020509@symantec.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010406000007030601010103"
This is a cryptographically signed message in MIME format.
--------------ms010406000007030601010103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
andy wrote:
> Bob McGowan wrote:
>> andy wrote:
>>> Andrew Sackville-West wrote:
>>>> On Mon, Jul 02, 2007 at 09:10:45PM +0100, andy wrote:
>>>>
>>>>> Hey folks
>>>>>
>>>>> I'm lazy and want to call the mencoder routine from mplayer into a
<----snipped>
> Thanks Bob for thinking through the problem I presented, as well as for
> the clarification on terminology. I am not a computer whiz but like to
> dabble here and there whenever I have that legendary "itch" to scratch.
> Nonetheless, I also obviously make some very silly (and embarrassing)
> errors.
> Thanks for your patience :)
>
> Cheers
> A
>
Thank you for *your* patience, as well. Sometimes, even the "best"
wording can come across in the wrong way. ;)
We all had to start as novices, at some point in our lives. Helping
others to become more knowledgeable is part of the game, as it were.
Cheers, and happy hacking.
--
Bob McGowan
--------------ms010406000007030601010103
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJHzCC
AuowggJToAMCAQICEGJ01+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkwNzIzMjIwM1oX
DTA3MDkwNzIzMjIwM1owSjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEnMCUG
CSqGSIb3DQEJARYYYm9iX21jZ293YW5Ac3ltYW50ZWMuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAreE3QGsl+S8sSMa+47mwvSsRUXRo7nAxCuPyO82co6aKIj3HfHpt
ad6Ct6JWTjWb6RHzkf5H5UvrlBxi1QhlLe5hALcdFNekO5vbtWSNAsQAUfEiPe4b1e7iOCNY
zefbNaEgM4yQX6zSZEhPAdSq4bU4cXbyxmw3lVA48AdhA/M18fCQ4Q/DfRNit72Iy2f3isSE
d8k2YI/Iq1vks9be2+3/5hR2adqfGUKwBP8/JIFsaB0dngifOTlwOOLQyVV4zCiCVlhIK/NI
ZIa6ldIU7Bs9QxauOoF9gIuOP/RaEPMrfrUMPMpJkSyqijAj0zsKBBEeftmIgkE9x1T7UrMN
0QIDAQABozUwMzAjBgNVHREEHDAagRhib2JfbWNnb3dhbkBzeW1hbnRlYy5jb20wDAYDVR0T
AQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQBkb7U/3ygdvn5n2H+1RFgerZkdQf4s5UwGwT4c
bFCynmuyekDmTcwPneekzPuYtVcrJXQRz2FGNyW7bZlZS7IG2Q5sxlc4lRX5O/H5XgzUOW3a
dAInokaS9OUioMv/HJ48cBt0ldLYQmrYPL+gVah6yWbJWxCZhOMgU8b9tU385zCCAuowggJT
oAMCAQICEGJ01+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkwNzIzMjIwM1oXDTA3MDkw
NzIzMjIwM1owSjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEnMCUGCSqGSIb3
DQEJARYYYm9iX21jZ293YW5Ac3ltYW50ZWMuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAreE3QGsl+S8sSMa+47mwvSsRUXRo7nAxCuPyO82co6aKIj3HfHptad6Ct6JW
TjWb6RHzkf5H5UvrlBxi1QhlLe5hALcdFNekO5vbtWSNAsQAUfEiPe4b1e7iOCNYzefbNaEg
M4yQX6zSZEhPAdSq4bU4cXbyxmw3lVA48AdhA/M18fCQ4Q/DfRNit72Iy2f3isSEd8k2YI/I
q1vks9be2+3/5hR2adqfGUKwBP8/JIFsaB0dngifOTlwOOLQyVV4zCiCVlhIK/NIZIa6ldIU
7Bs9QxauOoF9gIuOP/RaEPMrfrUMPMpJkSyqijAj0zsKBBEeftmIgkE9x1T7UrMN0QIDAQAB
ozUwMzAjBgNVHREEHDAagRhib2JfbWNnb3dhbkBzeW1hbnRlYy5jb20wDAYDVR0TAQH/BAIw
ADANBgkqhkiG9w0BAQUFAAOBgQBkb7U/3ygdvn5n2H+1RFgerZkdQf4s5UwGwT4cbFCynmuy
ekDmTcwPneekzPuYtVcrJXQRz2FGNyW7bZlZS7IG2Q5sxlc4lRX5O/H5XgzUOW3adAInokaS
9OUioMv/HJ48cBt0ldLYQmrYPL+gVah6yWbJWxCZhOMgU8b9tU385zCCAz8wggKooAMCAQIC
AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENh
cGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAm
BgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1h
aWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV
BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQD
EyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B
1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79A
gAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8E
CDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEa
MBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7M
DaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk1
3iSx0x1G/11fZU8xggNkMIIDYAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3
dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQQIQYnTX54sAOPQklBDqZhgPtjAJBgUrDgMCGgUAoIIBwzAYBgkq
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzA3MDMyMjU0MjBaMCMG
CSqGSIb3DQEJBDEWBBRQZ5q5lQPB4HCIislClWngNrtXHzBSBgkqhkiG9w0BCQ8xRTBDMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc
VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs
IEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ01+eLADj0JJQQ6mYYD7YwgYcGCyqGSIb3DQEJEAIL
MXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ0
1+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEBBQAEggEAUB+GsXSZDP5/ibWlCPeEVkUaG3WE
KcDo3v/gUBLqElUhg5CuRTRBUl6Cn9alXLkffZUXc7MKlMwdzK0d7shLFIadh7uSRfwhyBvi
2LKjHhAK9V6dCr4knCATDfD8/FZMf4rgu5lcejRkxbg64dttHl7d0xTnsFUCHW5x8qguB8MO
unwwkN0qIwCregU4k0uw6y2y/7teXsxFfUpYX4N6xptHRE/zUYwFJYC4oLHn0C5NI1QgzXed
nh6+yb+A/w2TmHqsOISZBs9HtkdHIfVXOlil32F666p26z3WIIbNt+gHf+JWYJXmp3RktYpV
MHMEqlb+3sKciVnw6Rc4LcKItwAAAAAAAA==
--------------ms010406000007030601010103--
Date: Tue, 03 Jul 2007 18:59:21 -0400
From: Kamaraju S Kusumanchi <kamaraju@bluebottle.com>
To: debian-user@lists.debian.org
Subject: Re: OT: knoppix memtest powers off after 35 mins
Message-ID: <f6ekdc$4cj$1@sea.gmane.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Kent West wrote:
> OT for Debian, but you folks are knowledgeable ...
>
>
> Running memtest86 from a Knoppix LiveCD on an HP pavilion ze4400 laptop.
> No errors, but the laptop powers off consistently after about 35 minutes
> of testing.
>
I am no expert in this area. To understand the problem better, could you
tell me, if you are using anything like acpi and/or X? I would try the
following.
1) Disable acpi etc., I think you can do this by entering acpi=off at the
boot prompt.
2) Disable X and run memtest from command line.
Also what version of knoppix CD are you using?
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
Date: Tue, 03 Jul 2007 18:22:46 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: Purpose of a hypervisor (was Re: rock solid)
Message-ID: <468ADA46.40303@cox.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 07/03/07 13:25, Andrew Sackville-West wrote:
> On Mon, Jul 02, 2007 at 09:46:06PM -0500, Ron Johnson wrote:
>> On 07/02/07 15:06, Andrew Sackville-West wrote:
>>> On Mon, Jul 02, 2007 at 02:11:18PM -0400, Kamaraju S Kusumanchi wrote:
>>>> Andrew Sackville-West wrote:
>>>>
>>>>> its almost boring...
>>>>>
>>>> May be true for stable; Neverthless Sid makes it all interesting!
>>> my home server here runs etch with xen and 3 vm's (at the moment). I
>> Why? Can't Linux's scheduler handle the load?
>
> 'cuz I can ;)
>
> seriously though, here's what I've got:
>
> Dom0: local file server (video, music, local backups)
>
> DomU1: firewall
I understand the need for a small, "separate" firewall.
> DomU2: dmz mail/imaps server
> DomU3: dmz apache server
>
> the primary reason is as a testbed for me to learn stuff. It has the
> nice feature of segmenting functionality without more machines
> running.
But then you are trying to statically do (allocate CPU and RAM) what
the kernel can do so much better.
> And the chicks dig it!
>
> I'm happy to learn the pros and cons of such a setup, but its hard to
> beat the last one...
--
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
Date: Tue, 3 Jul 2007 17:33:46 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: restarting pump (DHCP) automatically when network unavailable at boot time
Message-ID: <20070703233346.GA21415@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Vincent Lefevre wrote:
> But then, I don't see why I should use 'allow-hotplug eth0' instead of
> 'auto eth0'.
It is not required to use allow-hotplug but that is the new way of
doing things. The new debian-installer will set things up with
allow-hotplug. Then machines such as laptops with a pcmcia slot or
usb device can have network devices go online and offline in a nice
hotplug fashion. Same for any other hotpluggable device.
But this is not required. You could use 'auto' and then things will
happen at boot time (only) the same as it used to do before. For a
machine without any hotplugable devices then it shouldn't matter which
way things are configured and both should "just work". Both
configurations "just work" for me.
Note that '/etc/init.d/networking restart' only affects 'auto' devices
and not 'allow-hotplug' devices. This makes sense since this is the
old way of starting things up at boot time but it can catch people off
guard when they have not been exposed to this before. I am sure there
is a way to trigger the udev scripts to run the hotplug device scripts
too but I don't know how at this moment.
> But on the other machine (on which I have the problem I mentioned at
> the beginning of this thread), when I type "pump -i eth1" (again, the
> device exists but is down and not connected), I also get the error
> message "Operation failed." as expected, but "pump -i eth1" is no
> longer running. I think this can explain my problem if it can be
> confirmed on eth0 too (I'll have to try that).
I am not sure why operation failed is expected. I expect that to
succeed.
Bob
Date: Tue, 3 Jul 2007 17:44:03 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: restarting pump (DHCP) automatically when network unavailable at boot time
Message-ID: <20070703234403.GB21415@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Vincent Lefevre wrote:
> The problem with dhclient is that it disconfigures the loopback
> interface under some conditions. A bug is still open after 7 years!
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65718
That bug may still be open but I have never seen it in any
configuration. I think that bug may no longer be there but no one has
verified it to root cause and so it has not been closed. There is no
discussion after the first report. Is anyone else seeing that bug? I
would guess not.
> Also I need to control whether a DHCP client is running or not,
Hmm... Usually saying 'iface eth0 inet dhcp' is enough. When
ifupdown runs it will automatically start the installed dhcp client.
For me when I did not want that I simply did not configure that device
as an 'auto' device and then I could control it completely.
The Etch default is to use network-manager to bring network devices
online. See /usr/share/doc/network-manager/README.Debian for full
details.
> because on another machine (a laptop) I use netenv and DHCP is not
> used on some networks (BTW, I've already have a "killall pump" in
> my netenv scripts on this laptop, and I could probably do the same
> thing with dhclient).
I have not used netenv and I don't know about it but I think that
maybe you simply need to remove all of the 'auto' and 'allow-hotplug'
lines from the file. Then it won't be started automatically. Then
you won't have to kill the dhcp clients. Then you can use netenv to
start up the device the same as you have been doing. I would guess
anyway. That seems cleaner.
Bob
Date: Tue, 3 Jul 2007 17:49:51 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: OT: knoppix memtest powers off after 35 mins
Message-ID: <20070703234951.GC21415@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Kent West wrote:
> Running memtest86 from a Knoppix LiveCD on an HP pavilion ze4400 laptop.
> No errors, but the laptop powers off consistently after about 35 minutes
> of testing.
If that is consistently 35 minutes then it makes me wonder how the
BIOS power saving settings are configured. I would guess that the
BIOS is not seeing any input and therefore turning the machine off
because it thinks it is idle. I believe that after the OS is booted
it takes over these things. But memtest may not be programmed to do
this for that machine while the linux kernel in knoppix does.
Just a guess...
Bob
Date: Tue, 3 Jul 2007 17:54:54 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: [SOLVED] Re: Importing mencoder into a bash script
Message-ID: <20070703235454.GD21415@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
andy wrote:
> I owe you each an apology for wasting your time. After I had reinstalled
> my system I was convinced that I had installed it as part of the mplayer
> package. However, running Bob's scriptlet demonstrated that I hadn't
> done so, and so I have now fixed that problem which now fixes the
> original problem.
>
> My bad - and sorry about that!!
>
> Thanks for your helpful suggestions.
As Shakespeare said, all's well that ends well. And also remember
that old debugging technique, make sure that it is plugged in. :-)
Glad it is now working for you.
Bob
End of debian-user-digest Digest V2007 Issue #1888
**************************************************
Received on Tue Jul 3 20:31:25 2007