I created a merge request for desktop-data three weeks ago. It's just
a minor patch that doesn't really fix anything but a warning from
kbuildsycoca4. I'm not sure about how Gitorious works, maintainers are
supposed to notice the "1" in the merge requests section or they
receive an email notifying it?
And since I'm on it. Since I updated my 11.3 system to KDE to 4.5 the
"inline" part of the menu is not honored... Expected behavior? Known
problem?
--
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 all -
Since technically we're in feature freeze for 11.4, I thought I'd put
this out for discussion.
Factory is currently using 2.6.36 which was released 3 weeks ago.
Upstream versions tend to take about 10-11 weeks, on average, to
release. The scheduled release for the first openSUSE RC is Jan 20.
The scheduled release for the first RC is Jan 20. The typical
development time for a kernel release, on average, is about 10-11 weeks.
That puts the release of 2.6.37 around Dec 29 to Jan 12.
That sounds like kind of a tight window, but the reality is that the
differences in the later kernel RCs tend to be small and fix bugs. The
"real" development happens in -rc1, which was released about two weeks
ago. Later -rcs serve to stabilize the development that went into -rc1.
So, the the feature freeze aspect of it will be a one-shot, when I
update to -rc1. (Actually, I hardly ever update to -rc1 and instead use
- -rc2 which tends to be more stable).
I've already done the merge work for 2.6.37-rc1 since the master kernel
always tracks the latest upstream. Xen is the lone exception, as it
usually is, but Jan Beulich has been great about getting that completed
shortly after I do the update. This time might be a little more
difficult because much of the Xen code has been merged into the mainline
kernel so there's some sorting out to be done.
As far as testing goes, we're still early enough that we won't lose a
lot of effort. I'd update Factory to 2.6.37-rc2 as soon as it is
released upstream, which should be this week. Our usual corps of
dedicated testers can dig in quickly. In my experience, though, the
number of testers drastically increases around the RC1 release. I wish
it weren't so, but it is. So revving the kernel now isn't likely to toss
out a lot of testing.
The biggest "feature" I'm going for is not having to backport fixes from
2.6.37. The BKL removal patches and the VFS scalability patches are
going to improve performance on multicore systems. The removal of I/O
barriers should also be pretty noticeable but I haven't had time to
verify that yet.
So, opinions?
- -Jeff
Features that are going into 2.6.37:
- - The inode portion of the VFS scalability patches
- - More BKL removal, including parts of the core kernel
- - Block I/O can be throttled via cgroups
- - Simple pNFS support
- - In-kernel PPTP (tunneling) acceleration
- - "Lazy" inode table creation for ext4 to allow faster fs creation
- - Batched discard support, which allows the file system to advise the
block layer to use the TRIM command. This allows online TRIMs, but
is only implemented in ext4 so far.
- - Xen dom0 support (mostly)
- - The usual round of bug fixes.
- - fanotify
- - Block barriers have been removed[1]
Drivers:
- - Systems and processors:
- Flexibility Connect boards
- Telechips TCC ARM926-based systems
- Telechips TCC8000-SDK development kits
- Vista Silicon Visstrim_m10 i.MX27-based boards
- LaCie d2 Network v2 NAS boards
- Qualcomm MSM8x60 RUMI3 emulators
- Qualcomm MSM8x60 SURF eval boards
- Eukrea CPUIMX51SD modules
- Freescale MPC8308 P1M boards
- APM APM821xx evaluation boards
- Ito SH-2007 reference boards
- IBM "SMI-free" realtime BIOS's
- MityDSP-L138 and MityDSP-1808 systems
- OMAP3 Logic 3530 LV SOM boards
- OMAP3 IGEP modules
- taskit Stamp9G20 CPU modules
- aESOP Samsung S5PV210-based Torbreck boards
- - Block:
- Chelsio T4 iSCSI offload engines
- Cypress Astoria USB SD host controllers
- Marvell PXA168/PXA910/MMP2 SD host controllers
- ST Microelectronics Flexible Static Memory Controllers
- - Input:
- Roccat Pyra gaming mice
- UC-Logic WP4030U, WP5540U and WP8060U tablets
- several varieties of Waltop tablets
- OMAP4 keyboard controllers
- NXP Semiconductor LPC32XX touchscreen controllers
- Hanwang Art Master III tablets
- ST-Ericsson Nomadik SKE keyboards
- ROHM BU21013 touch panel controllers
- TI TNETV107X touchscreens
- - Miscellaneous:
- Freescale eSPI controllers
- Topcliff platform controllher hub devices
- OMAP AES crypto accelerators
- NXP PCA9541 I2C master selectors
- Intel Clarksboro memory controller hubs
- OMAP 2-4 onboard serial ports
- GPIO-controlled fans
- Linear Technology LTC4261 Negative Voltage Hot Swap Controller I2C
interfaces
- TI BQ20Z75 gas gauge ICs
- OMAP TWL4030 BCI chargers
- ROHM ROHM BH1770GLC and OSRAM SFH7770 combined ALS and proximity sensors
- Avago APDS990X combined ALS and proximity sensors
- Intersil ISL29020 ambient light sensors
- Medfield Avago APDS9802 ALS sensor modules
- Basic, memory-mapped GPIO controllers
- Intel Topcliff GPIO controllers
- Intel Moorestown/Medfield i2c controllers
- IDT CPS Gen.2 SRIO RapidIO switches
- Freescale i.MX DMA engines
- ARM PrimeCell PL080 or PL081 DMA engines
- Cypress West Bridge Astoria controllers
- USB ENE card readers
- Asahi Kasei AK8975 3-axis magnetometers
- OLPC XO display controller devices
- Analog Devices AD799x analog/digital converters
- Winbond/Nuvoton W83795G/ADG hardware monitoring chips
- Flarion OFDM usb and pcmcia modems
- Maxim MAX8952 and MAX8998 Power Management ICs
- National Semiconductors LP3972 PMIC regulators
- Broadcom BCM63xx hardware watchdogs
- - Network:
- Brocade 1010/1020 10Gb Ethernet cards
- Conexant CX82310 USB ethernet ports
- Atheros AR9170 "otus" 802.11n USB devices
- Topcliff PCH Gigabit Ethernet controllers
- Intel Topcliff platform controller hub CAN interfaces
- Technologic Systems TS-CAN1 PC104 peripheral boards
- SBE wanPMC-2T3E3 interfaces
- RealTek RTL8712U (RTL8192SU) Wireless LAN NICs (replaces older
rtl8712 driver)
- Atheros AR6003 wireless interface controllers
- Beeceem USB Wimax adapters
- Broadcom bcm43xx wireless chipsets
- - Sound:
- Marvell 88pm860x codecs
- TI WL1273 FM radio codecs
- HP iPAQ RX1950 audio devices
- Native Instruments Traktor Kontrol S4 audio devices
- Aztech Sound Galaxy AZT1605 and AZT2316 ISA sound cards
- Wolfson Micro WM8985 and WM8962 codecs
- Wolfson Micro WM8804 S/PDIF transceivers
- Samsung S/PDIF controllers
- Cirrus Logic EP93xx AC97 controllers
- Intel MID SST DSP devices
- - USB: Intel Langwell USB OTG transceivers
- YUREX "leg shake" sensors
- USB-attached SCSI devices
- - Video4Linux2: remotes using the RC-5 (streamzap) protocol
- Konica chipset-based cameras
- Sharp IX2505V silicon tuners
- LME2510 DM04/QQBOX USB DVB-S boxes
- Samsung s5h1432 demodulators
- Several new Conexant cx23417-based boards
- Nuvoton w836x7hg consumer infrared transceivers
- OmniVision OV6650 sensors
- OMAP1 camera interfaces
- Siliconfile SR030PC30 VGA cameras
- Sony imx074 sensors
- VIA integrated chipset camera controllers
- -Jeff
[1] This is because they were a very big hammer that had a reputation
for killing performance. They're necessary for safely using journals on
devices with write caching enabled, but were implemented by flushing the
entire I/O queue to physical media -- not just "to disk" which includes
the disk's write cache. The new implementation will still use the
flush-to-media feature but will not stall the i/o queue.
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkzhW0YACgkQLPWxlyuTD7JgBACbBfR+uJwfKKnEcBZIg/KeIj/S
hikAnRiL9nG50QoKZkrn1AsmGljnGvYn
=T/Hp
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
I wonder whether our IPv6 settings are the right ones after reading the following article (sorry, German only):
http://www.heise.de/newsticker/meldung/IPv6-Smartphones-gefaehrden-Privatsp…
which references:
http://www.heise.de/netze/hotline/IPv6-anonym-1100727.html
We set use_tempaddr to 0 by default (disabling privacy extensions) and set it to 1
if enabled. The article advises to use 2.
Background: By default (value 0) my IPv6 address will be derived from my hardware
(macaddr) and therefore be the same independend how I connect to the internet. So,
it's easy to track my computer...
So, my proposal is to do the following two changes:
* Use 2 instead of 1 in /etc/rc.d/boot.ipconfig for enabling the privacy extensions
* Set IPV6_PRIVACY=yes in /etc/sysconfig/sysctl
Any concerns with this change?
Btw. here's an Ubuntu bugreport:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/176125
and Windows (since XP) is doing it the same way on desktops.
Andreas
--
Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
openSUSE 11.3 on one box and openSUSE 11.4 Milestone 4 on the other.
I have a message that says the built modules not found. When I check
e.g /lib/modules/2.7.37-rc3-git7-smp, most modules are zero bytes long.
I have to "make modules_install" and use modprobe on each.
To get the network up on the 11.3 box "modprobe r6189" then "rcnetwork
restart", "modprobe rtl8187", "/etc/init.d/network-remotefs start",
etc., etc.
Then ifconfig is OK for those devices.
eth_s1_0 Link encap:Ethernet HWaddr 00:1C:F0:BB:14:E1
inet addr:192.168.10.10 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::21c:f0ff:febb:14e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1927 errors:0 dropped:0 overruns:0 frame:0
TX packets:1923 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:287532 (280.7 Kb) TX bytes:283044 (276.4 Kb)
Interrupt:17 Base address:0xe000
wlan0 Link encap:Ethernet HWaddr 00:15:AF:23:04:37
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:afff:fe23:437/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4324 (4.2 Kb) TX bytes:18470 (18.0 Kb)
On 11.3 module-init-tools-3.12-1.3.x86_64
On 11.4 Milestone 4 module-init-tools-3.12-5.3.x86_64
tindog:/usr/src/linux-2.6.37-rc3-git7 # grep MODULE .config
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODULE_SRCVERSION_ALL=y
Another guy has emailed me saying he's seen the same.
11.3
====
gcc version 4.5.0 20100604 [gcc-4_5-branch revision 160292] (SUSE Linux)
11.4 Milestone 4
================
gcc version 4.5.1 20101116 [gcc-4_5-branch revision 166793] (SUSE Linux)
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Building xine-lib-1.1.19 on 11.3 x86_64, I hit this error.
/usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/ld:
/usr/lib64/libxcb-shape.a(shape.o): relocation R_X86_64_32 against
`.rodata' can not be used when making a shared object; recompile with
-fPIC
/usr/lib64/libxcb-shape.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[3]: *** [xineplug_vo_out_xcbshm.la] Error 1
make[3]: Leaving directory `/ftp/dec10/xine-lib-1.1.19/src/video_out'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/ftp/dec10/xine-lib-1.1.19/src/video_out'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/ftp/dec10/xine-lib-1.1.19/src'
make: *** [all-recursive] Error 1
It was a rogue library lying around from 2009
"zypper rm xorg-x11-libxcb-unstable-devel" fixed it.
When zypper upgraded it installed xorg-x11-libxcb-devel and left files
from the old one in place. It seems it's not able to detect and deal
with a package name that differs but offers largely the same files, so
it leaves any file that isn't part of the current package in place.
In fact it leaves the old package installed.
I shall open a bug later.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
hi folks,
as you might know, since virtualbox 4.0.0 "usb guest support" feature
is now open source code,
but during tests i found the problem : virtualbox needs full access to
usb nodes, which of course, could lead to serious security problem
(see bnc#664520 for details) - this means that (currently) virtualbox
(provided by suse) doesn't have usb guest support enabled, by default
as a workaround I added comment with two udev lines, which creates usb
nodes in /dev/vboxusb/ dir with r/w access for vboxusers group (which
feeds the virtualbox's needs), so after enabling these two lines (in
/etc/udev/rules.d/60-vboxdrv.rules) , your attached usb devices will
be available also in virtualized guest system, but please keep in mind
this could be real security problem !
JFYI how Oracle's virtualbox rpm deal with this situation
(unacceptable due to possible security issue - basically they do the
same as we with our two line comment in .rules file):
- in post install of specfile : udev rule is added,
http://www.virtualbox.org/browser/trunk/src/VBox/Installer/linux/rpm/Virtua…
- this udev rule is triggered if usb device is added/removed - and it
call VBoxCreateUSBNode.sh script
http://www.virtualbox.org/browser/trunk/src/VBox/Installer/linux/VBoxCreate…
- VBoxCreateUSBNode.sh (build /dev/vboxusb dir with usb devices and
grand acces to $group) || (destroy /dev/vboxusb device)
bye
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I tried to upgrade my 11.4 guest running zypper dup, then zypper
downloaded/installed more than 1000 pkgs, at reboot X stops to starts.
Then I downloaded 11.4 Build 1034-i586 and attempted to install it as
guest on Virtualbox 3.2.12, in this case it has been a worst case since
installation crashes after drivers loading.
Wonder if are there some workaround in order to install M6 on Virtualbox
PUEL.
Cheers,
--
opensuse 11.2 - Linux 2.6.31.14-0.6-desktop x86_64
AMD Turion(tm) 64 Mobile Technology MK-36 - GeForce Go 6150
Gnome 2.28.2
I now know why I've stayed away from maintaining gstreamer. It's members
are strewn across from multimedia:libs to kde. I'm trying to get the <
11.4 members to build, first problem was no gobject-introspection was
new enough, I aggregated it from GNOME:Factory but no 11.2 rpms so I've
linked it. Next somebody put pkg-config() s in the Buildrequires of a
few packages without a suse_version conditional to take care of 11.2,
see opensuse-kde mail subject "Gstreamer update (opensuse+packman) break
pulseaudio on 11.2 / 4.4.4 Stable" this is when I discover
python-gstreamer lives in kde.
My proposal is take gstreamer out of multimedia and (I see GNOME:Factory
already has it) move it to where somebody cares about it in kde.
ATM I feel like the only multimedia maintainer, I'm getting an ulcer and
I don't get paid.
Thanks
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
is there some kind of statement if source services should or should/must
not be used for openSUSE:Factory packages? I cannot remember to have
read anything about that before.
Or does it matter at all?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
