From: adam@address.invalid
Moe Trin wrote:
> On Sun, 04 Nov 2012, in the Usenet newsgroup alt.os.linux.mandriva, in
article
> , Adam wrote:
[modem-on-hold]
>> the winmodem only switches from
>> (probably) v.34a to v.90 when it /connects/ as v.90. Although it now
>> gets initialized to v.90, the NZ/J software first does an ATZ which
>> resets that to v.92, so no connection is made using v.90 (unless I
>> make one myself) and NZ/J has the v.92 setting but connects at 33.4k.
>
> I'm lost here - I thought you said that ATZ wasn't mucking with the
> AT+MS=V90 because that +MS setting wasn't in NVRAM. If you set it on
> power-up, how is it being reset AFTER that?
On the winmodem, the +MS setting isn't stored in "NVRAM", but both ATZ
and AT&F reset it to V92.
>> or else disable the NZ/J software from sending ATZ
>
> Some modems take "ATZ" to mean "reset to NVRAM _and_ empty the command
> buffer", such that anything following the "Z" in a command is lost.
> I'd suggest resetting the init-string from "ATZ" to "ATF1+MS=V90".
Yep, ATZ does empty the command buffer. I'd expect AT&F to do the same,
but it doesn't. It turns out that 'nzppp' (their modified pppsetup)
gets the init string from a separate file (a one-line text file called
'mdminit'), so I changed the init strings (for both NZ & J) to
"AT&FW1+MS=V90" so it now connects to NZ/J at v.90. The "W1" isn't
necessary, but gives me more info on the connection when I look at the
NZ/J log afterward. 'mdminit' will /definitely/ get mentioned in
netzero-juno.txt 1.3.1!
[boot with wireless]
>> (the boot messages still report failure), but by the time
>> it gets to the login screen wireless is working.
>
> Is this because the /etc/rc.d/rc?.d/S??network is starting later than
> you want/need, or because the act of bringing up the wireless link is
> taking longer than it took to bring up the Ethernet interface
Under CentOS, it's S10network so I assume it's started fairly early on.
The boot messages still report failure both for the wireless device
and for ntpd, but by the time it gets to the level 3 login prompt
there's a message that wlan0 is up. In
/etc/sysconfig/network-scripts/ifcfg-Wireless_connecection_1 I tried
changing IPV4_FAILURE_FATAL to "no" and also tried adding
NETWORKDELAY=30s (which did /not/ cause a delay during startup) but
neither prevented those failure messages. OTOH since wireless is up by
the time I'm logging in, I don't think it's worth worrying about.
BTW my neighbor on SSID "frrggl" has switched to channel 4, which I'd
guess had something to do with my using channel 9. The other 4 or 5
neighbors with Wi-Fi are still on 1, 6 or 11.
[new systems not coming with internal modems]
> Not surprising - it seems that most domestic systems expect that there
> is broad-band of some variety.
It also saves the manufacturer a few bucks, because (I'd guess) most
users don't care that it comes without any dialup modem, and dialup
modems are still available separately (for a cost) for anyone who wants one.
> Sure, if you need the speed
> of broadband, you can probably get satellite, but you've mentioned
> relatives in Vermont where that isn't practical.
Dialup is sufficient for my aunt and uncle (who just celebrated their
64th anniversary BTW). Satellite /might/ be possible for some of their
Vermont neighbors. Also, they're snowbirds, and have enough problems
getting their POTS activated and suspended each year. Their
granddaughter sensibly set them up to use Gmail, so they don't need the
same ISP at both homes.
> But likewise, the
> computer stores aren't out there in the country (implying that their
> customers have got broadband)
Or else because there aren't enough potential customers in the country.
['route' vs 'ip route']
>> In the (current?) version of Debian on eris, /sbin/ip is a symlink to
>> /bin/ip ; the others are in /sbin. I might as well check for both,
>> and then just use 'ip route' to invoke whichever's first in the
>> user's PATH.
>
> Do all of your users have /sbin/ in their $PATH? Mine don't. And
> don't forget that the 'test' or '[' function doesn't know about $PATH.
"All of your users" means anyone who tries to use that script, so I
can't predict anything. However, since it /has/ to be run as root, I
think it's a safe assumption that /sbin will be in the PATH. I've
decided to just check for /sbin/ip.
I recently found out that 'sudo' has its own $PATH, separate from both
the user's and root's.
[adam@stolid ~]$ sudo which asdf
which: no asdf in (/sbin:/bin:/usr/sbin:/usr/bin)
[adam@stolid ~]$
That /may/ explain why 'sudo' doesn't work properly with that script.
>> Actually my biggest worry about the kidney transplant is that for
>> unknown reasons, many successful ones eventually stop working.
>> I remember my nephrologist saying happily that I should be good for
>> another 15-20 years, but even that would run out before I'm 70.
>
> That's still at least a dozen years down the pike, and a lot can
> happen in that time. They may discover why the failures occur, and
> can work around it.
And also, anyone whose transplant lasted "only" 15-20 years obviously
had it done at least 15-20 years ago. Perhaps procedures are better
now. At the county fair one year, someone dropped by who'd had a kidney
transplant in the early 1990s, and things were a lot more complicated
and unpleasant back then.
> The old question always asked by the people on the hell-desk is "what
> did you change"? Or in this case, "why"?
Transplant failure has happened in people where nothing has changed.
>> Some of my XL t-shirts don't even fit decently any more.
>
> ;-) Know about that one too. Have you a rational explanation of
> why you're gaining?
Some of the transplant meds cause weight gain (from increased hunger).
Also, I like food, and I'm not exercising much. One "trick" I ought to
go back to is to go to bed hungry (no eating after dinner).
> I am _trying_ to use
> "portion control" as well as avoiding snacks, etc., but that doesn't
> always work. On top of that, the primary care _wants_ me to eat a
> "small" breakfast (150-250 calories max) to "control hunger".
One serving of hot cereal is less than that, for example.
Adam
--
Registered Linux User #536473
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
