debian-user-digest Digest V2007 #1886

From: <debian-user-digest-request(at)lists.debian.org>
Date: Tue Jul 03 2007 - 13:05:10 EDT

Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 1886

Today's Topics:

  Re: Problem with sendmail, error cod  [ Shams Fantar  ]
  Re: Problem with sendmail, error cod  [ Shams Fantar  ]
  Re: svn checkout via a web-browser?   [ "Tshepang Lekhonkhobe"  ]
  [SOLVED] Re: Importing mencoder into  [ andy  ]
  Re: Automounting USB drive on GNOME   [ bob@proulx.com (Bob Proulx) ]
  Re: Importing mencoder into a bash s  [ Bob McGowan  ]

  Re: Continuing saga of xorg restarts [ Carl Fink <carl@finknetwork.com> ]   unbale to do dhclient after MAC chan [ Jabka Atu <mashrom.head@gmail.com> ]

Date: Tue, 03 Jul 2007 17:34:57 +0200
From: Shams Fantar <sfantar@snurf.info>
To: debian-user@lists.debian.org
Subject: Re: Problem with sendmail, error code 67.

Message-ID: <468A6CA1.9030401@snurf.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Richard A Nelson wrote:
> On Mon, 2 Jul 2007, Shams Fantar wrote:
>
>>> I have used Google to have the answers at my problem, but I did not
>>> find anything.
>
> You need more practice, the 1st page of my only search turned up this:
> --------------------------------------------------------------------------
>
> Take a look at /usr/include/sysexits.h on your system. It lists all of
> the standard exit codes for programs. On a Linux 2.0.35 system I
> have:
>
> #define EX_NOUSER 67 /* addressee unknown */
>
> And further up:
>
> * EX_NOUSER -- The user specified did not exist. This might
> * be used for mail addresses or remote logins.
> ----------------------------------------------------------------------------
>
>

I did not know /usr/include/sysexits.h. ;-)

>
>>> If I make 'sendmail -s testing sfantar@localhost', the prompt
>>> doesn't come back and there is no message. But if I make 'mail -s
>>> testing sfantar@localhost', I have an error message : Can't send
>>> mail: sendmail process failed with error code 67
>
> sendmail and mail are different commands, with different syntax, it
> isn't surprising that you see different results.

Yes, I know, I tested just.

>
>>> My php.ini for mail() : sendmail_path = /usr/sbin/sendmail -t -i
>
> Looks good
>
>>> If I want to use mail(), I can't !
>
> Because you are passing bad data, have a misconfigured mta, or both.
>
>>> There is nothing in the logs.
>
> If there is truly nothing in /var/log/mail.log, it implies that sendmail
> saw the mail recipient as being local, and as such, refused to accept
> the mail for a non-existant local user.

Yes, you are right. But, what is the solution ? I have no idea...

Logs of errors : http://jumble.snurf.info/pb_sendmail

>
> --------------------------------------------------------------------------
>
> $ mail -stesting asdf@localhost
> .
> Cc: Null message body; hope that's ok
> /home/cowboy/dead.letter... Saved message in /home/cowboy/dead.letter
> Can't send mail: sendmail process failed with error code 67
> ---------------------------------------------------------------------
>

-- 
Shams Fantar (
http://snurf.info)

Date: Tue, 03 Jul 2007 17:36:20 +0200 From: Shams Fantar <sfantar@snurf.info> To: debian-user@lists.debian.org Cc: debian-user@lists.debian.org Subject: Re: Problem with sendmail, error code 67. Message-ID: <468A6CF4.9010502@snurf.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Nelson Castillo wrote:
> On 7/2/07, Richard A Nelson <cowboy@debian.org> wrote:
>> On Mon, 2 Jul 2007, Shams Fantar wrote:
>>
>> >> I have used Google to have the answers at my problem, but I did
>> not find
>> >> anything.
>>
>> You need more practice, the 1st page of my only search turned up this:
>> --------------------------------------------------------------------------
>>
>> Take a look at /usr/include/sysexits.h on your system. It lists all of
>> the standard exit codes for programs. On a Linux 2.0.35 system I
>> have:
>>
>> #define EX_NOUSER 67 /* addressee unknown */
>
> Gee. I thought Error 67 meant "Migrate to postfix".
>
> Couldn't help it,
> N.-
>
For the moment, I use sendmail. ;) -- Shams Fantar (http://snurf.info)

Date: Tue, 3 Jul 2007 17:50:08 +0200 From: "Tshepang Lekhonkhobe" <tshepang@gmail.com> To: "Thomas Jollans" <thomas@jollans.com> Cc: debian-user <debian-user@lists.debian.org> Subject: Re: svn checkout via a web-browser? Message-ID: <857993970707030850p20c8c8c7maa12dfed6f93e9f9@mail.gmail.com> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 7/3/07, Thomas Jollans <thomas@jollans.com> wrote:
> On Tuesday 03 July 2007, Tshepang Lekhonkhobe wrote:
> > On 7/3/07, Vincent Lefevre <vincent@vinc17.org> wrote:
> > > On 2007-07-03 13:40:47 +0200, Tshepang Lekhonkhobe wrote:
> > > > Me have been struggling to access a subversion repo (svn checkout
> > > > svn.gnome.org/svn/tracker/trunk) due to being behind a proxy server=
. I
> > > > wonder if there's a way to download such repos without having an sv=
n
> > > > client since I can access the web with a web-browser.
> > >
> > > Only if your web browser is a also svn client. But if it isn't, why
> > > don't you install a svn client?
> >
> > I failed: http://lists.debian.org/debian-user/2007/07/msg00075.html
> > And help didn't help:
> > http://lists.debian.org/debian-user/2007/07/msg00162.html
>
> [guessing]
> "GSSAPI authentication error" =97 are http-proxy-username and
> http-proxy-password correctly set ?
I suppose that this is the same password I use on GNOME proxy GUI (which allowed me to access the web) and if so, yes it's correctly set, only I didn't show it on the example. --=20 my place on the web: floss-and-misc.blogspot.com

Date: Tue, 3 Jul 2007 11:57:21 -0400 From: Douglas Allan Tutty <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: Kernel 2.4 on Etch Message-ID: <20070703155721.GC9440@titan> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 03, 2007 at 05:24:59PM +0200, Thomas Jollans wrote:
> On Tuesday 03 July 2007, Gudjon I. Gudjonsson wrote:
> > Is there any simple way of making kernel 2.4 and 2.6 coexist in Debian
> > Etch? I know a lot of complicated ways :) but I need version 2.4 to test
> > old kernel modules.
>
> I suggest that if you want to use old kernel-level software, you use an
> adequately old OS, e.g. sarge. (as Kumar indirectly pointed out,
> http://www.debian.org/releases/etch/i386/release-notes/ch-information.en.html#s-incompatible-2.4
> looks like this is actually as good as impossible)
>
So backup. What is it you are trying to do that you have Etch installed but need to test old kernel modules? Doug.

Date: Tue, 3 Jul 2007 17:46:25 +0200 From: Vincent Lefevre <vincent@vinc17.org> To: debian-user@lists.debian.org Subject: Re: svn checkout via a web-browser? Message-ID: <20070703154625.GJ18533@prunille.vinc17.org> Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-07-03 16:26:40 +0200, Tshepang Lekhonkhobe wrote:
> On 7/3/07, Vincent Lefevre <vincent@vinc17.org> wrote:
>> On 2007-07-03 13:40:47 +0200, Tshepang Lekhonkhobe wrote:
>> > Me have been struggling to access a subversion repo (svn checkout
>> > svn.gnome.org/svn/tracker/trunk) due to being behind a proxy server.=
I
>> > wonder if there's a way to download such repos without having an svn
>> > client since I can access the web with a web-browser.
>>
>> Only if your web browser is a also svn client. But if it isn't, why
>> don't you install a svn client?
>
> I failed: http://lists.debian.org/debian-user/2007/07/msg00075.html
> And help didn't help:=20
> http://lists.debian.org/debian-user/2007/07/msg00162.html
You'll probably have the same problem with a web browser having a svn client extension. With a proxy server that filters some method, you can't access all the web, and changing the client won't solve your problem. If you control the web server itself, perhaps you can try something like SSH over HTTP (if CONNECT is allowed). --=20 Vincent Lef=E8vre <vincent(at)vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Date: Tue, 3 Jul 2007 09:10:22 -0700 (PDT) From: Jeff D <fixedored@gmail.com> To: debian user <debian-user@lists.debian.org> Subject: Re: svn checkout via a web-browser? Message-ID: <Pine.LNX.4.62.0707030908590.13288@proto.technobounce.com> Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-154299452-1183479022=:13288" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-154299452-1183479022=:13288 Content-Type: TEXT/PLAIN; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 3 Jul 2007, Tshepang Lekhonkhobe wrote:
> On 7/3/07, Thomas Jollans <thomas@jollans.com> wrote:
>> On Tuesday 03 July 2007, Tshepang Lekhonkhobe wrote:
>> > On 7/3/07, Vincent Lefevre <vincent@vinc17.org> wrote:
>> > > On 2007-07-03 13:40:47 +0200, Tshepang Lekhonkhobe wrote:
>> > > > Me have been struggling to access a subversion repo (svn checkout
>> > > > svn.gnome.org/svn/tracker/trunk) due to being behind a proxy serve=
r.=20
>> I
>> > > > wonder if there's a way to download such repos without having an s=
vn
>> > > > client since I can access the web with a web-browser.
>> > >
>> > > Only if your web browser is a also svn client. But if it isn't, why
>> > > don't you install a svn client?
>> >
>> > I failed: http://lists.debian.org/debian-user/2007/07/msg00075.html
>> > And help didn't help:
>> > http://lists.debian.org/debian-user/2007/07/msg00162.html
>>=20
>> [guessing]
>> "GSSAPI authentication error" =97 are http-proxy-username and
>> http-proxy-password correctly set ?
>
> I suppose that this is the same password I use on GNOME proxy GUI
> (which allowed me to access the web) and if so, yes it's correctly
> set, only I didn't show it on the example.
>
did you also set it in ~/.subversion/servers? -+- 8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Tec= hno. --8323328-154299452-1183479022=:13288--

Date: Tue, 03 Jul 2007 17:13:43 +0100 From: andy <geek_show@dsl.pipex.com> To: debian-user@lists.debian.org Subject: [SOLVED] Re: Importing mencoder into a bash script Message-ID: <468A75B7.6090702@dsl.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Bob Proulx wrote:
> andy wrote:
>
>> No - it is definitely installed - I've used it on the cli plenty of
>> times. I am interested in finding out how I am to call it from within a
>> bash script, because simply putting mencoder <options> <file> in the
>> bash script isn't working.
>>
>
> Hmm... Okay. Then let's debug why. Try this scriptlet:
>
> #!/bin/sh
> ls -ld /usr/bin/mencoder
> type mencoder
> echo PATH=$PATH
> dpkg -l mencoder | grep mencoder
> dpkg -L mencoder | grep /bin/
> exit 0
>
> What does it say? On one of my Etch systems it says:
>
> -rwxr-xr-x 1 root root 4107292 2007-06-19 00:42 /usr/bin/mencoder
> mencoder is /usr/bin/mencoder
> PATH=/usr/local/bin:/usr/bin:/bin:/usr/games
> ii mencoder 1.0-pre7-0.0 MPlayer's Movie Encoder
> /usr/bin/mencoder
>
> My guess is that on your system it is installed someplace special and
> so is in your PATH when called from your shell but not on PATH when
> you are trying to run the script.
>
> Bob
>
>
>
Bob, Florian & others 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. A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"

Date: Tue, 3 Jul 2007 10:28:07 -0600 From: bob@proulx.com (Bob Proulx) To: debian-user@lists.debian.org Subject: Re: Automounting USB drive on GNOME stopped working... Message-ID: <20070703162807.GA3614@dementia.proulx.com> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cassiano Bertol Leal wrote:
> Also, would gnome-mount be a requirement for the kind of behaviour I am
> expecting? I didn't have the chance to check if I do have it installed,
> but it seems that it's not a dependency of gnome-volume-manager, so I
> might not have it.
I don't have gnome-mount installed on a gnome machine and gnome still seems to mount this fine. So I would say no it is not needed. Bob

Date: Tue, 03 Jul 2007 09:48:13 -0700 From: Bob McGowan <bob_mcgowan@symantec.com> To: debian-user@lists.debian.org Subject: Re: Importing mencoder into a bash script Message-ID: <468A7DCD.80102@symantec.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070002060008010403040606" This is a cryptographically signed message in MIME format. --------------ms070002060008010403040606 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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
>>> bash script I'm writing to automatically convert different video
>>> files into dvd format *.mpg files.
>>>
>>> Anybody know how to call in just the routine without any unnecessary
>>> mplayer stuff?
>>>
>>
>> ummm.... mencoder is a command-line program. just figure out your
>> options and use it like any other cli tool. it should "just work"
>>
>>
> Hi Andrew
>
> Yeah, it is a cli tool and I have traditionally used it as such at the
> vt and just entered it directly. However, in a shell script I have tried
> to do that but get the error message:
>
> mencoder: command not found
This is because the command is not found in the PATH as seen *in the script*. Since you have 'traditionally used it', I presume you mean when you type 'mencoder' at a shell prompt, it runs. I've played around with the PATH variable and interactive sub-shells to see how things work. The only thing I can see is if your script is setting the PATH to '/bin:/usr/bin', you'd lose mencoder if it were in /usr/local/bin, so either not explicitly setting the PATH in the script or being sure if you do that it includes the location of mencoder, is what you need to do (as you note, below).
>
> I'm wondering if I need to explicitly set my path in the script file in
> order to call this function.
By the way, a note on terminology: in computerese, 'function' has a special meaning, usually for a bit of code that is not standalone but needs to be "called" from some other bit of code (shell "functions" are not quite the same thing, causing some confusion). I expect you were thinking of 'function' in the sense of 'what it does'. But, what scripts do is run 'programs', the word I'd encourage you to use. Using the correct terminology helps reduce confusion and needless questions ;)
>
> A
>
-- Bob McGowan Symantec, Inc. --------------ms070002060008010403040606 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 hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzA3MDMxNjQ4MTNaMCMG CSqGSIb3DQEJBDEWBBS6cE/Q+m8MEbh2upCV+I5e9ISFUzBSBgkqhkiG9w0BCQ8xRTBDMAoG CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq hkiG9w0DAgIBKDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs IEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ01+eLADj0JJQQ6mYYD7YwgYcGCyqGSIb3DQEJEAIL MXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGJ0 1+eLADj0JJQQ6mYYD7YwDQYJKoZIhvcNAQEBBQAEggEALG34XkTp0Xk420BaX/6RgtePp7Zn 7GpuEw1gWdUuYsrAMfGKCu8ddOfzMDx2f+nmaZ9aIXtInRfNoHFTmC5etRv81F7JNsa3vm5K uZ8lpgTQgux8UuDakekhYc7u4XUz/FvRswYRed3OHom6FPyjQ4VRXQSsAlKlfzDQbLCKwH3+ iEglzsRj1JHuCoihH8ulLUc6knstYbZTAmfNhN5D452CEiuOdGjDxsfzex26Snn2TI30bP7Z JWHHOaxIiO0WjRyZr0MGynyYOumOUZalx9hYiiMkulRW3ndEa/XPAmMOvl88qMV52p8ilA3w pUiIU/hYTSjylrUJW8JwWryJSAAAAAAAAA== --------------ms070002060008010403040606--

Date: Tue, 3 Jul 2007 08:38:49 -0800 From: Ken Irving <fnkci@uaf.edu> To: debian-user@lists.debian.org Subject: Re: Media Wiki 1.7 - Set-up / Install Help Message-ID: <20070703163848.GA9379@localhost> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 03, 2007 at 08:33:38AM -0500, John W. Foster wrote:
> On Monday 02 July 2007 12:04, Ken Irving wrote:
> > On Mon, Jul 02, 2007 at 09:19:15AM +0100, Nick Adie wrote:
> > >
> > > The read me file is very confusing as it talks about a file that does not
> > > exist and a symbolic link that appears to have no relevence.
> > >
> > > Has anyone experience of the installation/set-up of MediaWiki, and if so
> > > could I have a few pointers please.
> >
> > ...
> > 1. Move /var/lib/mediawiki1.7/config/LocalSettings.php to
> > /var/lib/mediawiki1.7/LocalSettings.php for normal install,
> > root of your install for multisite, with rights 640
> >
> > There's presumably somem reason this isn't done automatically by the
> > installer, but here you're just relocating the setup script generated
> > by the installer. Somewhere else there's a suggestion to create a
> > symlink to this setup script into /etc/mediawiki1.7/; this just puts
> > the script into the more conventional /etc/ tree, which makes sense
> > -- not sure why this isn't done automatically, but maybe it has to do
> > with single- or multi-wiki sites...
> > ...
> -------------------------------------------------------
> I had the same problem as Nick when I recently installed Mediawiki as a single
> user system on a etch box. I did something similar to Ken's suggestion, only
> I used syslinks (which were there but not properly connected) instead of
> moving the files. I did also have a disconnected syslink after I got MW
> working to AdminSettings.php. I have been unable to figure out what/where I
> should link this to. Any ideas? I have seen this problem only rarely and an
> explanation in the Readme file would be very helpful (hint,hint, to
> developer)
> Thanks!
I see a "dead" symlink at /usr/share/mediawiki1.7/AdminSettings.php pointing back to /var/lib/mediawiki1.7/AdminSettings.php which doesn't exist. A number of other .php files in /var/lib/mediawiki1.7/ are symbolic links back to (existing) files in /usr/share/mediawiki1.7/. I did what was described in the installation script, and ended up with a working system. The LocalSettings.php file I moved was generated by the installation script, at the end of which are instructions to move it to /var/lib/mediawiki1.7/; my guess is that that generated script is what might be intended as the target of the dead AdminSettings.php link, but the instructions were to call it "LocalSettings.php". The /etc/mediawiki1.7/README file explains (the arcane reasons) why things are located in /var/lib/mediawiki1.7, and *suggests* setting this symbolic link: ln -s /var/lib/mediawiki1.7/LocalSettings.php /etc/mediawiki1.7/my-site.org.config Again, LocalSettings.php must be moved to that location from the config/ directory, or it won't exist. The my-site.org.config file in /etc/ is suggested for convenience, putting the main config file for the wiki in a sensible place. I have no idea why things seem so obtuse, kind of rare for debian packages, but it does work if you follow the directions. Ken -- Ken Irving, fnkci@uaf.edu

Date: Tue, 3 Jul 2007 12:39:05 -0400 From: Carl Fink <carl@finknetwork.com> To: debian-user@lists.debian.org Subject: Re: Continuing saga of xorg restarts Message-ID: <20070703163905.GA18275@nitpicking.com> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 03, 2007 at 08:29:40AM -0700, Andrew Sackville-West wrote: [much snipping]
> I've seen some xorg crashes lately too... mostly caused by mplayer,
> but not reliably. I'll grab my backtrace too.

> contact the xorg team (Debian X strike force?) and see what they
> say...
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.) -- Carl Fink nitpicking@nitpicking.com Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct!

Date: Tue, 03 Jul 2007 19:48:58 +0300 From: Jabka Atu <mashrom.head@gmail.com> To: debian-user@lists.debian.org Subject: unbale to do dhclient after MAC change (ifconfig eth1 hw ether XX:XX..) Message-ID: <468A7DFA.8080608@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello,.. im using debian SID (64 bit) on Acer 5102. using bcm4318 wifi card. kernel 2.6.21-2-amd64. since i noticed that my local AP started to collected data about my serf i guesed it is time to play with MAC masquerade. i have compiled the madwifi module . and loaded it. i installed bcm43xx-fwcutter with the firmware Code: apt-get install bcm43xx-fuxtter Code: m-a -> choose -> madwifi get / build / install then i read some man s Code: man ifconfig then: Code: ifconfig eth1 hw ether 0a:b0:03:23:45:22 to set a fake MAC addres. then dhclient eth1 but .. Code: Internet Systems Consortium DHCP Client V3.0.5 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth1/0a:b0:03:23:45:22 Sending on LPF/eth1/0a:b0:03:23:45:22 Sending on Socket/fallback DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 No DHCPOFFERS received. so i thought that mac was bad so i reload it (modprobe -r bcm43xx modprobe bcm43xx) and set to using the same MAC as the real mac. and again the same (No DHCPOFFERS receive.). P.s. i was able to do iwlist eth1 scan (returend results); i am able to connect to the same AP without changing the MAC. what am i doing wrong ? -- -- Could you at least use man ? Jabka Atu (aka mha13/Mashrom Head) -- End of debian-user-digest Digest V2007 Issue #1886 ************************************************** Received on Tue Jul 3 13:04:47 2007