----- Original Message -----
From: "Carlos E. R." <robin.listas(a)telefonica.net>
To: "OS-en" <opensuse(a)opensuse.org>
Sent: Tuesday, December 23, 2008 7:53 AM
Subject: Re: [opensuse] 11.0 cusrses mode yast printer config fail
-----BEGIN PGP SIGNED MESSAGE-----
On Tuesday, 2008-12-23 at 06:54 -0500, Brian K. White wrote:
I reproduced the problem on 4 boxes, but, they
are all practically clones of each other.
Then you could write a bugzilla, the problem can be confirmed.
Can anyone else confirm this or know about it and
know what the problem
is and a work-around other than manually creating & editing
printers.conf? Pretend I only have serial console access and that
can't be operated well enough via lynx.
Well, the workaround is http://localhost:631
. If lynx is not good enough,
there are more: links, w3m... and of course, you can use mozilla from
another computer with graphical interface, but first you have to edit the
security settings of cups so that it allows remote access. You do have a
network, so it should be feasible.
And, if the network is secure and not accessible, then you can get another
network through the serial port (ppp), instead of console.
I know all that but the problem is not get a printer working. I did that a lot easier than
setting up ppp over a series of serial, telnet & ssh connections and getting all the
intervening connections into binary modes that wouldn't choke on ppp protocol data
(or munge it). The problem is yast curses interface should work.
I originally wrote this whole big tirade pointing out why it should work and why none of
those options are any sort of excuse, but really it just comes down to, a) lynx actually
seems to work ok, so maybe that wouldn't be such a bad answer, and/or b) Sure I can
also just create/edit the files directly without yast or any other front end, which is
exactly what I did here, but if that's a valid argument for one thing then it's
a valid argument for everything and if I have to do that as a rule, then I should be using
debian or gentoo where I can -really- do it myself. Suse, as an rpm based distro that
isn't redhat, without yast being really really excellent way above anything anyone
else has, is just a lemon.
11.0 is pretty well peppered with breakages and downgrades in yast curses interface.
And I only use the curses interface. I don't have gui's on my servers and
don't want to enable remote access to the http based things like swat/cups/apcupsd.
Setting up a single form of protected shell access, and only having to worry about the
security that one thing, and having text based utils that are used locally via that shell
access, and without any ^%$# vpns, the same app, working the same way, the same interface,
whether you're remote, local, via telnet, via serial, via ssh to serial console
appliace, via direct modem dialup, via the servers vga console, etc... is SO the only sane
way to go untill you scale up so far that the only sane way to go is centralized
administration systems (ie, neither yast nor direct admin).
Brian K. White brian(a)aljex.com http://www.myspace.com/KEYofR
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org