Hi yarad Try editing the /etc/X11/gdm/gdm.connf and edit the value of xdmcp section Change from Enable=false to Enable= true and resart X session and try connecting from humming bird . Regards Karthik redhat-list-request@xxxxxxxxxx wrote: Send redhat-list mailing list submissions to redhat-list@xxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/redhat-list or, via email, send a message with subject or body 'help' to redhat-list-request@xxxxxxxxxx You can reach the person managing the list at redhat-list-owner@xxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of redhat-list digest..." Today's Topics: 1. Re: paravirtualized 32-bit on 64-bit host? (Jose R R) 2. X config RH 3 (Yard, John) 3. RE: fsck ext3 (Krishnaprasad_K@xxxxxxxx) ---------------------------------------------------------------------- Message: 1 Date: Fri, 14 Mar 2008 09:43:17 -0700 From: "Jose R R" Subject: Re: paravirtualized 32-bit on 64-bit host? To: "General Red Hat Linux discussion list" Message-ID: Content-Type: text/plain; charset=ISO-8859-1 On 3/7/08, Furnish, Trever G wrote: > > Anyone managed to get a paravirtualized 32-bit guest working on a 64-bit > redhat host? The RHEL5.1 release notes claim there's preview support > for it. If by "technology preview" they mean, "We tried it and it > didn't work", then yeah, I guess there's support. But I'm having no > luck. :-( > > http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/release-note > s/RELEASE-NOTES-U1-x86_64-en.html > > Anyone else fairing better? > > -- > Trever > Well last year I installed a 32-bit WinXP instance under 64-bit OpenSuSE host implementation of Xen. Of course, proprietary technology is not actually paravirtualized, but rather fully virutalized with the help of the (AMD CPU in my specific case) hardware extensions. You can find an overview of what I did, if interested of course, at: http://www.metztli-it.com/blog/index.php?blog=4&title=open-source-on-sun-microsystems-sun-ultr-20&more=1&c=1&tb=1&pb=1 Regards, Jose R Rodriguez http://www.metztli-it.com ------------------------------ Message: 2 Date: Fri, 14 Mar 2008 13:27:15 -0700 From: "Yard, John" Subject: X config RH 3 To: "General Red Hat Linux discussion list" Message-ID: <435F8F2B1312334BAB5F0A1509A11E5E041ADD13@xxxxxxxxxxxxxxx> Content-Type: text/plain; charset="us-ascii" SSH is not in the picture. We are using the pc Hummingbird client, another admin says he remembers commenting out a line from an X config file , and then being able to connect using xdmcp . Has nothing to do with xhost, I've tried all variations. JYard -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Andrew Bacchi Sent: Friday, March 14, 2008 5:44 AM To: General Red Hat Linux discussion list Subject: Re: X config RH 3 You probably need to start your ssh session using the "-X" switch. That will enable xforwarding. ssh -X somehost@xxxxxxx Or, you may need to add those hosts to your xhost table. xhost +somehost@xxxxxxx Yard, John wrote: > When I point my X window server to 2 new > RH 3 systems , I get the following messages : > > > AUDIT: Thu Mar 13 16:26:43 2008: 3704 X: client 4 rejected from local > host > Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > AUDIT: Thu Mar 13 16:55:53 2008: 3704 X: client 4 rejected from local > host > Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > AUDIT: Thu Mar 13 17:38:31 2008: 3704 X: client 4 rejected from local > host > Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > > I never get a signin screen. > > My other RH3 systems work fine, and I see no differences . > > Any suggestions ? > > JYard > UCLA > > > -- veritatis simplex oratio est Andrew Bacchi Staff Systems Programmer Rensselaer Polytechnic Institute phone: 518 276-6415 fax: 518 276-2809 http://www.rpi.edu/~bacchi/ -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ------------------------------ Message: 3 Date: Sat, 15 Mar 2008 11:39:18 +0530 From: Subject: RE: fsck ext3 To: Message-ID: <4132777EBCB7D7439B2F85053A5A58D8C0F06F@xxxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="us-ascii" I thought ur facing issues with your root file system. The file system that ur facing issues won't be mounted in runlevel 1 right?. Can you run the same command for the device that is mounted to /ora_za3 Thanks, Krishnaprasad -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Dave Martini Sent: Friday, March 14, 2008 9:26 PM To: General Red Hat Linux discussion list Subject: Re: fsck ext3 I can't do that because the root file system is mounted in run level 1 and it says WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Or, is it ok to run it even though it's mounted. Did you mean boot from a CD rom? Dave. Dave Martini wrote: > Why the root file system when the problem is on one of my > volumes in an external drive? > Dave. > > > Krishnaprasad_K@xxxxxxxx wrote: >> Boot into runlevel 1 and then fix the bad block using the following >> command >> >> e2fsck -y /dev/sdxx where sdxx is your root file system partition.. >> >> >> Thanks, >> Krishnaprasad >> >> -----Original Message----- >> From: redhat-list-bounces@xxxxxxxxxx >> [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Dave Martini >> Sent: Thursday, March 13, 2008 10:28 PM >> To: General Red Hat Linux discussion list >> Subject: fsck ext3 >> >> One of my est3 file systems went into read only mode. Does this usually >> mean the drive is going bad? >> >> When I umounted and the mounted it again it said to run fsck manually. >> I did but keep getting the Illegal block in inode messages below. >> Is there a way to fix this? >> Thanks. >> Dave. >> >> >> >> #fsck -v /u02 >> fsck 1.35 (28-Feb-2004) >> e2fsck 1.35 (28-Feb-2004) >> Resize inode not valid. Recreate? yes >> >> /ora_za3 contains a file system with errors, check forced. >> Pass 1: Checking inodes, blocks, and sizes >> Inode 54473213 has illegal block(s). Clear? yes >> >> Illegal block #-1 (542592844) in inode 54473213. CLEARED. >> Illegal block #-1 (1162168403) in inode 54473213. CLEARED. >> Illegal block #-1 (1162545998) in inode 54473213. CLEARED. >> Illegal block #-1 (542723148) in inode 54473213. CLEARED. >> Illegal block #-1 (1380929357) in inode 54473213. CLEARED. >> Illegal block #-1 (843188549) in inode 54473213. CLEARED. >> Illegal block #-1 (1142960440) in inode 54473213. CLEARED. >> Illegal block #-1 (1728513729) in inode 54473213. CLEARED. >> Illegal block #-1 (1869376609) in inode 54473213. CLEARED. >> Illegal block #-1 (822506350) in inode 54473213. CLEARED. >> Illegal block #-1 (808662326) in inode 54473213. CLEARED. >> Too many illegal blocks in inode 54473213. >> Clear inode? yes >> >> Inode 54473328 has illegal block(s). Clear? >> >> > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ------------------------------ __ redhat-list mailing list Unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list End of redhat-list Digest, Vol 49, Issue 13 ******************************************* --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
