home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.mandriva      Somewhat decent but also getting bloated      29,919 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 28,699 of 29,919   
   Adam to Moe Trin   
   Re: OT: Off-Topic (1/2)   
   04 Nov 12 13:04:55   
   
   From: adam@address.invalid   
      
   Moe Trin wrote:   
   > On Thu, 01 Nov 2012, in the Usenet newsgroup alt.os.linux.mandriva, in   
   article   
   > , Adam wrote:   
      
   [modem-on-hold]   
      
   > From what I understand, this is part of the v.92 specification, and   
   > the question is more if the ISP has enabled the function.   
      
   According to AT+PCW and AT+PMH, the Linuxant driver on eris doesn't   
   support it, but the USB modem does.  A NetZero web page says they   
   support it, but the page is old, pre-2006.  I'm also not sure whether   
   their Linux software supports it.  Again, doesn't sound worth it for me.   
      
   >>> But if you've got v.90 working, that probably good enough.   
      
   Another complication discovered: 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   
   suppose somewhere in the Linuxant software there's code that makes it   
   default to v.92.  Maybe someday I'll look at it and try to change it to   
   v.90, or else disable the NZ/J software from sending ATZ (maybe just "AT   
   " instead).   
      
   [boot with wireless]   
      
   > I don't have a CentOS to look at,. but "the Red Hat way" was that   
   > /etc/rc.d/init.d/network eventually calls the script[s] in   
   > /etc/sysconfig/network-scripts/ and works it's magic there.   
      
   Fedora and CentOS are slightly different.  The problem was that CentOS   
   had some of the files in /etc/sysconfig/network-scripts/ named   
   *-wireless and others were *-Wireless_connection_1 .  Now that there are   
   both versions of all three relevant files, it boots with wireless   
   connected.  Not as early in the boot process as I'd like (the boot   
   messages still report failure), but by the time it gets to the login   
   screen wireless is working.   
      
   [Linuxant driver]   
      
   > I was looking at new systems at Frys recently   
      
   Considering getting one?   
      
   > none had an internal modem,   
      
   Seems to be standard these days.   
      
   > and the choices of externals is essentially limited now to   
   > the USB interface.   
      
   Well, USB hardware modems should work with any system with a USB port,   
   regardless of OS.  The local Best Buy now stocks only one modem, a USB   
   hardware modem, and if it were my decision I'd say that's just about the   
   right number of modems to carry nowadays given the limited shelf space   
   of the store.  I'd be surprised if they even sell one a week.   
      
   [which modems]   
      
   >>> 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?   
   >   
   >   [ -L /dev/modem ]   
      
   But [ -L /dev/modem ] would return true even if it was an incorrect or   
   dangling link.  Basically I'm going to describe the one-time setup in   
   the text, instead of complicating my script.  Besides, it's   
   distro-dependent.   
      
   ['route' vs 'ip route']   
      
   >> /etc/avahi/avahi-autoipd.action (in several distros)   
   >   
   >> if [ -x /bin/ip -o -x /sbin/ip ] ; then   
   >   
   > While the FHS says that (and doesn't mention the "ip" command), it's   
   > not that much extra.  One of the people at work says Debian/clones   
   > puts "ip" in /bin, and retains /sbin/ifconfig and /sbin/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.   
      
   >> 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".   
      
   The problem is in some versions of Java.   
      
   [adam@stolid ~]$ cat /opt/juclient/runclient.sh   
   #!/bin/sh   
   cd /opt/juclient   
   cp=./lib/zcast1_6.jar:./lib/bwt300.jar   
   java -cp $cp -Dnz.browser=mozilla -Dnz.clientName=$0 -Dnz.RAS=./nzppp   
   -Dnz.rasdelay=60000 -Dnz.TextFontName=SansSerif -Dnz.TextFontSize=7   
   -Dnz.FontName=Arial -Dnz.FontSize=9 nzcom.ZCast   
   [adam@stolid ~]$   
      
   The "java..." is one long line.  This is the NZ/J-supplied script that   
   actually makes the connection, or rather runs the Java software to make   
   the connection.  On stolid, the java command in that works (brings up   
   the splash screen) whether invoked as "adam" or root using "su -c" or   
   "su - -c".  However, when run with sudo, java reports "No protocol   
   specified" and aborts.  On eris under CentOS, it's successful in all of   
   those cases.  I suspect an obscure bug in:   
      
   [adam@stolid ~]$ java -version   
   java version "1.7.0_09"   
   Java(TM) SE Runtime Environment (build 1.7.0_09-b05)   
   Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)   
   [adam@stolid ~]$   
      
   but not:   
      
   [adam@eris ~]$ java -version   
   java version "1.6.0_24"   
   OpenJDK Runtime Environment (IcedTea6 1.11.5)   
   (rhel-1.50.1.11.5.el6_3-x86_64)   
   OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)   
   [adam@eris ~]$   
      
   I can either look into it, or just put a warning in my file.  Probably   
   the latter, given the limited interest in it.   
      
   >> 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.   
   >   
   > that really is good to hear, and I know how good it must feel.   
      
   Thanks!  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.  Some   
   transplants have lasted considerably longer, and of course those were   
   done years ago using older procedures and medications.   
      
   >> Unfortunately that's no excuse for not working harder on losing weight.   
   >   
   > Ah, you would have to bring that up.  I'm catching it from the Primary   
   > Care that I really should loose a minimum of 10 pounds.   
      
   I've gained at least 30 pounds just since the transplant, about one a   
   month.  Some of my XL t-shirts don't even fit decently any more.   
      
   Meanwhile, I'm working on another story for class.  It's a parody of the   
   "hard-boiled" detective in 1940s L.A., and I'm trying to find some way   
   to work the phrase "out in the tules" into it.   
      
   Adam   
   --   
   Registered Linux User #536473   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca