From: adam@address.invalid
Moe Trin wrote:
> On Mon, 29 Oct 2012, in the Usenet newsgroup alt.os.linux.mandriva, in
article
> , Adam wrote:
[slow dialup connections]
>> Mueller also says v.92 has additional features, like modem-on-hold,
>
> "modem-on-hold" requires you to buy additional services from your
> telephone provider.
I gather you mean "call waiting" which I already have (and pay for)
although my NZ/J dialing string currently starts with "*70" to
temporarily disable it. Personally I hate that "feature", but got it
just in case I was on the phone when the transplant center called. I
suppose if I wanted to use it, I'd have to see whether both the modem
driver and the ISP support it too. Doesn't sound worth it.
> But if you've got v.90 working, that probably good enough.
Yes, since apart from testing I expect to use dialup at most a few times
a year.
>> I also put an additional command needed to start the wireless
>> connection into rc.local which is later in the boot process than I'd
>> like (e.g. after it's tried nfs).
>
> I would have thought that would have been handled by the S??network
> script, which should be run before S??netfs. If this is systemd or
> upstart rather than the SysVInit, the NFS script needs to check that
> "some" networking is up, rather than just Ethernet.
CentOS is still using SysVInit, but I'm not sure where in
/etc/rc.d/init.d/network I should add that command. It's "iwconfig
wlan0 essid abcdef" or whatever my ESSID is, which is why it couldn't be
included in CentOS as shipped. I suppose I could add a line there
calling some customized file if it exists, once I figure out where to
add that line.
[Linuxant driver]
>> The driver(s) from Linuxant haven't been updated
>> since about 2010, and they're expecting to find system headers that
>> aren't in newer kernels.
>
> And given the declining importance of modems, I suspect they won't
> be updating them either.
I'm surprised their website is still up, as they don't seem to have done
anything in the past few years. Maybe that's why they let Mandriva
include their driver (gratis) in the repository, although the one in the
2011.0 repository still has 2010.1 in its name.
[netzero-juno.txt]
>> [root@stolid nzclient]# file nzppp
[...]
>> which is the program that actually makes the connection -- it's
>> actually a modification of pppsetup-2.28.
>
> which is also ancient
I have the C source for that, and it looks like the NZ/J file has a few
text strings that aren't in the C source, at least not the source I
found. In fact, wouldn't NZ/J's modification without offering their
source technically have been a license violation? (Not that I'm going
to complain!)
>> I suppose that when the shared libraries it uses no longer exist,
>> their software won't work either. From "strings", those seem to
>> include /lib/ld-linux.so.2 and libc.so.6 although on my system
>> they're both symlinks.
>
> They're symlinks on all systems - they point to the actual version of
> the various libraries.
Okay -- so I can count on those "libraries" working on (nearly) all
future distros and releases.
>> The issue of "which modems
>> are usable under Linux" is broad enough and confusing enough so that
>> I think I'll stick to generalities and suggest a web search for any
>> particular model.
>
> [...] I doubt there will ever be
> a comparable list again. The best that can be done is to refer them
> to a search engine, looking for the make/model and the keyword "Linux".
Seems like every time I revise it, I cut out more information. :-)
>> And I suppose SysVInit vs. systemd. I can either find a way to
>> determine whether udev is involved, or just say "you may need to...".
>
> I suspect the latter - as far as I know, udev is here to stay, and
> it's just how the individual distribution implements static device
> links.
Another "see your distro's documentation" item, then?
['route' vs 'ip route']
> if [ -x /sbin/ip ] ; then
> GATEWAY=$(/sbin/ip route list | grep default | cut -d' ' -f 3)
> /sbin/ip route del default
> elif [ -x /sbin/route ] ; then
That looks reasonable -- I'm trying it out. Two things, though. The
one existing file I've found that checks is
/etc/avahi/avahi-autoipd.action (in several distros), and that has
(excerpts):
if [ -x /bin/ip -o -x /sbin/ip ] ; then
ip addr add "$3"/16 brd 169.254.255.255 label "$2:avahi" scope
link dev "$2"
ip route add default dev "$2" metric "$METRIC" scope link ||:
[more commands]
elif [ -x /bin/ifconfig -o -x /sbin/ifconfig ] ; then
# We have the old ifconfig tool
ifconfig "$2:avahi" inet "$3" netmask 255.255.0.0 broadcast
169.254.255.255 up
route add default dev "$2:avahi" metric "$METRIC" ||:
[more commands]
else
echo "No network configuration tool found." >&2
exit 1
fi
Think it's important to check for 'ip' and 'route' in /bin as well as /sbin?
Another unexpected problem is that the current (test) version of the
script doesn't run correctly if invoked by 'sudo' but runs correctly if
invoked by "su -c". I haven't narrowed it down yet, but I thought that
wasn't supposed to happen. I thought if an executable was invoked with
'sudo', then any other files it accesses (or runs) are also done with
root privileges.
[Hurricane Sandy]
> My sister reported some wind damage, but the rainfall wasn't
> significant. Apparently a tree limb came down nearby
The house across the street from my parents had a tree knocked down, but
fortunately it didn't hit anything.
I was at Albany (80 miles N of me) today for the transplant clinic, and
I asked around a bit in the waiting room, and the locals reported either
mild rain or no rain at all. The PA said I'm doing extremely well
(going by lab work), and the surgeon wants me back in _six_ months.
Last time it was four months, and before that three months.
Unfortunately that's no excuse for not working harder on losing weight.
Adam
--
Registered Linux User #536473
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
