Re: How to do WPA wifi authentication at run level 3 on SL 5.5 ?
On Thu, Oct 9, 2014 at 1:30 AM, David G.Miller d...@davenjudy.org wrote: Allen Wilkinson aw@... writes: David, Key question is how do I configure network connections with NetworkManager from the command line? SNIP Probably not the answer you want to hear but you don't with EL5 and earlier. It is possible to work directly with the appropriate configuration files like we did in the good old days before NetworkMangler. There were some reasonably good how-tos that I followed to get WiFi working on my laptop back in 2005. Getting the original how-to is probably much better than me trying to remember what I did. It also tends to be far more flexible, consistent, and reliable than letting NetworkManager anywhere *near* your configuraiton files. The only uses I've found for NetworkManager are for VPN systems, which are awkward to disalbe and reset from the command line, But setting up pair bonding, tagged VLAN's,and bridged devices for KVM are only a few of the problems that are better solved thorugh direct command line access.
Re: paraview
On Wed, 2014-10-08 at 18:01 -0700, Yasha Karant wrote: I have downloaded and yum installed paraview-3.10.1-4.el6.x86_64.rpm paraview-data-3.10.1-4.el6.noarch.rpm The application installs, but immediately crashes X windows. /var/log/Xorg.*.log and /var/log/messages, and the like, show nothing obvious (to me). The screen goes black, and then I am back to the window manager SL 6 login splash screen. The system allows me to log in and everything works unless I again invoke paraview, in which case the cycle repeats. Does anyone have a working EL 6 X86-64 paraview, and if so, was it an RPM install, the binaries as provided by Paraview as a tar.gz file, or was it built from source? How is it configured? Thus far, there has been response via the paraview list (a different list than SL). Yasha Karant We have it installed from the ParaView-4.0.1-Linux-64bit.tar.gz file and it supposedly works - I am not a ParaView user but it certainly starts up and does not crash in the way you describe. -- Mark Whidby Infrastructure Coordinator (Unix) Physics/Chemistry/EAES/Mathematics Team IT Services, Faculty of Engineering and Physical Sciences
Re: paraview
Hello, I installed paraview from the epel repo (version: 3.8.1-2). This runs without any problems. Best regards, Horst On Wed, Oct 08, 2014 at 06:01:10PM -0700, Yasha Karant wrote: I have downloaded and yum installed paraview-3.10.1-4.el6.x86_64.rpm paraview-data-3.10.1-4.el6.noarch.rpm The application installs, but immediately crashes X windows. /var/log/Xorg.*.log and /var/log/messages, and the like, show nothing obvious (to me). The screen goes black, and then I am back to the window manager SL 6 login splash screen. The system allows me to log in and everything works unless I again invoke paraview, in which case the cycle repeats. Does anyone have a working EL 6 X86-64 paraview, and if so, was it an RPM install, the binaries as provided by Paraview as a tar.gz file, or was it built from source? How is it configured? Thus far, there has been response via the paraview list (a different list than SL). Yasha Karant smime.p7s Description: S/MIME cryptographic signature
Re: Network aliases
thank you this was very helpful. On Mon, Jul 28, 2014 at 5:09 PM, Orion Poplawski or...@cora.nwra.com wrote: On 07/28/2014 01:49 PM, Andrew Z wrote: I havent figured out how to manage those files.. The original script creates dozens of aliases - one per destination, by replacing first Xxx with 127. This makes it intuitive where alias points to. Now with each file having the same name (lo:port) imnot sure how to manage these aliases. I want to add, that I suspect that im missing something obvious and/or just dont understand how network stack works now. Any help is very much appreciated, since all my information is from rhel one page guide , some blog and just trying to get aliases to work. Manually you could do: ip addr add 127.112.113.xxx dev lo On Jul 28, 2014 10:40 AM, Orion Poplawski or...@cora.nwra.com mailto:or...@cora.nwra.com wrote: On 07/28/2014 08:08 AM, Andrew Z wrote: I have an apple os script, that creates an lo alias ( for example 127.112.113) and then ssh -p 127.112.113 rest of the command To begin with ifconfig doesn't work on creating aliases and according to rhel docs I need to copy ethXxx files if I want to create these aliases. Is there a better way, than to copy files, to achieve the same? What's the concern with making a new ifcfg-* file to create the alias? -- Orion Poplawski Technical Manager 303-415-9701 x222 tel:303-415-9701%20x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 tel: 303-415-9702 3380 Mitchell Lane or...@nwra.com mailto:or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com
Re: paraview
Two information items: 1. I did yum remove (all existing paraview rpm installs) followed by the GUI install of the X86-64 versions from EPEL referenced below in this thread. Execution of paraview failed in the same manner -- immediate death of X 2. As I maintained a login screen as a terminal on a different screen (ctrl-alt-F4), the postmortem in ~/.xsession-errors, where ~ is my home (not root) directory. is paraview: Fatal IO error: client killed with no additional messages I can provide the various log files in /var/log if this will help. Any additional suggestions? Is there a way to execute paraview within some sort of tracing shell to find the exact call or calls that failed? Thanks, Yasha Karant On 10/09/2014 02:59 AM, Horst Hettrich wrote: Hello, I installed paraview from the epel repo (version: 3.8.1-2). This runs without any problems. Best regards, Horst On Wed, Oct 08, 2014 at 06:01:10PM -0700, Yasha Karant wrote: I have downloaded and yum installed paraview-3.10.1-4.el6.x86_64.rpm paraview-data-3.10.1-4.el6.noarch.rpm The application installs, but immediately crashes X windows. /var/log/Xorg.*.log and /var/log/messages, and the like, show nothing obvious (to me). The screen goes black, and then I am back to the window manager SL 6 login splash screen. The system allows me to log in and everything works unless I again invoke paraview, in which case the cycle repeats. Does anyone have a working EL 6 X86-64 paraview, and if so, was it an RPM install, the binaries as provided by Paraview as a tar.gz file, or was it built from source? How is it configured? Thus far, there has been response via the paraview list (a different list than SL). Yasha Karant
Re: paraview
One additional possibility. My laptop is running IA-32 SL6x (I fully understand that this will not be possible for SL7 that will require me to enable the laptop as X86-64 64 bit mode). Paraview works fine there. I thus downloaded from EPEL the IA-32 version to run on my office workstation that is running X86-64 SL6x (and thus previously I had installed and attempted to run the X86-64 version of paraview). The yum install output appears below; however, I answered N to terminate the install as it appears to be updating a number of various gcc and associated library files and utilities. My understanding is that these are an integral part of Linux system execution and any mismatch can cause full operating system failure. Is this correct or should I proceed? Thanks. [root@jb344 Downloads]# yum install paraview-3.8.1-2.el6.i686.rpm Loaded plugins: downloadonly, priorities, refresh-packagekit, security, tmprepo, : verify Setting up Install Process Examining paraview-3.8.1-2.el6.i686.rpm: paraview-3.8.1-2.el6.i686 Marking paraview-3.8.1-2.el6.i686.rpm to be installed Resolving Dependencies -- Running transaction check --- Package paraview.i686 0:3.8.1-2.el6 will be installed -- Processing Dependency: paraview-data = 3.8.1-2.el6 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libOSMesa.so.6 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtCLucene.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtCore.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtGui.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtHelp.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtNetwork.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtSql.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libQtXml.so.4 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libhdf5.so.6 for package: paraview-3.8.1-2.el6.i686 -- Processing Dependency: libpython2.6.so.1.0 for package: paraview-3.8.1-2.el6.i686 -- Running transaction check --- Package hdf5.i686 0:1.8.5.patch1-7.el6 will be installed -- Processing Dependency: libgfortran.so.3(GFORTRAN_1.0) for package: hdf5-1.8.5.patch1-7.el6.i686 -- Processing Dependency: libgfortran.so.3 for package: hdf5-1.8.5.patch1-7.el6.i686 --- Package mesa-libOSMesa.x86_64 0:9.0-0.8.el6_4.3 will be updated --- Package mesa-libOSMesa.i686 0:9.2-0.5.el6_5.2 will be installed --- Package mesa-libOSMesa.x86_64 0:9.2-0.5.el6_5.2 will be an update --- Package paraview-data.noarch 0:3.8.1-2.el6 will be installed --- Package python-libs.x86_64 0:2.6.6-51.el6 will be updated -- Processing Dependency: python-libs(x86-64) = 2.6.6-51.el6 for package: python-2.6.6-51.el6.x86_64 --- Package python-libs.i686 0:2.6.6-52.el6 will be installed -- Processing Dependency: libgdbm.so.2 for package: python-libs-2.6.6-52.el6.i686 -- Processing Dependency: libffi.so.5 for package: python-libs-2.6.6-52.el6.i686 --- Package python-libs.x86_64 0:2.6.6-52.el6 will be an update --- Package qt.x86_64 1:4.6.2-26.el6_4 will be updated -- Processing Dependency: qt = 1:4.6.2-26.el6_4 for package: 1:qt-doc-4.6.2-26.el6_4.noarch -- Processing Dependency: qt(x86-64) = 1:4.6.2-26.el6_4 for package: 1:qt-sqlite-4.6.2-26.el6_4.x86_64 -- Processing Dependency: qt(x86-64) = 1:4.6.2-26.el6_4 for package: 1:qt-mysql-4.6.2-26.el6_4.x86_64 -- Processing Dependency: qt(x86-64) = 1:4.6.2-26.el6_4 for package: 1:qt-devel-4.6.2-26.el6_4.x86_64 --- Package qt.i686 1:4.6.2-28.el6_5 will be installed --- Package qt.x86_64 1:4.6.2-28.el6_5 will be an update --- Package qt-x11.x86_64 1:4.6.2-26.el6_4 will be updated --- Package qt-x11.i686 1:4.6.2-28.el6_5 will be installed -- Processing Dependency: qt-sqlite(x86-32) = 1:4.6.2-28.el6_5 for package: 1:qt-x11-4.6.2-28.el6_5.i686 -- Processing Dependency: phonon-backend(x86-32) = 4.3 for package: 1:qt-x11-4.6.2-28.el6_5.i686 -- Processing Dependency: libmng.so.1 for package: 1:qt-x11-4.6.2-28.el6_5.i686 -- Processing Dependency: libgstvideo-0.10.so.0 for package: 1:qt-x11-4.6.2-28.el6_5.i686 -- Processing Dependency: libgstreamer-0.10.so.0 for package: 1:qt-x11-4.6.2-28.el6_5.i686 -- Processing Dependency: libgstinterfaces-0.10.so.0 for package: 1:qt-x11-4.6.2-28.el6_5.i686 -- Processing Dependency: libgstbase-0.10.so.0 for package: 1:qt-x11-4.6.2-28.el6_5.i686 --- Package qt-x11.x86_64 1:4.6.2-28.el6_5 will be an update -- Running transaction check --- Package gdbm.i686 0:1.8.0-36.el6 will be installed --- Package gstreamer.i686 0:0.10.29-1.el6 will be installed --- Package gstreamer-plugins-base.i686 0:0.10.29-2.el6 will be installed -- Processing Dependency: libvorbisenc.so.2 for package: gstreamer-plugins-base-0.10.29-2.el6.i686 -- Processing Dependency: libvorbis.so.0 for package: gstreamer-plugins-base-0.10.29-2.el6.i686 -- Processing Dependency: libvisual-0.4.so.0
Re: paraview
Hi, try to run it via 'strace' command from CLI, like eg. strace paraview and see where it stops, sometime it gives usefull hint.. On 10/09/2014 09:09 PM, Yasha Karant wrote: Two information items: 1. I did yum remove (all existing paraview rpm installs) followed by the GUI install of the X86-64 versions from EPEL referenced below in this thread. Execution of paraview failed in the same manner -- immediate death of X 2. As I maintained a login screen as a terminal on a different screen (ctrl-alt-F4), the postmortem in ~/.xsession-errors, where ~ is my home (not root) directory. is paraview: Fatal IO error: client killed with no additional messages I can provide the various log files in /var/log if this will help. Any additional suggestions? Is there a way to execute paraview within some sort of tracing shell to find the exact call or calls that failed? Thanks, Yasha Karant On 10/09/2014 02:59 AM, Horst Hettrich wrote: Hello, I installed paraview from the epel repo (version: 3.8.1-2). This runs without any problems. Best regards, Horst On Wed, Oct 08, 2014 at 06:01:10PM -0700, Yasha Karant wrote: I have downloaded and yum installed paraview-3.10.1-4.el6.x86_64.rpm paraview-data-3.10.1-4.el6.noarch.rpm The application installs, but immediately crashes X windows. /var/log/Xorg.*.log and /var/log/messages, and the like, show nothing obvious (to me). The screen goes black, and then I am back to the window manager SL 6 login splash screen. The system allows me to log in and everything works unless I again invoke paraview, in which case the cycle repeats. Does anyone have a working EL 6 X86-64 paraview, and if so, was it an RPM install, the binaries as provided by Paraview as a tar.gz file, or was it built from source? How is it configured? Thus far, there has been response via the paraview list (a different list than SL). Yasha Karant
Re: paraview
On 10/09/2014 01:40 PM, Yasha Karant wrote: One additional possibility. My laptop is running IA-32 SL6x (I fully understand that this will not be possible for SL7 that will require me to enable the laptop as X86-64 64 bit mode). Paraview works fine there. I thus downloaded from EPEL the IA-32 version to run on my office workstation that is running X86-64 SL6x (and thus previously I had installed and attempted to run the X86-64 version of paraview). The yum install output appears below; however, I answered N to terminate the install as it appears to be updating a number of various gcc and associated library files and utilities. My understanding is that these are an integral part of Linux system execution and any mismatch can cause full operating system failure. Is this correct or should I proceed? I think you'll find that you have system updates ready regardless of the paraview install. Run yum upgrade to verify. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
