From jsmeix at suse.de Mon Jun 30 01:37:24 2014 From: jsmeix at suse.de (Johannes Meixner) Date: Mon, 30 Jun 2014 09:37:24 +0200 (CEST) Subject: [sles-beta] default btrfs subvolumes under / in SLES 12 In-Reply-To: References: Message-ID: Hello Chris, On Jun 27 16:59 Magargee, Chris - Contractor {BIS} wrote (excerpt): > Can I be added to? I added you to CC of https://bugzilla.novell.com/show_bug.cgi?id=882982 > We have similar requirements/interests as Wendy > with the default and new subvolumes for Root. That bug report is mainly about AutoYaST and only partially about btrfs subvolumes and it does not at all explain any reasoning behind why SLE12 has its particular btrfs subvolumes default settings. Please do not misuse that bug report for issues regarding the SLE12 btrfs subvolumes default settings. In case of such issues please file new separated reports. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer From fcrozat at suse.com Mon Jun 30 01:53:23 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 30 Jun 2014 09:53:23 +0200 Subject: [sles-beta] "/var/lock/subsys" missing in SLES12 In-Reply-To: References: Message-ID: <1404114803.4202.31.camel@par-r81vxc7.par.novell.com> Le dimanche 29 juin 2014 ? 23:59 -0700, Nikita Kodkani a ?crit : > Hi, > > > > Earlier in SLES11sp3, ?/var/lock/subsys? was being used for > maintaining locks. Looks like in SLES12 it has been removed. > > Is it deprecated or missing in current beta release? > > If it?s deprecated what is the recommended way to add locks in > SLES12? /var/lock is now a symlink to /run/lock (which is a tmpfs). Those locks were using by RH initscripts to prevent restarting initscripts, which is now longer used with the switch to system. I would recommend you just write your file in /var/lock (or /run/lock) directly. -- Frederic Crozat Project Manager Enterprise Desktop SUSE From gjn at gjn.priv.at Mon Jun 30 01:56:21 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Mon, 30 Jun 2014 09:56:21 +0200 Subject: [sles-beta] YaST2 ??? Message-ID: <5243338.vTISNrKFoi@gjn.priv.at> Hello, have we a docu what the new Yast2 can configure and what is deleted? The most of the featcher is gon. I mean all for the consumer nice featcher are deleted. I tested a master Ldap / kerberos installation, this is not possible with Yast2 also the Mirror config is broken usw. The nice quick view for ldap is gon. What can we do with the new YaST2? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From Klaus.Gmeinwieser at oce.com Mon Jun 30 02:54:06 2014 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Mon, 30 Jun 2014 10:54:06 +0200 Subject: [sles-beta] Recent Autoyast Documentation Message-ID: <53B125AE.7090703@oce.com> Hi all, is there a recent doc for all SLE 12 autoyast things available? I played around a lot with the Beta9 YaST2 autoinstallation to generate the necessary xml snippets, but some of those are invalid (e.g. grub1 is no longer supported I learned) but I did not get information on the stuff to do an autoinstallation (1.) without reboot and (2.) where the network settings may be provided by the user by means of a "questionnaire popup". As those 2 things would be a great advantage for installation to provide the hostname, IP, etc. at installation time, I am still trying to get this done Please advise how I can get the matching doc(s) or any helpful info on this Thanks a lot in advance Klaus -- Klaus Gmeinwieser T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 E klaus.gmeinwieser at oce.com W www.oce.com Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company P.O. Box 1260 ? 85581 Poing Siemensallee 2 ? 85586 Poing ? Germany Oc? enables its customers to manage their documents efficiently and effectively by offering innovative print and document management products and services for professional environments. Oc? Printing Systems GmbH & Co. KG The company is a limited partnership with its registered office in Poing ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 05 443 General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht M?nchen) Executive Officer: Andr? Mittelsteiner This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. From jsmeix at suse.de Mon Jun 30 04:06:50 2014 From: jsmeix at suse.de (Johannes Meixner) Date: Mon, 30 Jun 2014 12:06:50 +0200 (CEST) Subject: [sles-beta] default btrfs subvolumes under / in SLES 12 In-Reply-To: References: Message-ID: Hello, On Jun 27 15:25 Wendy Palm wrote (excerpt): > In the default installation of SLES 12, these btrfs subvolumes > are created underneath /. What exactly do you mean with "underneath /"? In particular what exactly do you mean with '/' here? In other words: >From what point of view is '/' the root of exactly what in SLE12? On my SLES12-beta8 installation with default partitioning and default filesystem (btrfs with our default subvolumes) I get: ------------------------------------------------------------------------- # btrfs subvolume list -a / ID 257 gen 487 top level 5 path /@ ID 258 gen 396 top level 257 path @/boot/grub2/i386-pc ID 259 gen 396 top level 257 path @/boot/grub2/x86_64-efi ID 260 gen 396 top level 257 path @/home ID 261 gen 396 top level 257 path @/opt ID 262 gen 396 top level 257 path @/srv ID 263 gen 486 top level 257 path @/tmp ID 264 gen 408 top level 257 path @/usr/local ID 265 gen 396 top level 257 path @/var/crash ID 266 gen 396 top level 257 path @/var/lib/mailman ID 267 gen 396 top level 257 path @/var/lib/named ID 268 gen 396 top level 257 path @/var/lib/pgqsl ID 269 gen 487 top level 257 path @/var/log ID 270 gen 396 top level 257 path @/var/opt ID 271 gen 491 top level 257 path @/var/spool ID 272 gen 486 top level 257 path @/var/tmp ID 276 gen 486 top level 257 path @/.snapshots ID 277 gen 55 top level 276 path /@/.snapshots/1/snapshot ID 278 gen 56 top level 276 path /@/.snapshots/2/snapshot # btrfs subvolume get-default / ID 257 gen 487 top level 5 path @ # mount | grep btrfs /dev/sda2 on / type btrfs (rw,relatime,space_cache) /dev/sda2 on /.snapshots type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/tmp type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/spool type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/opt type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/log type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/lib/mailman type btrfs (rw,relatime,space_cache) /dev/sda2 on /srv type btrfs (rw,relatime,space_cache) /dev/sda2 on /usr/local type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/lib/named type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/lib/pgqsl type btrfs (rw,relatime,space_cache) /dev/sda2 on /tmp type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/crash type btrfs (rw,relatime,space_cache) /dev/sda2 on /opt type btrfs (rw,relatime,space_cache) /dev/sda2 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache) /dev/sda2 on /home type btrfs (rw,relatime,space_cache) /dev/sda2 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache) # mkdir /tmp/btrfs-default # mount -t btrfs /dev/sda2 /tmp/btrfs-default # ls /tmp/btrfs-default bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux .snapshots srv sys tmp usr var # ls / bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux .snapshots srv sys tmp usr var # mkdir /tmp/btrfs-toplevel # mount -t btrfs -o subvolid=0 /dev/sda2 /tmp/btrfs-toplevel/ # ls /tmp/btrfs-toplevel/ @ # ls /tmp/btrfs-toplevel/@ bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux .snapshots srv sys tmp usr var # mount | grep tmp/btrfs /dev/sda2 on /tmp/btrfs-toplevel type btrfs (rw,relatime,space_cache) /dev/sda2 on /tmp/btrfs-default type btrfs (rw,relatime,space_cache) ------------------------------------------------------------------------- Note our special '/@' btrfs default subvolume and its matching '/@' directory which makes it ambiguous what '/' means. Therefore my above question: >From what point of view means '/' the root of exactly what in SLE12? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer From schubi at suse.de Mon Jun 30 04:16:59 2014 From: schubi at suse.de (Stefan Schubert) Date: Mon, 30 Jun 2014 12:16:59 +0200 Subject: [sles-beta] Recent Autoyast Documentation In-Reply-To: <53B125AE.7090703@oce.com> References: <53B125AE.7090703@oce.com> Message-ID: <53B1391B.4010504@suse.de> Hi, the "latest" documentation can be found here: http://docserv.suse.de/documents/SLES12/SLES-autoyast/pdf/book.autoyast_remarks_color_draft_meta_en.pdf But we really have to update it. Sorry for being so late :-( A nice example for asking network settings has been posted by a customer in bugzilla sometime ago: networking,dns,hostname Enter Hostname initial /tmp/ask_hostname 1 1 networking,interfaces,0,ipaddr Enter IP-Address initial 2 1 More general examples for the asking can be found here: https://github.com/yast/yast-autoinstallation/blob/master/test_xml/ask.xml https://github.com/yast/yast-autoinstallation/blob/master/test_xml/ask2.xml You can suppress rebooting by using these settings in the general options: false false Greetings Stefan Schubert Am 30.06.2014 10:54, schrieb Klaus Gmeinwieser: > Hi all, > > is there a recent doc for all SLE 12 autoyast things available? > > I played around a lot with the Beta9 YaST2 autoinstallation to generate > the necessary xml snippets, but some of those are invalid (e.g. grub1 is > no longer supported I learned) but I did not get information on the > stuff to do an autoinstallation (1.) without reboot and (2.) where the > network settings may be provided by the user by means of a > "questionnaire popup". > > As those 2 things would be a great advantage for installation to provide > the hostname, IP, etc. at installation time, I am still trying to get > this done > > Please advise how I can get the matching doc(s) or any helpful info on > this > > Thanks a lot in advance > Klaus > > -- > Klaus Gmeinwieser > T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 > E klaus.gmeinwieser at oce.com W www.oce.com > > Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company > P.O. Box 1260 ? 85581 Poing > Siemensallee 2 ? 85586 Poing ? Germany > > Oc? enables its customers to manage their documents efficiently and > effectively by offering > innovative print and document management products and services for > professional > environments. > > Oc? Printing Systems GmbH & Co. KG > The company is a limited partnership with its registered office in Poing > ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 > 05 443 > > General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH > Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht > M?nchen) > Executive Officer: Andr? Mittelsteiner > This message and attachment(s) are intended solely for use by the > addressee and may contain information that is privileged, confidential > or otherwise exempt from disclosure under applicable law. If you are > not the intended recipient or agent thereof responsible for delivering > this message to the intended recipient, you are hereby notified that > any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, > please notify the sender immediately by telephone and with a 'reply' > message. Thank you for your co-operation. > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From urs.frey at post.ch Mon Jun 30 04:21:13 2014 From: urs.frey at post.ch (urs.frey at post.ch) Date: Mon, 30 Jun 2014 10:21:13 +0000 Subject: [sles-beta] default btrfs subvolumes under / in SLES 12 In-Reply-To: References: Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B5E1C@HXMB12.pnet.ch> Hi I get a bit confused seeing /home and /tmp also under the btrfs tree in context production environment. In a production environment /tmp must be an independent filesystem and partition, because you never know what users gonna place on /tmp and possibly filling the filesystem. And /home I certainly do not want to snapper undo changes, because this is in each user's very own competence if one deletes, or copies of whatever. As system admin I wil newer undo in yast for some specific user files under /home. >From production admin context /tmp and /home are really out of btrfs scope and should be treated as data spaces. RPM and zypper will certainly never use /home or /tmp in context of a possible undo changes.. But in case you have a single user installation it might make sense to have everything under btrfs. Best regards Urs Frey????????????????????????????????????????????? Post CH AG Informationstechnologie IT Betrieb Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Johannes Meixner Gesendet: Monday, June 30, 2014 12:07 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] default btrfs subvolumes under / in SLES 12 Hello, On Jun 27 15:25 Wendy Palm wrote (excerpt): > In the default installation of SLES 12, these btrfs subvolumes > are created underneath /. What exactly do you mean with "underneath /"? In particular what exactly do you mean with '/' here? In other words: >From what point of view is '/' the root of exactly what in SLE12? On my SLES12-beta8 installation with default partitioning and default filesystem (btrfs with our default subvolumes) I get: ------------------------------------------------------------------------- # btrfs subvolume list -a / ID 257 gen 487 top level 5 path /@ ID 258 gen 396 top level 257 path @/boot/grub2/i386-pc ID 259 gen 396 top level 257 path @/boot/grub2/x86_64-efi ID 260 gen 396 top level 257 path @/home ID 261 gen 396 top level 257 path @/opt ID 262 gen 396 top level 257 path @/srv ID 263 gen 486 top level 257 path @/tmp ID 264 gen 408 top level 257 path @/usr/local ID 265 gen 396 top level 257 path @/var/crash ID 266 gen 396 top level 257 path @/var/lib/mailman ID 267 gen 396 top level 257 path @/var/lib/named ID 268 gen 396 top level 257 path @/var/lib/pgqsl ID 269 gen 487 top level 257 path @/var/log ID 270 gen 396 top level 257 path @/var/opt ID 271 gen 491 top level 257 path @/var/spool ID 272 gen 486 top level 257 path @/var/tmp ID 276 gen 486 top level 257 path @/.snapshots ID 277 gen 55 top level 276 path /@/.snapshots/1/snapshot ID 278 gen 56 top level 276 path /@/.snapshots/2/snapshot # btrfs subvolume get-default / ID 257 gen 487 top level 5 path @ # mount | grep btrfs /dev/sda2 on / type btrfs (rw,relatime,space_cache) /dev/sda2 on /.snapshots type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/tmp type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/spool type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/opt type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/log type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/lib/mailman type btrfs (rw,relatime,space_cache) /dev/sda2 on /srv type btrfs (rw,relatime,space_cache) /dev/sda2 on /usr/local type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/lib/named type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/lib/pgqsl type btrfs (rw,relatime,space_cache) /dev/sda2 on /tmp type btrfs (rw,relatime,space_cache) /dev/sda2 on /var/crash type btrfs (rw,relatime,space_cache) /dev/sda2 on /opt type btrfs (rw,relatime,space_cache) /dev/sda2 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache) /dev/sda2 on /home type btrfs (rw,relatime,space_cache) /dev/sda2 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache) # mkdir /tmp/btrfs-default # mount -t btrfs /dev/sda2 /tmp/btrfs-default # ls /tmp/btrfs-default bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux .snapshots srv sys tmp usr var # ls / bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux .snapshots srv sys tmp usr var # mkdir /tmp/btrfs-toplevel # mount -t btrfs -o subvolid=0 /dev/sda2 /tmp/btrfs-toplevel/ # ls /tmp/btrfs-toplevel/ @ # ls /tmp/btrfs-toplevel/@ bin boot dev etc home lib lib64 media mnt opt proc root run sbin selinux .snapshots srv sys tmp usr var # mount | grep tmp/btrfs /dev/sda2 on /tmp/btrfs-toplevel type btrfs (rw,relatime,space_cache) /dev/sda2 on /tmp/btrfs-default type btrfs (rw,relatime,space_cache) ------------------------------------------------------------------------- Note our special '/@' btrfs default subvolume and its matching '/@' directory which makes it ambiguous what '/' means. Therefore my above question: >From what point of view means '/' the root of exactly what in SLE12? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From schubi at suse.de Mon Jun 30 04:38:24 2014 From: schubi at suse.de (Stefan Schubert) Date: Mon, 30 Jun 2014 12:38:24 +0200 Subject: [sles-beta] Recent Autoyast Documentation In-Reply-To: <53B1391B.4010504@suse.de> References: <53B125AE.7090703@oce.com> <53B1391B.4010504@suse.de> Message-ID: <53B13E20.8080402@suse.de> Am 30.06.2014 12:16, schrieb Stefan Schubert: > > > You can suppress rebooting by using these settings in the general > options: > > false -- since 11.0 --> > false -- since 11.0 --> But these settings are valid for the second installation stage only: /"final_halt/ and /final_reboot/ have been introduced with openSUSE 11.0 and SLES11. You can reboot or halt the machine after installation and configuration are finished at the end of stage 2. " -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From kukuk at suse.de Mon Jun 30 04:43:56 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Mon, 30 Jun 2014 12:43:56 +0200 Subject: [sles-beta] default btrfs subvolumes under / in SLES 12 In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B5E1C@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0F9B5E1C@HXMB12.pnet.ch> Message-ID: <20140630104356.GA3716@suse.de> On Mon, Jun 30, urs.frey at post.ch wrote: > Hi > I get a bit confused seeing /home and /tmp also under the btrfs tree in context production environment. > In a production environment /tmp must be an independent filesystem and partition, because you never know what users gonna place on /tmp and possibly filling the filesystem. > And /home I certainly do not want to snapper undo changes, because this is in each user's very own competence if one deletes, or copies of whatever. As system admin I wil newer undo in yast for some specific user files under /home. /home is on a seperate XFS partition as long as you have enough disk space. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From lukas.ocilka at suse.com Mon Jun 30 04:48:46 2014 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Mon, 30 Jun 2014 12:48:46 +0200 Subject: [sles-beta] YaST2 ??? In-Reply-To: <5243338.vTISNrKFoi@gjn.priv.at> References: <5243338.vTISNrKFoi@gjn.priv.at> Message-ID: <53B1408E.9060508@suse.com> On 30.6.2014 09:56, G?nther J.Niederwimmer wrote: > Hello, > > have we a docu what the new Yast2 can configure and what is deleted? > > The most of the featcher is gon. > > I mean all for the consumer nice featcher are deleted. > > I tested a master Ldap / kerberos installation, this is not possible with > Yast2 also the Mirror config is broken usw. > > The nice quick view for ldap is gon. > > What can we do with the new YaST2? Hi G?nther, The whole LDAP/Kerberos stuff has been rewritten for SLE 12 by Peter Varkoly and Christian Kornacker. We have now two new Yast modules that replace the old functionality: * yast2-auth-server * yast2-auth-client Could you, please, give us your use case where you would describe what you need to configure and what are your expectations from this configuration? We can try to help you, but we need to know what the problem is. Thanks in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux From Klaus.Gmeinwieser at oce.com Mon Jun 30 05:03:28 2014 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Mon, 30 Jun 2014 13:03:28 +0200 Subject: [sles-beta] Recent Autoyast Documentation In-Reply-To: <53B1391B.4010504@suse.de> References: <53B125AE.7090703@oce.com> <53B1391B.4010504@suse.de> Message-ID: <53B14400.6010109@oce.com> Hi Stefan, thanks for your quick answer. Unfortunately my proxy tells me the link (to the pdf) is broken - maybe not suse.de? Anyway, I used the SLES11 SP3 doc, which leads to the following - similar code: networking,dns,hostname Enter Hostname Popup initial networking,dns,domain Enter Domain initial for.the.domain As I see, I am missing the inner pathlist tag, but with SLE12 Beta9 the whole "ask tree" is completely ignored! I can start installation, but this leads to a system with a root password I do not know, I set it in the autoyast file. So I need to find out what I missed within the file :( Pls. check for the pdf link, if it is accessible from outside SUSE, so I can correct my file Thx in advance & Rgds Klaus Am 30.06.2014 12:16, schrieb Stefan Schubert: > Hi, > the "latest" documentation can be found here: > http://docserv.suse.de/documents/SLES12/SLES-autoyast/pdf/book.autoyast_remarks_color_draft_meta_en.pdf > > > But we really have to update it. Sorry for being so late :-( > > A nice example for asking network settings has been posted > by a customer in bugzilla sometime ago: > > > > > networking,dns,hostname > > Enter Hostname > initial > > /tmp/ask_hostname > 1 > 1 > > > > networking,interfaces,0,ipaddr > > Enter IP-Address > initial > > > | cut -d > " " -f4]]> > > 2 > 1 > > > > > More general examples for the asking can be found here: > https://github.com/yast/yast-autoinstallation/blob/master/test_xml/ask.xml > https://github.com/yast/yast-autoinstallation/blob/master/test_xml/ask2.xml > > You can suppress rebooting by using these settings in the general options: > > false -- since 11.0 --> > false -- since 11.0 --> > > > Greetings > Stefan Schubert > > > Am 30.06.2014 10:54, schrieb Klaus Gmeinwieser: >> Hi all, >> >> is there a recent doc for all SLE 12 autoyast things available? >> >> I played around a lot with the Beta9 YaST2 autoinstallation to generate >> the necessary xml snippets, but some of those are invalid (e.g. grub1 is >> no longer supported I learned) but I did not get information on the >> stuff to do an autoinstallation (1.) without reboot and (2.) where the >> network settings may be provided by the user by means of a >> "questionnaire popup". >> >> As those 2 things would be a great advantage for installation to provide >> the hostname, IP, etc. at installation time, I am still trying to get >> this done >> >> Please advise how I can get the matching doc(s) or any helpful info on >> this >> >> Thanks a lot in advance >> Klaus >> >> -- >> Klaus Gmeinwieser >> T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 >> E klaus.gmeinwieser at oce.com W www.oce.com >> >> Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company >> P.O. Box 1260 ? 85581 Poing >> Siemensallee 2 ? 85586 Poing ? Germany >> >> Oc? enables its customers to manage their documents efficiently and >> effectively by offering >> innovative print and document management products and services for >> professional >> environments. >> >> Oc? Printing Systems GmbH & Co. KG >> The company is a limited partnership with its registered office in Poing >> ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 >> 05 443 >> >> General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH >> Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht >> M?nchen) >> Executive Officer: Andr? Mittelsteiner >> This message and attachment(s) are intended solely for use by the >> addressee and may contain information that is privileged, confidential >> or otherwise exempt from disclosure under applicable law. If you are >> not the intended recipient or agent thereof responsible for delivering >> this message to the intended recipient, you are hereby notified that >> any dissemination, distribution or copying of this communication is >> strictly prohibited. If you have received this communication in error, >> please notify the sender immediately by telephone and with a 'reply' >> message. Thank you for your co-operation. >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta > > -- Klaus Gmeinwieser T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 E klaus.gmeinwieser at oce.com W www.oce.com Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company P.O. Box 1260 ? 85581 Poing Siemensallee 2 ? 85586 Poing ? Germany Oc? enables its customers to manage their documents efficiently and effectively by offering innovative print and document management products and services for professional environments. Oc? Printing Systems GmbH & Co. KG The company is a limited partnership with its registered office in Poing ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 05 443 General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht M?nchen) Executive Officer: Andr? Mittelsteiner This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. From bjoern.lotz at suse.com Mon Jun 30 05:04:28 2014 From: bjoern.lotz at suse.com (Bjoern Lotz) Date: Mon, 30 Jun 2014 13:04:28 +0200 Subject: [sles-beta] default btrfs subvolumes under / in SLES 12 In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B5E1C@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0F9B5E1C@HXMB12.pnet.ch> Message-ID: <53B1443C.1020707@suse.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 30.06.2014 12:21, urs.frey at post.ch wrote: > And /home I certainly do not want to snapper undo changes, because > this is in each user's very own competence if one deletes, or > copies of whatever. As system admin I wil newer undo in yast for > some specific user files under /home. That is exactly the reason why /home is in a separate subvolume (and also why there are so many subvolumes for various directories). Btrfs snapshots are done on a per-subvolume-basis. So if you do a snapshot of /, /home, being on a separate subvolume, is not affected. Same with undo - if you undo a change on /, /home is not affected because it is on a separate subvolume. The snapper configuration in /etc/snapper/configs/root is only for / - as long as you do not create a separate configs for /home or other subvolumes, no snapshots will be created by default. You can of course always put /tmp and /home on entirely different file systems during the installation, that is up to you. And as Torsten mentioned, indeed /home is put on XFS by default if there is enough disk space. Kind regards, Bj?rn - -- Dr. Bj?rn Lotz, Instructional Designer, CISSP SUSE Linux GmbH, Maxfeldstrasse 5, 90409 N?rnberg Tel: +49 89 8639 9664 Mobil: +49 173 5876724 bjoern.lotz at suse.com PGP-ID: 0xD437D363 - ------------------ SUSE Linux GmbH, N?rnberg; HRB 21284 (AG N?rnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOxRDYACgkQKZToxtQ302MnhwCfc7ovTdUL7pSPF6QDdLc1iju6 +nEAnj5/2yFQI2ZeKyFuwsBz6TMxCK0B =Pzi2 -----END PGP SIGNATURE----- From bjoern.lotz at suse.com Mon Jun 30 05:08:46 2014 From: bjoern.lotz at suse.com (Bjoern Lotz) Date: Mon, 30 Jun 2014 13:08:46 +0200 Subject: [sles-beta] Recent Autoyast Documentation In-Reply-To: <53B1391B.4010504@suse.de> References: <53B125AE.7090703@oce.com> <53B1391B.4010504@suse.de> Message-ID: <53B1453E.9070207@suse.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 30.06.2014 12:16, Stefan Schubert wrote: > Hi, the "latest" documentation can be found here: > http://docserv.suse.de/documents/SLES12/SLES-autoyast/pdf/book.autoyast_remarks_color_draft_meta_en.pdf Sorry, > this link cannot be reached from outside SUSE. The other two links Stefan posted work, though. Kind regards, Bj?rn - -- Dr. Bj?rn Lotz, Instructional Designer, CISSP SUSE Linux GmbH, Maxfeldstrasse 5, 90409 N?rnberg Tel: +49 89 8639 9664 Mobil: +49 173 5876724 bjoern.lotz at suse.com PGP-ID: 0xD437D363 - ------------------ SUSE Linux GmbH, N?rnberg; HRB 21284 (AG N?rnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOxRSgACgkQKZToxtQ302PMbwCfVMbG7psBbs+LxtaaMfRwPPgw 9dgAmwTNRmb/UXCKft+kbV9zt3X3Vbhl =5oes -----END PGP SIGNATURE----- From schubi at suse.de Mon Jun 30 05:18:57 2014 From: schubi at suse.de (Stefan Schubert) Date: Mon, 30 Jun 2014 13:18:57 +0200 Subject: [sles-beta] Recent Autoyast Documentation In-Reply-To: <53B14400.6010109@oce.com> References: <53B125AE.7090703@oce.com> <53B1391B.4010504@suse.de> <53B14400.6010109@oce.com> Message-ID: <53B147A1.107@suse.de> Am 30.06.2014 13:03, schrieb Klaus Gmeinwieser: > Hi Stefan, > > thanks for your quick answer. Unfortunately my proxy tells me the link > (to the pdf) is broken - maybe not suse.de? > I have asked the docu team for another link. I will post it on the list. > Anyway, I used the SLES11 SP3 doc, which leads to the following - > similar code: > > > > networking,dns,hostname > Enter Hostname > Popup > initial > > > networking,dns,domain > Enter Domain > initial > for.the.domain > > > > As I see, I am missing the inner pathlist tag, but with SLE12 Beta9 the > whole "ask tree" is completely ignored! > I can start installation, but this leads to a system with a root > password I do not know, I set it in the autoyast file. Beta 9 has an issue regarding root password if it is uncrypted in the autoinst.xml file. It will not be crytped in /etc/shadow. A workaround would be to use a crypted root password in autoinst.xml. (Just copy and paste it from /etc/shadow AND the set crypted flag true ) If you still have problems with the "ask" stuff you can try the example: https://github.com/yast/yast-autoinstallation/blob/master/test_xml/ask.xml I have tested it some days ago with beta9 and it has worked quite nice. Greetings Stefan -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From gjn at gjn.priv.at Mon Jun 30 08:26:12 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Mon, 30 Jun 2014 16:26:12 +0200 Subject: [sles-beta] YaST2 ??? In-Reply-To: <53B1408E.9060508@suse.com> References: <5243338.vTISNrKFoi@gjn.priv.at> <53B1408E.9060508@suse.com> Message-ID: <2030276.htdn5KBqA9@gjn.priv.at> Hello Lukas, Am Montag, 30. Juni 2014, 12:48:46 schrieb Lukas Ocilka: > On 30.6.2014 09:56, G?nther J.Niederwimmer wrote: > > Hello, > > > > have we a docu what the new Yast2 can configure and what is deleted? > > > > The most of the featcher is gon. > > > > I mean all for the consumer nice featcher are deleted. > > > > I tested a master Ldap / kerberos installation, this is not possible with > > Yast2 also the Mirror config is broken usw. > > > > The nice quick view for ldap is gon. > > > > What can we do with the new YaST2? > The whole LDAP/Kerberos stuff has been rewritten for SLE 12 by Peter > Varkoly and Christian Kornacker. We have now two new Yast modules that > replace the old functionality: > > * yast2-auth-server > * yast2-auth-client I have make a #SR ;-) > Could you, please, give us your use case where you would describe what > you need to configure and what are your expectations from this > configuration? We can try to help you, but we need to know what the > problem is. My testing scenario is a Master server with kerberos and Mirroring. In the moment I have no chance to do this The Mirroring Module I mean is broken, I have always a fallback to "normal" Ldap Module, I don't know what this Module like to do. Is the nice ldap Viewer gone :-( Thanks, but I can't found a Documentation for this new Modules. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From darrent at akurit.com.au Mon Jun 30 20:22:22 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Tue, 1 Jul 2014 12:22:22 +1000 Subject: [sles-beta] YAST using "wrong" commands to configure ISCSI targets Message-ID: Team I will include exerts of a conversation had about some bugs in the LIO (ISCSI Target) configuration. Is it sufficient to note that YAST is using the wrong tools in the existing Bug notes or should I raise a new SR? History: https://bugzilla.novell.com/show_bug.cgi?id=881553#c26 ..."> lio-utils are deprecated, being replaced by targetcli. => Why are depreciated > tools in the SLES12 codebase, please replace with "working" and update > documentation accordingly. Perhaps you do not understand. Upstream development of these public-domain tools no longer occurs. The documentation that comes with the package, in /usr/share/doc/packages/lio-utils/lio-utils.HOWTO, says (among other things): Warning: Use targetcli instead. lio-utils are deprecated and have been superseded by targetcli. Seems up to date to me. > > These utilities are brittle at best, as you have discovered. If you get your > configuration correct, it works just fine (sans bugs).=> The "stop" option > f**ks with the working configuration and should not. That is bad design. > Why are "brittle" tools in the SLES12 codebase, please replace with "working" > and update documentation accordingly. I did not add these tools to sles12, so I cannot answer that question. The updated tools _are_ present and working in sles 12. At least they will be working once IBS approves my update requests. > > ISCSI can be mission critical, it certainly is the core to one of my clusters. > "Brittle" would be unacceptable in a production system and certainly not in an > "enterprise"/Supported Linux Offering which we could be using to offering SLA > based support contracts to our clients. Then I would suggest you use targetcli. Or you can continue to use lio-utils, which seem to work once configured correctly. We will continue to support them for SLE 12, but enhancements are unlikely. This is simply a fact of the public software universe: when upstream development ends, you have to move to newer software." .... https://bugzilla.novell.com/show_bug.cgi?id=881553#c27 "Then I would suggest you use targetcli. => I did not choose which tool was used. I used the GUI in YAST to create the target configuration. If YAST is using the wrong tools, then YAST needs to be changed to use the correct tools." " -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From darrent at akurit.com.au Tue Jul 1 01:26:08 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Tue, 1 Jul 2014 17:26:08 +1000 Subject: [sles-beta] YAST using "wrong" commands to configure ISCSI targets In-Reply-To: References: Message-ID: Team The original bug was updated with this explanation. This is my last post on this topic, sorry for the SPAM. "To shed some more light here: - Both targetcli and lio-utils are just elaborate scripts to configure the target in /sys/kernel/config. None of the utilities are actually _required_; you can as well configure the whole thing by hand if you so chooses. - lio-utils was used for the YaST2 interface as it was the only program available by the time the YaST2 module was written; it precedes targetcli by several years. - When targetcli would be made to deprecate lio-utils you either have to rewrite the YaST2 interface to use targetcli or any installation of targetcli you cause the YaST2 module to be removed. - The idea of the 'target' service is to capture the current state of the target in /sys/kernel/config and to push this configuration back into configfs upon startup. Currently we're using lio-utils for that. But of course any other program or script would work here, too." Darren On 1 July 2014 12:22, Darren Thompson wrote: > Team > > I will include exerts of a conversation had about some bugs in the LIO > (ISCSI Target) configuration. > > Is it sufficient to note that YAST is using the wrong tools in the > existing Bug notes or should I raise a new SR? > > History: > > https://bugzilla.novell.com/show_bug.cgi?id=881553#c26 > > ..."> lio-utils are deprecated, being replaced by targetcli. => Why are > depreciated > > > tools in the SLES12 codebase, please replace with "working" and update > > documentation accordingly. > > Perhaps you do not understand. Upstream development of these public-domain > tools no longer occurs. > > The documentation that comes with the package, in > /usr/share/doc/packages/lio-utils/lio-utils.HOWTO, says (among other things): > > Warning: Use targetcli instead. > lio-utils are deprecated and have been superseded by targetcli. > > Seems up to date to me. > > > > These utilities are brittle at best, as you have discovered. If you get your > > configuration correct, it works just fine (sans bugs).=> The "stop" option > > f**ks with the working configuration and should not. That is bad design. > > Why are "brittle" tools in the SLES12 codebase, please replace with "working" > > and update documentation accordingly. > > I did not add these tools to sles12, so I cannot answer that question. > > The updated tools _are_ present and working in sles 12. At least they will be > working once IBS approves my update requests. > > > > ISCSI can be mission critical, it certainly is the core to one of my clusters. > > "Brittle" would be unacceptable in a production system and certainly not in an > > "enterprise"/Supported Linux Offering which we could be using to offering SLA > > based support contracts to our clients. > > Then I would suggest you use targetcli. Or you can continue to use lio-utils, > which seem to work once configured correctly. We will continue to support them > for SLE 12, but enhancements are unlikely. This is simply a fact of the public > software universe: when upstream development ends, you have to move to newer > software." > > > .... > > > https://bugzilla.novell.com/show_bug.cgi?id=881553#c27 > > > "Then I would suggest you use targetcli. => I did not > > choose which tool was used. I used the GUI in YAST to create the target > configuration. If YAST is using the wrong tools, then YAST needs to be changed > to use the correct tools." > > > " > > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From gjn at gjn.priv.at Sun Jul 6 10:11:21 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sun, 06 Jul 2014 18:11:21 +0200 Subject: [sles-beta] SuSEconfig.postfix missing Message-ID: <1908893.d78kHZ4BvF@gjn.priv.at> Hello, What is with SuSEconfig.postfix i missing this file. I can't update the config from the /etc/sysconfig/postfix ? Or have this a other name or ... -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From p.heinlein at heinlein-support.de Sun Jul 6 14:01:39 2014 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Sun, 06 Jul 2014 22:01:39 +0200 Subject: [sles-beta] SuSEconfig.postfix missing In-Reply-To: <1908893.d78kHZ4BvF@gjn.priv.at> References: <1908893.d78kHZ4BvF@gjn.priv.at> Message-ID: <53B9AB23.1080802@heinlein-support.de> Am 06.07.2014 18:11, schrieb G?nther J. Niederwimmer: Hi, > What is with SuSEconfig.postfix i missing this file. I can't update the config > from the /etc/sysconfig/postfix ? > > Or have this a other name or ... In OpenSUSE it has changed to config.postfix, so it should be the same at SLES12. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Gesch?ftsf?hrer: Peer Heinlein -- Sitz: Berlin From darrent at akurit.com.au Sun Jul 6 15:08:37 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 7 Jul 2014 07:08:37 +1000 Subject: [sles-beta] Question: Migration tools for ISCSI config from SLES11 Message-ID: Team The ISCSI engine changes from SLES11 to SLES12 In SLES11 they were (STGT/TGT) based but under SLES12 they are LIO based. Is thaere any tools to parse/migrate a valid SLES11 ISCSI configuartion to a SLES12 ISCSI configuration, in particular I would like to ensure that what is presented to the ISCSI clients is identical so their configuration is not scrambled. -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: From darrent at akurit.com.au Sun Jul 6 15:11:38 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Mon, 7 Jul 2014 07:11:38 +1000 Subject: [sles-beta] Question: Migration tools for ISCSI config from SLES11 In-Reply-To: References: Message-ID: Team Less critical but on a similar note, are there tools to convert the ISCSI client configs from SLSE11 to SLES12. I'm wanting to migrate a ISCSI dependant cluster from SLES11 to SLES12 and want to see if it con be done without a full break/rebuild. Darren On 7 July 2014 07:08, Darren Thompson wrote: > Team > > The ISCSI engine changes from SLES11 to SLES12 > > In SLES11 they were (STGT/TGT) based but under SLES12 they are LIO based. > > Is thaere any tools to parse/migrate a valid SLES11 ISCSI configuartion to > a SLES12 ISCSI configuration, in particular I would like to ensure that > what is presented to the ISCSI clients is identical so their configuration > is not scrambled. > > -- > > Darren Thompson > > Professional Services Engineer / Consultant > > *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* > > Level 3, 60 City Road > > Southgate, VIC 3006 > > Mb: 0400 640 414 > > Mail: darrent at akurit.com.au > Web: www.akurit.com.au > -- Darren Thompson Professional Services Engineer / Consultant *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]* Level 3, 60 City Road Southgate, VIC 3006 Mb: 0400 640 414 Mail: darrent at akurit.com.au Web: www.akurit.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 3692 bytes Desc: not available URL: