August 2014 - YaST Development - openSUSE Mailing Lists

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 06 Aug '14

06 Aug '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-ftp-server: - Using different defaults about logging for vs/pure-ftpd (bnc#888287) (4 days) https://github.com/yast/yast-ftp-server/pull/5 Pending requests in repository yast-storage: - - fixed used-by information for multipath with LVM (bnc#888838) (6 days) https://github.com/yast/yast-storage/pull/98 Pending requests in repository yast-theme: - A stub of a README. (11 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (26 days) https://github.com/yast/yast-cio/pull/7 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] very unimpressed by found changes
by Felix Miata 04 Aug '14

04 Aug '14

Via HTTP I just did my first Factory installation in several months. White on brown is ugly. Is there or will there be an option for an installation GUI theme more like the old, black text on light background, with visible borders, scrollers, and tabs where applicable? Red on brown (in changes to partitioning) is barely legible. Green on brown on summary screen is virtually invisible. I can tell something is there, but not what it says, and there is no popup to explain whatever is hovered. In expert partitioner, there are "checkboxes" lacking boxes. I don't like that either. Once they are all unchecked, there is nothing to indicate boxes exist, much less where they are. This particular section has always puzzled me: "visible information on storage devices" for what (installation summary/storage settings) purpose? When I open Fstab options after having selected volume label as the default mount by, why for a freshly formatted target / partition with volume label is UUID preselected instead of Volume Label? Seeing parts of the content of the fullscreen "Edit Partition /dev/sda16" spilling out from under that (apparently) borderless brown void that is the Fstab options "window" is seriously unimpressive. In detailed software selection those itty bitty things in left pane apparently representing checked boxes need to be much bigger to tell that's what they're supposed to be. Choice between no bootloader and Grub2 is very Fedora-ish, would cause all my installations to be much more complicated, since I have no need and thus no use for the overcomplicated monster (to be obsoleted in not too distant future by UEFI) that is Grub2. Since Grub remains available to select among packages, will it be possible to set it up from running the grub shell on tty2 before rebooting from the installer (I tried simply 'grub', which produces command not found from bash)? Towards the end it claimed to be installing boot manager even though Grub2 was tabooed, produced no error message. Neither did it leave a /boot/grub/menu.lst to be used as configfile from elsewhere, though it did produce a device.map. /etc/sysconfig/bootloader is too stripped to be useful. Trying to chainload it produced the invalid executable format message I'm used to seeing on installations containing no bootloader on /. I copied and edited menu.lst from 13.1 for now, and gfxboot and perl-Bootloader apparently work as always even though I had to manually configure Grub. y2logs: http://fm.no-ip.com/Tmp/SUSE/y2l-gx28b-os132-201407.tgz -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 11

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 04 Aug '14

04 Aug '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-theme: - A stub of a README. (9 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (24 days) https://github.com/yast/yast-cio/pull/7 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] sle12 network config in linuxrc
by Steffen Winterfeldt 01 Aug '14

01 Aug '14

As the latest linuxrc with the new network code mostly active accidentally slipped into rc1, I better describe the changes now. :-) == network config before sle12 == ** These options are still available in sle12. ** If the repo location is a network url you either get a dhcp config or can supply a static config, e.g. hostip=10.0.1.1/24 gateway=10.0.1.254 nameserver=10.0.1.2 domain=suse.de This config is tried on every network interface in turn until it works. If you don't have a network repo you can still get a network config by netsetup=1 Also, if you do an ssh or vnc installation, linuxrc knows you'll need a network config. The major drawback here is that you can only configure a single interface. == network config in sle12 == That's why there is now the new 'ifcfg' option. The example above would look like static: ifcfg=*=10.0.1.1/24,10.0.1.254,10.0.1.2,suse.de dhcp: ifcfg=*=dhcp The general syntax is ifcfg=interface_name_or_pattern[.vlanid]=ip_addr_list,gateway,namserver_list,ns_search_list[,any_ifcfg_option=foo,...] ifcfg=interface_name_or_pattern[.vlanid]=dhcp[46] It will create ifcfg/ifroute files for all matching interfaces (dhcp) resp. the first matching interface (static setup), then run 'wicked ifup all' and if wicked managed to bring up at least one interface, assume that tings worked. ip_addr_list and namserver_list are space-separated lists, so don't forget to quote the 'ifcfg' option value. If you use a wildcard pattern, it is matched against all existing interfaces and mac addresses; if you use just an interface name, a config is created regardless whether the interface exists. A wildcard pattern will never match 'lo'. You can have several 'ifcfg' options, of course. Advantages: - more than one interface can be configured - supports vlan setup (e.g. ifcfg=eth0.55=dhcp) - can set arbitray ifcfg options (ifcfg=eth3=dhcp,STARTMODE=nfsroot) - no trial-and-error on all interfaces Note: the transition to the new code is WIP. You may find occasionally that linuxrc thinks the network is not configured even though it really is. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 5

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 01 Aug '14

01 Aug '14

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-theme: - A stub of a README. (6 days) https://github.com/yast/yast-theme/pull/40 Pending requests in repository yast-cio: - Coverage with Travis and Coveralls (21 days) https://github.com/yast/yast-cio/pull/7 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0