Re: [opensuse] VNC Remote Install on 11.0 Broken
----- Original Message ----- From: "Andrew Joakimsen" <joakimsen@gmail.com> To: "Brian K. White" <brian@aljex.com> Sent: Tuesday, July 01, 2008 5:51 AM Subject: Re: [opensuse] VNC Remote Install on 11.0 Broken
Mind chiming in on bug 390837?
I think it's sort of offensive how they label the thing "RESOLVED" just because one dude doesn't see the problem on his test box. Call it "UNVERIFIED" or something but resolved is pretty assenine as long as there are people reporting the problem. Espcially when one guy takes a picture of his screen with a camera and another guy has captured serial console output and a screen shot of the scrambled vnc client display, and other guy describes the same symptoms out of the blue in a completely different venue but which I linked in, all saying the same thing from wildly unrelated sources. I wish I could give myself a pay raise and a grilfriend simply by decree like that. Hey while we're at it, how about that ozone hole huh? Resolved! yay! Stupidity of our president? Resolved! Cancer? Resolved! -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message ----- From: "Brian K. White" <brian@aljex.com> To: <opensuse@opensuse.org> Sent: Tuesday, July 01, 2008 10:17 PM Subject: Re: [opensuse] VNC Remote Install on 11.0 Broken ----- Original Message ----- From: "Andrew Joakimsen" <joakimsen@gmail.com> To: "Brian K. White" <brian@aljex.com> Sent: Tuesday, July 01, 2008 5:51 AM Subject: Re: [opensuse] VNC Remote Install on 11.0 Broken
Mind chiming in on bug 390837?
I wish I could give myself a pay raise and a grilfriend simply by decree like that. Hey while we're at it, how about that ozone hole huh? Resolved! yay! Stupidity of our president? Resolved! Cancer? Resolved!
Wow, now they have taken some ridiculously unrelated other bug, and decided it' a duplicate of this one. Let's see, this one involves _only_ 11.0 installer, 10.3 _works_, and happens _before install_, and has _nothing_ to do with nic device name assignment. The other one involes the 10.3 installer, and happens _after install_, and seems to be about how the nics are treated after install vs during install. Clearly identical problems. I don't even care about the vnc install option but this is just so stupid it's drawing my attention anyways. If SUSE will act like this here, where else are they being retards? Not inspiring continued confidense in my choice that all our servers will run suse a few years ago when we finally moved off of that other os everyone hates these days that isn't Windows. The choice was made because it was the "best engineered all around" and because no one else had anything as good as yast. Attention to detail was a key factor. A phrase I used to tout was "Every distribution has lots of nice looking configurators, but it's only true for Suse that if there is a button, it works." Oh well. Everything comes and goes in waves I guess. SCO was the best thing you could possibly run for a long time and the company was outstanding to deal with as people as well. That changed. If Suse is going to get all slipshod and sloppy like every other distribution, that was really their only distinction as far as I can see. Take away that and you have just another pain in the neck do-it-yourself linux distro. No more boot installed system, repair system that doesnt repair (which is understandable but what's unforgivable is it _says_ everything is fixed), installer that doesn't work nearly as smoothely as before*. I've encountered smaller things that weren't show stoppers to me, almost cosmetic, but, they didn't exist in 10.3 or earlier, so it's a regression. * early in the 2nd stage of install from http source, it attempts to access the repos and fails, apparently because the nics have not yet been (re?)configured after the reboot. the failure generates a couple of ugly looking errorboxes but doesn't seem to otherwise affect the actual conclusion of the install. * when using a serial console, something in bashrc keeps setting LINES=24, which screws up some yast screens and makes some yast dialog elements not appear anywhere n the screen. Specifically ne big example, the nic cofig section, there are no tabs on top for overview/general/hardware/hostname/dns/routing Those dialogs are simply not reachable by any means. The work around is, manually set & export LINES=25 and then readonly LINES, or go edit bashrc or whatever files it's sourcing that is doing that. This behaviour continues after install in the normal running os. telnet/ssh sessions are fine. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mind chiming in on bug 390837?
Wow, now they have taken some ridiculously unrelated other bug, and decided it' a duplicate of this one.
After all that rant, it turned out the duplicate tag was just a mistake, but one good thing, the attention has caused them to reopen the thing. There actually was duplicate bugs elsewhere which of course just lends more weight to the theory that maybe there is a bug even if one developer doesn't see it on his machine. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (1)
-
Brian K. White