Hi all,
Progress so far is another patchset for the tst_tmpdir file in the test library.
This patchset includes coding style fixes, removal of obsolete calls / methods
as well as a test file implementing a simple test case to check that the file
works as expected.
Work currently undergoing:
Creating a file to document the tst_ inrface of the test library to be uploaded
in github's documentation pages as well as cleaning up/fixing a few more files
from the tst_ inteface.
You can track the progress in the ltp mailing list
(https://lists.sourceforge.net/lists/listinfo/ltp-list)
or the ltp's github (https://github.com/linux-test-project/ltp)
--
Marios Makris
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello all,
The openSUSE Travel Support Team is happy to announce that we are
ready to process applications to sponsor openSUSE people to attend
openSUSE Summit.
The openSUSE Summit will happen in Orlando, Florida - September 21-23, 2012.
Instructions on how to apply and further information about the Travel
Support Program and eligibility can be found
http://en.opensuse.org/openSUSE:Travel_Support_Program
Important dates!
The Sponsorship Request period for openSUSE Summit ends on July 20,
2012. Responses will be given before July 30, 2012.
Some additional comments:
* A clear and complete application is faster and easier to process, so
please read the wiki page carefully!
* We cannot fulfill all requests, keep in mind that there is no
guarantee you will get sponsored.
* Sponsorship decisions are influenced by the history of the
requester, like having followed the requirement of writing a report
about a conference you attended with sponsorship or having send in the
required paperwork in time.
* If you were part of Google Summer of Code as openSUSE student or
mentor you should mention it in your application.
* If you submitted an abstract to be presented at openSUSE Summit
should mention it in your application.
The Travel Team sends a reply upon receiving your application. We will
then wait for all applicants to send in their requests for the event
and only once we have a full overview, responses will be given. Please
do not send personal emails, always CC the travel-support team in your
replies.
Best Regards,
Izabel Valverde
On behalf of openSUSE Travel Support Team
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
we are running a computer pool for students with 48 machines on openSUSE
12.1. Ususally we try to install "almost everything" except software that
is really annoying when $HOME is on NFS (e.g. beagle in former times).
In older times we used autoyast to install a new version of openSUSE. But
autoyast is just taking too long to install such a long list of software,
and when you forget about a small thing, the turnaround time with such a
big number of packages to install is too long. So we switched to autoyast
and images (tar.gz method) for new machines (or new harddisks) and zypper
dup for upgrading on working machines to new releases. These upgrades take
place in the break between semesters.
zypper dup usually works great. But somehow from 11.4 to 12.1 the
update-alternative files for java were messed up resulting in a
non-working java plugin for browsers. Found out by accident last week.
Since our university uses Novell iprint for charging the students for
printouts, we had to find out, that cups 1.5 does not work with iprint
client. And so we had to build cups 1.4 for openSUSE 12.1.
Printing seems to be one of the most complicated problems in universe ;)
Students love n-up printing to save money. But somehow this seems to
confuse printers from all kinds of different manufacturers (HP, Lexmark,
Sharp). There is also no clear statement how to do it right, because for
some PDFs you better use n-up printing from acroread and for others you
can only use okular and cups n-up printing. Failure of printing "the right
way" (TM) will result in hanging or resetting the printer.
Since the machines are administered by central root, we disable
NetworkManager, Update Notifications, and so on. Bad thing is, this
changes from release to release, and we have to consider all desktop
flavours (KDE, Gnome, LXDE, ...).
For updates we use the automatic online update. Problem here was:
SuSEconfig is not run. But this problem decreases, since SuSEconfig does
less from release to release.
Another thing I'm not quite sure about is: when e.g. openssl library is
updated, a lot of services are affected (zypper ps can tell you), but the
services are not restarted automatically. Since our machine run rather
long (until next kernel update or crash or power plug pulled) they only
get restarted when we do a zypper ps manually and either restart services
manually or reboot. Well this should not be necessary, but I'd feel better
if zypper ps shows nothing.
To change the configuration on all machines, we usually copy the
configuration file(s) to all machines and restart the service. We have
scripts using SSH with authorized_keys for that. Problem is, if a machine
is not online, it does not get the change and one must remember to change
it, when the machine comes back. If there is a better solution, please let
me know.
Wow, that was log. I didn't intend a such long post ;-)
--
Mit freundlichen Gruessen,
Andreas Vetter
Informations- und Kommunikationstechnik
Fakultaet fuer Physik und Astronomie
Universitaet Wuerzburg
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
The last week has not been very eventful as I had to shift to
Singapore from India for higher studies. But there have been a few
changes. The major work pertains to supporting custom regex in the URL
input fields. A partial support for this is available, but is not
sufficient. We would ideally like to have full regex support and this
is the main part of the project I am currently working on. Apart from
this, support to track sourceforge hosted projects has been added.
Once the custom regex has been implemented, DEHS imports can be worked upon.
--
Regards,
N.B.Prashanth
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
here's a small summary of the 7th (coding) week. Last week
I was really busy with university stuff (it was the second
last week in the lecture period so I had to recap quite
some stuff) and didn't manage to work much on the GSoC project.
I'm going work off the TODO this weekend.
Marcus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
vetter(a)physik.uni-wuerzburg.de wrote:
> we are running a computer pool for students with 48 machines on openSUSE
> 12.1. Ususally we try to install "almost everything" except software that
> is really annoying when $HOME is on NFS (e.g. beagle in former times).
Ah, the famous "zzz All" entry :-)
> and images (tar.gz method) for new machines (or new harddisks) and zypper
> dup for upgrading on working machines to new releases. These upgrades take
> place in the break between semesters.
So for that I guess you have to log into each machine and run and watch
zypper dup manually?
> Printing seems to be one of the most complicated problems in universe ;)
Yeah :-)
> For updates we use the automatic online update. Problem here was:
> SuSEconfig is not run. But this problem decreases, since SuSEconfig does
> less from release to release.
> Another thing I'm not quite sure about is: when e.g. openssl library is
> updated, a lot of services are affected (zypper ps can tell you), but the
> services are not restarted automatically. Since our machine run rather
> long (until next kernel update or crash or power plug pulled) they only
> get restarted when we do a zypper ps manually and either restart services
> manually or reboot. Well this should not be necessary, but I'd feel better
> if zypper ps shows nothing.
Indeed. With systemd it should even be possible to automatically
determine the service for each pid. Maybe worth filing a feature
request.
> To change the configuration on all machines, we usually copy the
> configuration file(s) to all machines and restart the service. We have
> scripts using SSH with authorized_keys for that. Problem is, if a machine
> is not online, it does not get the change and one must remember to change
> it, when the machine comes back. If there is a better solution, please let
> me know.
Isn't that someting puppet or func try to solve?
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
To begin, it's worth summarizing were fdisk currently stands as per gsoc
tasks. Up to this point a good part of the API is now established and
implemented - with the device, MBR, geometry and topology information
already upstream. For the next few weeks the label specific disk
operations will be implemented. There are still a few details as to the
design, specially keeping in mind that it must be generic and labels
operations often aren't.
Specifically, this week the label probing logic is being written and
will be sent for review as soon as possible.
Thanks,
Davidlohr
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi
here's a small summary of the 6th (coding) week. Last week I
continued working on the build module and developed a concept
for the package fetcher (and discussed some parts
with darix:) ).
The main idea is to modularize the fetcher code, verify code etc.
Thus we have a fetcher class which takes care of retrieving the
packages. The fetcher class utilizes a "cache manager" which takes
care of storing the fetched packages on the filesystem. The goal is
that at some point in time one can exchange the "simple" cache manager
with a more "clever" cache manager (which for instance cleans up the
cache from time to time or only allows exactly one version of a
package in the cache etc.). In order to achieve this no code in the
fetcher has to be touched - instead it's sufficient to pass a different
cache manager object to the fetcher.
Additionally the fetcher provides some hooks like pre, pre_fetch,
post_fetch and post. For instance a post_fetch hook can be used to
verify the just fetched package etc.
TODO:
- write testcases and implement the concept from above
If you have questions, suggestions etc. feel free to contact me:)
Marcus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org