Hello,
I prepared updated syslog-ng packages with the close supervision of
Marius Tomaschewski, the maintainer of the syslog-ng package. They are
available in home:czanik in the openSUSE BS. I would like to see these
packages included in Factory, to replace the ancient 2.0 syslog-ng, but
MT seems to have disappeared (no response to e-mails in the past two weeks).
Questions:
- it works fine on my machines, but could anybody else test it?
- what is the proper way to get syslog-ng updated in factory, if the
maintainer seems to be unavailable?
- I have now both 3.0 and 3.1 packages there, called syslog-ng and
syslog-ng31. The ultimate goal is to include 3.1. Should I drop the
current syslog-ng package and rename syslog-ng31 to syslog-ng?
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm asking here a question not related to factory directly, because I want to reach the devs. You
can reply on opensuse list instead if you prefer.
To keep it short (longer post in the opensuse list), I'm attempting to upgrade from 11.0 to 11.2 (32
bits) using the retail DVD, wich turns out it has only the x64 version. It offers to upgrade to 64
bit the 32 bit install:
The architecture of the system installed in the selected partition
is different from the one of this product" [continue] [cancel]
I said "continue", then I checked the package list. As far as I could see, it intended to replace
all packages with those corresponding to the 64 bits version. If this works, fine... but I was
afraid, and I cancelled. Not because risking data (it is a copy), but because of possible waste of
time. I thought I'd better RFC.
Has anybody done this, an upgrade from 32 to 64 bits? Does it work? Is it "supported"?
- --
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 "Emerald" GM (Elessar))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAktvNHIACgkQU92UU+smfQVsTwCfSYFG8N7Owo/PWNu0ylYKGqmr
fuQAoJQSLDrMlTDMYeRihU5SfBa0fVz8
=zvu9
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
It would be good if we would start with collection release notes
snippets for 11.2 now. Do not hesitate to provide input!
Here is some background information:
http://en.opensuse.org/Release_Notes
--
Karl Eichwalder
R&D / Documentation
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello there,
I hope I'm in the right place. I am interested in running the 11.3
Mileston 6 release later in the week, when it becomes available.
I have a Lenovo T410s. I have the output of 'hwinfo', which I will
happily share. I'm not sending it here, since somebody may want it
in a particular place or may not want it at all.
I tried installing 11.2, which installs beautifully, but fails on
boot, whether I boot to runlevel 3 or 5.
The 11.3 Milestone 5 installation failed utterly.
I'm looking for advice:
- I'm prepared to wait until later in the week, banking on
Milestone 6.
- Would the 'hwinfo' output be of use to anybody in particular?
- Is this a well known issue?
- -Martin
- --
Martin A. Brown --- Wonderfrog Heavy Industries --- martin(a)wonderfrog.net
"I'm trying to ovoid him, but he keeps circling!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: pgf-0.72 (http://linux-ip.net/sw/pine-gpg-filter/)
iD8DBQFL2HVhki79Zb8hnmwRAiv1AJ0T2sEacl8ViqCl5Ks7nRU75f9wXACeKzgI
EEXF0PUEQEaZ3wpGrqh15gs=
=izd8
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I am planning to run regular (e.g. daily to weekly) semi-automatic tests of current factory .isos to increase installability/testability of those and milestone releases for testers, thus increasing overall quality.
Todays score is poor. Out of 5 tested .isos only the i586-NET got past the install stage and even then hung during the printer configuration phase, so
0.5/5 would be a fair total.
I run this on KVM with a self-made perl script generating keyboard-input and capturing pictures (currently 2/sec). As a nice side-effect, there can now be seen compact ogg-theora-videos of the current boot/install having 6x speed at
http://www3.zq1.de/bernhard/mirror/opensuse/video/
You might also notice the predicted remaining time on the NET-install to jump up and down.
Also the "Loading Installation System" part of the NET-boot is suspiciously long at 100%... and does not have a size given.
If you are interested in those scripts, you can get them from
http://www3.zq1.de/bernhard/git/autoinst/
but they are nowhere near perfect, yet.
have a lot of fun
--
Bernhard M. Wiedemann
software engineer
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I was wondering if there is a definite decision about how to go on forward
with the seperation of Contrib and mainline Factory.
If I remember correctly Contrib was the place to submit stuff to as normal
contributor to openSUSE, now Factory is open for everybody to submit stuff,
based on reputation, skills and whatnot. So what's the future of Contrib now,
this looks like a limbo state to me.
Also does openSUSE try to be as inclusive as debian now (everything in one big
repository) or seperate atleast into Factory and Contrib?
Or even further with repositories like network:utilities, games, GNOME:Extra,
KDE:Community etc. which currently have a 'rolling release' way of life.
I can't come up with a big weighing pro for any of the possibilities, but I
just can't say what model is currently followed.
Karsten
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
All,
Let me know where the below should be posted if not the factory list.
It relates to how 11.3 will handle SSD discards.
===
There is currently a fairly large thread on the Ext4 mailing list that
I've been participating in.
The basic conclusion is that for SSD based drives that can benefit
from discards, there are two existing approaches.
One is in the current kernels and it involves invoking discard any
time data blocks are freed up. Thus it can mean large number of
discards per second. This code was written and accepted into the
kernel prior to any hardware to really test it with.
Apparently now that vendors are shipping SSDs that support discard,
that methodology is proving to be a loser and SSD performance is lower
if it is enabled, instead of higher which is the entire goal of the
discards. I haven't seen benchmarks yet for this with high-end SCSI
array backends. If they too are bad, the existing logic is very
likely to be tossed from the kernel. Not sure what will replace it in
the kernel, if anything.
Alternatively, hdparm was enhanced a year or so ago to have several
discard related functionalities. That functionality is already in
11.2 and factory, so there's no issue there.
But hdparm is only providing base functionality and it needs a script
to actually invoke it correctly and cause the appropriate sectors to
be discarded. Fortunately Mark Lord (the hdparm maintainer) is now
also including "wiper.sh" with hdparm that will scan a filesystem
(ext4 and xfs for sure and possibly others) and invoke discard in a
very efficient way.
I don't think 11.2 or factory are including that script, but I'd like
to see it go in as the opensuse 11.3 methodology for calling discard
on a SSD.
That will mean including the script, testing it as part of opensuse,
and getting it in the nightly cron scripts or something.
How does a decision like that get made, etc.
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
oo3 even as recent as today still has a bug. It is openSuSE's version
and is still a pain. It came from a zypper dup from days a go and
attempted updated today.
Still the same problem "oofromtemplate". It has been in M5 and M6.
"creation of executable memory area failed: Too many open files".
ooo3 comes up and request fixing the file last opened.
Fix it and try to save it. ooo3 crashes.
--
73 de Donn Washburn
307 Savoy Street Email:" n5xwb(a)comcast.net "
Sugar Land, TX 77478 LL# 1.281.242.3256
Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net "
VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg
BMW MOA #: 4146 - Ambassador
" http://counter.li.org " #279316
Hi,
Unfortunately we have some pretty bad dependency issue
in the KDE stack, so we had to get in another round. But
it should still be possible to have it all done till tomorrow.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
