From: adam@address.invalid
Moe Trin wrote:
> On Mon, 22 Oct 2012, in the Usenet newsgroup alt.os.linux.mandriva, in
article
> , Adam wrote:
>>> Those older versions on the distro repositories - are they old, and
>>> unpatched for recent security updates? If that's the case, you may
>>> want to be looking at a different distro
>
>> That's what I have a test system for. :-)
>
> Not many people think to look at the updates issue. Yes, the packages
> included and the versions thereof, but how does the distribution
> respond to bugs and security problems?
I can see where if this were my job, a great many factors would go into
choosing a distro. I expect every user would have a complaint that some
feature was better in a distro I'd rejected.
>> I've stayed with the latest Mandriva-customized kernel which ATM is
>> 2.6.39.4-5.1.
>
> I don't believe 2.6.39 is being maintained by kernel.org.
"Notice: This is an official package supported by Mandriva"
[slow dialup connections]
I think I found it. Looks like a small bug in the linmodem software.
When powered up, the modem is set ("AT+MS?") to v.92, but acts as if
it's v.34 or whatever the 33.6k standard is. If I set it to v.90
("AT+MS=V90"), it can connect with v.90 speed and compression. After
one connection using v.90, I can set it to v.92 and it'll use v.92 speed
and compression. (Or I could just leave it at v.90, which doesn't seem
much worse than v.92.)
Unfortunately that setting isn't part of its "NVRAM". It looks to me
like the default protocol setting is in the part of the package/tarball
that's distributed as object code (some is .O, some is .c and .h), and I
think tracking that down would be more work than it's worth. I'll look
into whether "echo AT+MS=V90 > /dev/modem" will work, or maybe invoking
minicom with a very short script. BTW the Linuxant driver is now a
non-free part of the Mandriva repository, though not other distros AFAIK.
>> I haven't been able to get that driver to compile under 3.x kernels
>> yet. It /is/ working under CentOS with kernel 2.x.
>
> What kind of error messages? Do you have all of the assorted -devel
> packages installed?
So far, I've only been able to try it under Fedora and Mageia (and
CentOS where it succeeded the first time). At first, both complained
that one system header file (different one for each) wasn't found. I
created empty files with that name in the appropriate kernel source
directory, hoping that would do it. Now both distros give the same errors:
[start of error log snipped -- no problems in that part]
In file included from /usr/lib/hsfmodem/modules/osservices.c:20:0:
/usr/lib/hsfmodem/modules/GPL/oscompat.h:201:57: error:
'SPIN_LOCK_UNLOCKED' undeclared here (not in a function)
/usr/lib/hsfmodem/modules/osservices.c: In function 'cnxt_thread':
/usr/lib/hsfmodem/modules/osservices.c:468:2: error: implicit
declaration of function 'lock_kernel'
[-Werror=implicit-function-declaration]
/usr/lib/hsfmodem/modules/osservices.c:502:2: error: implicit
declaration of function 'unlock_kernel'
[-Werror=implicit-function-declaration]
/usr/lib/hsfmodem/modules/osservices.c: In function 'OsInit':
/usr/lib/hsfmodem/modules/osservices.c:1287:80: warning: format '%d'
expects argument of type 'int', but argument 2 has type 'long unsigned
int' [-Wformat]
/usr/lib/hsfmodem/modules/osservices.c:1287:80: warning: format '%d'
expects argument of type 'int', but argument 3 has type 'long unsigned
int' [-Wformat]
cc1: some warnings being treated as errors
make[2]: *** [/usr/lib/hsfmodem/modules/osservices.o] Error 1
make[1]: *** [_module_/usr/lib/hsfmodem/modules] Error 2
make[1]: Leaving directory `/usr/src/kernels/3.5.4-2.fc17.x86_64'
make: *** [all] Error 2
I don't know much C, but maybe some headers are missing. I could either
spend time looking into it, or I could consider how seldom I'd be using
dialup (especially on eris) and that I already have it working under
CentOS and just leave it at that. I think I'll be replacing Fedora
there anyway.
> I had a [USR] 5686-03 for a while, and sold it for some reason. It
> was a fine modem.
This one was given away ~2008 at the local Windows UG back when my
parents were curious about Linux, so I had louise-desktop use it for
both WinXP and Ubuntu (through USB-RS232 adapter) instead of the winmodem.
>> Connection speeds were 45333/ARQ to 50666/ARQ
>
> Were those speeds here, or at the previous place?
All "here", which I believe is about a mile from the H.P. CO, and all to
the same H.P. POP phone number.
>> There's another PCI winmodem in there that I might try on eris.
>
> I'd probably keep only one plugged in at a time - both noise/loading
> issues and avoiding exposing them to the same lightning surge at the
> same time.
I have to, as eris only has 2 PCI slots (plus two PCIe) and one's needed
for the Wi-Fi card.
>> I revised netzero-juno.txt to include those and
>> posted the new version on my home page.
Well, I tried not to bother you with yet another request for comments on
it, but you have some good points. There IS a need for version 1.3.1.
> Re: internal PCI modems - my understanding is the the USR 5610C is
> still available, though I haven't seen it locally. It works fine.
I haven't seen any in years, which was why I wrote that. I suppose I
should check NewEgg, TigerDirect, Amazon, et al. to see whether they
still have anything.
> Re: /dev/modem link - udev problems?
Yep. I forgot I had to create a link in /lib/udev/devices for it to be
persistent on stolid. With CentOS on eris, /dev/modem just stays there.
> Re: Revise script to use 'ip route' instead of 'route'
Thanks! Sounds like they're similar enough to cause confusion when
there are differences. I just hadn't looked into 'ip route', because
I'm not sure I understand 'route' as it is. :-)
>> Dad and I wired the house for extra phones before that
>> was allowable. The hard part was getting the phones.
>
> There was a surplus joint over near the freeway in Mountain View that
> was selling phones then
A friend of Dad's did part-time maintenance at an apartment building, so
if any tenant moved out but left their phone behind...
>> When we wired the house in the mid-late '70s, those 4-pin plugs and
>> jacks were standard so we used them
>
> Larger, uglier, but they worked reliably.
More reliable than RJ-11, I'd say, and could be connected without
special tools. Also repairable if necessary, which RJ-11 isn't.
>> In other news, my parents offered me some of their bookcases, as
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
