On 11/8/2011 11:23 PM, Ken Schneider - openSUSE wrote:
On 11/08/2011 11:10 PM, Brian K. White pecked at the keyboard and wrote:
On 11/8/2011 3:33 AM, Andreas Jaeger wrote:
On Tuesday, November 08, 2011 01:38:23 Felix Miata wrote:
Not quite that bad, but way too many for an RC2.
Many KDE base packages apparently depend on bootsplash, many more
in previous KDE releases, which, along with splashy, I taboo on every install.
Grub failed to finish installing. I booted 11.4 and finished it myself with the Grub shell. Menu.lst had two copies of the default stanza, non-identical, besides a useless HD stanza and two failsafes.
Startx as root failed even after fixing permissions.local and doing 'SuSEconfig --module permissions'. How it failed I couldn't tell. It appeared the default X session was icewm, and it gave some wacko lack of space error, then shut down after I clicked OK, the only thing on the screen to click.
AllowRootLogin=true in kdmrc was apparently ignored (once it could be found squirreled away somewhere in the /usr rats nest instead of logically where config files belong in /etc), so getting into KDE via runlevel 5 was initially impossible, since I create no users on test systems, and even when not test systems I only create users after base installation is complete in order to assign user and group IDs appropriately to match all the other installed distros on the system.
Too many failed deps to remember, most probably based upon taboo of *kde*branding-openSUSE and *splash*.
So, you're doing something outside the normal way. Please fix it yourself. Fixes to packages are welcome but I doubt anybody will help debugging all this,
Typically unhelpful suse answer of the last few years.
Requiring those splash programs without some clear and sure way to ensure that they never try to touch the video hardware is broken.
The safe mode boot options are not the answer for this either. It's already too late to even select them by the time gfxboot has killed the console or worse.
It's like this: if you want to say that it's the users responsibility to fix opensuse bugs and develop opensuse enhancements, then why should
user use opensuse in the first place?
Brian,
You just do not get it! openSuSE is provided with a specified set of packages that need to be from the "official repos" _only_ AND package dependencies need to be adhered to. If the person installing the distro doesn't want to follow these simple guidelines then they are on their own. There is no magic here.
If anyone doesn't like the way the openSuSE is assembled they are free to create their own distribution.
I get all any user needs to get. If the distribution sucks, it sucks. You can't tell a user who pops the cd in, tries to use the system, and encounters all those problems, that it's their fault.
Those branding packages *break some systems*.
I also taboo them because I CAN NOT have grub loading gfxboot and I CAN NOT have the kernel trying to switch into graphical console modes, and I CAN NOT have any xdm-alike trying to start up at all. I can not have these things happen even the very first time so I can't let the installer install whatever and then go in and adjust config files to disable the problem actions. I will not be able to go in and do anything at all the instant any of those things happens the very first time. So I have to prevent them from even being installed in the first place during initial install, that way even if I miss one of the several manual things I have to do during text-only installs, and say, the menu.lst is left with the gfxboot line in it and uncommented, if it's not installed the line becomes harmless since the file isn't actually there and the console doesn't get killed and I can resume the install without having to boot the install media from the network to use it as a repair platform.
When I remove the gfxboot, splashy and bootsplash packages, the branding packages "require" them, so the branding packages end up going too.
It not our fault for needing to prevent these things, it's the distros fault for being so thoughtlessly assembled that we have to go through such contortions just to get installed.
Either that or suse should just stop all pretense of being a suitable OS for servers.
That would change everything and make your attitude correct. If they would say that, then, and only then, you would be able to say "Hey you're mis-using the system so of course it doesn't work. You can't do text-only installs or because this is only a gui system, and you can't do server optimized installs because this is a desktop system." and I'd have to agree.
I would complain but only once and only briefly and for a different reason, because then it would mean I have to toss out my time investment in crafting my opensuse based system and procedures and scripts and documentation for the rest of the company etc, and start working on probably an Arch one. Then I would go and do that and suse's unsuitability for servers would no longer be a problem for me and you would no longer have to hear reports of things that don't work and it would no longer annoy me that you don't care about anything you don't happen to do yourself.
Seriously sometimes it's like trying to order eggs without spam here. So what do you think we can do? Do you consider this a bug, or something more akin to a feature? This issue is more complex than I can easily comprehend, and it may take a thorough bug report or feature request to achieve what you need. Point is, lets start thinking about what we can do... not how a few
On Tuesday, November 08, 2011 09:36:10 PM Brian K. White wrote: than the people who apparently equal everybody are out to make life difficult. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org