From jsrain at suse.cz Mon Sep 29 07:35:00 2014 From: jsrain at suse.cz (Jiri Srain) Date: Mon, 29 Sep 2014 15:35:00 +0200 Subject: [sles-beta] New testing snapshot of SMT11-SP3 update available Message-ID: <54296004.8080601@suse.cz> Dear SLES12 testers, a new testing version of SMT is now available at http://beta.suse.com/private/SMT-Beta/ This version is necessary for further downloading of packages due to the switch from nu.novell.com to updates.suse.com. Without this update, mirroring repositories will not work any more. For updating, make sure to use the latest repo, as referenced at the URL above. If you use the date stamp as part of the repository URL instead of the symlink 'LATEST', please, adjust the repository URL. For fresh installation, you need both the new repository and the original SMT media. If you updated from previous testing snapshots, update your /etc/smt.conf file and make sure that the URL for mirroring repositories is set as NUUrl = https://updates.suse.com Other settings can be kept unchanged. More information is available in the README-SCC file, which is available at the URL above. Happy testing and thanks for your feedback! The SUSE SMT team. -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com From jsrain at suse.cz Tue Sep 30 02:13:46 2014 From: jsrain at suse.cz (Jiri Srain) Date: Tue, 30 Sep 2014 10:13:46 +0200 Subject: [sles-beta] New testing snapshot of SMT11-SP3 update available In-Reply-To: <54296004.8080601@suse.cz> References: <54296004.8080601@suse.cz> Message-ID: <542A663A.3090909@suse.cz> On 09/29/2014 03:35 PM, Jiri Srain wrote: > Dear SLES12 testers, > > a new testing version of SMT is now available at > > http://beta.suse.com/private/SMT-Beta/ > > This version is necessary for further downloading of packages due to the > switch from nu.novell.com to updates.suse.com. Without this update, > mirroring repositories will not work any more. > > For updating, make sure to use the latest repo, as referenced at the URL > above. If you use the date stamp as part of the repository URL instead > of the symlink 'LATEST', please, adjust the repository URL. For fresh > installation, you need both the new repository and the original SMT media. > > If you updated from previous testing snapshots, update your > > /etc/smt.conf > > file and make sure that the URL for mirroring repositories is set as > > NUUrl = https://updates.suse.com > > Other settings can be kept unchanged. After the update is done, you need to re-synchronize with SCC before repositories can get mirrored again. To do so, run smt-scc-sync after the packages are updated and the NUUrl is set. Jiri > > More information is available in the README-SCC file, which is available > at the URL above. > > Happy testing and thanks for your feedback! > > The SUSE SMT team. > > > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com From mge at suse.com Tue Sep 30 02:29:56 2014 From: mge at suse.com (Matthias G. Eckermann) Date: Tue, 30 Sep 2014 10:29:56 +0200 Subject: [sles-beta] [ ] Re: btrfs & tooling In-Reply-To: References: <1401278011.31434.37.camel@ibrokeit.suse.de> <5426DE05.1070604@suse.com> Message-ID: <20140930082956.GB4006@suse.com> Hello Mr. Schumacher and all, On 2014-09-29 T 15:30 +0200 Christoph Schumacher wrote: > Basically there should be a tool showing usage as df > does for subvolumes human readable at a glance. I'll > talk to Ralf Dannert on the workshop in Nuremberg on > Wednesday. as I will not be in N?rnberg at the workshop either, I was curious about the Use Case (as some of you might have been). And the Use Case is as a classic one: monitor /tmp and /var/log for their size, and prevent these subdirectories (or subvolumes) from filling the whole filesystem. Now, there are two ways to solve this Use Case. 1. Use btrfs subvolumes and quota groups. As seen, this has issues, specifically in the way how to "account", and how to use the tools. For obvious reasons (see Jeff's mails), a simple "df" does not work in the context of any CoW filesystem (btrfs is not alone here!), thus we have to come up with a good "how to", and improved output of our tools. This is an action item I take to drive with our engineering teams after the release of SUSE Linux Enterprise 12. 2. Put /tmp and /var/log on separate partitions or filesystems, as many have done in the past. This may raise the question, which subdirectories can be put on separate partitions / filesystems without impacting Snapshot/Rollback? The answer is as simple as obvious: those subdirectories which our default partitioning puts on a separate _subvolume_ can also be placed on a separate _partition_ (with the exception of the bootloader related subvolumes). The SUSE Linux Enterprise Server 12 Release Notes have a comprehensive list; see: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#fate-316522 Hope this helps! so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From kukuk at suse.de Tue Sep 30 02:39:56 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Tue, 30 Sep 2014 10:39:56 +0200 Subject: [sles-beta] Question about xrdp In-Reply-To: References: Message-ID: <20140930083956.GA4111@suse.de> On Tue, Sep 30, Murakawa Ryo wrote: > Hi All > > Today I install xrdp on SLES 12 RC3. > But I can?t find how to start xrdp when system booting. > On SLES 11SP3 I can find startup script in /etc/rc.d. But > In SLES 12 RC3 I can?t find this. I think xrdp.service is registered in > systemd. > So how do I register xrdp in systems? "man systemctl", search for the enable section: systemctl enable xrdp 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 RMurakawa at suse.com Tue Sep 30 02:46:07 2014 From: RMurakawa at suse.com (Murakawa Ryo) Date: Tue, 30 Sep 2014 17:46:07 +0900 Subject: [sles-beta] Question about xrdp In-Reply-To: <20140930083956.GA4111@suse.de> References: <20140930083956.GA4111@suse.de> Message-ID: Hi Thorsten Thank you for your replying. But when I run ?systemctl enable xrdp?, I got the error below. Failed to execute operation: No such file or directory So can I use the configuration file to register in systemd? Regards. Ryo On 2014/09/30 17:39, "Thorsten Kukuk" wrote: >On Tue, Sep 30, Murakawa Ryo wrote: > >> Hi All >> >> Today I install xrdp on SLES 12 RC3. >> But I can?t find how to start xrdp when system booting. >> On SLES 11SP3 I can find startup script in /etc/rc.d. But >> In SLES 12 RC3 I can?t find this. I think xrdp.service is registered in >> systemd. >> So how do I register xrdp in systems? > >"man systemctl", search for the enable section: > >systemctl enable xrdp > > 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) >_______________________________________________ >sles-beta mailing list >sles-beta at lists.suse.com >http://lists.suse.com/mailman/listinfo/sles-beta > From darrent at akurit.com.au Tue Sep 30 02:53:55 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Tue, 30 Sep 2014 18:53:55 +1000 Subject: [sles-beta] Question about xrdp In-Reply-To: References: <20140930083956.GA4111@suse.de> Message-ID: Murakawa Lets just be sure that systemd knows about xrdp Try typing 'systemctl | grep -i xrdp' and see what (if anything) is found. Darren 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 On 30 September 2014 18:46, Murakawa Ryo wrote: > Hi Thorsten > > Thank you for your replying. > But when I run ?systemctl enable xrdp?, I got the error below. > > Failed to execute operation: No such file or directory > > > So can I use the configuration file to register in systemd? > > Regards. > > Ryo > > On 2014/09/30 17:39, "Thorsten Kukuk" wrote: > > >On Tue, Sep 30, Murakawa Ryo wrote: > > > >> Hi All > >> > >> Today I install xrdp on SLES 12 RC3. > >> But I can?t find how to start xrdp when system booting. > >> On SLES 11SP3 I can find startup script in /etc/rc.d. But > >> In SLES 12 RC3 I can?t find this. I think xrdp.service is registered in > >> systemd. > >> So how do I register xrdp in systems? > > > >"man systemctl", search for the enable section: > > > >systemctl enable xrdp > > > > 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) > >_______________________________________________ > >sles-beta mailing list > >sles-beta at lists.suse.com > >http://lists.suse.com/mailman/listinfo/sles-beta > > > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -------------- 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 Tue Sep 30 05:00:50 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Tue, 30 Sep 2014 13:00:50 +0200 Subject: [sles-beta] question systemd Message-ID: <1814869.f7iGWv7GnB@gjn.priv.at> Hello, I have two Problems with systemd, can any say way. On a new installation I miss the /etc/tmpfiles.d/tmp.conf The second Problem is, way work this on a reboot but not on start time I make a new kinit.service, the cron parameter "@reboot" don't work anymore /etc/tmpfiles.d/kinit.conf d /run/user/0/krb5cc 1777 root root - /etc/systemd/system/kinit.service [Unit] Description=Kerberos initial kinit Wants=SuSEfirewall2_setup.service After=SuSEfirewall2_setup.service [Service] Type=simple ExecStart=/usr/bin/kinit -k host/asmtp.gjn.prv Restart=on-failure RestartSec=30 [Install] WantedBy=multi-user.target /etc/systemd/system/kinit.timer [Unit] Description=Fist Initialisation of KRB5 [Timer] OnBootSec=3min [Install] WantedBy=timers.target Thanks for a answer, -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From fcrozat at suse.com Tue Sep 30 05:08:42 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 30 Sep 2014 13:08:42 +0200 Subject: [sles-beta] question systemd In-Reply-To: <1814869.f7iGWv7GnB@gjn.priv.at> References: <1814869.f7iGWv7GnB@gjn.priv.at> Message-ID: <1412075322.5188.12.camel@par-r81vxc7.par.novell.com> Le mardi 30 septembre 2014 ? 13:00 +0200, G?nther J. Niederwimmer a ?crit : > Hello, > > I have two Problems with systemd, can any say way. > > On a new installation I miss the > > /etc/tmpfiles.d/tmp.conf This is expected, we don't ship any files in /etc/tmpfiles.d by default, since those are for administrators. All packaged tmpfiles.d files are located in /usr/lib/tmpfiles.d (where you'll find tmp.conf) > The second Problem is, way work this on a reboot but not on start time > > I make a new kinit.service, the cron parameter "@reboot" don't work anymore > > /etc/tmpfiles.d/kinit.conf > d /run/user/0/krb5cc 1777 root root - > > /etc/systemd/system/kinit.service > [Unit] > Description=Kerberos initial kinit > Wants=SuSEfirewall2_setup.service > After=SuSEfirewall2_setup.service > > [Service] > Type=simple > ExecStart=/usr/bin/kinit -k host/asmtp.gjn.prv > Restart=on-failure > RestartSec=30 > > [Install] > WantedBy=multi-user.target > > /etc/systemd/system/kinit.timer > [Unit] > Description=Fist Initialisation of KRB5 > > [Timer] > OnBootSec=3min > > [Install] > WantedBy=timers.target I'm not 100% sure I understand what you want to do. Could you elaborate a bit more ? -- Frederic Crozat Project Manager Enterprise Desktop SUSE From gjn at gjn.priv.at Tue Sep 30 05:53:09 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Tue, 30 Sep 2014 13:53:09 +0200 Subject: [sles-beta] question systemd In-Reply-To: <1412075322.5188.12.camel@par-r81vxc7.par.novell.com> References: <1814869.f7iGWv7GnB@gjn.priv.at> <1412075322.5188.12.camel@par-r81vxc7.par.novell.com> Message-ID: <54333587.jxNWrKk29Z@gjn.priv.at> Am Dienstag, 30. September 2014, 13:08:42 schrieb Frederic Crozat: > Le mardi 30 septembre 2014 ? 13:00 +0200, G?nther J. Niederwimmer a > > ?crit : > > Hello, > > > > I have two Problems with systemd, can any say way. > > > > On a new installation I miss the > > > > /etc/tmpfiles.d/tmp.conf > > This is expected, we don't ship any files in /etc/tmpfiles.d by default, > since those are for administrators. All packaged tmpfiles.d files are > located in /usr/lib/tmpfiles.d (where you'll find tmp.conf) OK thanks, this was a old Installation, only with "zypper dup" updated, so I have the tmp.conf twice. > > The second Problem is, way work this on a reboot but not on start time > > > > I make a new kinit.service, the cron parameter "@reboot" don't work > > anymore > > > > /etc/tmpfiles.d/kinit.conf > > d /run/user/0/krb5cc 1777 root root - > > > > /etc/systemd/system/kinit.service > > [Unit] > > Description=Kerberos initial kinit > > Wants=SuSEfirewall2_setup.service > > After=SuSEfirewall2_setup.service > > > > [Service] > > Type=simple > > ExecStart=/usr/bin/kinit -k host/asmtp.gjn.prv > > Restart=on-failure > > RestartSec=30 > > > > [Install] > > WantedBy=multi-user.target > > > > /etc/systemd/system/kinit.timer > > [Unit] > > Description=Fist Initialisation of KRB5 > > > > [Timer] > > OnBootSec=3min > > > > [Install] > > WantedBy=timers.target > > I'm not 100% sure I understand what you want to do. Could you elaborate > a bit more ? I like to do, on start up a kinit -k host/......... for the first initialisation from kerberos after the network is on, and the server is running. (KVM Client) with SLES 11 I make a cron file with the extra character "@reboot" but this don't work with SLES 12 anymore. so I google a bit and found a way with systemd. But my construct is only working after a reboot and not on start up the system. :-( So I hope any can help me, to say way. ? Thanks for a answer, -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From fcrozat at suse.com Tue Sep 30 06:09:02 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 30 Sep 2014 14:09:02 +0200 Subject: [sles-beta] question systemd In-Reply-To: <54333587.jxNWrKk29Z@gjn.priv.at> References: <1814869.f7iGWv7GnB@gjn.priv.at> <1412075322.5188.12.camel@par-r81vxc7.par.novell.com> <54333587.jxNWrKk29Z@gjn.priv.at> Message-ID: <1412078942.5188.21.camel@par-r81vxc7.par.novell.com> Le mardi 30 septembre 2014 ? 13:53 +0200, G?nther J. Niederwimmer a ?crit : > Am Dienstag, 30. September 2014, 13:08:42 schrieb Frederic Crozat: > > Le mardi 30 septembre 2014 ? 13:00 +0200, G?nther J. Niederwimmer a > > > > ?crit : > > > Hello, > > > > > > I have two Problems with systemd, can any say way. > > > > > > On a new installation I miss the > > > > > > /etc/tmpfiles.d/tmp.conf > > > > This is expected, we don't ship any files in /etc/tmpfiles.d by default, > > since those are for administrators. All packaged tmpfiles.d files are > > located in /usr/lib/tmpfiles.d (where you'll find tmp.conf) > > OK thanks, this was a old Installation, only with "zypper dup" updated, so I > have the tmp.conf twice. > > > > The second Problem is, way work this on a reboot but not on start time > > > > > > I make a new kinit.service, the cron parameter "@reboot" don't work > > > anymore > > > > > > /etc/tmpfiles.d/kinit.conf > > > d /run/user/0/krb5cc 1777 root root - > > > > > > /etc/systemd/system/kinit.service > > > [Unit] > > > Description=Kerberos initial kinit > > > Wants=SuSEfirewall2_setup.service > > > After=SuSEfirewall2_setup.service > > > > > > [Service] > > > Type=simple > > > ExecStart=/usr/bin/kinit -k host/asmtp.gjn.prv > > > Restart=on-failure > > > RestartSec=30 > > > > > > [Install] > > > WantedBy=multi-user.target > > > > > > /etc/systemd/system/kinit.timer > > > [Unit] > > > Description=Fist Initialisation of KRB5 > > > > > > [Timer] > > > OnBootSec=3min > > > > > > [Install] > > > WantedBy=timers.target > > > > I'm not 100% sure I understand what you want to do. Could you elaborate > > a bit more ? > > I like to do, on start up a kinit -k host/......... for the first > initialisation from kerberos after the network is on, and the server is > running. (KVM Client) > > with SLES 11 I make a cron file with the extra character "@reboot" but this > don't work with SLES 12 anymore. > > so I google a bit and found a way with systemd. But my construct is only > working after a reboot and not on start up the system. :-( On the dependency side, you should drop the "Wants" (it is not needed) and replace After with: After=network.target (this will ensure network is up before starting kinit). You also should ensure kinit.service is enabled (running systemctl enable kinit.service one time). This should be enough to have this unit started each time 3min after booting is complete (please note systemd doesn't make any difference between initial boot and reboot in the startup sequence). -- Frederic Crozat Project Manager Enterprise Desktop SUSE From tparker at cbnco.com Wed Oct 1 05:13:50 2014 From: tparker at cbnco.com (Tom Parker) Date: Wed, 1 Oct 2014 07:13:50 -0400 Subject: [sles-beta] memtest86+ is horribly out dated Message-ID: <542BE1EE.3030503@cbnco.com> Good morning list. Is there any reason that the version of memtest86+ that is shipping with SLES 12 RC3 was released in 2011? Version 5.01 was released in 2013 over a year ago. Version 4.20 does not properly detect any of the modern Xeon CPUs shipping in HP servers. I know we are long past feature freeze but I thought that someone might want to take a look at this, if not for now then for RC1 Tom From kukuk at suse.de Thu Oct 2 03:31:31 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 2 Oct 2014 11:31:31 +0200 Subject: [sles-beta] Can't restart ntpd with yast and systemctl In-Reply-To: References: Message-ID: <20141002093131.GA31713@suse.de> On Thu, Oct 02, Murakawa Ryo wrote: > Hi All > > I download SLES12 GM from download.suse.de and installed this on my machine. Can you send me your timemachine? Because there is no SLES12 GM yet. > I set ntp service with yast. But the service restart failed. And I tried to > restart with > systemctl restart ntpd.service and failed this. > > So is this bug? Depends on the error. 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 behlert at suse.com Thu Oct 2 07:33:30 2014 From: behlert at suse.com (Stefan Behlert) Date: Thu, 2 Oct 2014 15:33:30 +0200 Subject: [sles-beta] [REMINDER] SLE 12 GMC release date Oct 6th Message-ID: <20141002133330.GF30237@suse.de> Hi all, I'd like to remind everybody that the scheduled release date for the GMC of SLE 12 (SLES, SLED, HA, SDK) is not - as you are all familiar with - on Thursday/Friday, but on Monday the 6th. In case you wonder why, this is because we have currently National Day in China (1st to 7th) and a Public Holiday in Germany this Friday. In addition to that, we wanted to release GMC in time, so when the schedule was made it was moved to a Monday ;) thanks for considering it, and a happy bug-free weekend, Stefan -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Server Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From gjn at gjn.priv.at Fri Oct 3 07:22:08 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Fri, 03 Oct 2014 15:22:08 +0200 Subject: [sles-beta] SLES 12 in XEN SLES11 Message-ID: <2046922.nGlUJO0PXW@gjn.priv.at> Hello, Is this known, I have tested now to install a SLES 12 Instance on a SLES 11 XEN Server the default Installation crash with Btrfs installation. I have a kernel Problem with btrfs open_ctree failed and more -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From jdouglas at suse.com Fri Oct 3 07:38:46 2014 From: jdouglas at suse.com (Jason Douglas) Date: Fri, 03 Oct 2014 07:38:46 -0600 Subject: [sles-beta] SLES 12 in XEN SLES11 In-Reply-To: <2046922.nGlUJO0PXW@gjn.priv.at> References: <2046922.nGlUJO0PXW@gjn.priv.at> Message-ID: <542E528C0200006F00103B94@prv-mh.provo.novell.com> Hi G?nther, We have released updates to enable support for SLE 12 on SLES 11 SP3 XEN (or will shortly), but kernel problems were not among the known issues. It's probably best to open an SR. Thanks for testing. Jason Douglas > On Oct 3, 2014, at 7:22 AM, G?nther J.Niederwimmer wrote: > > Hello, > > Is this known, > I have tested now to install a SLES 12 Instance on a SLES 11 XEN Server the > default Installation crash with Btrfs installation. > > I have a kernel Problem with btrfs open_ctree failed and more > > -- > mit freundlichen Gr??en / best Regards, > > G?nther J. Niederwimmer > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From allen at ua.edu Fri Oct 3 14:12:38 2014 From: allen at ua.edu (Beddingfield, Allen) Date: Fri, 3 Oct 2014 20:12:38 +0000 Subject: [sles-beta] Official VMware support and SLE 12 friendly SMT availability. Message-ID: So, with the final release for SLES 12 coming soon, do we have any ETA from VMware about when they will officially support SLES 12, and more importantly, when the option to customize a cloned SLES 12 VM will work? (We normally deploy new SLES VMs by cloning/customizing a template VM). I wonder if they will release support for this as an update, or wait for the next release? Also, will a production-ready release of SMT server supporting SLES 12 be available at or near release time? Allen B. -- Allen Beddingfield Systems Engineer The University of Alabama From Joerg.Reisenweber at btc-it-services.com Sat Oct 4 14:18:39 2014 From: Joerg.Reisenweber at btc-it-services.com (Joerg.Reisenweber at btc-it-services.com) Date: Sat, 4 Oct 2014 22:18:39 +0200 Subject: [sles-beta] graphical diff utility? In-Reply-To: References: Message-ID: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C100DC23B@OLCA9095.btcnet.btc-ag.com> Wendy, did you try vimdiff? Greetings J?rg ________________________________________ Von: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] im Auftrag von Wendy Palm [wendy at cray.com] Gesendet: Samstag, 4. Oktober 2014 01:24 An: sles-beta at lists.suse.com Betreff: [sles-beta] graphical diff utility? Can someone give me an idea of a preferred or "best of breed" graphical diff utility is included in SLE 12? Our users are wanting xxdiff, but that's not included in SLE at this time, but if there's something else that's equally valuable, I'd appreciate a head's up. Thanks, wendy - - - When in trouble, when in doubt, run in circles, scream and shout.