Re: one-sided ssh connection, restricted access to X.

2009-12-05 Thread Steven Timm

Put the output of ssh -v in E-mail, it should say what is allowed.

Steve


On Sat, 5 Dec 2009, William Shu wrote:


Hi, Please for help on two [related] problems (I'm probably missing something 
glaring!):

1)  On my newly installed SL54 on a machine *not* connected to the internet, I 
tried to connect to a remote machine (Redhat 9) via ssh and it does not allow 
me. I am lost, as sshd is activated on both machines, and I had used a laptop 
to make the connection to the remote machine  before. I can ssh connect from 
the Redhat 9 machine.

QUESTION:  What could I be doing wrong? (script of my attempts below). I can;t 
pick up what to do from man pages.


2) I tried to open emacs as root, but was not allowed.  I was only allowed 
connection after I executed
$ xhost +
to allow everybody access.

QUESTION: Is there no more secure way of enabling users on local machine to use 
X without having to enumerate them, or allow all to access? In the past, I've 
always been able to open a terminal window as root or 3rd party and use without 
probs.

Regards,

William.
 


[...@csc101a ~]$ uname -a
Linux csc101A 2.6.18-164.2.1.el5PAE #1 SMP Tue Sep 29 19:14:47 EDT 2009 i686 
i686 i386 GNU/Linux
[...@csc101a ~]$
[...@csc101a ~]$ ssh -XY 192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ xhost
access control enabled, only authorized clients can connect
SI:localuser:wss
[...@csc101a ~]$ xhost +
access control disabled, clients can connect from any host
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ man xhost
[...@csc101a ~]$ ssh -v -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -vv -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -vvv -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$


--
[r...@csc101a wss]# emacs &
[1] 4833
[r...@csc101a wss]# Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

emacs: Cannot connect to X server :0.0.
Check the DISPLAY environment variable or use `-d'.
Also use the `xhost' program to verify that it is set to permit
connections from your machine.








--
--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.



RE: Any 'best' hard drives and incremental backup approaches to home systems?

2009-12-05 Thread Neil Aggarwal
> What is the best approach to handle incremental backup 
> data, if hard disks are not that reliable this days? 
> (This is a home system, and tape drives and variants are out!)

That depends on the size of your data.  
How big are we talking about?

For me, I use Subversion to keep full history of my 
development files on a remote server.  For the databases,
I pull daily backups using scp.  Then, at the end
of each week, I write the data backups and a copy
of all my working files to a DVD.

That works well for me.

> Which are the best marks of hard drives to purchase, 
> especially for linux-based systems that can be on for 
> relatively long periods -- 6-24 hours a day?

I use Seagate drives on all my servers.  They are running
Linux and are on 24x7.  Failures are very rare and Seagate
replaces anything that fails within 5 years with no
hassle.

I hope this helps,
Neil

--
Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net
CentOS 5.4 VPS with unmetered bandwidth only $25/month!
No overage charges, 7 day free trial, Google Checkout accepted


Re: one-sided ssh connection, restricted access to X.

2009-12-05 Thread William Shu
Thanks Miles,
Will implement solution for #2 ASAP..

For #1, the settings are the defaults obtained when installing from DVD (x86) 
-- enforcing, I think. Or is there a more specific setting I should search for? 
(can only access machine on working day, earliest.)

William.

--- On Sat, 12/5/09, Miles O'Neal  wrote:

From: Miles O'Neal 
Subject: Re: one-sided ssh connection, restricted access to X.
To: "William Shu" 
Cc: scientific-linux-us...@fnal.gov
Date: Saturday, December 5, 2009, 7:22 PM

For #1, what are your SELinux settings>

For #2, that also applies, but... you should NOT by default be able to have 
other users access your X display.  That's the way it is supposed to work.

If you want local users to be able to access your display, type in a terminal 
window:


xhost +localhost

Then as long as the DISPLAY is :0 they should work (if SELinux isn't in the 
way).  If you wnat DISPLAY to be set to $HOST:0 you need to type

xhost +$HOST


On Sat, Dec 5, 2009 at 8:58 AM, William Shu  wrote:


Hi, Please for help on two [related] problems (I'm probably missing something 
glaring!):

1)  On my newly installed SL54 on a machine *not* connected to the internet, I 
tried to connect to a remote machine (Redhat 9) via ssh and it does not allow 
me. I am lost, as sshd is activated on both machines, and I had used a laptop 
to make the connection to the remote machine  before. I can ssh connect from 
the Redhat 9 machine.


QUESTION:  What could I be doing wrong? (script of my attempts below). I can;t 
pick up what to do from man pages.


2) I tried to open emacs as root, but was not allowed.  I was only allowed 
connection after I executed 

$ xhost + 
to allow everybody access.

QUESTION: Is there no more secure way of enabling users on local machine to use 
X without having to enumerate them, or allow all to
 access? In the past, I've always been able to open a terminal window as root 
or 3rd party and use without probs.

Regards,

William.
 


[...@csc101a ~]$ uname -a
Linux csc101A 2.6.18-164.2.1.el5PAE #1 SMP Tue Sep 29 19:14:47 EDT 2009 i686 
i686 i386 GNU/Linux

[...@csc101a ~]$ 
[...@csc101a ~]$ ssh -XY 192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ xhost
access control enabled, only authorized clients can connect
SI:localuser:wss

[...@csc101a ~]$ xhost +
access control disabled, clients can connect from any host
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused

[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -XY w...@192.168.10.1

ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$
 man xhost
[...@csc101a ~]$ ssh -v -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.

debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -vv -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008

debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused

ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -vvv -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data
 /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused

ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ 


--
[r...@csc101a wss]# emacs &
[1] 4833
[r...@csc101a wss]# Xlib: connection to ":0.0" refused by server

Xlib: No protocol specified

emacs: Cannot connect to X server :0.0.
Check the DISPLAY environment variable or use `-d'.
Also use the `xhost' program to verify that it is set to permit
connections from your machine.







  





  


Any 'best' hard drives and incremental backup approaches to home systems?

2009-12-05 Thread William Shu
Hi,
I would be grateful for feedback on the following.

At some point in time, I preferred to backup data and software on disks
on separate machines so as to be able to have incremental backups. Use
of CD/DVD R or RW was not adequate, as they frequently went bad, kept 
incoherent trail of updates or simply could not be updated. Thus, I settled for 
having material on multiple drives.



I've been having disk crash on my computers at home (with Maxtor drives) and 
some informal
investigations suggested Western Digital harddrives were among the best
on the market. Unfortunately, I suddenly lost my laptop and two western
digital internal disk drives, and one external drive (also a Western
digital), sort of without warning. Ironically, the Fijutsu drive on a clone I 
had 10 years ago, and bought the WD for fear it might fail, is working (it 
fails the S. M. A. R. T. boot test sometimes)!

My questions are:
QUESTION 1
What is the best approach to handle incremental backup data, if hard disks are 
not that reliable this days? (This is a home system, and tape drives and 
variants are out!)


QUESTION 2)
Which are the best marks of hard drives to purchase, especially for linux-based 
systems that can be on for relatively long periods -- 6-24 hours a day?

REgards,

William.







Re: 5.4 fail to install from DVD

2009-12-05 Thread feddds
Hola Antonio,

Try CD media. Worked great on my installations. I have made 5 in this
week. No problems at all.

Good luck.
Feddds.



2009/12/5 Antonio Silvestri :
> Hi,
>
> this step does not appear. First page is "choose language" then "keyboard
>
> type" then "Installation method"  from here
>
> I have installed only via network. It seems that DVD is not recognized
> after booting.
>
> Bye
>
> Antonio
>


Re: SL forums

2009-12-05 Thread feddds
Well Troy, I might be a creazy guy but I tried to install vlc on my
box now, and gave me conflict with famous lib.flac.8 on atrmps
repository. Odd, yestarday I did it without problem on muy dad`s box.

Tried your way and went OK!

I really prefer VLC but Xine is fine too.

Also found very easy your comand " yum --enablerepo=dag install xine"

Not keen to console, but I accept that is very practical! Fun to learn
like this.

Thanks!




2009/12/4 Troy Dawson :
> Hi,
> I see that you already have an answer, but for me, I prefer xine.  This is
> what I usually do to get various movie playback
>
>  yum --enablerepo=dag install xine
>
> If mplayer is working for you, that's great.  Just wanted you to know that
> there are options.
>
> Troy
>
> feddds wrote:
>>
>> Ok then Urs.
>>
>> Here it goes then:
>> Have you try to view .wmv files in SL?
>> (dont kill me, I know what means for a linux user to give hints on how
>> to reproduce non free video formats on windows)
>> But I need to install SL on my dad`s box.
>>
>> Through a google search I decided to install mplayer but gave problems
>> of depency with atrm and dag repositories.
>>
>> Tried vlc right now and dependecies were solved successfully. Tell you
>> later how it goes.
>>
>> Feddds.
>>
>>
>>
>>
>>
>>
>>
>> 2009/12/4 Urs Beyerle :
>>>
>>> Hi Feddds,
>>>
>>> There is no SL forum. This mailing list is the right place to ask
>>> questions and give some feedback.
>>>
>>> Cheers,
>>>
>>>   Urs
>>>
>>>
>>>
>>> On 12/04/2009 08:39 PM, feddds wrote:

 I was wondering if there was a SF forum to get help and give some
 feedback.
 Thanks,
 Feddds.

>
>
> --
> __
> Troy Dawson  daw...@fnal.gov  (630)840-6468
> Fermilab  ComputingDivision/LSCS/CSI/USS Group
> __
>


one-sided ssh connection, restricted access to X.

2009-12-05 Thread William Shu
Hi, Please for help on two [related] problems (I'm probably missing something 
glaring!):

1)  On my newly installed SL54 on a machine *not* connected to the internet, I 
tried to connect to a remote machine (Redhat 9) via ssh and it does not allow 
me. I am lost, as sshd is activated on both machines, and I had used a laptop 
to make the connection to the remote machine  before. I can ssh connect from 
the Redhat 9 machine.

QUESTION:  What could I be doing wrong? (script of my attempts below). I can;t 
pick up what to do from man pages.


2) I tried to open emacs as root, but was not allowed.  I was only allowed 
connection after I executed 
$ xhost + 
to allow everybody access.

QUESTION: Is there no more secure way of enabling users on local machine to use 
X without having to enumerate them, or allow all to access? In the past, I've 
always been able to open a terminal window as root or 3rd party and use without 
probs.

Regards,

William.
 


[...@csc101a ~]$ uname -a
Linux csc101A 2.6.18-164.2.1.el5PAE #1 SMP Tue Sep 29 19:14:47 EDT 2009 i686 
i686 i386 GNU/Linux
[...@csc101a ~]$ 
[...@csc101a ~]$ ssh -XY 192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ xhost
access control enabled, only authorized clients can connect
SI:localuser:wss
[...@csc101a ~]$ xhost +
access control disabled, clients can connect from any host
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -XY w...@192.168.10.1
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ man xhost
[...@csc101a ~]$ ssh -v -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -vv -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ ssh -vvv -XY 192.168.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.10.1 [192.168.10.1] port 22.
debug1: connect to address 192.168.10.1 port 22: Connection refused
ssh: connect to host 192.168.10.1 port 22: Connection refused
[...@csc101a ~]$ 


--
[r...@csc101a wss]# emacs &
[1] 4833
[r...@csc101a wss]# Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

emacs: Cannot connect to X server :0.0.
Check the DISPLAY environment variable or use `-d'.
Also use the `xhost' program to verify that it is set to permit
connections from your machine.




  


Re: 5.4 fail to install from DVD

2009-12-05 Thread Antonio Silvestri
Hi, 

this step does not appear. First page is "choose language" then "keyboard

type" then "Installation method"  from here

I have installed only via network. It seems that DVD is not recognized
after booting.

Bye

Antonio