Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2851
Today's Topics:
Asynchronous network start [Was: 1 i [ Raj Kiran Grandhi ]
Re: [OT] firefox 3 [ Kent West ]
Re: command line wordperfect [ Ron Johnson ]
Re: listening to radio stations [ Ed Jabbour ]
Re: Is it exist a mailing-list for c [ "Douglas A. Tutty" ]
Date: Sat, 24 Nov 2007 06:04:57 +0530
From: Raj Kiran Grandhi <grajkiran@gmail.com>
To: debian-user <debian-user@lists.debian.org>
Subject: Asynchronous network start [Was: 1 in 2 chance : need to issue "/etc/init.d/networking
restart" after boot]
Message-ID: <474771B1.90801@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Marc Auslander wrote:
> is
> http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#s-asynchronous-network-start
> relevant?
>
> I also believe there is information in the wiki or release notes about workarounds.
>
>
I have had a somewhat similar problem with some servers at work. The
servers in question acquire their ip address from a dhcp server and
either mount some filesystems over nfs or, in case of the nfs server
itself, export the relevant directories to specific hosts. During
bootup, dhclient tries to acquire an ip address but fails and
backgrounds since the network link is not yet activated. The link is
activated some time later in the boot sequence and dhclient succeeds on
its second attempt, the default being after several minutes of the first
attempt. However it is too late for the system, since by that time both
the nfs mounting and the nfs server process would have failed. The
server process fails because it is not able to resolve the host
addresses to which it is supposed to allow access.
I had realized it was some timing issue with the network driver. I tried
explicitly loading the network related modules at the
S20module-init-tools stage by adding the module to /etc/modules. I have
added a couple of echo statements to the modules-init-tools in order to
verify that the network module is indeed loaded before the networking
stage. However the problem still persisted.
I was finally able to workaround the problem by adding a 60 second sleep
at the end of /etc/init.d/networking and reducing the dhclient timeout
to 5 seconds and the retry to 10 seconds. This way, dhclient backgrounds
some 5-10 seconds after starting, but is able to succeed the second time
before the end of sleep.
I wonder if there is some better way to do it though. The link provided
by Marc describes this issue, but I could not find any workaround anywhere.
The relevant network module in my case was: bnx2
Thanks & regards,
--
Raj Kiran Grandhi
Date: Sat, 24 Nov 2007 01:20:47 +0100
From: Joris Van Herzele <jvh@whitenix.com>
To: debian-user@lists.debian.org
Cc: Marty <martyb@ix.netcom.com>, marcslists@gmail.com,
masatran@research.iiit.ac.in
Subject: Re: 1 in 2 chance : need to issue "/etc/init.d/networking restart"
after boot
Message-Id: <200711240021.lAO0L2SP025999@rs30.luxsci.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Marty wrote:
> Because of the intermittency of the problem, I would first suspect
> autonegotiation. Try a different device on the opposite end, or if you
> roll your own kernel, just manually force the mode. (If this works,
> please report it as a potential bug in the NIC driver.)
>
Thank you all for your interest and advice.
I really appreciate this.
Marty definitely had a point worth checking and indeed there appeared to
be an issue with auto-negotiation since the interface which I always
configured first, was working in half duplex mode ...
Something I only noticed when using 'ethtool'. In my defense I am more
familiar with BSD and seeing media- types and options by simply running
'ifconfig'. I had not noticed that this info does not show up in Debian
by just running 'ifconfig'.
Additionally I always assumed a duplex mismatch only causes severe
collisions and very slow access (the only behaviour I have previously
encountered in networks) but I never considered this would totally stop
the link from functioning.
Nonetheless I added lines such as 'post-up ethtool -s eth1 speed 100
duplex full autoneg off' to '/etc/network/interfaces' both on this
Debian testbox and at the same time reconfigured the appliance on the
other side. And yes I could get it to work like that. :)
The solution I went with however was replacing the crossover cable
between this Debian-host and the appliance by straight-through cables
and another switch. Both the Debian box and the appliance (also RealTek
NIC's by the way) not only always negotiate correctly this way, it has
an additional advantage.
The appliance on the other end sometimes has to go in layer2-fallback
and that once again tends to break the connectivity with a direct
crossover cable. Going in layer2-fallback does however not cause any
disruptions with this additional switch in place.
So the conclusion : Yes, it was indeed an autonegotiation failure :) and
No, I have no idea why I can have layer2-fallback with the additional
switch in place, yet not when the appliance is directly connected :(
Anyway another lesson learned, thanks for that ;)
--
Joris Van Herzele
Date: Fri, 23 Nov 2007 18:46:02 -0600
From: Kent West <westk@acu.edu>
To: debian-user@lists.debian.org
Subject: Re: [OT] firefox 3
Message-ID: <4747744A.2080006@acu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hugo Vanwoerkom wrote:
> Kent West wrote:
>> Kent West wrote:
>>> Hugo Vanwoerkom wrote:
>>>> Anybody try the new firefox 3?
>>>
>>
>> Also, most of my add-ons are incompatible with FF3. Reckon I'll have
>> to wait a while on those ....
>>
>
> Indeed. Keep us posted on that freeze up. I have not found any trouble
> thusfar.
>
> Hugo
>
>
I'm convinced now that the freeze was unrelated to FF3; I was logged in
as the second user, and I experienced another freeze as I shut down
Galeon followed by Icewm/X. I'm leaning toward it being an Icewm problem.
But, another issue with FF3; it defaults to what I consider an
unpleasant behavior, in that when you middle-click on a link to open the
link in a new tab, FF3 switches focus to that tab. There's a setting to
turn that off, which is good. But later when I went back to FF2
(iceweasel), it now exhibits that same default FF3 behavior (which it
has not done in the past), and I can't figure any way to turn it off,
even though I've found the setting for it. Arg. I should have known
better than to use FF3 by a live user and then switch back to FF2 so
that settings could mix.
--
Kent
Date: Fri, 23 Nov 2007 18:52:06 -0600
From: Kent West <westk@acu.edu>
To: debian-user@lists.debian.org
Subject: Re: [OT] firefox 3
Message-ID: <474775B6.3070102@acu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Kent West wrote:
> Hugo Vanwoerkom wrote:
>> Kent West wrote:
>>> Kent West wrote:
>>>> Hugo Vanwoerkom wrote:
>>>>> Anybody try the new firefox 3?
>>>>
>>>
>>> Also, most of my add-ons are incompatible with FF3. Reckon I'll have
>>> to wait a while on those ....
>>>
>>
>> Indeed. Keep us posted on that freeze up. I have not found any
>> trouble thusfar.
>>
>> Hugo
>>
>>
> I'm convinced now that the freeze was unrelated to FF3; I was logged
> in as the second user, and I experienced another freeze as I shut down
> Galeon followed by Icewm/X. I'm leaning toward it being an Icewm problem.
>
> But, another issue with FF3; it defaults to what I consider an
> unpleasant behavior, in that when you middle-click on a link to open
> the link in a new tab, FF3 switches focus to that tab. There's a
> setting to turn that off, which is good. But later when I went back to
> FF2 (iceweasel), it now exhibits that same default FF3 behavior (which
> it has not done in the past), and I can't figure any way to turn it
> off, even though I've found the setting for it. Arg. I should have
> known better than to use FF3 by a live user and then switch back to
> FF2 so that settings could mix.
>
Ah, just found another setting not obvious, and it fixed my problem.
All's good now.
So, my final answer? FF3 is fine, but I see no compelling reason yet to
upgrade. Once my plugins work with it, and it's packaged for Sid, I'll
pro'lly upgrade.
--
Kent
Date: Fri, 23 Nov 2007 18:53:49 -0600
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: command line wordperfect
Message-ID: <4747761D.6060004@cox.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/23/07 17:59, s. keeling wrote:
> Ron Johnson <ron.l.johnson@cox.net>:
>> On 11/23/07 14:37, Jude DaShiell wrote:
>>> I don't think such can be installed on debian. Probably not on freebsd
>>> either, so I'm curious have any of the emacs experts ever put together a
>>> key bindings package for emacs that can make a wordperfect user feel
>>> right at home? The internet service provider runs freebsd and a couple
>>> other subscribers on another email list would like to get a wp-like
>>> environment up and available on shellworld.net.
>> You mean the old DOS WP?
>
> On etch I see:
>
> v libwpd-dev -
> p libwpd-stream8c2a - Library for handling WordPerfect documents (sha
> p libwpd-tools - Tools from libwpd for converting WordPerfect to
> p libwpd8-dev - Library for handling WordPerfect documents (dev
> p libwpd8-doc - Library for handling WordPerfect documents (doc
> i A libwpd8c2a - Library for handling WordPerfect documents (sha
> p wp2x - WordPerfect 5.x documents to whatever converter
> p wpd2sxw - WordPerfect to OpenOffice.org converter
>
> Make of that what you will. If perl/python can interface with those
> libraries, you're off to the races.
Or install FreeDOS and DOS WordPerfect...
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHR3YdS9HxQb37XmcRAjL5AJwNMztQ+Fdmsb9uogMYiMdj0HDDsACg0lEA
7gtKsiZpydDfjraUb5H+PPM=
=Nk1J
-----END PGP SIGNATURE-----
Date: Fri, 23 Nov 2007 22:32:29 -0500
From: Ed Jabbour <ejbr@att.net>
To: debian-user@lists.debian.org
Subject: Re: listening to radio stations
Message-Id: <200711232232.29940.ejbr@att.net>
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Friday 23 November 2007 09:17, Jude DaShiell wrote:
> Do any command line tools exist in debian that will allow a user to listen
> to a streaming broadcast say from
> http://sc1.liquidviewer.com:9062/listen.pls I had that working fine on my
> mac mini yesterday then the stream went away so I am interested to know if
> debian can play this too if it's actually working. It's in the way of a
> cross -check.
I have xmms set to play pls files. Plays your link w/o a hitch.
Date: Fri, 23 Nov 2007 22:29:45 -0500
From: "Douglas A. Tutty" <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: Is it exist a mailing-list for console only users ?
Message-ID: <20071124032945.GA7188@titan.hooton>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sat, Nov 24, 2007 at 12:31:57AM +0100, s. keeling wrote:
> Paul Cartwright <ale@pcartwright.com>:
> > On Fri November 23 2007, Douglas A. Tutty wrote:
> > > When was the last time we had a questio from someone wondering how do do
> > > something in ed?
> >
> > I still use ed commands.. not daily, but.
>
> I never learned ed, except in vi.
There are unixes (mostly BSD) that don't have a single-user editor other
than ed. The logic being that if /usr can't mount, there may also be a
problem with termcap/terminfo. Ed is a nice small exec that can be
statically linked and remain small. In my emergency toolkit I have ed's
man page.
I suppose editing a file on NetBSD's toaster with a 2-line display is
easier in ed than vim.
Now, if only I could get my head around re's.
Doug.
Date: Fri, 23 Nov 2007 19:21:21 -0800 (PST)
From: Rich <rlcarr@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: RAID1 arrays not starting when drive is missing
Message-ID: <a72f7592-5575-4f06-814a-2308137667df@e1g2000hsh.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Nov 23, 5:10 am, martin f krafft <madd...@debian.org> wrote:
> also sprach Rich <rlc...@gmail.com> [2007.11.22.1345 +0000]:
>
> > I have two RAID1 devices -- /dev/md0 which is /boot (and
> > does NOT use LVM) and is made up of /dev/sda2 and /dev/sdb2,
> > and /dev/md1 which has LVM (and the rest of the system) over it
> > and is made up of /dev/sda3 and /dev/sdb3.
>
> Please show your mdadm.conf file.
Here it is:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD
superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=8c7280d3:5b4c9cd9:541ba3e9:02d46f81
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=bc6c4e8c:
7310603a:e1e7e1f0:3c1631ca
# This file was auto-generated on Tue, 20 Nov 2007 07:37:57 +0000
# by mkconf $Id: mkconf 324 2007-05-05 18:49:44Z madduck $
--
Rich Carreiro
End of debian-user-digest Digest V2007 Issue #2851
**************************************************
Received on Fri Nov 23 23:30:15 2007