That's why Odyssey is still powering my boxes -- the little engine (release)
that could.........

    Now Pierre, don't hold back, go ahead and tell us how you really
feel................

Pierre Fortin wrote:

> I don't like this resorting to this kind of post, and I'll probably start
> a small war; but I need to vent...
>
> <rant>
> So far, 9.0 has been more irritation than help...  I have a new IBM
> ThinkPad A20m which moves around with me.  So...  as I move around, I
> setup my environment for each new type of location...  the unit is called
> "gypsy" for obvious reasons.
>
> Anyway...  in NC, gypsy connects to my main LAN -- setup everything and
> all worked fine in the "default" profile.
>
> Next, in SC, gypsy connects to another LAN -- same parameters, except for
> the DNS servers, so I setup profiles NC and SC.
>
> Last night, I got around to setting it up for dialup...  and there started
> the descent into hell...
>
> Summary:
> * MCC/Network&Internet is thoroughly confused with 3 profiles (not incl
> default)
>   location   interface   status   net_access
>      NC         eth0      down     connected
>      SC         eth0      down     connected
>    DialUp       modem     down     connected
>   This SUX cuz the there's no LAN connection and the modem can't even be
>   dialed up because...
>
> * devfsd keeps clobbering my /dev/modem -- I want/need it to be:
> lr-xr-xr-x    1 root  root    12 Nov 20 22:32 /dev/modem -> /dev/tts/LT0
> NOT:
> lr-xr-xr-x    1 root  root     5 Nov 20 22:04 /dev/modem -> ttyS0
> which does NOT work with an internal Lucent LinModem...
>
> # ll  /etc/devfs/conf.d/
> total 16
> -rw-r--r--    1 root     root          983 Aug 30 12:19 dynamic.conf
> -rw-r--r--    1 root     root          105 Nov 20 22:04 modem.conf
> -rw-r--r--    1 root     root          103 Oct 30 20:25 mouse.conf
> -rw-r--r--    1 root     root          105 Nov 20 22:04 ttyS0.conf
>
> Gee... any chance "conf" in {modem,ttyS0}.conf is really just the
> abbreviation for "confusion"...?  Somehow, I doubt {modem,ttyS0}.conf are
> intended to be used at the same time...
>
> # for f in /etc/devfs/conf.d/*; do echo "--------- $f"; cat $f;done
> --------- /etc/devfs/conf.d/dynamic.conf
> # dynamic desktop and co
>
> REGISTER        .*/part.*       EXECUTE /etc/dynamic/scripts/part.script
> add $devpath
> UNREGISTER      .*/part.*       EXECUTE /etc/dynamic/scripts/part.script
> del $devpath
>
> REGISTER        v4l/video.*     EXECUTE /etc/dynamic/scripts/webcam.script
> add $devpath
> UNREGISTER      v4l/video.*     EXECUTE /etc/dynamic/scripts/webcam.script
> del $devpath
>
> REGISTER        usb/scanner.*   EXECUTE
> /etc/dynamic/scripts/scanner.script add $devpath
> UNREGISTER      usb/scanner.*   EXECUTE
> /etc/dynamic/scripts/scanner.script del $devpath
>
> REGISTER        usb/rio500      EXECUTE /etc/dynamic/scripts/rio500.script
> add $devpath
> UNREGISTER      usb/rio500      EXECUTE /etc/dynamic/scripts/rio500.script
> del $devpath
>
> REGISTER        usb/tts/[13579] EXECUTE /etc/dynamic/scripts/visor.script
> add $devpath
> UNREGISTER      usb/tts/[13579] EXECUTE /etc/dynamic/scripts/visor.script
> del $devpath
>
> REGISTER        (usb/lp.*|printers/.*)  EXECUTE
> /etc/dynamic/scripts/lp.script add $devpath
> UNREGISTER      (usb/lp.*|printers/.*)  EXECUTE
> /etc/dynamic/scripts/lp.script del $devpath
> --------- /etc/devfs/conf.d/modem.conf
> REGISTER        ^tts/0$ CFUNCTION GLOBAL mksymlink tts/0 modem
> UNREGISTER      ^tts/0$ CFUNCTION GLOBAL unlink modem
> --------- /etc/devfs/conf.d/mouse.conf
> REGISTER        ^psaux$ CFUNCTION GLOBAL symlink psaux mouse
> UNREGISTER      ^psaux$ CFUNCTION GLOBAL unlink mouse
> --------- /etc/devfs/conf.d/ttyS0.conf
> REGISTER        ^tts/0$ CFUNCTION GLOBAL mksymlink tts/0 ttyS0
> UNREGISTER      ^tts/0$ CFUNCTION GLOBAL unlink ttyS0
>
> * just enabling modem access resulted in shorewall being silently
> enabled...  When I tried to switch back to LAN mode, I was unable to
> connect to ANYTHING...
>
> Nov 19 23:25:37 gypsy drakgw[27131]: running: chkconfig --add shorewall
> Nov 19 23:25:37 gypsy drakgw[27131]: running: service > /dev/null
> shorewall restart
> Nov 19 23:25:41 gypsy logger: Shorewall Started
> Nov 19 23:25:41 gypsy drakgw[27131]: Configuring a DHCP server on
> 192.168.1.0
> Nov 19 23:25:41 gypsy drakgw[27131]: launched command:
> /usr/sbin/update_dhcp.pl
> Nov 19 23:25:41 gypsy drakgw[27131]: Updating CUPS configuration
> accordingly
> Nov 19 23:25:41 gypsy drakgw[27131]: Starting daemons
> Nov 19 23:25:41 gypsy drakgw[27131]: launched command:
> /etc/rc.d/init.d/cups status >/dev/null
> Nov 19 23:25:42 gypsy drakgw[27131]: launched command:
> /etc/rc.d/init.d/cups stop
> Nov 19 23:25:43 gypsy cups: cupsd shutdown succeeded
> Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
> /etc/rc.d/init.d/dhcpd status >/dev/null
> Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
> /etc/rc.d/init.d/named status >/dev/null 2>/dev/null
> Nov 19 23:25:43 gypsy drakgw[27131]: launched command:
> /etc/rc.d/init.d/named stop
> Nov 19 23:25:44 gypsy named[1246]: shutting down
> Nov 19 23:25:44 gypsy named[1246]: stopping command channel on
> 127.0.0.1#953
> Nov 19 23:25:44 gypsy named[1246]: no longer listening on 127.0.0.1#53
> Nov 19 23:25:44 gypsy named[1236]: exiting
> Nov 19 23:25:45 gypsy named: named shutdown succeeded
> Nov 19 23:25:45 gypsy drakgw[27131]: launched command:
> /etc/sysconfig/network-scripts/net_cnx_down >/dev/null
> Nov 19 23:25:45 gypsy drakgw[27131]: [drakgw] Warning, sys failed for
> /etc/sysconfig/network-scripts/net_cnx_down >/dev/null
> Nov 19 23:25:45 gypsy drakgw[27131]: launched command:
> /etc/rc.d/init.d/network restart >/dev/null
> Nov 19 23:25:46 gypsy network: Shutting down interface eth0:  succeeded
> Nov 19 23:25:46 gypsy network: Shutting down loopback interface:
> succeeded
> Nov 19 23:25:46 gypsy network: Disabling IPv4 packet forwarding:
> succeeded
> Nov 19 23:25:46 gypsy network: Setting network parameters:  succeeded
> Nov 19 23:25:47 gypsy network: Bringing up loopback interface:  succeeded
> Nov 19 23:25:47 gypsy network: Enabling IPv4 packet forwarding succeeded
> Nov 19 23:25:49 gypsy network: Bringing up interface eth0:  succeeded
> Nov 19 23:25:49 gypsy drakgw[27131]: launched command:
> /etc/sysconfig/network-scripts/net_cnx_up >/dev/null
> Nov 19 23:25:50 gypsy ifup-ppp: Setting up a new /etc/ppp/peers/ppp0
> config file
> Nov 19 23:25:50 gypsy pppd[28737]: pppd 2.4.1 started by root, uid 0
> Nov 19 23:25:50 gypsy ifup-ppp: pppd started for ppp0 on /dev/modem at
> 115200
>
> Followed by the following ad infinitum...
>
> Nov 19 23:29:53 gypsy kernel: Shorewall:all2all:REJECT:IN= OUT=eth0
> SRC=192.168.1.1 DST=<destination> LEN=57 TOS=0x00 PREC=0x00
>  TTL=64 ID=0 DF PROTO=UDP SPT=35560 DPT=53 LEN=37
>
> I know some people will argue *for* shorewall; but until I find out more
> about it, it is OUT of here...  shutting down my networking with a
> misconfigured (or UNconfigured) shorewall for which there is no "man" or
> "info" page is downright INconsiderate, IMO.  And NO,
> file:///usr/share/doc/shorewall-1.3.7c is not worthy of a mention.
>
> The MCC/Network&Internet stuff is (or SHOULD be) intended to make life
> easier... since it allows for multiple "profiles", you'd think it would
> work a little better than total confusion ("connected" with NO LAN/modem
> even wired into the box is... well... horse puckey!)
>
> Am I UNimpressed with this GUI stuff...?  DAMN RIGHT!!!
>
> At this rate, I don't need protection from the 'net; I need protection
> from Mandrake's decisions to release distros with config tools which are
> not production ready!!
> </rant>
>
> 9.0 is making it extremely difficult for me to promote Mandrake these
> days...
>
> Pierre
>
>   ------------------------------------------------------------------------
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com

--
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to