Hi,
Please follow bnc#478461 and bnc#478099 before you try factory ISOS, currently
they do not work.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Folks-
The source kernel rpm for factory is
http://download.opensuse.org/source/factory/repo/oss/suse/src/kernel-source…
while the default image for x86-64 is
http://download.opensuse.org/factory/repo/oss/suse/x86_64/kernel-default-2.…
The image version is newer than the source.
Where can I get kernel-source-2.6.27.10-2.7.src.rpm, to match the
factory image?
Thanks,
Toni
-------------------------------------------------------------------
Toni Harbaugh-Blackford
Advanced Biomedical Computing Center (ABCC)
National Cancer Institute
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
It's really annoying to have zypper up remove working kernels and initrds before replacements have
been tested positive, particularly since networking is broken absent a post-2.6.25 kernel.
--
"Do not let any unwholesome talk come out of your
mouths, but only what is helpful for building
others up." Ephesians 4:29 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
I read the threads about boot performance effort an preload settings and
wanted to do some tests by my own. So I just startet to disable the
automatically startet services one by one via YaST, here the results (Phenom
II System with Intel SSD, boot time measured from Grub to XDM (XFCE-System)
Default OpenSuse 11.1: 25 seconds
with crond, auditd and sshd disabled: 15 seconds
So 10 seconds only by disabling crond, auditd and sshd at boot time. No
preload experiments no other changes.
Usually you want auditd at boot time, so maybe this is not a good idea to
disable it, but it might be a good starting point for improvement.
Also sshd does not have to be started at boot time, as it's blocked by the
firewall anyway, so you can just leave ssh away and tell users to enable it,
if they need it. (I hate Ubuntu for doing so, but an average user does not
need sshd anyway).
Crond is probably not needed during boot process neighter, so there just has
to be a solution to start it later, after X.
--
Mit freundlichen Grüßen,
Marcel Hilzinger
Linux New Media AG, Putzbrunner Str. 71, 81739 München, Germany
Tel: +49 89 99 34 110, Fax: +49 89 99 34 1199
mhilzinger(a)linuxnewmedia.de - http://www.linuxnewmedia.de
----------------------------------------------------------
Linux New Media, the Pulse of Open Source: Lawrence, KS - Málaga
Manchester - München - São Paulo - Timisoara - Warszawa
----------------------------------------------------------
Sitz der Gesellschaft: Putzbrunner Str. 71, 81739 München
Amtsgericht München: HRB 129161
Vorstand: Rosemarie Schuster, Hermann Plank
Aufsichtsratsvorsitzender: Rudolf Strobl
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
We have quite some issues currently:
- the NET isos are currently broken due to a new format of modules.dep
(bnc#475850).
- we're currently looking at the fallouts from a possible gcc 4.4 update
- we switched from an early lzma-utils snapshot used for 11.0 to the
official xz-4.999.8 beta - which will very likely cause a small change
in the compression format breaking deltas. Due to this I wanted to make
this step early as a 11.1->11.2a1 deltas is usually less interesting than
an a1->a2 delta
- we merged kernel 2.6.29-rc5, which will most likely create some suprises
- Qt 4.5 broke the KDE desktop in a couple of subtle ways
- I dropped most of KDE3 desktop and we're still sorting out what to do
with packages that depend on more advanced features of the desktop
(we stay with kde3 libraries and runtime environment, but some packages
rely e.g. on kdvi or on kscd)
On the good news:
- I pushed preload 1.0, which should show some improvements over the old
preload
- we merged 2.6.29-rc5, which brings ext4 as !dev to openSUSE
- we saw tons of GNOME 2.25.X updates
- we reduced the build failures from last week dramatically (that was before
the kernel merge though :)
And of course we have tons of version updates within Factory, but that are
simply too many for me to list them. See opensuse-commits ml for details.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
good morning,
This morning I get updates that would replace libgcc 4.3 with libgcc 4.4. The same goes for libstdc++44
Does this now mean we're going faster to gcc 4.4 as default than it was announced before or is this just an unintentional glitch?
Dominique
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Am Sunday 15 February 2009 17:31:49 schrieb Peter Czanik:
> Hello,
>
> Stephan Kulow írta:
> >> And if you don't mind me asking... It has been several weeks since I've
> >> had any factory updates. Where are you getting yours from?
> >
> > Huh? download.opensuse.org/factory/repo/oss changed 3 times last week.
> > We're at build 51 at the moment.
>
> Well, I mirror from stage.opensuse.org, and the last x86 factory update
> seems to be from 27th January. A huge upgrade for PPC arrived today.
Indeed, stage is broken. And the reason is this:
# now staged. poeml, Wed Jan 28 04:07:55 CET 2009
Peter, I called publish_factory. I hope I didn't broke something.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
After a few weeks of staying with one state of the Factory system, I
decided to update to a current state once again a few hours ago. This
requires about 5 GB of download and a few hours to run, so it's not
something I'm doing lightly and often.
And once again, as so often, YaST started to spit out errors right in
the middle of the process telling me the Factory repo doesn't contain
some of the packages it wanted to install - probably it's been updated
underneath my install and the packages had been replaced with newer
versions. I canceled and tried again and then I ran into the same
problem with the KDE4 Desktop OBS repo halfway in the install.
Can't we have some system that doesn't frustrate you by pulling out
files you need right while you're installing them? Couldn't OBS keep
files, say, 12-24h after they have been removed from the repo index?
This is frustrating enough that I'm only updating this system very
rarely nowadays, and I think updating often and testing newer stuff is
actually what Factory should be about. The problems I should deal with
(if any at all) are ones that arise due to new code, not due to the repo
info not matching the available files at the time I'm actually trying to
install them.
Is there any solution for this?
Robert Kaiser
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
as some of you might have noticed - I didn't :-( - stunnel was dropped
from openSUSE between 11.0 and 11.1. I don't think it's a good idea,
because it is widely used (at least here) to securely connect remote
services that don't support SSL or TLS.
So I am left with the OBS version of stunnel:
http://download.opensuse.org/repositories/security:/Stunnel/
Since there is no bug owner defined in OBS, I'll write the problems here:
1. The directory /var/lib/stunnel/var/run is not created. It should be
writable for the stunnel user.
2. stunnel starts 5 childs on rcstunnel start. On stunnel stop only the
parent is stopped, but not the child processes. I think this is solved in
stunnel-4.26 upstream, if I interpret the changelog correctly.
What would be the correct way to file a bug against the OBS version of
stunnel?
--
Mit freundlichen Gruessen,
Andreas Vetter
Informations- und Kommunikationstechnik Tel: +49 (0)931 31-85890
Fakultaet fuer Physik und Astronomie Fax: +49 (0)931 888-5508
Universitaet Wuerzburg iuk(a)physik.uni-wuerzburg.de
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
I've been thinking and MySQL uses MYSQLD_MULTI in /etc/sysconfig/mysql
to determine whether user wants to start several instances of MySQL. If
it is set to yes, init script starts mysql daemon for every mysqldN
section in /etc/my.cnf As some users find it confusing to have
/etc/my.cnf and /etc/sysconfig/mysql at the same time, I propose to drop
/etc/sysconfig/mysql. It should be possible to check in init script
whether user has several daemons configured and act accordingly. So we
can get rid of the other configuration file and depend only on one
configuration file. Only question is if anybody else then mysql need
this sysconfig file... Does anybody think that we should preserve this
sysconfig file? Do you know about anything else what needs this
sysconfig variable?
--
Michal Hrusecky
Package Maintainer
SUSE LINUX, s.r.o
e-mail: mhrusecky(a)suse.cz
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org