735
Comment:
|
← Revision 5 as of 2017-05-24 09:32:00 ⇥
2099
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
* Users and groups are encouraged to their software packages for SL7-compliance | * Users and groups are encouraged to test their software packages for SL7-compliance |
Line 7: | Line 7: |
A '''test system''' is available: A virtual machine with an alias name of '''sl7.zeuthen.desy.de''' has been set up with a WGS configuration. It is meant to be used for tests and development, not for running production jobs. | A '''test system''' is available: A virtual machine with an alias name of '''el7.zeuthen.desy.de''' has been set up with a WGS configuration. It is meant to be used for tests and development, not for running production jobs. Another way to try SL7 is to use the [[Singularity]] container, which is possible on WGSs, compute nodes and even Linux desktops. |
Line 13: | Line 15: |
* Nothing, yet | * [[attachment:Linux-20170509-2up.pdf|Technical Seminar, Zeuthen, 2017-05-09]] |
Line 21: | Line 23: |
* The '''AFS sysname list''' is `'amd64_rhel70' 'amd64_rhel60' 'amd64_rhel50' 'i586_rhel50' 'amd64_linux26' 'i386_linux26'`. Note that making use of the AFS sysname (list) is deprecated. Other methods, like parsing the output of `lsb_release`, are recommended to find the right binaries in AFS. Future Linux releases in Zeuthen may drop the list and just provide the default of `amd64_linux24`. |
|
Line 24: | Line 28: |
== Known Problems == * When started remotely (after ssh login), many applications will print a warning {{{ WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NEN7dYkiMc: Connection refused }}} There's no serious problem here (unless you depend on "assistive technologies"), but the messages are annoying. They can be suppressed by setting the environment variable `NO_AT_BRIDGE` to `1`. * Starting '''emacs''' remotely (after ssh login) may hang or crash, and the user may or may not see the warning {{{ dconf-WARNING **: unable to open file '/run/user/19916/dconf-service/keyfile/user }}} As a remedy, run `dbus-launch emacs` once. Subsequent starts of emacs on the same system will then work normally. |
Contents
Status
SL7 at Zeuthen will become the default and recommended Linux version:
- Users and groups are encouraged to test their software packages for SL7-compliance
A test system is available: A virtual machine with an alias name of el7.zeuthen.desy.de has been set up with a WGS configuration. It is meant to be used for tests and development, not for running production jobs.
Another way to try SL7 is to use the Singularity container, which is possible on WGSs, compute nodes and even Linux desktops.
There are currently no plans to provide SL7-based desktop systems.
SL7 presentations
Changes w.r.t. SL6 from the user's point of view
Enhancements
General changes
The AFS sysname list is 'amd64_rhel70' 'amd64_rhel60' 'amd64_rhel50' 'i586_rhel50' 'amd64_linux26' 'i386_linux26'. Note that making use of the AFS sysname (list) is deprecated. Other methods, like parsing the output of lsb_release, are recommended to find the right binaries in AFS. Future Linux releases in Zeuthen may drop the list and just provide the default of amd64_linux24.
Changes regarding software
- The new default compiler version is GCC 4.8.5
Known Problems
- When started remotely (after ssh login), many applications will print a warning
WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NEN7dYkiMc: Connection refused
There's no serious problem here (unless you depend on "assistive technologies"), but the messages are annoying. They can be suppressed by setting the environment variable NO_AT_BRIDGE to 1.
Starting emacs remotely (after ssh login) may hang or crash, and the user may or may not see the warning
dconf-WARNING **: unable to open file '/run/user/19916/dconf-service/keyfile/user
As a remedy, run dbus-launch emacs once. Subsequent starts of emacs on the same system will then work normally.