Re: SL 7.2 on a HP Zbook
Hi Yasha It is a Zbook 15 G2. Ken and Mark put me on the right path. We use our laptops unconnected to any networks. Previous to RHEL 7 the system clock was saved to the hardware clock on shutdown or reboot by default. However NTP does sync the system and hardware clocks. Since we do not use NTP no synchronization happens. -Bill -- On 10/07/2016 11:14 AM, Bill Askew wrote: > Hi everyone > I am using SL 7.2 on a HP Zbook. So far the only issue that I have is > setting the date and time does not set the Zbook's hardware clock. It does > change the time for the duration of the session but when the ZBook is > rebooted the time goes back to what it was before plus the amount of time I > spent during the session. > Does anyone have a fix for this? > Thanks I am using SL 7.2x on a HP Zbook without this issue. Which model? Mine is several years old and thus might be different from yours. Yasha Karant
Re: SL 7.2 on a HP Zbook
On 10/07/2016 11:14 AM, Bill Askew wrote: Hi everyone I am using SL 7.2 on a HP Zbook. So far the only issue that I have is setting the date and time does not set the Zbook's hardware clock. It does change the time for the duration of the session but when the ZBook is rebooted the time goes back to what it was before plus the amount of time I spent during the session. Does anyone have a fix for this? Thanks I am using SL 7.2x on a HP Zbook without this issue. Which model? Mine is several years old and thus might be different from yours. Yasha Karant
Re: SL 7.2 on a HP Zbook
If you grep'd the rc init files for hwclock, you will find it in halt. You can't grep systemd. All you can do is read the man page and there's a lot of man pages to read. :( On 10/07/2016 01:28 PM, stod...@pelletron.comwrote: - Original Message - From: "Bill Askew" <r.w.as...@boeing.com> To: scientific-linux-us...@listserv.fnal.gov Sent: Friday, October 7, 2016 1:14:04 PM Subject: SL 7.2 on a HP Zbook Hi everyone I am using SL 7.2 on a HP Zbook. So far the only issue that I have is setting the date and time does not set the Zbook's hardware clock. It does change the time for the duration of the session but when the ZBook is rebooted the time goes back to what it was before plus the amount of time I spent during the session. Does anyone have a fix for this? Thanks There is probably a more "systemd" type method, but this as root has always worked: hwclock --systohc
Re: SL 7.2 on a HP Zbook
On 10/07/2016 02:09 PM, Bill Askew wrote: Mark The hwclock --systohc worked thanks! :-) Still kind of odd that the date command does not cause the date and time to the hardware clock when shutting down (this is how it works on a Lenovo T61p running SL 6.2) Bill This is probably useful: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Configuring_the_Date_and_Time-hwclock.html There is a note about how the system clock is synced every 11 minutes to hardware. This might be a configuration option in chrony or ntpd. Plenty of good information in that document to dig through.
Re: SL 7.2 on a HP Zbook
Mark The hwclock --systohc worked thanks! :-) Still kind of odd that the date command does not cause the date and time to the hardware clock when shutting down (this is how it works on a Lenovo T61p running SL 6.2) Bill
Re: SL 7.2 on a HP Zbook
- Original Message - From: "Bill Askew" <r.w.as...@boeing.com> To: scientific-linux-us...@listserv.fnal.gov Sent: Friday, October 7, 2016 1:14:04 PM Subject: SL 7.2 on a HP Zbook Hi everyone I am using SL 7.2 on a HP Zbook. So far the only issue that I have is setting the date and time does not set the Zbook's hardware clock. It does change the time for the duration of the session but when the ZBook is rebooted the time goes back to what it was before plus the amount of time I spent during the session. Does anyone have a fix for this? Thanks There is probably a more "systemd" type method, but this as root has always worked: hwclock --systohc
SL 7.2 on a HP Zbook
Hi everyone I am using SL 7.2 on a HP Zbook. So far the only issue that I have is setting the date and time does not set the Zbook's hardware clock. It does change the time for the duration of the session but when the ZBook is rebooted the time goes back to what it was before plus the amount of time I spent during the session. Does anyone have a fix for this? Thanks
Re: SL 7.2 issues
On 29/07/16 09:11, Yasha Karant wrote: On 07/28/2016 02:57 PM, Lamar Owen wrote: On 07/28/2016 01:44 PM, Yasha Karant wrote: I was updating an application on my SL7.1 laptop workstation, not using a terminal screen yum but the GUI interface that automagically appears after "clicking" on the downloaded RPM in the web browser download window. Unfortunately, the ISP network failed during the update (that evidently downloaded other RPMs required). The update did not appear to be re-entrant recoverable. ... yum-complete-transaction may have saved you a whole lot of work. It's in the 'yum-utils' package and it attempts to re-enter and complete the yum transaction. The yum database is semi-atomic and has a transactional characteristic. Yum and the GUI updaters are all supposed to download everything before updating anything, but depending upon exactly which RPM installer you were using it may have behaved differently. I did try that from a scrolling screen, but to no avail -- something may have broken yum for all I know. I did look at the logs in /var but found no smoking gun(s). There were suggested hints displayed by yum when I invoked it on the scrolling screen (the GUI had been absolutely silent -- just an activity indicator that halted momentarily then continued ad naseum that made me suspicious something was amiss -- and only after GUI failure did I continue with the scrolling screen method -- a different F key screen than the one with Xwindows). The 802.11 connection was not lost, but DNS, etc., was -- a web browser could not get out. It is possible that one of the automagic updates needed to satisfy the update of the package upon which I was updating pulled in some network utility/resource update and that froze the Internet Protocol Suite stack -- but the 802.11 MAC was fine. It definitely smashed Xwindows. What I found most annoying was with the SL7.2 ISO 4 Gbyte installation DVD in the drive, yum upgrade did find it and did claim to succeed -- but the machine would not boot. Only a fresh install smashing (formatting) the boot, /, /usr, and swap partitions allowed it to complete and boot. Also, the fact that the current 7.2 MATE evidently has issues with a home directory that worked with a 7.1 MATE (7.2 current MATE caja failed) was not pleasing; I still have the previous home directory and can attempt to find which . file(s) contained the offending configuration(s). In any event, I do now have a working 7.2 laptop and am not looking forward to 7.3 unless the yum upgrade path works, or the GUI booted installer also has an update "button" that will not smash any existing directories (except for swap that only has ephemeral data/files as I understand things). I understand that 8 will be a fresh install of all of the systems partitions. A question: does yumex (that is working and installed on this system) allow for easy control of which "installed" repositories are used? Yes. Install them, eg from a repo rpm, in /etc/yum.repos.d/ Select the 'Repositories' view, either from 'View' or from the third icon on the LeftHandSide. Right-click options include 'Enable/Disable permanently.' That will also affect yum.cron jobs. IIUC ticks(UK)/checks(US) from a single left-click affect only the current yumex session. Other screens can display yum history, dependencies, package changesets, package filelists, ... In general, tool tips will identify what an icon does and anything important asks for confirmation. Describing procedures takes up much more space than quoting the correct command-line but I find the GUI quite friendly. Unleash your inner 10-year-old! :-) A second question: if I want to go from "old" partitions to LVM layouts, do I need two LVM "parts" on a drive so that /home /usr/local /opt and the like do not have to be smashed upon a full install? At some point I shall need to install a hard drive and use LVM rather than the "old" partition scheme. Yasha Karant
Re: SL 7.2 issues
On 07/28/2016 02:57 PM, Lamar Owen wrote: On 07/28/2016 01:44 PM, Yasha Karant wrote: I was updating an application on my SL7.1 laptop workstation, not using a terminal screen yum but the GUI interface that automagically appears after "clicking" on the downloaded RPM in the web browser download window. Unfortunately, the ISP network failed during the update (that evidently downloaded other RPMs required). The update did not appear to be re-entrant recoverable. ... yum-complete-transaction may have saved you a whole lot of work. It's in the 'yum-utils' package and it attempts to re-enter and complete the yum transaction. The yum database is semi-atomic and has a transactional characteristic. Yum and the GUI updaters are all supposed to download everything before updating anything, but depending upon exactly which RPM installer you were using it may have behaved differently. I did try that from a scrolling screen, but to no avail -- something may have broken yum for all I know. I did look at the logs in /var but found no smoking gun(s). There were suggested hints displayed by yum when I invoked it on the scrolling screen (the GUI had been absolutely silent -- just an activity indicator that halted momentarily then continued ad naseum that made me suspicious something was amiss -- and only after GUI failure did I continue with the scrolling screen method -- a different F key screen than the one with Xwindows). The 802.11 connection was not lost, but DNS, etc., was -- a web browser could not get out. It is possible that one of the automagic updates needed to satisfy the update of the package upon which I was updating pulled in some network utility/resource update and that froze the Internet Protocol Suite stack -- but the 802.11 MAC was fine. It definitely smashed Xwindows. What I found most annoying was with the SL7.2 ISO 4 Gbyte installation DVD in the drive, yum upgrade did find it and did claim to succeed -- but the machine would not boot. Only a fresh install smashing (formatting) the boot, /, /usr, and swap partitions allowed it to complete and boot. Also, the fact that the current 7.2 MATE evidently has issues with a home directory that worked with a 7.1 MATE (7.2 current MATE caja failed) was not pleasing; I still have the previous home directory and can attempt to find which . file(s) contained the offending configuration(s). In any event, I do now have a working 7.2 laptop and am not looking forward to 7.3 unless the yum upgrade path works, or the GUI booted installer also has an update "button" that will not smash any existing directories (except for swap that only has ephemeral data/files as I understand things). I understand that 8 will be a fresh install of all of the systems partitions. A question: does yumex (that is working and installed on this system) allow for easy control of which "installed" repositories are used? A second question: if I want to go from "old" partitions to LVM layouts, do I need two LVM "parts" on a drive so that /home /usr/local /opt and the like do not have to be smashed upon a full install? At some point I shall need to install a hard drive and use LVM rather than the "old" partition scheme. Yasha Karant
Re: SL 7.2 issues
On 07/28/2016 01:44 PM, Yasha Karant wrote: I was updating an application on my SL7.1 laptop workstation, not using a terminal screen yum but the GUI interface that automagically appears after "clicking" on the downloaded RPM in the web browser download window. Unfortunately, the ISP network failed during the update (that evidently downloaded other RPMs required). The update did not appear to be re-entrant recoverable. ... yum-complete-transaction may have saved you a whole lot of work. It's in the 'yum-utils' package and it attempts to re-enter and complete the yum transaction. The yum database is semi-atomic and has a transactional characteristic. Yum and the GUI updaters are all supposed to download everything before updating anything, but depending upon exactly which RPM installer you were using it may have behaved differently.
Re: SL 7.2 issues
On 28/07/16 20:20, Yasha Karant wrote: On 07/28/2016 11:33 AM, John Pilkington wrote: On 28/07/16 18:44, Yasha Karant wrote: Several observations, questions -- all pertaining to SL 7.2 / mate (if a KDE, etc., application/interface works under mate, such qualify as "mate"). Q1 I previously had gpk-application as the primary software GUI installer. This has been replaced by gnome-software that appears quite different. Q1.1 Is there a GUI application that will list all installed RPMs (obviously, this does not work for packages installed/built other than through the RPM methodology)? Q1.2 Is there a GUI means to select software sources (repositories) to enable/disable these at will? Q1.3 Other than a web search for an application RPM followed by the command line yum install, is there a GUI application other than gnome-software to list all available applications from all selected/installed repositories? Q2 How does yumex work in 7.2 -- the same as in 7 previous? For me, with a single-box, single-HD 7.2 KDE plasma installation, it does Q1.1, Q1.2, Q1.3 competently with a slower but much friendlier response than the command-line; but you will probably need to have that in reserve. What is the name (file name and RPM) of the KDE application that you are using? Presumably, if I login using KDE Plasma, I would find this (I also specify SL to install KDE) and could track down the actual name of the file (via ps axw in any event). Mate runs KDE applications (as did and presumably does gnome). I use k3b as my preferred CD/DVD burning application now that Nero Linux does no longer seem to work under SL (stopped with the upgrade to SL 7). You asked about yumex. That's what I'm using: https://dl.fedoraproject.org/pub/epel/7/x86_64/y/yumex-3.0.17-1.el7.noarch.rpm so '# yum install yumex' would presumably get you started. I use the KD(esktop)E(nvironment) but I have no idea how much of that is required. yumex needs (among others) pygtk2. You must have any repos you might need defined in /etc/yum.repos.d/ but then you can enable/disable them either 'permanently' (right-click) or for immediate use. There are other small glitches and changes, but nothing severe for the nonce.
Re: SL 7.2 issues
On 07/28/2016 11:33 AM, John Pilkington wrote: On 28/07/16 18:44, Yasha Karant wrote: Several observations, questions -- all pertaining to SL 7.2 / mate (if a KDE, etc., application/interface works under mate, such qualify as "mate"). Q1 I previously had gpk-application as the primary software GUI installer. This has been replaced by gnome-software that appears quite different. Q1.1 Is there a GUI application that will list all installed RPMs (obviously, this does not work for packages installed/built other than through the RPM methodology)? Q1.2 Is there a GUI means to select software sources (repositories) to enable/disable these at will? Q1.3 Other than a web search for an application RPM followed by the command line yum install, is there a GUI application other than gnome-software to list all available applications from all selected/installed repositories? Q2 How does yumex work in 7.2 -- the same as in 7 previous? For me, with a single-box, single-HD 7.2 KDE plasma installation, it does Q1.1, Q1.2, Q1.3 competently with a slower but much friendlier response than the command-line; but you will probably need to have that in reserve. What is the name (file name and RPM) of the KDE application that you are using? Presumably, if I login using KDE Plasma, I would find this (I also specify SL to install KDE) and could track down the actual name of the file (via ps axw in any event). Mate runs KDE applications (as did and presumably does gnome). I use k3b as my preferred CD/DVD burning application now that Nero Linux does no longer seem to work under SL (stopped with the upgrade to SL 7). There are other small glitches and changes, but nothing severe for the nonce.
Re: SL 7.2 issues
On 28/07/16 18:44, Yasha Karant wrote: Several observations, questions -- all pertaining to SL 7.2 / mate (if a KDE, etc., application/interface works under mate, such qualify as "mate"). Q1 I previously had gpk-application as the primary software GUI installer. This has been replaced by gnome-software that appears quite different. Q1.1 Is there a GUI application that will list all installed RPMs (obviously, this does not work for packages installed/built other than through the RPM methodology)? Q1.2 Is there a GUI means to select software sources (repositories) to enable/disable these at will? Q1.3 Other than a web search for an application RPM followed by the command line yum install, is there a GUI application other than gnome-software to list all available applications from all selected/installed repositories? Q2 How does yumex work in 7.2 -- the same as in 7 previous? For me, with a single-box, single-HD 7.2 KDE plasma installation, it does Q1.1, Q1.2, Q1.3 competently with a slower but much friendlier response than the command-line; but you will probably need to have that in reserve. There are other small glitches and changes, but nothing severe for the nonce.
SL 7.2 issues
I was updating an application on my SL7.1 laptop workstation, not using a terminal screen yum but the GUI interface that automagically appears after "clicking" on the downloaded RPM in the web browser download window. Unfortunately, the ISP network failed during the update (that evidently downloaded other RPMs required). The update did not appear to be re-entrant recoverable. The system was left in a state whereby the entire Xwindows system failed (a terminal screen on other F keys did work), and there was no easy rollback method. I then used the SL 7.2 ISO DVD via a terminal screen in yum upgrade (a switch/qualifier to yum); the "upgraded" system would not boot. I finally did a fresh install of SL 7.2 via booting from the SL 7.2 ISO DVD, having to reformat / , /usr , /boot, swap, but saving /home, /opt, and /usr/local as I am using "conventional" partitions (the machine only has a 1 Tbyte drive) with XFS format. (I have left the EXT series and now exclusively use XFS on all new installations. XFS appears to be mature and stable.) Has anyone done the above (or portions thereof) with RHEL 7.2 or CentOS 7.2, and if so, are there any differences? Several observations (recall: this a minor release update -- 7.1 to 7.2; also, the mv scenarios explained below would require a detailed algorithmic or equivalent diagram to be precise -- I have not done this here to save space): 1. During the install, I was required to enter a new root password and create a user account (mine) to which I granted admin privileges under the GUI installer (this evidently makes me a sudo-er). 1.1 The installer created a new /home under the / partition, and renamed the old /home to /hiome . 1.2 After installing the ELRepo and EPEL repository files, I did the yum package install of mate (the window manager system I prefer). 1.4 As root, I exchanged (via a set of mv commands, not a simple mv) the old /home and the newly created /home . 1.5 After a restart, now logged into my old /home, I discovered that the current mate did not work, with symptoms I had seen before (a failure of caja). Call my home directory (account) on SL 7.1 foo . I then did a mv foo oldfoo on /home (the old home, a real partition, not the /home created by the install, merely a directory under / but residing in the / partition). From the /home created by the installer (and now renamed /hiome), I moved that foo to foo under the real /home. Mate now worked. On the first run, my desktop did not correctly appear (missing icons/entries). Upon one more full reboot, my old desktop appeared (many links broken that required re-installation into 7.2) but not in the same layout as before (the apparent arrangement of the icon upon the desktop screen display). I have now reinstalled most of these. Several observations, questions -- all pertaining to SL 7.2 / mate (if a KDE, etc., application/interface works under mate, such qualify as "mate"). Q1 I previously had gpk-application as the primary software GUI installer. This has been replaced by gnome-software that appears quite different. Q1.1 Is there a GUI application that will list all installed RPMs (obviously, this does not work for packages installed/built other than through the RPM methodology)? Q1.2 Is there a GUI means to select software sources (repositories) to enable/disable these at will? Q1.3 Other than a web search for an application RPM followed by the command line yum install, is there a GUI application other than gnome-software to list all available applications from all selected/installed repositories? Q2 How does yumex work in 7.2 -- the same as in 7 previous? There are other small glitches and changes, but nothing severe for the nonce.
Re: SL 7.2 can't find blank disk
Goodbye.
Re: SL 7.2 can't find blank disk
On 07/05/2016 05:31 PM, ToddAndMargo wrote: Hi All, I have added a second black (new) hard drive to a customer's server for use as backup (removalbe sata sleeve). I registers as /dev/sdc I must have the disk removed at boot or the machine times out trying to boot up. So, I have it hot swapped into the system. The disk is a Toshiba HDD MG03ACA400 4TB SATA 6Gb/s Problem. No one can work on the disk: # ls -al /dev/sdc* brw-rw. 1 root disk 8, 32 Jun 30 10:31 sdc # fdisk -l /dev/sdc fdisk: cannot open /dev/sdc: No medium found # gdisk /dev/sdc GPT fdisk (gdisk) version 0.8.6 Problem opening /dev/sdc for reading! Error is 123. gparted: doesn't show up on its list of devices What now? I could boot into Fedora off a Live USB, but I am not physically at the system. (I am remoted in with xRDP.) Many thanks, -T Reported it to Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=1353423 The work around was to format it with a direct install Fedora Core 23 USB flash drive. -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
SL 7.2 can't find blank disk
Hi All, I have added a second black (new) hard drive to a customer's server for use as backup (removalbe sata sleeve). I registers as /dev/sdc I must have the disk removed at boot or the machine times out trying to boot up. So, I have it hot swapped into the system. The disk is a Toshiba HDD MG03ACA400 4TB SATA 6Gb/s Problem. No one can work on the disk: # ls -al /dev/sdc* brw-rw. 1 root disk 8, 32 Jun 30 10:31 sdc # fdisk -l /dev/sdc fdisk: cannot open /dev/sdc: No medium found # gdisk /dev/sdc GPT fdisk (gdisk) version 0.8.6 Problem opening /dev/sdc for reading! Error is 123. gparted: doesn't show up on its list of devices What now? I could boot into Fedora off a Live USB, but I am not physically at the system. (I am remoted in with xRDP.) Many thanks, -T -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
SL 7.2 and MIT-MAGIC-COOKIE messages
I just rebooted, and as usual a message flashed up and vanished a few seconds after login; so I tried Xorg.0.log. The new log, and the .old one, has a continuing sequence of Auth name: MIT-MAGIC-COOKIE-1 ID: 141 [ 1619.936] AUDIT: Wed Jun 22 19:11:50 2016: 1662: client 37 disconnected [ 1622.416] AUDIT: Wed Jun 22 19:11:53 2016: 1662: client 37 connected from local host ( uid=1000 gid=1000 pid=4642 ) which looks like https://access.redhat.com/solutions/230703 with a solution unverified in 2015 Jan and apparently not generally available. Any info? John P
how to upgrade with yum from SL 7.2 DVD
The upgrade procedure that I posted was from 7 to later 7 not 6 to 7.
Re: how to upgrade with yum from SL 7.2 DVD
On Fri, May 20, 2016 at 8:50 PM, Yasha Karant <ykar...@csusb.edu> wrote: > > Would someone please remind me how to do the following. > > The current SL 7.2 DVD does not have an upgrade in place choice (only from a > SL 7.x system; EL does not support upgrade between different major > releases). I recall that someone explained that one can treat the DVD as an > upgrade repository, point yum or some other utility (possibly a GUI) to the > (mounted?) DVD, and then an ungrade in place without considering the process > a new install (e.g., requesting time zone, etc.) will automagically happen. This should do it (untested): Mount DVD. # cat > /etc/yum.repos.d/dvd.repo <
Re: T430 (was RE: SL 7.2 - Gnome 3.14 - gnome-terminal - titles)
On 13 May 2016 at 23:37, Carl Friedberg <friedb...@exs.esb.com> wrote: > Greetings, > > > > My first post in a long time. Today, I installed SL 7.2 (workstation options > > including Gnome) from the 2-DVD distribution downloaded from the > > SL website, onto a Lenovo T430. On reboot, the system hung. > > That sounds more like a kernel problem with the hardware. The black screen means that it is stuck in rhgb quiet mode to make it pretty but is hiding quietly the real problem. In the grub2 edit of a boot line remove rhgb and quiet and try a reboot again. It should stop at a certain point which will help pinpoint the error. [My guess with the T430 is that it is one of the BIOS update issues. It could also be a problem with an nvidia extra chipset in some of the units when it is in a docking unit.] > > I tried the rescue option, hung also (by hung, I mean a completely black > > screen, no way to get a response). > > > > I did try the grub emergency boot, but I don't know enough about SL > > to do anything with that. > > > > Just another data point for those who might be interested > > > > Carl Friedberg > > www.comets.com > > carl.friedb...@comets.com > > http://about.me/carl.friedberg > > > > From: owner-scientific-linux-us...@listserv.fnal.gov > [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of > Thompson, Herb > Sent: Sunday, February 07, 2016 5:51 PM > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV > Subject: SL 7.2 - Gnome 3.14 - gnome-terminal - titles > > > > FYI for those who might be affected: 7.2 comes with an upgrade to Gnome 3.14 > which, as is usually the case for Gnome upgrades, results on the loss of > some features present in the previous version. The first nuisance I’ve > encountered is the loss of the ability to set a custom window title in a > gnome-terminal profile. (For those tempted to suggest I try > I plan to stick with Gnome as on the whole I do find > it tolerable despite continued strange decisions by the developers.) > > > > > > This e-mail communication (including any or all attachments) is intended > only for the use of the person or entity to which it is addressed and may > contain confidential and/or privileged material. If you are not the intended > recipient of this e-mail, any use, review, retransmission, distribution, > dissemination, copying, printing, or other use of, or taking of any action > in reliance upon this e-mail, is strictly prohibited. If you have received > this e-mail in error, please contact the sender and delete the original and > any copy of this e-mail and any printout thereof, immediately. Your > co-operation is appreciated. > Le présent courriel (y compris toute pièce jointe) s'adresse uniquement à > son destinataire, qu'il soit une personne ou un organisme, et pourrait > comporter des renseignements privilégiés ou confidentiels. Si vous n'êtes > pas le destinataire du courriel, il est interdit d'utiliser, de revoir, de > retransmettre, de distribuer, de disséminer, de copier ou d'imprimer ce > courriel, d'agir en vous y fiant ou de vous en servir de toute autre façon. > Si vous avez reçu le présent courriel par erreur, prière de communiquer avec > l'expéditeur et d'éliminer l'original du courriel, ainsi que toute copie > électronique ou imprimée de celui-ci, immédiatement. Nous sommes > reconnaissants de votre collaboration. -- Stephen J Smoogen.
T430 (was RE: SL 7.2 - Gnome 3.14 - gnome-terminal - titles)
Greetings, My first post in a long time. Today, I installed SL 7.2 (workstation options including Gnome) from the 2-DVD distribution downloaded from the SL website, onto a Lenovo T430. On reboot, the system hung. I tried the rescue option, hung also (by hung, I mean a completely black screen, no way to get a response). I did try the grub emergency boot, but I don't know enough about SL to do anything with that. Just another data point for those who might be interested Carl Friedberg www.comets.com carl.friedb...@comets.com<mailto:carl.friedb...@comets.com> http://about.me/carl.friedberg From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Thompson, Herb Sent: Sunday, February 07, 2016 5:51 PM To: SCIENTIFIC-LINUX-USERS@FNAL.GOV Subject: SL 7.2 - Gnome 3.14 - gnome-terminal - titles FYI for those who might be affected: 7.2 comes with an upgrade to Gnome 3.14 which, as is usually the case for Gnome upgrades, results on the loss of some features present in the previous version. The first nuisance I've encountered is the loss of the ability to set a custom window title in a gnome-terminal profile. (For those tempted to suggest I try I plan to stick with Gnome as on the whole I do find it tolerable despite continued strange decisions by the developers.) This e-mail communication (including any or all attachments) is intended only for the use of the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this e-mail, any use, review, retransmission, distribution, dissemination, copying, printing, or other use of, or taking of any action in reliance upon this e-mail, is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete the original and any copy of this e-mail and any printout thereof, immediately. Your co-operation is appreciated. Le présent courriel (y compris toute pièce jointe) s'adresse uniquement à son destinataire, qu'il soit une personne ou un organisme, et pourrait comporter des renseignements privilégiés ou confidentiels. Si vous n'êtes pas le destinataire du courriel, il est interdit d'utiliser, de revoir, de retransmettre, de distribuer, de disséminer, de copier ou d'imprimer ce courriel, d'agir en vous y fiant ou de vous en servir de toute autre façon. Si vous avez reçu le présent courriel par erreur, prière de communiquer avec l'expéditeur et d'éliminer l'original du courriel, ainsi que toute copie électronique ou imprimée de celui-ci, immédiatement. Nous sommes reconnaissants de votre collaboration.
Re: SL 7.2
On 07/07/2015 10:25 PM, Nico Kadel-Garcia wrote: And Larry, where is your code base for Spice? Is it RPM based? Because I find several different spice software packages for SL 6, none of which are the CAD circuitry software. ngspice is probably what is being talked about, although GNUCAP is also out there. Much of the upstream Fedora EDA tools will be difficult to pull over to EPEL for 7; I'm trying to get a recent kicad built myself, and it wants boost 1.54+ among other things. The source RPM for kicad that shipped with Fedora 20 builds ok, but the source RPMs for Fedoras 21 and 22 do not.
Re: SL 7.2
On Tue, Jul 14, 2015 at 5:11 PM, Nico Kadel-Garcia nka...@gmail.com wrote: I'm getting more and more inclined to give SL 7 a complete miss, and see if SL 8 will be contemporary enough to ease my backporting work. Or switch to a distribution with an explicit policy of we will never adopt systemd. Do you know of any? This is perhaps not a sufficient condition to have maintainers without their heads up their backsides, but it is surely a necessary one. - Pat
Re: SL 7.2
On Friday July 3 2015 11:21 am, Nico Kadel-Garcia wrote: On Fri, Jul 3, 2015 at 10:43 AM, Larry Linder larry.lin...@micro-controls.com wrote: Dear Sir: Loaded SL 7.2 for third time and finally got it to where we can run it. I hate to complain but doe anyone check their work anymore. Or just compile it without errors and shove it out the door. There a several major things missing or wrong: 1. It groans and complains about size of /boot - its set to 101 Meg. Reloaded 7.2 again and there does not seem to be way away to change size of /boot partition. I periodically nags at you because there is only 25K left. Now way to fix problem or to shut of NAG function. This is not SL, this is upstream at Red Hat Enterprise Linux. There's a great deal to dislike about the current, highly graphical anaconda. The change from a flow chart, one step at a time, ncurses based, checklist installer of much older versions of Red Hat to the newer, bulky, graphical toolkits came with inconsistent layout, confusing options, confusing dependencies that used to be automatically handled as blockers and dealt with before proceeding in the ncurses, text based tools. It looks to me,, like in this case, you need to custom partition the disk. No idea why /boot is so small, but can you reduce the size of / and then expand /boot? The OS is installed on a 200 Meg Disk and nothing else is on the disk. Removed all the install partations and still could not change any partation size. It just does not work. Unfortunately, each layer of anaconda installer on top of undelying tools like parted for disk management, yum for package selection, and NetworkManager has injected its own layer of interface on top of *another* interface, on top of the actual configuration commands and tools. And the results are predictable: edge cases result form assumptions that were made, and which break down in practice. The size of /boot is one of those. 2. Could not find a way to set up groups or add new users. Had to go back to hand edit of passwd and groups to make it happen. No way to assign user id numbers. What? What happened to useradd and luseradd, groupadd and lgroupadd ? As root they are no where to be found which I thought was pretty strange. 3. Could not find a utility to set up Internet connection - When you used a KDE or Gnome the Mac address of the router was different. We have not been able to connect it to Network. Yeah, NetworkManager is not my friend. You might benefit from the lightweight 'nmcli'. I'm fairly unhappy about NetworkManager: Networking setup is pretty simple and who ever ginned this up apparantly does not know it. 4. Default monitor was set to a pixel size you need a microscope to make out the text. If you used the Gnome it said monitor was IBM 12 France. KDE said monitor was IBM 12 Brazil. No other options were available. Maybe go back and hand edit Xterm stuff. A major step back by 20 years. Ouch. You're on a laptop? No we have everything from 17 - 21 CRT's and LCD's from 17' to 34 we don't use anything but CRT's in the shop because a small piece of metal hits it and its lights out. 5. With out com and a way to make display readable it becomes useless to run word processor, spread sheet, or anything. Can't optimize width or set width, You can go to full screen and the result is the same. There no way to set up terminal for other colors or text. Borders of GNOME are same color as other windows so you have to look twice to see which is which. List of dislikes goes on and on. Gnome is not my friend. I've not tried porting 'vtwm' to SL 7 or RHEL 7, but my tools for putting it on SL 6 and RHEL 6 are available at https://github.com/nkadel/vtwm-5.5.x-srpm. 6. We (everyone in the shop) unanimously hates the GENOME desk top. There does not appear to be able to select an alternate. See above. 7. Could not find a way to turn off high pitched sound when you tried to step back too far on a line. This part of NAG function and can't turn it off. 8. Tried to play a CD - old Marty Robins and it skipped tracks and got hung up and could not X it out. Had to Reboot. There is something basically wrong with the OS if you can't kill an application. Disk plays fine in my Dodge truck and does not have any visible defects. DVD writer is good as we were able to make a dual layer DVD for 7.2 with it using SL 5.11. 9. Gave up on SL 7.2 Notes: The default set up was like a quadriplegic Windows 7. We use one on our UPS account to ship stuff. Everyone who uses it hates it. Another disaster story. We have SL 5.11 deployed in the shop and support about 50 systems. I would not like to tell the boss that we had to trash 45 to 50 perfectly good monitors and give up our ability to add users, groups and network extensions etc. example: We have a number systems in shop and one
Re: SL 7.2
On Mon, Jul 06, 2015 at 01:53:46PM -0400, Larry Linder wrote: Loaded SL 7.2 for third time ... The OS is installed on a 200 Meg Disk ... Please move this gibberish to an insane asylum. a) there is no SL 7.2 (yet) b) 200 Meg Disk (truely?) Okey to use of this forum for free support (as opposed to paying people for their knowledge), but there must be some limits. First learn to spell gnome desktop, google the difference between Meg and Gig, and get a clue how 7.0, 7.1 and 7.2 is not all the same and why it makes a difference. Then maybe post here. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: SL 7.2
On Mon, Jul 6, 2015 at 1:53 PM, Larry Linder larry.lin...@micro-controls.com wrote: On Friday July 3 2015 11:21 am, Nico Kadel-Garcia wrote: It looks to me,, like in this case, you need to custom partition the disk. No idea why /boot is so small, but can you reduce the size of / and then expand /boot? The OS is installed on a 200 Meg Disk and nothing else is on the disk. Removed all the install partations and still could not change any partation size. It just does not work. I'm going to be very, very surprised if it's actually a 200 Meg disk. I'm assuming you mean a 200 Gig disk, because even I would have difficulty finding a working 200 Meg disk in this day and age. You have *zero* chance of filling all the critical libraries and binaries of even a stripped SL 7.1 build onto 200 Meg. I'm also a bit surprised at your difficulty with this, although I admit the interface is confusing. Perhaps you can walk through it one step at a time? I'll need to delete the LVM setup, including the physical volume allocated for LVM, to resize /boot. Unfortunately, each layer of anaconda installer on top of undelying tools like parted for disk management, yum for package selection, and NetworkManager has injected its own layer of interface on top of *another* interface, on top of the actual configuration commands and tools. And the results are predictable: edge cases result form assumptions that were made, and which break down in practice. The size of /boot is one of those. 2. Could not find a way to set up groups or add new users. Had to go back to hand edit of passwd and groups to make it happen. No way to assign user id numbers. What? What happened to useradd and luseradd, groupadd and lgroupadd ? As root they are no where to be found which I thought was pretty strange. Look in /usr/sbin/, which is not on your PATH as a root user unless you logged in directly, at a console or inside terminal window as root. That has to do with interesting SSH PATH settings if SSH in remotely. They've always been in /sbin or /usr/sbin as system tools that a normal user shouldn't need on a casual basis. 3. Could not find a utility to set up Internet connection - When you used a KDE or Gnome the Mac address of the router was different. We have not been able to connect it to Network. Yeah, NetworkManager is not my friend. You might benefit from the lightweight 'nmcli'. I'm fairly unhappy about NetworkManager: Networking setup is pretty simple and who ever ginned this up apparantly does not know it. They know the complex features they want to support. Those have gotten better and make a better stab at pair bonding and KVM bridging and multiple VLAN's than they used to be: I used to have to do those manually, and published notes. The evaluation box is a dual core AMD, 16 Gig of Ram, 4 disks - totaling 2 TB. and a GForce Video card, all pretty current stuff and a working 5.11 system. We will reload SL5.11 on to test box and start looking for another Linux distribution that has not been mangled by Ex Microsoft employees, working at RH. Due to obtuse problems we quit evaluation and will not deploy SL 7 - The best solution is to drop back and evaluate SL 6.5 and see if we can live with it. We have a SL 6.2 used on special project. We need to run spice, a Circuit layout editor, many spread sheets and a number of in house programs to manage inventory, component ordering, e-mail, VMWare to run several cad packages and a stress analysis program. Some employees run 12 desktops and two monitors. So fare we have not see a limitation for 5.11 but have had to install a number of newer libs to accommodate new SW. I'm slightly familiar with spice and xspice. I ported them to SunOS 4.1.4, I think? I found they didn't have large enough parts libraries to justify the effort, I'd spend any time and money saved building up parts libraries. But things may have changed. Larry Linder Your name is strangely familiar. Where did you go to college? Nico Kadel-Garcia
Re: SL 7.2
On 07/03/2015 07:43 AM, Larry Linder wrote: Dear Sir: Loaded SL 7.2 for third time and finally got it to where we can run it. I hate to complain but doe anyone check their work anymore. Or just compile it without errors and shove it out the door. There a several major things missing or wrong: 1. It groans and complains about size of /boot - its set to 101 Meg. Reloaded 7.2 again and there does not seem to be way away to change size of /boot partition. I periodically nags at you because there is only 25K left. Now way to fix problem or to shut of NAG function. 2. Could not find a way to set up groups or add new users. Had to go back to hand edit of passwd and groups to make it happen. No way to assign user id numbers. 3. Could not find a utility to set up Internet connection - When you used a KDE or Gnome the Mac address of the router was different. We have not been able to connect it to Network. 4. Default monitor was set to a pixel size you need a microscope to make out the text. If you used the Gnome it said monitor was IBM 12 France. KDE said monitor was IBM 12 Brazil. No other options were available. Maybe go back and hand edit Xterm stuff. A major step back by 20 years. 5. With out com and a way to make display readable it becomes useless to run word processor, spread sheet, or anything. Can't optimize width or set width, You can go to full screen and the result is the same. There no way to set up terminal for other colors or text. Borders of GNOME are same color as other windows so you have to look twice to see which is which. List of dislikes goes on and on. 6. We (everyone in the shop) unanimously hates the GENOME desk top. There does not appear to be able to select an alternate. 7. Could not find a way to turn off high pitched sound when you tried to step back too far on a line. This part of NAG function and can't turn it off. 8. Tried to play a CD - old Marty Robins and it skipped tracks and got hung up and could not X it out. Had to Reboot. There is something basically wrong with the OS if you can't kill an application. Disk plays fine in my Dodge truck and does not have any visible defects. DVD writer is good as we were able to make a dual layer DVD for 7.2 with it using SL 5.11. 9. Gave up on SL 7.2 Notes: The default set up was like a quadriplegic Windows 7. We use one on our UPS account to ship stuff. Everyone who uses it hates it. Another disaster story. We have SL 5.11 deployed in the shop and support about 50 systems. I would not like to tell the boss that we had to trash 45 to 50 perfectly good monitors and give up our ability to add users, groups and network extensions etc. example: We have a number systems in shop and one by Mill and Lathe so there are no paper prints. Guys can review prints on line and set up CNC stuff on line. Saves a lot of time. The evaluation box is a dual core AMD, 16 Gig of Ram, 4 disks - totaling 2 TB. and a GForce Video card, all pretty current stuff and a working 5.11 system. We will reload SL5.11 on to test box and start looking for another Linux distribution that has not been mangled by Ex Microsoft employees, working at RH. Due to obtuse problems we quit evaluation and will not deploy SL 7 - The best solution is to drop back and evaluate SL 6.5 and see if we can live with it. We have a SL 6.2 used on special project. We need to run spice, a Circuit layout editor, many spread sheets and a number of in house programs to manage inventory, component ordering, e-mail, VMWare to run several cad packages and a stress analysis program. Some employees run 12 desktops and two monitors. So fare we have not see a limitation for 5.11 but have had to install a number of newer libs to accommodate new SW. Larry Linder According to http://ftp1.scientificlinux.org/linux/scientific/7x/x86_64/iso/ we are still on 7.1. Where did you find 7.2? -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
Re: SL 7.2
Hi Konstantin Olchanski! On 2015.07.04 at 15:17:11 -0700, Konstantin Olchanski wrote next: On Sat, Jul 04, 2015 at 04:59:42PM -0400, prmari...@gmail.com wrote: The reason for the small /boot is ... ... the introduction of dracut ... alt.comp.separate.slash.boot.die.die.die alt.comp.dracut.die.die.die To be fair, there is not many reasons to have separate /boot on modern system (with grub2). Especially if it's also UEFI system and has boot loader on UEFI system partition. Or, at VERY least, if people are so comfortable with separate partition for some reason, it should reside on LVM. For grub2, it doesn't matter if you use software raid or LVM or w/e and have /boot together with the rest of partitions on raid/LVM stack. But nooo upstream installer insists on having /boot as a clean separate partition for the reasons unknown and will complain if you try to put it on LVM. Still, it's very possible to move /boot on LVM after that, grubby or whoever modifies grub config on kernel install (it's so complicated nowadays if you consider all the tuning knobs, I'm just not sure anymore which is responsible for what) will handle it just fine. As for dracut, personally I don't think it's evil, it has many nice features: rescue shell available without root fs, nice and reliable way to execute code before mounting root fs (libguestfs uses that. Oh, and zfs on linux works reliably thanks to dracut), rescue initrd with all drivers (useful when you have to replace storage controller on the path to your system drive). -- Vladimir
Re: SL 7.2
The reason for the small /boot is since the introduction of dracut you can now use a shockingly small kernel because the initrd is now customized to your box and less modules need to be compiled in too. That said that is a bit small but you can override it it just takes a lot of clicks. As for gnome it's always been Red Hats favorite because they have had a heavy hand in developing it. It's never been easy to override. That said I've done it with XFCE on rhel 7 and fedora so it's not impossible. Further more if you are doing a lot of deploys you should be using kickstarts which give you far more control over the installation and guarantee consistency. What it comes down to is 7 is a new beast with a big learning curve. You need to play with it and not worry about messing it up the first few time because it will happen. Original Message From: Konstantin Olchanski Sent: Friday, July 3, 2015 22:10 To: Larry Linder Cc: scientific-linux-users@fnal.gov Subject: Re: SL 7.2 On Fri, Jul 03, 2015 at 10:43:52AM -0400, Larry Linder wrote: Dear Sir: 6. We (everyone in the shop) unanimously hates the GENOME desk top. There does not appear to be able to select an alternate. Pretty cool! All my bases are belong to you! What did you use to generate this gibberish? -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: SL 7.2
On Sat, Jul 04, 2015 at 04:59:42PM -0400, prmari...@gmail.com wrote: The reason for the small /boot is ... ... the introduction of dracut ... alt.comp.separate.slash.boot.die.die.die alt.comp.dracut.die.die.die -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: SL 7.2
On Fri, Jul 3, 2015 at 10:43 AM, Larry Linder larry.lin...@micro-controls.com wrote: Dear Sir: Loaded SL 7.2 for third time and finally got it to where we can run it. I hate to complain but doe anyone check their work anymore. Or just compile it without errors and shove it out the door. There a several major things missing or wrong: 1. It groans and complains about size of /boot - its set to 101 Meg. Reloaded 7.2 again and there does not seem to be way away to change size of /boot partition. I periodically nags at you because there is only 25K left. Now way to fix problem or to shut of NAG function. This is not SL, this is upstream at Red Hat Enterprise Linux. There's a great deal to dislike about the current, highly graphical anaconda. The change from a flow chart, one step at a time, ncurses based, checklist installer of much older versions of Red Hat to the newer, bulky, graphical toolkits came with inconsistent layout, confusing options, confusing dependencies that used to be automatically handled as blockers and dealt with before proceeding in the ncurses, text based tools. It looks to me,, like in this case, you need to custom partition the disk. No idea why /boot is so small, but can you reduce the size of / and then expand /boot? Unfortunately, each layer of anaconda installer on top of undelying tools like parted for disk management, yum for package selection, and NetworkManager has injected its own layer of interface on top of *another* interface, on top of the actual configuration commands and tools. And the results are predictable: edge cases result form assumptions that were made, and which break down in practice. The size of /boot is one of those. 2. Could not find a way to set up groups or add new users. Had to go back to hand edit of passwd and groups to make it happen. No way to assign user id numbers. What? What happened to useradd and luseradd, groupadd and lgroupadd ? 3. Could not find a utility to set up Internet connection - When you used a KDE or Gnome the Mac address of the router was different. We have not been able to connect it to Network. Yeah, NetworkManager is not my friend. You might benefit from the lightweight 'nmcli'. I'm fairly unhappy about NetworkManager: 4. Default monitor was set to a pixel size you need a microscope to make out the text. If you used the Gnome it said monitor was IBM 12 France. KDE said monitor was IBM 12 Brazil. No other options were available. Maybe go back and hand edit Xterm stuff. A major step back by 20 years. Ouch. You're on a laptop? 5. With out com and a way to make display readable it becomes useless to run word processor, spread sheet, or anything. Can't optimize width or set width, You can go to full screen and the result is the same. There no way to set up terminal for other colors or text. Borders of GNOME are same color as other windows so you have to look twice to see which is which. List of dislikes goes on and on. Gnome is not my friend. I've not tried porting 'vtwm' to SL 7 or RHEL 7, but my tools for putting it on SL 6 and RHEL 6 are available at https://github.com/nkadel/vtwm-5.5.x-srpm. 6. We (everyone in the shop) unanimously hates the GENOME desk top. There does not appear to be able to select an alternate. See above. 7. Could not find a way to turn off high pitched sound when you tried to step back too far on a line. This part of NAG function and can't turn it off. 8. Tried to play a CD - old Marty Robins and it skipped tracks and got hung up and could not X it out. Had to Reboot. There is something basically wrong with the OS if you can't kill an application. Disk plays fine in my Dodge truck and does not have any visible defects. DVD writer is good as we were able to make a dual layer DVD for 7.2 with it using SL 5.11. 9. Gave up on SL 7.2 Notes: The default set up was like a quadriplegic Windows 7. We use one on our UPS account to ship stuff. Everyone who uses it hates it. Another disaster story. We have SL 5.11 deployed in the shop and support about 50 systems. I would not like to tell the boss that we had to trash 45 to 50 perfectly good monitors and give up our ability to add users, groups and network extensions etc. example: We have a number systems in shop and one by Mill and Lathe so there are no paper prints. Guys can review prints on line and set up CNC stuff on line. Saves a lot of time. Consider testing SL 6, which has _not_ had these problems for me. The evaluation box is a dual core AMD, 16 Gig of Ram, 4 disks - totaling 2 TB. and a GForce Video card, all pretty current stuff and a working 5.11 system. We will reload SL5.11 on to test box and start looking for another Linux distribution that has not been mangled by Ex Microsoft employees, working at RH. Due to obtuse problems we quit evaluation and will not deploy SL 7 - The best solution is to drop back and evaluate SL 6.5 and see if we can
SL 7.2
Dear Sir: Loaded SL 7.2 for third time and finally got it to where we can run it. I hate to complain but doe anyone check their work anymore. Or just compile it without errors and shove it out the door. There a several major things missing or wrong: 1. It groans and complains about size of /boot - its set to 101 Meg. Reloaded 7.2 again and there does not seem to be way away to change size of /boot partition. I periodically nags at you because there is only 25K left. Now way to fix problem or to shut of NAG function. 2. Could not find a way to set up groups or add new users. Had to go back to hand edit of passwd and groups to make it happen. No way to assign user id numbers. 3. Could not find a utility to set up Internet connection - When you used a KDE or Gnome the Mac address of the router was different. We have not been able to connect it to Network. 4. Default monitor was set to a pixel size you need a microscope to make out the text. If you used the Gnome it said monitor was IBM 12 France. KDE said monitor was IBM 12 Brazil. No other options were available. Maybe go back and hand edit Xterm stuff. A major step back by 20 years. 5. With out com and a way to make display readable it becomes useless to run word processor, spread sheet, or anything. Can't optimize width or set width, You can go to full screen and the result is the same. There no way to set up terminal for other colors or text. Borders of GNOME are same color as other windows so you have to look twice to see which is which. List of dislikes goes on and on. 6. We (everyone in the shop) unanimously hates the GENOME desk top. There does not appear to be able to select an alternate. 7. Could not find a way to turn off high pitched sound when you tried to step back too far on a line. This part of NAG function and can't turn it off. 8. Tried to play a CD - old Marty Robins and it skipped tracks and got hung up and could not X it out. Had to Reboot. There is something basically wrong with the OS if you can't kill an application. Disk plays fine in my Dodge truck and does not have any visible defects. DVD writer is good as we were able to make a dual layer DVD for 7.2 with it using SL 5.11. 9. Gave up on SL 7.2 Notes: The default set up was like a quadriplegic Windows 7. We use one on our UPS account to ship stuff. Everyone who uses it hates it. Another disaster story. We have SL 5.11 deployed in the shop and support about 50 systems. I would not like to tell the boss that we had to trash 45 to 50 perfectly good monitors and give up our ability to add users, groups and network extensions etc. example: We have a number systems in shop and one by Mill and Lathe so there are no paper prints. Guys can review prints on line and set up CNC stuff on line. Saves a lot of time. The evaluation box is a dual core AMD, 16 Gig of Ram, 4 disks - totaling 2 TB. and a GForce Video card, all pretty current stuff and a working 5.11 system. We will reload SL5.11 on to test box and start looking for another Linux distribution that has not been mangled by Ex Microsoft employees, working at RH. Due to obtuse problems we quit evaluation and will not deploy SL 7 - The best solution is to drop back and evaluate SL 6.5 and see if we can live with it. We have a SL 6.2 used on special project. We need to run spice, a Circuit layout editor, many spread sheets and a number of in house programs to manage inventory, component ordering, e-mail, VMWare to run several cad packages and a stress analysis program. Some employees run 12 desktops and two monitors. So fare we have not see a limitation for 5.11 but have had to install a number of newer libs to accommodate new SW. Larry Linder
Re: SL 7.2
On Fri, Jul 03, 2015 at 10:43:52AM -0400, Larry Linder wrote: Dear Sir: 6. We (everyone in the shop) unanimously hates the GENOME desk top. There does not appear to be able to select an alternate. Pretty cool! All my bases are belong to you! What did you use to generate this gibberish? -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
