July 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Systemd parallel startup/shutdown and dependencies (This is not a rant).
by Rodney Baker 04 Jul '14

04 Jul '14

Hi all. Slowly getting my head around Systemd and how to "control" it. I understand the idea of speeding up boot/shutdown by taking advantage of modern processor/system capabilities by parallelising startup and shutdown wherever possible, but this does lead to some potential race conditions and I'm not sure there's a generic "patch" that can fix all of them since some are very system-specific. With SysV Init, one could fairly easily control the order in which services were started (at boot) and killed (at shutdown) simpy by changing the Sxx or Kxx prefix of the scripts in /etc/rc.d/init.d (or /etc/init.d, depending on your distro), however this assumes that the entire startup process is serialised. The same approach doesn't work with systemd, leading to one unintended side effect that I (and others, judging by open bug reports for other distros) have been dealing with. One example - mounting remote file systems at boot time, especially Samba shares defined in /etc/samba/cifstab. With the default systemd configuration, the remote-fs and remote-fs-pre services (required by the remote-fs target) don't have the network.service listed in their "Requires=" parameter in the unit file; thus, in the default state the system can (and does) try to mount remote file systems before the network is started, but apparently only if you're bringing up the network using ifup instead of NetworkManager. [To my mind, NetworkManager is great on a laptop or other mobile system but makes no sense on a desktop or server system where the network configuration is static.] Furthermore, the system also takes down the network before trying to unmount the remote file systems, resulting in delayed shutdown until the unmount job times out. The fix for the boot problem was easy; add "Requires=network.service" to the remote-fs.target unit file (in /usr/lib/systemd/system). This did not fix the shutdown problem though - the network interface was shut down before the remote file-systems were umounted, even though the network.service apparently wasn't. I also had to add "Requires=network(a)eth0.service" to the remote-fs.service (and, for good measure, to the remote-fs-pre.target file, because it seems cifs.service may be started from remote-fs-pre.target rather than remote- fs.target). Adding a dependency on the specific (and in my case, only) network interface ensures that the remote filesystems are unmounted before the interface is taken down and fixes the shutdown issue. Herein lies the problem - creating a dependency on a specific network interface requires that the interface name be known when the unit file is created; there is no "network(a)eth0.service" file - on disk it exists as "network@.service" - the interface name is appended at runtime. Now, consistent naming of interfaces is obviously important here but this is what makes it system-specific, because under the new scheme the interface names are system-specific (unless you override them to use the traditional names as my system does). That's why I'm not sure that a generic fix is possible, because it is so specific to each individual system. That means that if you are going to be mounting remote file systems at boot time, you'd better get familiar with systemd unit files because it's going to require fixing on a system-by-system basis. That, I think, fits the definition of a broken design. It may have been a "corner case" that wasn't considered by the designers of systemd, I don't know, but there's got to be a better way. Changing the way the system handles the network startup/shutdown (to avoid the need to have dependencies on specific interfaces) is probably an area that needs addressing. Do I feel a bug report coming on? -- ============================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 12

[opensuse] Re: Vinyl vs CD's and Linux [Was: LibreOffice 4.2.4]
by Carlos E. R. 03 Jul '14

03 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-07-03 at 16:57 +0100, michael norman wrote: > On 03/07/14 16:43, James Knott wrote: >>> Rubbish. You know nothing about turntables and vinyl replay. >> Please explain how a needle can follow a track without any friction >> whatsoever. >> > I didn't say that it could, you appear to assume that friction, per se and in > this context must by definition cause damage. In other words that friction > is a bad thing. Is it ? The friction is minimal. So low with good equipment that you many not notice it. Being so minimal, the difference from one time you play a record to the next one is probably impossible to notice, by ear at least. After a hundred playing cycles you should notice the difference, if you can remember how it played the first time, not the 99th. You could try playing a record just once, then go out of the room for a week or so, while somebody else plays it a hundred times. Then you come back, and listen to it again. If your ear and memory are good enough you should notice the difference. If not, you can instead make a digital recording the first and the last time, and compare. Or better, make a hundred recordings, and compare all of them to find out how they degrade. Surely there is such a study somewhere already made. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlO131sACgkQtTMYHG2NR9UqVACdFuEiVBoKbP6HSFGX/eJgOoSg LOMAniTrW17J+AbjpHis+LIGUQgE0NIS =pT4s -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: Vinyl vs CD's and Linux [Was: LibreOffice 4.2.4]
by Carlos E. R. 03 Jul '14

03 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-07-03 at 17:50 +0100, michael norman wrote: >> From a reproduction accuracy point of view, CDs are much better than >> vinyl, but then I doubt you'd know enough about the process to >> understand that. When it comes to frequency response, dynamic range and >> noise level, CDs are vastly superior to vinyl and that is fact. There >> are many who prefer vinyl, but that's because they prefer the >> distortions it causes to audio accuracy. > > I don't know anything about the fact that cd is superior to vinyl, and I > suspect I know more about the process than you do. What do you mean by > reproduction accuracy ? When it comes to frequency response dynamic range > and noise level analogue is in fact better than cd and that is fact. > > Those of us who prefer vinyl are interested in music, I have no idea what you > mean by audio accuracy. But that means that you don't know more about the process than others! :-) Facts have to be scientifically proven. That "it sounds better" is not a fact, is an impression on the ear and mind, which can be fooled (and how to fool them is very much studied). > I can and do compare the same music on vinyl and cd I know which sounds > better to me. See above :-) You can say, and I agree that you can say, that you "know which sounds better to me". But you can not say that "frequency response dynamic range and noise level analogue is in fact better than cd and that is fact" because those are measured with instruments and calculated by engineers, and the layman can not dispute the figures no matter what. However, engineers and scientifics can strive to find out why "it sounds better", and provide that sound with different technologies. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlO13GEACgkQtTMYHG2NR9WsKACfchhMeiRes3DvTwdWLmjc/0uO BFkAmwca785XOW5VjUdwAUO1wiWrDn02 =yPo6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] USB3 throughput
by Greg Freemyer 03 Jul '14

03 Jul '14

All, I happened to run a USB3 throughput test recently and it wrote 5 TB in 7 hours. I used a USB3 hub to let me hook up 5 1 TB drives and wrote to them simultaneously. That's about 200 MB / sec. It's the first time I've ever apparently saturated USB3. Does anyone know if 200MB / sec is a good max USB3 throughput? fyi: Per the spec, it should be possible to hit 500MB/sec., but real world seldom hits the spec limits so 200MB/sec may be as good as it gets. If not, I may need to look for a better USB3 hub. (I do a lot of high bandwidth transfers in my job.) Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 15

[opensuse] NTP clock slow
by James Knott 03 Jul '14

03 Jul '14

I run NTP to set my computer clock and the time is displayed on the task bar. I can also check the time on a U.S. government web site and on a clock that's synced to WWVB, the U.S. National Bureau of Standards time signal. My computer clock tends to be about a half second behind the other two. I though NTP was supposed to be able to do better than that. I connect to the time.nrc.ca NTP server, which is run by the National Research Council in Ottawa, which is the primary time standard for Canada. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 63

[opensuse] old documentation
by lynn 03 Jul '14

03 Jul '14

Are there non draft versions of this: http://doc.opensuse.org/products/draft/SLE-HA/SLE-ha-guide_sd_draft/cha.ha.… Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Firefox Location-Aware Browsing ?
by Per Jessen 02 Jul '14

02 Jul '14

Just wondering out loud - why is Firefox occasionally asking me for permission to share information that the webserver will have (or have access to) any way? > By default, Firefox uses Google Location Services to determine your > location by sending: > > your computer’s IP address, > information about the nearby wireless access points, and > a random client identifier, which is assigned by Google, that > expires every 2 weeks. All Firefox has is my (private) IP-address, so why bother asking when the webserver knows it too?? -- Per Jessen, Zürich (13.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 20

[opensuse] Fwd: [lca-announce] linux.conf.au 2015 opens call for presentations
by Tim Serong 02 Jul '14

02 Jul '14

Anyone who's going to be, or wants to be, in or near Australia and/or New Zealand in January 2015, please read on... -------- Original Message -------- Subject: [lca-announce] linux.conf.au 2015 opens call for presentations Date: Tue, 10 Jun 2014 16:58:00 +1000 (EST) From: linux.conf.au Announcements <lca-announce(a)lists.linux.org.au> Reply-To: lca-announce(a)lists.linux.org.au To: lca-announce(a)lists.linux.org.au === linux.conf.au Call For Proposals === The call for proposals for linux.conf.au 2015 is now open! The conference is a meeting place for the free and open source software communities. It will be held in Auckland at the University of Auckland Business School from Monday 12 to Friday 16 January, 2015, and provides a unique opportunity for open source developers, students, users and hackers to come together, share new ideas and collaborate. === Important Dates === * Call for Proposals opens 9 June 2014 * Call for Proposals closes 13 July 2014 * Email acceptances start September 2014 * Early bird registrations open 23 September 2014 * Conference dates: Monday 12 January to Friday 16 January, 2015 === Information on Proposals === The linux.conf.au 2015 papers committee is looking for a broad range of proposals, and will consider submissions on anything from programming and software, to desktop, mobile, gaming, userspace, community, government, space, and education. There is only one rule: *Your proposal must be related to open source* This year, the papers committee is going to be focused on open source in education as well as our usual focus on deep technical content. The conference is to a large extent what the speakers make it: if we receive heaps of excellent submissions on a topic, then itâs sure to be represented at the conference. Hereâs a few ideas to get you started: * Clouds, data centers and scalability. * Community challenges; legal threats; education and outreach. * Documentation for open source projects. * HTML5; multimedia codecs. * Kernel developments; new architectures. * Open hardware; embedded systems; wearable computing. * Security; privacy; anonymity. * Networking; Software defined networking; bufferbloat; network function virtualization. * Software development; programming languages. * Sysadmin and automation. linux.conf.au is known for presentations and tutorials that are strongly technical in nature, but proposals for presentations on other aspects of free software and open culture, such as educational and cultural applications of open source, are welcome. === Code of Conduct === linux.conf.au welcomes first-time and seasoned speakers from all free and open communities: people of all ages, genders, nationalities, ethnicities, backgrounds, religions, abilities, and walks of life. We respect and encourage diversity at our conference. By agreeing to present at or attend the conference, you are agreeing to abide by the terms and conditions (http://lca2015.linux.org.au/cor/terms_and_conditions) We also expect all speakers and delegates to have read and understood our Code of Conduct (http://lca2015.linux.org.au/cor/code_of_conduct) === Format === There are three different ways that you can present your content: * Presentations * Tutorials * Mini conferences _Presentations_ Presentations are 45 minute slots that are generally presented in lecture format. These form the bulk of the available conference slots. _Tutorials_ Tutorials are 100 minutes long, and are generally presented in a classroom format. They should be interactive or hands-on in nature. Tutorials are expected to have a specific learning outcome for attendees. _Mini conferences_ Miniconfs are one or two day long sessions on a specific topic. A separate CFP form will be used to propose and select miniconfs, and is available at http://lca2015.linux.org.au/miniconf-cfp === Speaker Information === In recognition of the value that speakers bring to our conference, once a proposal is accepted a speaker is entitled to: * Free registration, which holds all of the benefits of a Professional Delegate Ticket * Exclusive tickets to the Speakers' Dinner for the speaker and their immediate family * One free family ticket to the Partners' Programme If your proposal includes more than one speaker, these additional speakers are not entitled to free registration or to any extra benefits. linux.conf.au does not and will not pay speakers to present at the conference. linux.conf.au is able to provide limited financial assistance for some speakers, for instance, where the cost of flights or accommodation might prohibit a speaker from attending. Please note, however, that there is a limited budget for travel assistance and that asking for assistance could affect your chances of acceptance. === Recording and Licensing === To increase the number of people that can view your presentation, linux.conf.au might record your talk and make it publicly available after the event. When submitting your proposal you will be asked to release materials relating to your presentation under a Creative Commons ShareAlike License. Additionally, if you are discussing software in your presentation, you must ensure the software has an appropriate open licence. All presentation material should be suitable for people aged 12 and above. All presentations are subject to Linux Australiaâs code of conduct, including that they must not contain: sexual or violent imagery exclusionary language language which is not appropriate for an all-ages audience For more information, see: http://lca2015.linux.org.au/cfp === About Linux Australia === Linux Australia is the peak body for open source communities around Australia, and as such represents approximately 3500 Free and Open Source users and developers. Linux Australia supports the organisation of this international Free Software conference in a different Australasian city each year. For more information about Linux Australia see: http://www.linux.org.au/ === Papers Enquiries === For enquiries related to this CFP, or to presentations at linux.conf.au generally, contact the linux.conf.au 2015 Papers Committee by email: papers-chair at linux.org.au -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: Post to opensuse-kde@opensuse.org denied
by upscope 01 Jul '14

01 Jul '14

On Monday, June 30, 2014 12:03:58 PM Henne Vogelsang wrote: > Hey, > > On 28.06.2014 18:28, upscope wrote: > > On Thursday, June 26, 2014 04:51:12 PM you wrote: > >> Content-Type: text/plain; charset="us-ascii" > > > > I have checked all my settings, there is no HTML allowed on any of > > the browsers I use. KMail and SeaMonkey for mailing lists. > > > > All so no attachments or mail from other list. I normally use Kmail > > to send to the list. Only thing I can see there is a signature as > > below. If it is failing because of signature then it needs to > > looked at since alot of questions asked require configuration > > information. > > > > Can you look into this problem, I only appear to have it starting > > with this message, before that my mails all got posted. > > You are sending mails in multipart where one part is text/plain and > the other one HTML. As we don't allow HTML your mail is blocked. If > you turn HTML off everything will be fine. Thanks in advance. > > Henne Thanks for responding. As far as I can see in Kmail all my html is off. Also in SeaMonkey. I sent a message today at 8:15 Am and it went thru to opensuse(a)opensue.org. It is posted OK. Header of my message today. [CODE] ---------- Return-Path: <opensuse+bounces-161023-upscope=nwi.net(a)opensuse.org> Delivered-To: upscope(a)nwi.net Received: (qmail 22299 invoked from network); 30 Jun 2014 15:15:33 -0000 Received: from mx2.localtel.net (HELO mx2.localtel.net) (172.20.0.92) by mail.nwinternet.com with (DHE-RSA-AES256-GCM-SHA384 encrypted) SMTP (618656ea-0069-11e4-ae10-005056af000e); Mon, 30 Jun 2014 08:15:33 -0700 X-Virus-Scanned: by SpamTitan at nwinternet.com X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=1.49 tagged_above=-999 required=5 WHITELISTED tests=[SPF_NONE=1.5, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received-SPF: none (opensuse.org: No applicable sender policy available) receiver=mx2; identity=mailfrom; envelope-from="opensuse+bounces-161023- upscope=nwi.net(a)opensuse.org"; helo=lists4.suse.de; client- ip=195.135.221.135 Received: from lists4.suse.de (lists.opensuse.org [195.135.221.135]) by mx2.localtel.net (Postfix) with ESMTP id B578F385923 for <upscope(a)nwi.net>; Mon, 30 Jun 2014 08:15:19 -0700 (PDT) X-Original-To: opensuse(a)lists4.opensuse.org Delivered-To: opensuse(a)lists4.opensuse.org Received: from relay2.suse.de (unknown [149.44.160.134]) by lists4.suse.de (Postfix) with ESMTP id E115086362E for <opensuse(a)lists4.opensuse.org>; Mon, 30 Jun 2014 15:15:08 +0000 (GMT) X-Virus-Scanned: by amavisd-new at localhost Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 4D7291F42 for <opensuse(a)lists4.opensuse.org>; Mon, 30 Jun 2014 15:15:06 +0000 (UTC) Received: from mail.nwinternet.com (mail.nwinternet.com [206.130.133.14]) by mx2.suse.de (Postfix) with SMTP id 34A9FABA2 for <opensuse(a)opensuse.org>; Mon, 30 Jun 2014 15:15:05 +0000 (UTC) Received: (qmail 21227 invoked from network); 30 Jun 2014 15:15:13 -0000 Received: from 63.135.60.15.nwinternet.com (HELO linux-x5b8.localnet) (upscope@nwi.net@63.135.60.15) by mail.nwinternet.com with (DHE-RSA- AES256-SHA encrypted) SMTP (557381fc-0069-11e4-af83-005056af000e); Mon, 30 Jun 2014 08:15:13 -0700 From: upscope <upscope(a)nwi.net> To: opensuse(a)opensuse.org Subject: Re: [opensuse] Accumulating kernels Date: Mon, 30 Jun 2014 08:15:03 -0700 Message-ID: <1612547.T19LGt4ZI0@linux-x5b8> User-Agent: KMail/4.13.2 (Linux/3.11.10-17-desktop; KDE/4.13.2; x86_64; ; ) In-Reply-To: <53B06C40.6000705(a)antonaylward.com> References: <53B003A4.3000208(a)antonaylward.com> <53B0650A.9080609@bout- tyme.net> <53B06C40.6000705(a)antonaylward.com> Precedence: bulk Mailing-List: contact opensuse+help(a)opensuse.org; run by mlmmj X-Mailinglist: opensuse List-Post: <mailto:opensuse@opensuse.org> List-Help: <mailto:opensuse+help@opensuse.org> List-Subscribe: <mailto:opensuse+subscribe@opensuse.org> List-Unsubscribe: <mailto:opensuse+unsubscribe@opensuse.org> List-Owner: <mailto:opensuse+owner@opensuse.org> List-Archive: <http://lists.opensuse.org/opensuse/> X-MIME-Notice: attachments may have been removed from this message MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-MagicMail-UUID: 618656ea-0069-11e4-ae10-005056af000e X-MagicMail-SourceIP: 172.20.0.92 X-MagicMail-EnvelopeFrom: <opensuse+bounces-161023- upscope=nwi.net(a)opensuse.org> X-MagicMail-Whitelisted: Yes On Sunday, June 29, 2014 03:42:56 PM Anton Aylward wrote: ---------- I did change Rich Text Editing to unchecked (in Kmail - it was apparently installed that way) yesterday. Does that effect and add the HTML part? > On 06/29/2014 03:12 PM, Ken Schneider - openSUSE wrote: > > On 06/29/2014 08:16 AM, Anton Aylward pecked at the keyboard and wrote: > >> In /boot I have Thanks Russ -- openSUSE 13.1(Linux 3.11.10-17-desktop x86_64| Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3| GeForce 8400GS (NVIDIA-Linux-x86_64-331.79)|KDE 4.13.2 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] 11.2 Rsync command clarification
by Hylton Conacher (ZR1HPC) 01 Jul '14

01 Jul '14

Hi, As a fairly long time subscriber to this list and running Os 11.2 and looking at making a backup of my home directory to a locally connected NAS device that is owned by the root user. That is part of what will enable me to update to 13.2 on release. My current user can use 'sudo' but it is the syntax of the rsync command that is stopping me from executing as rsync can apparently be a BEAST if used incorrectly. I have read and re-read the man pages as well as doing some Google searches and reading Suse Linux Toolbox by Chris Negus. Many of references show copying from a remote host or using a remote daemon. Since I am doing it all locally I hope the list can help i.e. I am at the terminal on the machine that holds the information to be backed up and also has the Drobo is connected. My reading has given me that the command reads: >rsync [options] source dest I assume the 'source' mentioned is what I want to backup and the dest is the location I want the backup? My command so far is: $> sudo rsync -avPh /home root@Umalusi:/drobo/backup-'date +%A'/ This would, I believe, recursively copy all items in the /home directory, archiving files and folders, being verbose, and provide a human readable progress indicator, and place them in a dated folder on the backup medium with path being /Drobo. Since it is copying onto a root file-system is sudo still required or would it not still request the root password? Can you answer any of the queries, correct my command syntax, or redirect my thinking? Help towards using the cli property is the main aim, besides doing the backup etc etc. Your thoughts? Regards Hylton -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4