September 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] ntp default restrict options - seems to block broadcastclient ?
by Per Jessen 25 Sep '14

25 Sep '14

The current openSUSE packaged NTP config contains the following: restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery When they're enabled, ntp doesn't sync to my broadcast. Only when I comment them out does it work. Which one of "default kod notrap nomodify nopeer noquery" is preventing my broadcast sync? thanks Per -- Per Jessen, Zürich (15.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] Factory Snapshot Images
by Timothy Butterworth 25 Sep '14

25 Sep '14

All, What is the difference between: openSUSE-Factory-DVD-x86_64-Current.iso and openSUSE-Factory-DVD-x86_64-Snapshot20140918-Media.iso? These both show that they were published on the same date. Thanks Tim -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Fwd: Re: [oss-security] CVE-2014-6271: remote code execution through bash
by Christopher Myers 24 Sep '14

24 Sep '14

>>>> Solar Designer 09/24/14 4:34 PM >>> >On Wed, Sep 24, 2014 at 11:27:09PM +0200, Hanno B??ck wrote: >> Tavis Ormandy just tweetet this: >> https://twitter.com/taviso/status/514887394294652929 >> >> The bash patch seems incomplete to me, function parsing is still >> brittle. e.g. $ env X='() { (a)=>\' sh -c "echo date"; cat echo > >Thanks for bringing this to oss-security. I've added CC to Chet and >Tavis on this "reply". > >Alexander Will the oS versions include fixes for stuff like this, since it sounds like the official BASH patch isn't finished yet? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [review-team] Re: [opensuse] Bash Vulnerability - Fix for 13.1?
by Marcus Meissner 24 Sep '14

24 Sep '14

On Wed, Sep 24, 2014 at 11:26:27PM +0200, Marcus Rueckert wrote: > On 2014-09-24 23:18:41 +0200, Marcus Meissner wrote: > > On Wed, Sep 24, 2014 at 04:07:40PM -0500, Christopher Myers wrote: > > > It looks like the full SLES versions have a patch in QA at the moment: http://support.novell.com/security/cve/CVE-2014-6271.html So I would assume that oS will come soon? > > > > It is waiting only for the review team. > > > > SR 251834 > > done. and released. Will be available once the update repo has rebuild and synced out (in 1 - 2 hours). Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] openSUSE Release's and Maintenance Periods
by Timothy Butterworth 24 Sep '14

24 Sep '14

All, Is anyone interested in attempting to change openSUSE's release maintenance periods and increase the Evergreen release support timeframe to make it easier for Small Medium Businesses SMB to implement? Every SMB we can migrate over to evergreen becomes a potential future SUSE Enterprise and their input into the distro will certainly help steer it into better supporting their businesses. Currently openSUSE Evergreen releases can range from 3-4 years of support but 3 is essentially guaranteed. Starting with Ubuntu 12.04 LTS, both The Server and Desktop versions will receive 5 years support. We are currently slightly shorter by around two years for Evergreen LTS releases, as the next Evergreen release is also free of cost and openSUSE upgrades do work rather well. I do not really see needing to provide a hard 5 year guarantee. I would like to see openSUSE start using the Major.0 release again and possibly move to this type of release cycle. 14.0 Evergreen Release 14.1 Developer/Tester/Enthusiast Release targeted to development of the next Evergreen 14.2 Developer/Tester/Enthusiast Release targeted to development of the next Evergreen 14.3 Developer/Tester/Enthusiast Release targeted to development of the next Evergreen 15.0 Evergreen Release 15.1 Developer/Tester/Enthusiast Release targeted to development of the next Evergreen 15.2 = 14.0 Evergreen EOL This would put Evergreen under maintenance support for a period of 6 releases and provide a 2 release stabilization period before users would have to migrate approximately 18 Months. Most businesses that utilize Windows wait until Service Pack 1 or Service Pack 2 to migrate to enhance stability and fix design flaws so this would help put us on par with Microsoft some. There was once take about creating a service pack system for SUSE when Novell owned SUSE. I don't know what happened with it but we could look at releasing a updated DVD installer (15.0.1) with in conjunction with the 15.2 releases this would just be a software defect fix incorporating the first 12 months of updates from the maintenance period. To assist users in migrating between evergreen versions and provide extra emphasis on openSUSE's maintenance support. If a new DVD installer is not desirable then possibly a just a add-on installation CD or DVD that contains all the openSUSE patches that were released in the first year so it can be downloaded added as an additional installation source and used to quickly apply all the relevant updates. I personally like the idea of releasing a Evergreen updated Installation medium on a 12 month cycle and using a third point number so this could be treated as an equal to a service pack slipped streamed installation medium to speed up installation times. For the minor update releases they are currently supported for around 18 months (2 releases + 2 months). I would rather see these change to (1 release + 6 months). Most users do not keep minor releases for 18 months. Keeping them maintained for 18 months does use up resources even with OBS. I think we should treat the 3 minor update release's as the proving ground developer/tester/enthusiast targeted releases to work up to the new Evergreen release. In conjunction with this we could put together a long term goal section on the Wiki for the next Evergreen release instead of only using the goals per release cycle. The goal of The openSUSE Project of course is not to produce a perfect Enterprise Distribution with older stable software but to produce a good quality all around distribution allowing for newer software and exciting new features to be included. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Question on openSUSE 13.2 Beta 1
by S S 24 Sep '14

24 Sep '14

Can openSUSE 13.2 Beta 1 be used with the Packman repo, and are there repos for it or does it work with 13.1 repos? I would test it but I need to be able to run existing software in the 13.1 repos on it as I don't have a second computer available. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] new bugzilla - weird message when trying to add a reply
by Per Jessen 24 Sep '14

24 Sep '14

I got the following when I tried to update bug#890877 > You submitted changes to process_bug.cgi with an invalid token, which > may indicate that someone tried to abuse you, for instance by making > you click on a URL which redirected you here without your consent. -- Per Jessen, Zürich (11.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] Interpretation please
by Basil Chupin 24 Sep '14

24 Sep '14

I just ran smartctl on my 2 drives, sda and sdb, with the following results. Could someone please interpret these results and tell me if there is cause for worry. *sda* SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 130073028 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1006 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 4341556312 9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 12166 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 933 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 094 000 Old_age Always - 3228 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 053 045 Old_age Always - 28 (Min/Max 17/29) 194 Temperature_Celsius 0x0022 028 047 000 Old_age Always - 28 (0 10 0 0 0) 195 Hardware_ECC_Recovered 0x001a 042 027 000 Old_age Always - 130073028 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5553392728641 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2804485771 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 33088652 SMART Error Log Version: 1 No Errors Logged *sdb* SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 112 099 006 Pre-fail Always - 45408425 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 863 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 17202052028 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 11380 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 863 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 2 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 072 052 045 Old_age Always - 28 (Min/Max 18/29) 194 Temperature_Celsius 0x0022 028 048 000 Old_age Always - 28 (0 11 0 0 0) 195 Hardware_ECC_Recovered 0x001a 031 017 000 Old_age Always - 45408425 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 106661217842669 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1596433859 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 280736335 SMART Error Log Version: 1 No Errors Logged Thanks in advance. BTW, both drives are Seagate Barracuda 1TB SATA 3 and are 2 years old. BC -- Using openSUSE 13.1, KDE 4.13.3 & kernel 3.16.1-7 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 26

[opensuse] offtopic: laptop repair
by Greg Freemyer 23 Sep '14

23 Sep '14

Alright, after a decade or more of routinely carrying a laptop around I just broke my first screen. It's for a Dell XPS L502X. Looks like I can spend anywhere from $60 to $300 to replace it. (At $300 it may be smarter to replace it?) It looks like the 2 basic options are buying a complete lid with the screen and bezel already toghether, or I can buy just a screen. I'm reasonably handy with tools, so I'm wondering what the smart thing is for me to do. Any advice? On my own, I will likely order this one from Newegg: http://www.newegg.com/Product/Product.aspx?Item=9SIA2721DJ3574&cm_re=dell_x… Any gotcha's I should be aware of? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 11

[opensuse] Installing Java
by James Knott 23 Sep '14

23 Sep '14

I've tried installing Oracle Java from both rpm and tar, but for some reason, it does not appear to install properly. To enable Java in a browser, I'm supposed to create a symlink from either libjavaplugin_oji or libjavaplugin_oji.so to the .mozilla/plugin directory. However, after installing by either method, those files do not appear anywhere on my system. Even the directory those files are supposed to be in don't appear. Suggestions? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5