Date: Tue, 28 Aug 2007 09:53:09 -0700
From: Bob McGowan <bob_mcgowan@symantec.com>
To: debian-user@lists.debian.org
Subject: Re: All New rc2.d Scripts get Ignored. Debian from KNOPPIX
Message-ID: <46D452F5.4010300@symantec.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080002000505060201030209"
This is a cryptographically signed message in MIME format.
--------------ms080002000505060201030209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Martin McCormick wrote:
> 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
>
>
Martin,
During startup, /etc/inittab uses the /etc/init.d/rc script to run the
various scripts in the rc?.d directories. It has a commented out line
for debugging. If you uncomment it, from what I can see, it will tell
you what it's doing. It looks like this will propagate to the scripts
that it runs, so you may expect to see a lot of stuff printed during boot.
But you should be able to tell what it's doing just before your scripts
are supposed to run.
You could also add a 'set -x' near the beginning of the 'rc' script and
a 'set +x' at the end, to just see what it's doing. The 'set' command
only affects the running shell, not subshells.
You've already covered all the other possible problems I could think of,
good luck in debugging.
--
Bob McGowan
Symantec, Inc.
--------------ms080002000505060201030209
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
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzA4MjgxNjUzMDlaMCMG
CSqGSIb3DQEJBDEWBBRJhXHa1b+cSSTpeuRzPB/bvx8DLzBSBgkqhkiG9w0BCQ8xRTBDMAoG
CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq
hkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc
VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs
IEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ01+eLADj0JJQQ6mYYD7YwgYcGCyqGSIb3DQEJEAIL
MXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg
THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ0
1+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEBBQAEggEAV+lRsrX2Lpc1+V4Fo4MyepZ5WqyD
mQkGi6m6eKDcpl/uE8v6qy60q/YjKJEThe1LyCCPfAg6qkWHFO3Nc0et5l+4LqhJYiyG4caC
cTdI4eBXuMSJnVEDb9vGo5Cjidm0RoSBJFxAZH/3hWlRiE1Ag221dvpkdGEfJYVRzhN1HVtJ
E4dxunJHVinjetkQupQNdUfLXynduCF52yqoHYZ259nHRBrvvLBvUmHK2NZKi7QIzoyVGhDL
kNwCupGWpsa8mTjL38vDAJLlAI1M5i4TOb5iGl4L24ivYsZiEy1YFl3mD8hVZmzrMUnIywwp
BQ3hXf1O1iUJK1esuPv61NDmoAAAAAAAAA==
--------------ms080002000505060201030209--
Date: Tue, 28 Aug 2007 09:45:51 -0700
From: Jeff <debian@waysoft.com>
To: debian-user@lists.debian.org
Subject: Re: Shut down or leave on?
Message-ID: <46D4513F.1090904@waysoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Raquel wrote:
> On Tue, 28 Aug 2007 11:28:35 -0400
> "Richard Carter" <carter.r.a.l@gmail.com> wrote:
>
>> 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
>>
>
> I've always gone for leaving my machines on. I feel there is less
> wear and tear on components by leaving the machine on.
>
Specifically, as I understand it, thermal shock to minuscule electronic
components during power-on. In the past, I've lost a number of
motherboards and processors due (presumably) to this effect. Since
keeping my machines on 24/7 (for several years now), I have not had any
such problems.
Jeff
Date: Tue, 28 Aug 2007 17:46:51 +0100
From: Richard Lyons <richard@the-place.net>
To: debian-user@lists.debian.org
Subject: SOLVED: Re: smtp to bytemark.co.uk smarthost (was: using a remote IMAP server and smarthost)
Message-ID: <20070828164407.GA11717@the-place.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Aug 28, 2007 at 10:03:36AM -0500, Owen Heisler wrote:
> 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/.msmtprc)
> > [...]
> > > 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.
> >
> > 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.
>
> 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 DSN.
> 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 well.
> After disabling them there, Gmail accepted mail.
Wow! You are so right! I have commented them out there and -- hey
presto, this reply is from mutt over the tunnel!
Assuming it gets there...
Thanks to everybody.
--
richard
Date: Tue, 28 Aug 2007 13:02:59 -0400
From: icelinux@icelinux.net
To: debian-user@lists.debian.org
Subject: question about kernel source packages
Message-ID: <20070828130259.7a4h34qcis40cwss@icelinux.net>
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
one need to patch it with all of the included debian patches when
building a custom kernel?
"Everything should be made as simple as possible, but not simpler."
Albert Einstein
Date: Tue, 28 Aug 2007 13:19:25 -0400 (EDT)
From: Brett Charbeneau <brett@wrl.org>
To: debian-user@lists.debian.org
Subject: Running swatch dependably
Message-ID: <Pine.LNX.4.64.0708281310570.24665@franklin.wrl.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Is anyone out there running swatch (the log watcher) as a daemon in
Sarge/Edgy? If so - how the heck are you doing it?
I've been through the docs and Google, but I'm not getting a
workable answer - swatch behaves only if I start it manually and not for long.
I've been issuing
swatch --config-file=/home/swatch/.swatchrc --tail-file=/var/log/messages \
--awk-field-syntax --pid-file=/var/run/swatch.pid --daemon
at boot via a customized "local" file in /etc/init.d but this doesn't
seem to work - or the process zombifies somehow. (It's listed with ps aux,
but it doesn't work.) If started this way at boot, when I force the text string
swatch is looking for into syslog via the logger command nothing happens.
If I start the daemon manually swatch does it's thing as expected
but it seems to zombie out (although top doesn't indicate a zombie) or simply
stop working in a few hours.
Is there a startup script skeleton/template that I'm not finding? The
closest proper startup script I can find is related to Debian is
http://blogs.yahoo.co.jp/scebai3141/13167052.html
but I can't get this to work either.
I'd be grateful for any pointers!
--
********************************************************************
Brett Charbeneau, GSEC Gold, GCIH Gold
Network Administrator
Williamsburg Regional Library
7770 Croaker Road
Williamsburg, VA 23188-7064
(757)259-4044 www.wrl.org
(757)259-4079 (fax) brett@wrl.org
********************************************************************
Date: Tue, 28 Aug 2007 10:50:17 -0700
From: Raquel <raquel@thericehouse.net>
To: debian-user@lists.debian.org
Subject: Re: Shut down or leave on?
Message-Id: <20070828105017.5cec8e74.raquel@thericehouse.net>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 28 Aug 2007 09:45:51 -0700
Jeff <debian@waysoft.com> wrote:
> Raquel wrote:
> > On Tue, 28 Aug 2007 11:28:35 -0400
> > "Richard Carter" <carter.r.a.l@gmail.com> wrote:
> >
> >> 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?
> >>
<snip>
> >>
> >> I'd appreciate your advice.
> >>
> >> Robin Carter
> >>
> >
> > I've always gone for leaving my machines on. I feel there is
> > less wear and tear on components by leaving the machine on.
> >
> Specifically, as I understand it, thermal shock to minuscule
> electronic components during power-on. In the past, I've lost a
> number of motherboards and processors due (presumably) to this
> effect. Since keeping my machines on 24/7 (for several years
> now), I have not had any such problems.
>
> Jeff
>
I also understand that when the hard disks get power that the
platters torque just a tad, if not causing heads to come into
contact with the platter, at least causing wear on bearings.
--
Raquel
============================================================
Our particular principles of religion are a subject of
accountability to our god alone. I enquire after no man's and
trouble none with mine; nor is it given to us in this life to know
whether yours or mine, our friend's or our foe's, are exactly the
right.
--Thomas Jefferson
Date: Tue, 28 Aug 2007 13:05:50 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: icelinux@icelinux.net
Cc: Debian User List <debian-user@lists.debian.org>
Subject: Re: question about kernel source packages
Message-ID: <46D463FE.8010400@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 08/28/2007 12:02 PM, icelinux@icelinux.net wrote:
> I notice there is a source package for the kernel and a package of
> debian patches. Has the kernel source already been patched or would one
> need to patch it with all of the included debian patches when building a
> custom kernel?
>
It's already patched.
Date: Tue, 28 Aug 2007 11:32:44 -0700
From: David Brodbeck <brodbd@u.washington.edu>
To: List Debian User <debian-user@lists.debian.org>
Subject: Re: Shut down or leave on?
Message-Id: <B4B9949B-A1BB-451E-8464-FACDD7945690@u.washington.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
On Aug 28, 2007, at 10:50 AM, Raquel wrote:
> I also understand that when the hard disks get power that the
> platters torque just a tad, if not causing heads to come into
> contact with the platter, at least causing wear on bearings.
In theory start-ups put more stress on the spindle motor, yes. I
can't remember the last time I saw a hard disk that had a spindle
motor failure, though. Also, modern hard disks move the heads to a
safe "landing zone" before they spin down.
On machines I don't rely on to provide network services, I shut them
down when they're not in use. I also set hard disks to spin down
after a half hour or so of inactivity. I turn off the lights in
rooms I'm not in, too, although I'm sure this shortens the life of
the light bulbs. ;)
Date: Tue, 28 Aug 2007 14:39:05 -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: <8eb883950708281139g65308ae5l6cc22b98d01c783b@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/28/07, Richard Thompson <binary@freedom.prodigynetwork.co.uk> wrote:
>
> I don't get why your building you own intird?, if your using the kernel
> provided it already has it's own initrd and if your building the kernel
> yourself why are you using initrd at all?
Good question. I am building my own kernel (using kernel-package). The thing is,
I couldn't boot my computer in kernel 2.6 (but I could in 2.4.27). In
the former case,
it reported that the root filesystem had errors, but not in the latter
case. Then I
changed something in the kernel configuration to make the VIA south
bridge driver
a module, and then I had the error message in the title of this
thread. Then I added
an initrd image and it worked. But now I recall that I did an fsck
check and some
errors where indeed corrected during a session in 2.4.27. So I guess
the reason it
booted afterwards was maybe due to that rather than the initrd thing (which I
do not use on my laptop and I have no problems there). I guess that if
I build back the
driver into the kernel instead of a module, it should be ok without initrd.
But anyway, initrd or not, now my system is messed up, and I am still
stuck with DMA
problems and CRC errors that the 2.6 kernel seems to like much less than 2.4.27.
I wonder why only the root filesystem has been messed up?
--
Francois
Date: Tue, 28 Aug 2007 09:37:40 -0400
From: Celejar <celejar@gmail.com>
To: debian-user@lists.debian.org
Subject: [solved] Re: fstab and removable usb drives
Message-Id: <20070828093740.c0218d32.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Mon, 27 Aug 2007 14:51:04 -0700 (PDT)
Jeff D <fixedored@gmail.com> wrote:
> On Mon, 27 Aug 2007, Celejar wrote:
>
> > Hi,
> >
> > I'm experimenting with fstab lines to streamline mounting my removable
> > usb drives (flash and HDD). I have tried 'UUID-xxxx', 'LABEL-xxxx',
> > and '/dev/disk/by-label/xxxx', but with any of these the system refuses
> > to boot without manual intervention when the drive isn't attached (I am
> > told to hit <ctrl>-D and something about maintenance mode). This
> > occurs even when I set 'noauto'. Am I missing something, or are such
> > fstab lines really illegal for setups where the volume may not be
> > attached at boot?
> >
> > Celejar
> > --
>
> Hm, noauto should skip it at boot. On one of my laptops I have this:
> /dev/disk/by-id/xxxxxx /mnt/flash vfat user,noauto 0 0
>
> Boots up just fine..
Well, with a little careful digging I found the problem. The
error was fsck related; /etc/init.d/checkfs.sh runs 'fsck -C -R -A
-a'. The '-A' option tells fsck to check all filesystems in fstab that
don't have 0 in the last field. I had been setting mine to 2 as the
installer did for the system's fixed drives; you have it set to 0. I
suppose that I'll just have use 0 and perhaps remember to do a manual
fsck periodically.
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Tue, 28 Aug 2007 15:00:01 -0400
From: Celejar <celejar@gmail.com>
To: <electricalsciences@adelphia.net>
Cc: debian-user <debian-user@lists.debian.org>
Subject: Re: fstab and removable drives
Message-Id: <20070828150001.112a41ff.celejar@gmail.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Tue, 28 Aug 2007 7:18:25 -0700
<electricalsciences@adelphia.net> wrote:
> My ISP has "improved" my email to the point that I cannot
> post to newsgroups at all and even email is a struggle.
>
> The error message you describe is from fsck, which fails when
> trying to check the disconnected drive. The sixth (and last)
> field in your fstab entry must be zero. From man fstab:
>
> "The sixth field, (fs_passno), is used by the fsck(8) program to determine
> the order in which filesystem checks are done at reboot time.
> ...
> If the sixth field is not present or zero, a value of zero is returned and
> fsck will assume that the filesystem does not need to be checked."
>
> Hope this helps!
It does; thanks very much. I arrived at the same realization
independently, hence my other message.
> Roby
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Date: Tue, 28 Aug 2007 19:07:49 +0000 (UTC)
From: Amit Uttamchandani <amit.uttam@gmail.com>
To: debian-user@lists.debian.org
Subject: I just installed OpenNTP. Now what?
Message-ID: <loom.20070828T210551-797@post.gmane.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hey guys,
So just installed OpenNTP on a shiny new etch system. The daemon is started
during startup but now what? How do I know that my clock is being synchronized?
I checked the config and there are debian ntp servers listed.
So is that it? Or am I missing something here.
Thanks,
Amit
Date: Tue, 28 Aug 2007 20:09:03 +0100
From: Richard Lyons <richard@the-place.net>
To: debian-user@lists.debian.org
Subject: ssh-agent (was: using a remote IMAP server and smarthost)
Message-ID: <20070828190903.GB12155@the-place.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sun, Aug 26, 2007 at 12:27:32AM +0200, Florian Kulzer wrote:
[...]
> Method 2:
> ---------
>
> You can set up mutt's sendmail command to use a short script which
> invokes ssh to run sendmail on myvm directly. This requires that
> sendmail works on myvm, though. The advantage is that you don't have to
> do anything else before you send mail (unlike with method 1). It seems
> that you do not have sendmail fully operational on myvm at the moment,
> so maybe you will want to stick with method 1 right now. In any case,
> here is the necessary wrapper script for method 2:
>
> ---------- STARTS BELOW (this line is not part of the script) ----------
> #! /bin/sh
> # sendmail-via-ssh.sh
> # wrapper script for mutt to use sendmail via ssh
> #
> # activated by this option in ~/.muttrc:
> # set sendmail="/path/to/sendmail-via-ssh.sh"
>
> cat - | ssh myvm "/usr/sbin/sendmail -oem -oi $@"
> ---------- ENDS ABOVE (this line is not part of the script) ----------
[...]
Returning to this, after the essential problem was solved (the presence
of two dsn settings in my .muttrc), It is time to try method 2. I
assume this script is intended to address a real sendmail or exim4,
rather than the msmtp installed for the trial of method 1. As I read
the manual, the -oem -oi options are not relevant to msmtp.
But, again if I understand Florian's earlier post, Method 2 requires the
use of sssh-agent. And I cannot see fromt he man page how to use it or
configure it.
IF I simply let mutt run the script as above, I get
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory^M
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory^M
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory^M
Permission denied (publickey,keyboard-interactive).
So I think I really need the ssh-agent. Help anybody?
--
richard
Date: Tue, 28 Aug 2007 20:41:32 +0200
From: wimpunk <kwdpggwxwumz@spammotel.com>
To: debian-user@lists.debian.org
Subject: Re: how to add the bluetooth rfcomm0 device at boot up automatically
with debian.
Message-ID: <sr6eq4-ip9.ln1@tisnix.motzarella.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Michael Habashy wrote:
> i am trying to automate how my debian box acknowledges that there is a
> bluetooth device attached to my bluetooth dongle.
> Does anyone know how i can do that automatically at boot up?
> In order for me to create the rfcomm0 device, I have to execute:
> 1. hcitool scan ---to get the mac address.
> 2. rfcomm bind 0 00:0E:07:14:80:A9 ---to create the rfcomm0 device.
>
>
>
use the /etc/bluetooth/rfcomm.conf configuration file. I think you have
to enable rfcomm in /etc/default/bluetooth to.
Date: Tue, 28 Aug 2007 15:15:08 -0400
From: icelinux@icelinux.net
To: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
Cc: Debian User List <debian-user@lists.debian.org>
Subject: Re: question about kernel source packages
Message-ID: <20070828151508.51qmh8a1cc4gggsk@icelinux.net>
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Quoting "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>:
> On 08/28/2007 12:02 PM, icelinux@icelinux.net wrote:
>> I notice there is a source package for the kernel and a package of
>> debian patches. Has the kernel source already been patched or would
>> one need to patch it with all of the included debian patches when
>> building a custom kernel?
>>
>
> It's already patched.
Doublechecking, you are absolutely positive?
"Everything should be made as simple as possible, but not simpler."
Albert Einstein
End of debian-user-digest Digest V2007 Issue #2266
**************************************************
Received on Tue Aug 28 15:35:25 2007