openSUSE Status Meeting 2006-02-07 minutes
Hello, After being revised by 3 people (thx henne, benji), here are the minutes of the last irc meeting. Enjoy Marcio Ferreira --- aka_druid openSUSE Status Meeting 2006-02-08 minutes *** BEGIN MEETING *** Talk in #opensuse about the latest development topics and issues in the openSUSE project Initial topics: 1. mirrors - bill-barriere 2. frontpage redesign - Pflodo 3. forum discussion results - Henne 4. subfs discussion results - houghi 5. LinuxTag - Christian Boltz 6. Foreign language mailing lists - skh 7. SDB - howtos, migration, what is an SDB article - (not)localhorst 8. CDB/HCL - hardware database efforts - the_dude > didnt happen 9. SUSE Linux 10.1 Status / Roadmap - AJ o mirrors situation ~~~~~~~~~~~~~~~~~ - Several people expressed concerns about the current mirror model with separated repositories with the OSS/main repository at opensuse.org and the extra repository at suse.com. Adrian Schroeter stated that they could not be merged as the open source project must be strictly separated from the commercial services. - Mirrors outside of Europe are not in as good shape as the European/German mirrors (bottle necks, corruption, de-synced), specially the ones with installation sources (many mirrors have ISOs, few have installation-sources), which affects many people trying to perform network installations. Action Item henne: - Discuss this in opensuse@opensuse.org - Involve ftpadmin@suse in the discussion - The factory repository doesn't have enough mirrors - Mathieu Chouinard(chouimat) suggested drpmsync should be able to let the client decide what to sync or not - Opensuse is looking for more mirrors, so if anyone knows of one interested in running it, step forward - drpmsync needs better documentation and marketing so people will be more inclined to use it, at present there is not much interest. Action Item schiele: - discuss how we can make the drpmsync service better - help in the documentation process, extending http://en.opensuse.org/How_to_setup_a_drpmsync_server - It was suggested to put the torrent files of the downloads for the next release in the openSUSE wiki Action Item notlocalhorst: - upload final 10.1 torrents to the wiki o Foreign language mailing lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - It was requested that any foreign language wiki gets its associated mailing list in that language. - There was a discussion about whether or not it is a good thing to have lots of new localized mailing lists, but no conclusion was reached. Some suggested creating the lists to see how they go, so henne took the job. - Also a discussion about the format the lists should have Action Item henne: - put mailinglists into the next meetings agenda - setup opensuse-it mailinglist after naming convention is decided - come up with a proposal for mailing list layout in the future (helping skh) Action Item darix: - ask the Italian guys if it hurts them badly to wait a week or two (delay due to the name problem) Action Item skh: - come up with a proposal on mailing list layout in the future (henne will help) o opensuse.org frontpage lift-up/redesign ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Some people felt that the front page of opensuse.org is poorly designed, although some are happy with the way it is now. - People need to decide what is wrong and then what needs to be changed, and how it should be changed. There are 2 different issues: the layout/design and the way information is grouped/distributed in the front page and in the wiki. This needs to be discussed in the wiki mail list. Action Item michl: - discuss front page redesign on opensuse-wiki o Forum Discussions Result ~~~~~~~~~~~~~~~~~~~~~~~~ - Sonja Krause-Harder(skh) explained that some wish to have a forum at forum.opensuse.org. She also suggested the proposal that we now prepare to setup a forum, trying to involve the existing forum owners, but that would take some time to be done. - Viras (from an unofficial suse forum) expressed an opinion that an official forum is not needed. He questioned whether it would be a helpful step in the project. He thinks the forum would grow well but would not get the existing forum members involved. Action Item Viras: - take the discussion to the forum people in suselinuxsupport.de forum Action item skh: - talk to suse internal people to see about resources, etc if the forum idea goes ok Action Item StormX: - invite the other forum maintainers to the suselinuxsupport.de opensuse-forum category o subfs discussion ~~~~~~~~~~~~~~~~ - Several people expressed concern that the automounting feature would only be available for GNOME and KDE - SUSE people explained that subfs is gone for good, and keeping it is not up for discussion. Also that at present there is not a clear solution for that problem for non-KDE and non-GNOME users. - It was suggested that other users could run gnome-volume-manager even if they are using other environments, but this is not an ideal situation because it would use additional resources and some people simply don't have any parts of gnome installed installed. - Suggested alternatives: supermount, autofs, create a console daemon that will do the job of gnome-volume-manager. The problems are that autofs is poor documented, supermount status is unknown, and the console daemon would need to be implemented, it simply doesn't exist now. Action Item henne: - write SDB article about alternatives of subfs - discuss the alternatives in opensuse-factory@opensuse.org o Linux TAG ~~~~~~~~~ - openSUSE requested a community booth at the LinuxTag (http://www.linuxtag.org/2006/), SUSE people confirmed, but it needs to be discussed how opensuse will be represented there. - It was said that there will be no commerical Novell booth, which disappointed several users. No action items :( o SDB migration to wiki ~~~~~~~~~~~~~~~~~~~~~ - Migration of SDB is complete - Discussing is ongoing about how to migrate the how-to's, especially regarding style-guides on how to do a how-to (whats a how-to, whats a sdb article, etc). According to localhorst: howtos are more complex things than SDB articles. - Old SDB in {portal,sdb}.suse.com will be replaced by redirects to the opensuse wiki Action Item notlocalhorst: - write HOWTO style-guide - communicate that we want to keep SDB clean of HOWTO like writings o SUSE Linux 10.1 Status / Roadmap - AJ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - AJaeger brought us the latest major changes * Kernel Changes km_ packages / non-GPL kernel modules - The km_* packages are being replaced by the KMP, so packages can be built more easily independently from the kernel package build. Some information about kmp packages can be found in http://www.suse.de/~agruen/KMPM/ - Most developers of the kernel community consider non-GPL kernel modules to be infringing on their licensing/copyright. Novell does respect this position and refrains from distributing non-GPL kernel modules for future products. Novell works with vendors to supply alternative ways to provide the functionality that was previously only available with non-GPL kernel modules. So, the kernel-*nongpl package has been dropped and will not be provided anymore. Action Item notlocalhorst: - write documentation about the end user part of the KMP switch Action Item garloff: - provide notlocalhorst with details * Major bug in Beta3: Fontconfig - This bug in fontconfig can cause your X apps to crash. So that means the beta testers should take careful look at those bugs and report when something interesting is found. Action Item ajaeger: - announce fontconfig changes on factory - announce fontconfig location on factory * Package manager major changes - Lots of changes in this area, headed by the inclusion of new libzypp (cool name). This will cause a delay in beta4, the inclusion of a new beta5 test cycle, and reduced functionality of the package manager in beta4, so that the integration goes smoothly. - New Zen tools to make updates will be included, replacing SUSEplugger. The zmd daemon will handle yum and ZENworks installation sources, which means a complete switch to YUM. YaST sources may not be supported anymore (but 10.0 sources have YUM metadata so dont panic). Hopefully there is still lots of development in this area, which means that yast sources might be supported and the (awful) current Zen updater interface can be replaced by a more sane design, as its very raw in the current betas. Also there will be a web user interface for the updater. - Frontend wise the YaST software manager will be the same, as the change is in the back-end of the package manager as stated by AJaeger. Action Item AJ: - Document the change to libzypp so its more understandable. *** END OF MEETING ***
On Wed, 8 Feb 2006, Druid wrote:
o mirrors situation ~~~~~~~~~~~~~~~~~
- Several people expressed concerns about the current mirror model with separated repositories with the OSS/main repository at opensuse.org and the extra repository at suse.com. Adrian Schroeter stated that they could not be merged as the open source project must be strictly separated from the commercial services.
- Mirrors outside of Europe are not in as good shape as the European/German mirrors (bottle necks, corruption, de-synced), specially the ones with installation sources (many mirrors have ISOs, few have installation-sources), which affects many people trying to perform network installations.
Action Item henne: - Discuss this in opensuse@opensuse.org - Involve ftpadmin@suse in the discussion
- The factory repository doesn't have enough mirrors - Mathieu Chouinard(chouimat) suggested drpmsync should be able to let the client decide what to sync or not - Opensuse is looking for more mirrors, so if anyone knows of one interested in running it, step forward - drpmsync needs better documentation and marketing so people will be more inclined to use it, at present there is not much interest.
I did not intend to intifeer or distract from this item with the my email
on US mirrors. I had not seen the discussion/log or this item when I
posted. My intent was to let people on OpenSUSE know that this is a major
problem and does not look good to people/business that I am in contact
with. Trying to advance the openSUSE cause.
--
Boyd Gerber
Hi, On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
On Wed, 8 Feb 2006, Druid wrote:
o mirrors situation ~~~~~~~~~~~~~~~~~ [...] - Mirrors outside of Europe are not in as good shape as the European/German mirrors (bottle necks, corruption, de-synced), specially the ones with installation sources (many mirrors have ISOs, few have installation-sources), which affects many people trying to perform network installations. [...]
I did not intend to intifeer or distract from this item with the my email on US mirrors. I had not seen the discussion/log or this item when I posted. My intent was to let people on OpenSUSE know that this is a major problem and does not look good to people/business that I am in contact with. Trying to advance the openSUSE cause.
You should not feel bound to your "homeland" mirrors. The glass fibre light does not run slower under water. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Wed, 8 Feb 2006, Eberhard Moenkeberg wrote:
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
o mirrors situation [...] - Mirrors outside of Europe are not in as good shape as the European/German mirrors (bottle necks, corruption, de-synced), specially the ones with installation sources (many mirrors have ISOs, few have installation-sources), which affects many people trying to perform network installations. [...] I did not intend to intifeer or distract from this item with the my email on US mirrors. I had not seen the discussion/log or this item when I
On Wed, 8 Feb 2006, Druid wrote: posted. My intent was to let people on OpenSUSE know that this is a major problem and does not look good to people/business that I am in contact with. Trying to advance the openSUSE cause. You should not feel bound to your "homeland" mirrors. The glass fibre light does not run slower under water.
I agree but having 2-3 sites world wide that are good is not a good thing.
The load should be shared by others. Your site is the best, I just fear
it is overload sometimes. The load should be shared. We need a better
network for the OSS version. Using the ones that work sometimes gives
time outs or unavailability. I have to often use the IP address and not
download.opensuse.org... As the ones received do not have everything that
is needed.
--
Boyd Gerber
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
The load should be shared by others. Your site is the best, I just fear it is overload sometimes. The load should be shared. We need a better network for the OSS version. Using the ones that work sometimes gives time outs or unavailability. I have to often use the IP address and not download.opensuse.org... As the ones received do not have everything that is needed.
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available... The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right? Regards Christoph
On Wed, 8 Feb 2006, Christoph Thiel wrote:
The load should be shared by others. Your site is the best, I just fear it is overload sometimes. The load should be shared. We need a better network for the OSS version. Using the ones that work sometimes gives time outs or unavailability. I have to often use the IP address and not download.opensuse.org... As the ones received do not have everything that is needed. We should probably delay the redirection on download.openSUSE.org and have
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote: the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available...
Yes, sometimes the server only has some or a subset of what is needed for doing a YaST inst. I was trying to do an internet installation using a user.sel file as a starting point. I had over 20 packages that could not be installed because the were not on the server I was directed to. I have noticed on some upgrades that the files are unavailable as well.
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
Yes!
--
Boyd Gerber
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available...
Yes, sometimes the server only has some or a subset of what is needed for doing a YaST inst. I was trying to do an internet installation using a user.sel file as a starting point. I had over 20 packages that could not be installed because the were not on the server I was directed to. I have noticed on some upgrades that the files are unavailable as well.
So you didn't use download.openSUSE.org as your installation source, but used download.openSUSE.org to find a mirror and than c&p'ed it to be the installation source. Right? [If you had used download.openSUSE.org all the way, it should have choosen different mirrors for different files, because it has a local cache where it stores all the information about the status of all files on all servers.] To the server admins: If you feel you don't get enough or too much traffic, please contact me (of list), so I can do some fine tuning. ATM all request directed at download.openSUSE.org are distributed equally amongst our "primary" mirrors. If there is interest in this topic, I might prepare some slides to give a "speed talk" on this at FOSDEM.
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
Yes!
Alright, I'll put this onto my agenda... Regards Christoph
On Thu, 9 Feb 2006, Christoph Thiel wrote:
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into ... Yes, sometimes the server only has some or a subset of what is needed for doing a YaST inst. I was trying to do an internet installation using a user.sel file as a starting point. I had over 20 packages that could not be installed because the were not on the server I was directed to. I have noticed on some upgrades that the files are unavailable as well.
So you didn't use download.openSUSE.org as your installation source, but used download.openSUSE.org to find a mirror and than c&p'ed it to be the installation source. Right? [If you had used download.openSUSE.org all the way, it should have choosen different mirrors for different files, because it has a local cache where it stores all the information about the status of all files on all servers.]
Every time I have tried to use it all the way I have problems. It fails in many ways. I can not start the installation and leave. So I switched to finding a mirror and using it. At least that is managable to leave and have the person call once the error occurs. It is to hard to assist someone over the phone using it as you suggest. If I were to stay for the 6-12 hours of the installation it would not be a problem. But I have to earn money too.
If there is interest in this topic, I might prepare some slides to give a "speed talk" on this at FOSDEM.
I would love to hear it but, I am in the US and do not have a sponsor to attend.
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
Yes!
Alright, I'll put this onto my agenda...
Thanks, I have been a SUSE user/supporter since the first public release
of SUSE(SuSE and all it's incantations, SLES)
--
Boyd Gerber
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
Every time I have tried to use it all the way I have problems. It fails in many ways. I can not start the installation and leave. So I switched to finding a mirror and using it. At least that is managable to leave and have the person call once the error occurs. It is to hard to assist someone over the phone using it as you suggest. If I were to stay for the 6-12 hours of the installation it would not be a problem. But I have to earn money too.
Have you been using it lately, because it has been updated a few weeks ago...? Please file a bugreport in case of problems with download.openSUSE.org and assign it to me! Regards Christoph
On Thu, Feb 09, 2006 at 12:27:43AM +0100, Christoph Thiel wrote:
If there is interest in this topic, I might prepare some slides to give a "speed talk" on this at FOSDEM.
I have been thinking of an xml file that could include all installation sources. Think http://easyurpmi.zarb.org/, but with GeoIP included. Unfortunatly my knowledge of XML (and using it) is very limited. I would very much talk to people about this on FOSDEM and see what can do what and how. If I would have had more knowledge, I would have had a working example. I understand that the file (or at least not all of it) might not be allowed on openSUSE or Novell. It could be hosted somewhere else. Yet that could be decided at FOSDEM (and after the standard for the XML is fixed) An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real. Advatages of xml indes of array's is that it can be used in many more applications then just some website. I can imagine a program where you just point an application to e.g. http://opensuse/files/sources.xml and get the correct mirrors for you. houghi -- Ingrate, n.: A man who bites the hand that feeds him, and then complains of indigestion.
On 02/09/2006 01:53 AM houghi wrote:
An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real.
I like the idea, and it seems to work. You could add a selection for the actual release (10.0, 10.1,...). OJ -- "The United States of America is the only empire in history to have gone from Barbarism directly to Decadence, without any intervening period of Civilisation." (Oscar Wilde)
On Thu, Feb 09, 2006 at 09:49:51AM +0100, Johannes Kastl wrote:
On 02/09/2006 01:53 AM houghi wrote:
An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real.
I like the idea, and it seems to work.
You could add a selection for the actual release (10.0, 10.1,...).
I know, however I would like to do it in xml see what the best solution is for now and in the future. If possible automated in some way. So for now you will have to wait or come up with a solution. ;-) houghi -- In seeking the unattainable, simplicity only gets in the way. -- Epigrams in Programming, ACM SIGPLAN Sept. 1982
Johannes Kastl wrote:
On 02/09/2006 01:53 AM houghi wrote:
An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real.
I like the idea, and it seems to work.
You could add a selection for the actual release (10.0, 10.1,...).
OJ seems very nice.
don't we have a similar thing with YOU? jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On Thu, Feb 09, 2006 at 01:26:29PM +0100, jdd wrote:
Johannes Kastl wrote:
On 02/09/2006 01:53 AM houghi wrote:
An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real.
I like the idea, and it seems to work.
You could add a selection for the actual release (10.0, 10.1,...).
OJ seems very nice.
don't we have a similar thing with YOU?
Are the URL's that you see in YOU hardcoded, or are they downloaded from a file? Where is the data kept? houghi -- Ehrman's Commentary: (1) Things will get worse before they get better. (2) Who said things would get better?
On Thu, 9 Feb 2006, houghi wrote:
On Thu, Feb 09, 2006 at 01:26:29PM +0100, jdd wrote:
Johannes Kastl wrote:
On 02/09/2006 01:53 AM houghi wrote:
An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real.
I like the idea, and it seems to work.
You could add a selection for the actual release (10.0, 10.1,...).
OJ seems very nice.
don't we have a similar thing with YOU?
Are the URL's that you see in YOU hardcoded, or are they downloaded from a file? Where is the data kept?
They are downloaded on demand. But things will change dramatically with the new package manager ;) Regards Christoph
On Thu, Feb 09, 2006 at 01:47:04PM +0100, Christoph Thiel wrote:
They are downloaded on demand. But things will change dramatically with the new package manager ;)
OK. Will the new package manager have the ability to read from an xml file? No reason to invent things twice. Also no reason to work on an xml file if you suddenly say: We have that already coverd. The file WE use will look like XYZ. Any information regarding this would be welcome. houghi -- It will be advantageous to cross the great stream ... the Dragon is on the wing in the Sky ... the Great Man rouses himself to his Work.
On Thu, 9 Feb 2006, houghi wrote:
On Thu, Feb 09, 2006 at 01:47:04PM +0100, Christoph Thiel wrote:
They are downloaded on demand. But things will change dramatically with the new package manager ;)
OK. Will the new package manager have the ability to read from an xml file? No reason to invent things twice. Also no reason to work on an xml file if you suddenly say: We have that already coverd. The file WE use will look like XYZ.
Any information regarding this would be welcome.
Unfortunately I don't have any information on that right now -- so my suggestion would be to postpone this to FOSDEM, to create a solution ;) Maybe we will need to request / implement some enhancements for the package manager / online updater, but that should be none of a problem. Regards Christoph
On Thu, 9 Feb 2006, houghi wrote:
On Thu, Feb 09, 2006 at 12:27:43AM +0100, Christoph Thiel wrote:
If there is interest in this topic, I might prepare some slides to give a "speed talk" on this at FOSDEM.
I have been thinking of an xml file that could include all installation sources. Think http://easyurpmi.zarb.org/, but with GeoIP included.
Unfortunatly my knowledge of XML (and using it) is very limited. I would very much talk to people about this on FOSDEM and see what can do what and how. If I would have had more knowledge, I would have had a working example.
I understand that the file (or at least not all of it) might not be allowed on openSUSE or Novell. It could be hosted somewhere else. Yet that could be decided at FOSDEM (and after the standard for the XML is fixed)
An extremely basic idea of this is put on http://houghi.org/mirrors/main.php. This does not use XML and many mirrors are not up to date, so don't use it as anything real.
Advatages of xml indes of array's is that it can be used in many more applications then just some website. I can imagine a program where you just point an application to e.g. http://opensuse/files/sources.xml and get the correct mirrors for you.
Let's continue this discussion at FOSDEM! One option would be to put all those pieces together into download.openSUSE.org (which already has some infrastructure in place that we could leverage, e.g. GeoIP). Regards Christoph
On Thu, Feb 09, 2006 at 01:50:20PM +0100, Christoph Thiel wrote:
Let's continue this discussion at FOSDEM! One option would be to put all those pieces together into download.openSUSE.org (which already has some infrastructure in place that we could leverage, e.g. GeoIP).
OK. Will there be a specific time/place at FOSDEM? I have never been to such an event, so I do not know what to expect. I asume that it is not like a mailinglist where I just can start shouting what I have to say. :-) houghi -- Rules: (1) The boss is always right. (2) When the boss is wrong, refer to rule 1.
On Thu, 9 Feb 2006, houghi wrote:
On Thu, Feb 09, 2006 at 01:50:20PM +0100, Christoph Thiel wrote:
Let's continue this discussion at FOSDEM! One option would be to put all those pieces together into download.openSUSE.org (which already has some infrastructure in place that we could leverage, e.g. GeoIP).
OK. Will there be a specific time/place at FOSDEM? I have never been to such an event, so I do not know what to expect. I asume that it is not like a mailinglist where I just can start shouting what I have to say. :-)
We have a special slot in our DevRoom on Sunday (12:00 - 12:30), called "Speed Talks". Let's just try to present the topic in a 5-10 minute talk and then find a place to dicuss it with those who are interested. Regards Christoph
Hi, On Wed, 8 Feb 2006, Christoph Thiel wrote:
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available...
A very good idea. A failing redirected single-file request could get overcome with the "retry" button then if d.o.o does a round-robin redirection.
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
It seems so. So the "real" d.o.o server needs to have (and deliver) only the most recent metadata, but not deliver all files himself. The next feature request would be: make a "default=retry" configuration button in YaST2, to let us go to sleep after the first press and wakeup with a finished installation. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Thu, 9 Feb 2006, Eberhard Moenkeberg wrote:
On Wed, 8 Feb 2006, Christoph Thiel wrote:
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available...
A very good idea. A failing redirected single-file request could get overcome with the "retry" button then if d.o.o does a round-robin redirection.
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
It seems so. So the "real" d.o.o server needs to have (and deliver) only the most recent metadata, but not deliver all files himself.
The next feature request would be: make a "default=retry" configuration button in YaST2, to let us go to sleep after the first press and wakeup with a finished installation.
Yes, I would love that option. I once had to do the retry 20 times to get
the one file. It took 24 hours to get everything. I fell a sleep a
couple of times and had to hit retry till the file/s came across. Hard to
stay awake after being up for 36-48 hours.
--
Boyd Gerber
On Thu, 9 Feb 2006, Eberhard Moenkeberg wrote:
We should probably delay the redirection on download.openSUSE.org and have the user browse the local ftp tree and only redirect on file request, to make sure he can take all files that are available into account. ATM d.o.o redirects as early as possible, i.e. if you access http://d.o.o/somepath it will redirect you to a server that has the path. But that server might not have all the files that are actually available...
A very good idea. A failing redirected single-file request could get overcome with the "retry" button then if d.o.o does a round-robin redirection.
d.o.o doesn't do failing redirects -- if it does, please contact me ;)
The inital usecase for d.o.o (when I did the first implementation) was to have a generic URL for the announcements and to point the installer (YaST) to. But it actually seems people try to browse the inst-sources with it -- and end up on mirrors that are not completely in sync -- right?
It seems so. So the "real" d.o.o server needs to have (and deliver) only the most recent metadata, but not deliver all files himself.
The next feature request would be: make a "default=retry" configuration button in YaST2, to let us go to sleep after the first press and wakeup with a finished installation.
IMHO this isn't needed... Regards Christoph
Hi, On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
On Wed, 8 Feb 2006, Eberhard Moenkeberg wrote:
On Wed, 8 Feb 2006, Boyd Lynn Gerber wrote:
On Wed, 8 Feb 2006, Druid wrote:
o mirrors situation [...] - Mirrors outside of Europe are not in as good shape as the European/German mirrors (bottle necks, corruption, de-synced), specially the ones with installation sources (many mirrors have ISOs, few have installation-sources), which affects many people trying to perform network installations. [...] I did not intend to intifeer or distract from this item with the my email on US mirrors. I had not seen the discussion/log or this item when I posted. My intent was to let people on OpenSUSE know that this is a major problem and does not look good to people/business that I am in contact with. Trying to advance the openSUSE cause. You should not feel bound to your "homeland" mirrors. The glass fibre light does not run slower under water.
I agree but having 2-3 sites world wide that are good is not a good thing. The load should be shared by others. Your site is the best, I just fear it is overload sometimes. The load should be shared. We need a better network for the OSS version. Using the ones that work sometimes gives time outs or unavailability. I have to often use the IP address and not download.opensuse.org... As the ones received do not have everything that is needed.
My bottleneck is not the network, but the disk I/O. Due to the huge increase in size with opensuse, the 12 GB RAM is not enough buffercache anymore (was before, network output was up to 6 times the disk I/O), and always 1000 to 2000 users are in direct concurrence at the raid controller and the disk heads now. So usually I can't even use half of the 600 MBit bandwidth i got granted. The solution is very simple in terms of concept: just increase the buffercache to 32 GB - that would need a new machine with 16 RAM slots plus the RAM. But not in terms of money: machine + RAM is > 13.000 Euro. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Wed, Feb 08, 2006 at 06:57:49PM -0200, Druid wrote:
o Forum Discussions Result ~~~~~~~~~~~~~~~~~~~~~~~~ - Sonja Krause-Harder(skh) explained that some wish to have a forum at forum.opensuse.org. She also suggested the proposal that we now prepare to setup a forum, trying to involve the existing forum owners, but that would take some time to be done. - Viras (from an unofficial suse forum) expressed an opinion that an official forum is not needed. He questioned whether it would be a helpful step in the project. He thinks the forum would grow well but would not get the existing forum members involved.
Action Item Viras: - take the discussion to the forum people in suselinuxsupport.de forum
Action item skh: - talk to suse internal people to see about resources, etc if the forum idea goes ok
Action Item StormX: - invite the other forum maintainers to the suselinuxsupport.de opensuse-forum category
I think it is a pity that nothing from the discussion that was held here went into the conclusion or discussion. I realy was under the impression that we would just start with the forus, because the other forum members (exept for Viras) were absolutely not interested in wether we would do it or not. Instead of making a dicision yes or no, it was decided not to decide. :-( Personaly I feel as if all the arguments used in the discussion were trown out and we started from zero. In the transcript you see two times +1. My -1 is send is unfortunatly not shown. So my real question is: what good was the discussion here if nobody looked at it closer and what entails that for future discussions that will be held here? houghi -- Personifiers Unite! You have nothing to lose but Mr. Dignity!
Hi, On Thursday, February 09, 2006 at 02:42:45, houghi wrote:
On Wed, Feb 08, 2006 at 06:57:49PM -0200, Druid wrote:
o Forum Discussions Result ~~~~~~~~~~~~~~~~~~~~~~~~
I think it is a pity that nothing from the discussion that was held here went into the conclusion or discussion. I realy was under the impression that we would just start with the forus, because the other forum members (exept for Viras) were absolutely not interested in wether we would do it or not.
Youre under a wrong impression then :) We did not reach the forum community with our discussion here. Especially not the people that put their blood, sweat and tears into the forums. This is, as one one of the forum maintainers (Viras) stated, because we simply used the wrong communication method (this mailinglis instead of a forum).
So my real question is: what good was the discussion here
It was very helpfull and detailed input on this matter. It was mostly constructive and gave a real good impression on what the openSUSE mailinglist community thinks. But (and thats a BIG HUGE but) it cant be that this is the only input on this matter.
if nobody looked at it closer
Again a wrong impression. Everybody that participates here looked at it. Including you and novell staff that needs to take action if we want our own forum.
and what entails that for future discussions that will be held here?
Nothing except that it showed us that we here on the mailinglist are only a small fraction of the overall community and we cant decide on matters that includes other fractions on our own. Henne -- Henne Vogelsang, Core Services "Rules change. The Game remains the same." - Omar (The Wire)
Druid wrote:
o Foreign language mailing lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I really don't understand the problem here (after reading all the irc logs) we need at least one foreign language mailing list for the very same reason we needed a foreign langage wiki: an enormous count of users don't even read other language than they own :-! and we need them as soon as possible. time ago SUSE was one of the main french distribution. Comercial problems with the french distributors made suse nearly desapear from France. I hope this will change, but not if we are so conservatives :-( jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdd wrote:
Druid wrote:
o Foreign language mailing lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I really don't understand the problem here (after reading all the irc logs) we need at least one foreign language mailing list for the very same reason we needed a foreign langage wiki: an enormous count of users don't even read other language than they own :-! and we need them as soon as possible. time ago SUSE was one of the main french distribution. Comercial problems with the french distributors made suse nearly desapear from France. I hope this will change, but not if we are so conservatives :-(
Jean-Daniel, if you carefully look at the log, I pretty much pointed out exactly the same, and so
did Sonja ;)
Furthermore, we agreed to create "language" lists for de, fr, it - IIRC Sonja took that action item.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On 02/09/2006 09:17 AM Pascal Bleser wrote:
Jean-Daniel, if you carefully look at the log, I pretty much pointed out exactly the same, and so did Sonja ;)
Furthermore, we agreed to create "language" lists for de, fr, it - IIRC Sonja took that action item.
Nice to hear that. OJ -- The end of the world is best viewed with Microsoft Universe Exploder v6.66. (Unbekannt)
Pascal Bleser wrote:
Jean-Daniel, if you carefully look at the log, I pretty much pointed out exactly the same, and so did Sonja ;)
Hopefully I'm noty the only guy with this opinion :-)
Furthermore, we agreed to create "language" lists for de, fr, it - IIRC Sonja took that action item.
I didn't find this so evident in the logs. Really this logs looks a little too much (on my beleife) like the forum thread... quite generally, I think this should be exactly like I try to be with my childs. all what is asked for and is * not dangerous * not too many work for me I say yes. :-) if you don't, they do not ask anymore and they do behind your back. jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On 2/9/06, jdd
Druid wrote:
o Foreign language mailing lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I really don't understand the problem here (after reading all the irc logs)
I agree, why even talk about procedures and making requests in bugzilla, how will you tell the people about the procedure? In English? If we give them a wiki, give them a mailing list. Encourage Wiki maintainer (unless other nominated person), to be a conduit between english list and their own. eg Translate important announcements, bring important discussions from their language to the english one etc. Peter 'Pflodo' Flodin
On 2006-02-09 22:28:15 +1100, Peter Flodin wrote:
On 2/9/06, jdd
wrote: Druid wrote:
o Foreign language mailing lists ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I really don't understand the problem here (after reading all the irc logs)
I agree, why even talk about procedures and making requests in bugzilla, how will you tell the people about the procedure? In English?
If we give them a wiki, give them a mailing list.
why? maybe the will happily use "talk" pages in the wiki to coordinate everything. than they wont need a mailinglist. Doing something just because you can do something isnt always the best solution.
Encourage Wiki maintainer (unless other nominated person), to be a conduit between english list and their own. eg Translate important announcements, bring important discussions from their language to the english one etc.
depending on the activities on the wiki, they might busy enough with just the wiki translations. and coordination for this is done by opensuse-wiki. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
On 2/9/06, Marcus Rueckert
On 2006-02-09 22:28:15 +1100, Peter Flodin wrote:
If we give them a wiki, give them a mailing list.
why? maybe the will happily use "talk" pages in the wiki to coordinate everything. than they wont need a mailinglist.
The mailing list is for the users, not the wiki maintainers. My whole point is that if a language is worth a wiki, it is worth a mailing list. If it is not worth a mailing list , I will use your saying right back at you for creating the wiki :-)
Doing something just because you can do something isnt always the best solution.
Peter 'Pflodo' Flodin.
On 2006-02-09 22:53:50 +1100, Peter Flodin wrote:
The mailing list is for the users, not the wiki maintainers. My whole point is that if a language is worth a wiki, it is worth a mailing list.
If it is not worth a mailing list , I will use your saying right back at you for creating the wiki :-)
that is not true. if it is worth a wiki than someone volunteered for the maintainership. does this imply he volunteers for mailinglist maintainership aswell? No. looking at the many small wikis at wikipedia, i dont think we need to combine both. if the wiki is active enough and we see more than 2-3 people requesting the ml. than i am fine with setting one up. just my 2 cents darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
On 2/9/06, Marcus Rueckert
On 2006-02-09 22:53:50 +1100, Peter Flodin wrote: i dont think we need to combine both. if the wiki is active enough and we see more than 2-3 people requesting the ml. than i am fine with setting one up.
Good. No more discussion required. Wiki maintainers who also want to look after the mailing list just ask. If nobody asks well then no mailing list. In the end I think the outcome will be the same, all languages with active wikis will have mailing lists, how and when they end up there doesn't really matter. Peter 'Pflodo' Flodin.
Peter Flodin wrote:
On 2/9/06, Marcus Rueckert
wrote: On 2006-02-09 22:53:50 +1100, Peter Flodin wrote: i dont think we need to combine both. if the wiki is active enough and we see more than 2-3 people requesting the ml. than i am fine with setting one up.
Good. No more discussion required. Wiki maintainers who also want to look after the mailing list just ask. If nobody asks well then no mailing list. In the end I think the outcome will be the same, all languages with active wikis will have mailing lists, how and when they end up there doesn't really matter.
absolutly. how can a non english speaker ask for a mailing list? where? of course, if there is a fr mailing list I will be on that one also. anyway the mailing list do not need any work or near. and if nobody use it, who cares? jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On 2006-02-09 13:42:44 +0100, jdd wrote:
Peter Flodin wrote:
On 2/9/06, Marcus Rueckert
wrote: On 2006-02-09 22:53:50 +1100, Peter Flodin wrote: i dont think we need to combine both. if the wiki is active enough and we see more than 2-3 people requesting the ml. than i am fine with setting one up.
Good. No more discussion required. Wiki maintainers who also want to look after the mailing list just ask. If nobody asks well then no mailing list. In the end I think the outcome will be the same, all languages with active wikis will have mailing lists, how and when they end up there doesn't really matter.
absolutly. how can a non english speaker ask for a mailing list? where?
of course, if there is a fr mailing list I will be on that one also. anyway the mailing list do not need any work or near.
and if nobody use it, who cares?
just a few points: 1. there should be at least one guy in the french community with basic english skills to ask for a mailinglist. you can happily replace french with ever other language out there. why? because every wiki needs at least one person that migrates the changes from the english wiki into their local wiki. btw ... they have to ask for a wiki aswell and the best language for this is english aswell. 2. that might be true for you ... but maybe not for everyone. so what is wrong with explicitly asking for a mailinglist? what is wrong with tie the decision to the activity of the community? with kind regards darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
On Thursday 09 February 2006 08:07, Marcus Rueckert wrote:
On 2006-02-09 13:42:44 +0100, jdd wrote:
Peter Flodin wrote:
On 2/9/06, Marcus Rueckert
wrote: On 2006-02-09 22:53:50 +1100, Peter Flodin wrote: i dont think we need to combine both. if the wiki is active enough and we see more than 2-3 people requesting the ml. than i am fine with setting one up.
Good. No more discussion required. Wiki maintainers who also want to look after the mailing list just ask. If nobody asks well then no mailing list. In the end I think the outcome will be the same, all languages with active wikis will have mailing lists, how and when they end up there doesn't really matter.
absolutly. how can a non english speaker ask for a mailing list? where?
of course, if there is a fr mailing list I will be on that one also. anyway the mailing list do not need any work or near.
and if nobody use it, who cares?
just a few points: 1. there should be at least one guy in the french community with basic english skills to ask for a mailinglist.
you can happily replace french with ever other language out there. why? because every wiki needs at least one person that migrates the changes from the english wiki into their local wiki.
btw ... they have to ask for a wiki aswell and the best language for this is english aswell.
Exactly. And the way it started on the wiki was someone began translating a page (not realizing that he was changing the intended English version I guess), and I asked him to just stop, and created a new page for him. Then he began using that same style, and added on. Others did the same. When the number of translated pages goes up, even without saying something, I'm sure a wiki admin will notice and take appropriate actions. If there is a particular group that recently had their lang added to the wiki, then I don't think anyone would be surprised at, or even hold back on, a request for a ml. Not a big deal really, it grows as the community grows, without forcing a list or internationalization for the wiki that ends up completely empty.
2. that might be true for you ... but maybe not for everyone. so what is wrong with explicitly asking for a mailinglist? what is wrong with tie the decision to the activity of the community
with kind regards
darix
Joseph M. Gaffney aka CuCullin
Joseph M. Gaffney wrote:
wiki admin will notice and take appropriate actions. If there is a particular group that recently had their lang added to the wiki, then I don't think anyone would be surprised at, or even hold back on, a request for a ml.
Not a big deal really, it grows as the community grows, without forcing a list or internationalization for the wiki that ends up completely empty.
I was only asking for a mailing list for langages already with an opensuse wiki :-) in my advice it should be created right with the wiki. wiki is a very nice piece of software and a very nice medium, but not really given for daily discussion or questions/answers. it's more like an enhanced FAQ (pretty nice for SDB :-), but questions must have a place to be asked :-) and that is the mailing list use. I think that if some people prefere forum it is because the forum have to two uses in the same place: discussion and answers. and it's exactly why I don't like it, it needs always days before reaching the real answer :-) the couple mailing list/wiki is perfect for me :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On 2/9/2006 7:09 PM jdd wrote:
I was only asking for a mailing list for langages already with an opensuse wiki :-)
in my advice it should be created right with the wiki.
Seconded. I would be on the german one, too. OJ -- "A thing is not necessarily true because a man dies for it." (Oscar Wilde)
Druid wrote:
o subfs discussion
I personnaly _hate_ automounting. however I have no problem with this being done for the ones who like it, but, please, don't make it the default for console only systems! I want to be absolutly master of my server config. I would more insist on console only installs without any graphical option in the dependencies (but it's probably an other problem) thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On Thu, Feb 09, 2006 at 09:11:27AM +0100, jdd wrote:
Druid wrote:
o subfs discussion
I personnaly _hate_ automounting.
however I have no problem with this being done for the ones who like it, but, please, don't make it the default for console only systems!
I would opt for default on and an easy way to turn it off with no difference between the way you install. Be it KDE, Gnome, CLI, ... houghi -- We call our dog Egypt, because in every room he leaves a pyramid.
On 02/09/2006 09:22 AM houghi wrote:
I would opt for default on and an easy way to turn it off with no difference between the way you install. Be it KDE, Gnome, CLI, ...
ACK. OJ -- `...a very ancient wizarding family noted for a vein of instability and violence that flourished through the generations due to their habit of merrying their own cousins.? (Albus Dumbledore in Harry Potter and the Half-Blood Prince)
Druid wrote:
o subfs discussion ~~~~~~~~~~~~~~~~ - Several people expressed concern that the automounting feature would only be available for GNOME and KDE - SUSE people explained that subfs is gone for good, and keeping it is not up for discussion.
Does that mean that one of the best features SuSE up to 10.0 had on the desktop (ok, MY opinion) will be gone in 10.1, with no real replacement? I sure hope that it does NOT mean We're back to "sudo mount /dev/cdrom" days...
- Suggested alternatives: supermount, autofs, create a console daemon that will do the job of gnome-volume-manager. The problems are that autofs is poor documented, supermount status is unknown, and the console daemon would need to be implemented, it simply doesn't exist now.
Waitaminute... SuSE decided to drop subfs, without even having a replacement? ok, i refrain from making the obvious comments here.
o SUSE Linux 10.1 Status / Roadmap - AJ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- AJaeger brought us the latest major changes
* Kernel Changes km_ packages / non-GPL kernel modules
- The km_* packages are being replaced by the KMP, so packages can be built more easily independently from the kernel package build. Some information about kmp packages can be found in http://www.suse.de/~agruen/KMPM/
- Most developers of the kernel community consider non-GPL kernel modules to be infringing on their licensing/copyright. Novell does respect this position and refrains from distributing non-GPL kernel modules for future products. Novell works with vendors to supply alternative ways to provide the functionality that was previously only available with non-GPL kernel modules. So, the kernel-*nongpl package has been dropped and will not be provided anymore.
Which basically means that users of one of the best wlan cards (atheros) will have no wlan anymore. Whats the other modules in kernel-*-nongpl for? name suggests its for fritz! dsl stuff (which is quite prominent here in .de since you get them for free with your breakfast cereal eehh dsl account).
From what i've learned from those meeting minutes, most of the changes represent a step BACKWARDS for the user. Correct me if I'm wrong.
bye, MH
On 02/09/2006 10:04 AM Mathias Homann wrote:
Does that mean that one of the best features SuSE up to 10.0 had on the desktop (ok, MY opinion) will be gone in 10.1, with no real replacement?
No. Read the older messages in the factory list, there is a discussion about it. KDE and GNOME will have built-in-support for the new way, all users using other WMs will have to care for themselves. OJ -- `But he knows your dad was right all along now about Voldemort being back -? `Dumbledore says people find it far easier to forgive others for being wrong than being right,?said Hermione. (Ron and Hermione in Harry Potter and the Half-Blood Prince)
On Thu, Feb 09, 2006 at 10:17:04AM +0100, Johannes Kastl wrote:
On 02/09/2006 10:04 AM Mathias Homann wrote:
Does that mean that one of the best features SuSE up to 10.0 had on the desktop (ok, MY opinion) will be gone in 10.1, with no real replacement?
No. Read the older messages in the factory list, there is a discussion about it. KDE and GNOME will have built-in-support for the new way, all users using other WMs will have to care for themselves.
That is the curent situation. However alternatives should be discussed in factory. From the minutes: Suggested alternatives: supermount, autofs, create a console daemon that will do the job of gnome-volume-manager. The problems are that autofs is poor documented, supermount status is unknown, and the console daemon would need to be implemented, it simply doesn't exist now. Any solution (e.g. how other distro's handle this) are welcome as long as it is NOT subfs. People who have alternatives: please let it be known in factory (as long as it is not subfs) houghi -- In Seattle, Washington, it is illegal to carry a concealed weapon that is over six feet in length.
participants (13)
-
Boyd Lynn Gerber
-
Christoph Thiel
-
Druid
-
Eberhard Moenkeberg
-
Henne Vogelsang
-
houghi
-
jdd
-
Johannes Kastl
-
Joseph M. Gaffney
-
Marcus Rueckert
-
Mathias Homann
-
Pascal Bleser
-
Peter Flodin