openSUSE 11.3
in [Suse]
|
Prev: How to set up Viewsonic VA2012wb
Next: instructor's solutions manual for Cryptography and Network Security (4th Ed., William Stallings)
From: Paul J Gans on 16 Mar 2010 21:18 houghi <houghi(a)houghi.org.invalid> wrote: >David Bolt wrote: >>> But then the numbers are not really numbers. They are names. And the >>> names are pure marketing. So it could well be that SUSE starts a new >>> numbering when the years catch up with the versions. e.g. SUSE 14 is >>> released in 2014. >> >> I hope not. That would become more like Mandriva's, or possibly the >> xUbuntu's naming schemes. >Well, it is more logical to name them after months and years. openSUSE >10.06 is the next version coming out in june 2010. :-D Not only do you >have the year. You also have the month. Then they could change the name from openSuSE to ubun2! -- --- Paul J. Gans
From: Darrell Stec on 16 Mar 2010 21:37 houghi wrote: > Darrell Stec wrote: >> That would be nice. So many programs are broken in KDE4.3 like kpilot, >> pidgin, noteedit, Bibletime among them and which I use on a consistent >> basis. > > Are all those KDE programs? Not totally. > I have no idea, but it looks as if only > kpilot is a KDE program. So what is the problem with those programs? > I have to load the KDE3.5 version of kpilot because the newer versions that work under KDE4.3 have the conduits disabled. No data gets transferred to my old Palm Pilot m100. For the newer Bibletime versions when the application first starts up it skews the monitor for a few seconds. When dragging and dropping a verse from one language to another the program abruptly shuts down. In Pidgin I use to have keybindings in the .kde4/share/config/gtkrc-2.0 and gtkrc files so that Ctr-Enter sends and Enter adds a newline. In KDE4.3 those files are rewritten every time I either reboot or log in. The only way to fix that is to add the keybindings in the /etc/gtk-2.0/gtkrc file and mark it read-only. This breaks other programs. Those programs worked smoothly under openSUSE 10.3 and KDE3.5 > Now I must say I never had serious issues with any program. All ran fine > and most do what I want them to do. > > houghi Of course I have to remember what I did to make my old scanner and palm pilot work every time I upgrade to a new openSUSE version. -- Later, Darrell
From: David Bolt on 17 Mar 2010 05:49 On Wednesday 17 Mar 2010 09:05, while playing with a tin of spray paint, houghi painted this mural: > David Bolt wrote: >> True, but I'd still prefer to keep the naming scheme that's been in use >> for years. And it would end up causing an even bigger disconnect >> between SLES and openSUSE. > > Would that be such a bad thing? Not really, although I think it's nice that SLE still shows it's openSUSE roots. > It would make it even more clear that > there is a serious difference between openSUSE and SLE. I thought there was already a pretty clear difference between them, one very visible just from the software bundled with them. > Especcially one > is community driven and the other is company driven. Both of them are both company and community driven, purely because Novell is a part of the openSUSE community. It's true that the rest of the openSUSE community has no direct control over SLE, but it still has influence because of SLE using openSUSE as its roots. The only time I can see this changing will be where either they diverge enough that SLE can no longer use packages from openSUSE, or SLE moves to a completely different base. I don't see that happening, because it would mean the development of SLE couldn't benefit from the rest of the openSUSE community. Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 11.0 32b | | | openSUSE 11.3M3 32b openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b | TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11
From: David Bolt on 17 Mar 2010 09:41 On Wednesday 17 Mar 2010 12:20, while playing with a tin of spray paint, houghi painted this mural: > David Bolt wrote: >>> Would that be such a bad thing? >> >> Not really, although I think it's nice that SLE still shows it's >> openSUSE roots. > > I think the link is stil a bit to strong, I don't. It think it's quite okay as it stands. > although Novell has less > people in the board of however they are called then the 'normal' > community members. The openSUSE board? I think they have two out of the five seats, and a Novell employee is chairman. Other than that, I'm not actually sure who are members of the board, Pascal Bleser being the only one that I do know about. > A few years ago it was not even ruled out that > openSUSE would be completely seperated from SUSE and Novell. I don't think that has changed. I think it's still possible, just not very likely at the present time. > The tools are in place to do that if there is ever a reason or request > for it. No need to request it. As you said, the tools are in place for a person, or group of people, to fork openSUSE and create their own distro. And, since it's possible to interface with kiwi, it's possible to build both live CDs and installation media. >> I thought there was already a pretty clear difference between them, one >> very visible just from the software bundled with them. > > For people involved a bit in it, there is. For others the difference is > much more obscure. For those interested in SLE or openSUSE, they're likely to look at both of them to be able to decide which one is better for their situation. And if they aren't the ones making that decision, it doesn't really matter what software is bundled. >> The only time I can see this changing will be where either they >> diverge enough that SLE can no longer use packages from openSUSE, or >> SLE moves to a completely different base. I don't see that happening, >> because it would mean the development of SLE couldn't benefit from the >> rest of the openSUSE community. > > I could see it happening although at this moment it is not needed. > There could be a variation of reasons. All of them on a political > technical level. The chances of that happening are pretty small, but IF > it would happen, it is possible and Novell has done a lot of work to > make it possible. Yes they have, and that work is one of the reasons I don't think it will happen. There's too much work been put into it for them not to want to keep them fairly close. Plus, by having them close, it means that there's much more chance that someone, who has some influence with the IT departments, and who is used to openSUSE, would look at SLE and possibly suggest migrating users to it if a company decides to deploy Linux based desktop systems. > Opensourcing the build service is a very major step in > that process. Yes it was. Now if only I could get it to install and work properly on my machines... Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 11.0 32b | | | openSUSE 11.3M3 32b openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b | TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11
From: Chris Cox on 17 Mar 2010 13:09
On Tue, 2010-03-16 at 10:43 -0700, John Bowling wrote: > > I want what ever is next (12.0 or 11.3?) but with kde 3.5+ (upgraded but not > to 4.anything). > As nice as that sounds.... pretty much all app developers not to mention the KDE team has abandoned all support, updates, etc for KDE 3.5. Which means even if you DID manage to get KDE 3.5, not only would that be unsupported, but pretty much all of your KDE apps as well. Not recommended. KDE 3.5 is dead. Is KDE 4 ready? Well.... it's evolving. Takes a bit of getting used to. It's different. IMHO, it's best to look at KDE 3.5 as a FOSS project that died and KDE 4 is what many of the former KDE 3.5 users are switching to. Of course, many switched to Gnome... and sadly in the case of openSUSE in particular, many went running to Ubuntu (some ran and came back though). |