[CentOS] black display during installation of CentOS5.5

2010-10-23 Thread Ritika Garg 
I was doing the installation on DELL inspiron laptop and this problem
occurred for CentOS5.5 but not for CentOS5.3. So shall I install CentOS5.3
and then do "yum update"?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] ssh with shared home dir

2010-10-23 Thread Tim Dunphy 
hahah.. thanks john! :) fortunately that key was in existence for only
a few hours, and has now been deleted. it was behind a firewall. just
sayin! but good catch!!!

thanks!! :-)

On Fri, Oct 22, 2010 at 11:25 PM, JohnS  wrote:
>
> On Fri, 2010-10-22 at 23:17 -0400, Tim Dunphy wrote:
>> uhm.. what's your problem, dude?
>>
>
>
> My problem is you Private Key is Wide Open to the whole World so now go
> and create a new one, unless you the world to have it.
>
> :-)
>
> John
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
Here's my RSA Public key:
gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9

Share and enjoy!!
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] problem regarding rpmbuild : creating rpm for python files

2010-10-23 Thread Markus Falb 
On 20.10.10 20:17, saurabh verma wrote:
>
> And when i try to run rpmbuild -ba command on this spec file , rpmbuild
> tried to optimize the python byte coded files , which i can see from ( i
> guess macros ) " + /usr/lib/rpm/brp-python-bytecompile" , and fails
> after that .
>
> http://pastie.org/1236040
>
> please help me about controlling this behaviour so that I can skip the
> "brp-python-bytecompile" section .

Instead you could declare pyo files as ghosts, for instance:

%ghost /usr/lib/python2.4/site-packages/punjab/error.pyo

-- 
Best Regards,
Markus Falb

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] graphics driver

2010-10-23 Thread Ritika Garg 
I did installation of CentOS5.5 in text mode and made changes at the
following places in the file /etc/X11/xorg.conf :
section "device"
identifier : "vesa"
driver:"vesa"
section "screen"
device:"vesa"

Also in the file /etc/inittab I changed id:3:initdefault to id:5:initdefault
so that I can boot linux in graphical mode.
I had to make the changes in xorg.conf because the visibility of the
graphics was so poor that it was impossible to work.
The installation was done on Dell Inspiron N5010 with the chipset: Intel(R)
HM57 Express chipset LPC interface controller 3B0B which is a part of Mobile
intel 5 series
The video controller is: Intel (R) HD Graphics
Although graphics is there but the resolution and refresh rate are limited
to 1024*768 and 0Hz, so I need to find the video driver.
I had given "i810" in xorg.conf but that didn't work. Which driver is
recommended?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] graphics driver

2010-10-23 Thread John R Pierce 
On 10/23/10 11:23 AM, Ritika Garg wrote:
> I did installation of CentOS5.5 in text mode and made changes at the 
> following places in the file /etc/X11/xorg.conf :
> section "device"
> identifier : "vesa"
> driver:"vesa"
> section "screen"
> device:"vesa"
>
> Also in the file /etc/inittab I changed id:3:initdefault to 
> id:5:initdefault so that I can boot linux in graphical mode.
> I had to make the changes in xorg.conf because the visibility of the 
> graphics was so poor that it was impossible to work.
> The installation was done on Dell Inspiron N5010 with the chipset: 
> Intel(R) HM57 Express chipset LPC interface controller 3B0B which is a 
> part of Mobile intel 5 series
> The video controller is: Intel (R) HD Graphics
> Although graphics is there but the resolution and refresh rate are 
> limited to 1024*768 and 0Hz, so I need to find the video driver.
> I had given "i810" in xorg.conf but that didn't work. Which driver is 
> recommended?

I don't have one of those, but that system has the graphics controller 
integrated into the CPU (!) rather than the chipset...  Its called 
Arrandale, and I believe the correct X.org driver is IGDNG (Intel 
Graphics Device Next Generation)




___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [SOLVED] more software raid questions

2010-10-23 Thread fred smith 
On Thu, Oct 21, 2010 at 11:03:27AM -0700, Nataraj wrote:
> fred smith wrote:
> >
> > Thanks for the additional information.
> >
> > I'll try backing up everything this weekend then will take a stab at it.
> >
> > someone said earlier that the differing raid superblocks were probably
> > the cause of the misassignment in the first place. but I have no clue
> > how the superblocks could have become messed up, can any of you comment
> > on that? willl I need to hack at that issue, too, before I can succeed?
> >
> > thanks again!
> >
> >   
> >> Nataraj
> >> 
> I would first try adding the drives back in with:
> 
> mdadm /dev/mdN -a /dev/sdXn
> 
> Again, this is after having stopped the bogus md arrays.

Nataraj, that worked fine, didn't need to --force it. Now I'm back to
having two devices in md0 and two in md1, and they're the RIGHT two! :)
Put the box in single-user mode to do the work, then after the array
finished resyncing, rebooted and it came up with the right two md devices.

I appreciate your tutoring me on this, you've been most helpful.

Thanks a bunch!

Oh, can you refer me to any good documentation on how to admin a
software raid system? One aimed for people, like me, who are 
computer literate, but have never trained as a sysadmin, and who
don't know much about RAID...

thanks again!

Fred
> 
> If that doesn't work, I would try assemble with a --force option, which 
> might be a little more dangerous than the hot add, but probably not 
> much. I can say that when I have a drive fall out of an array I am 
> always able to add it back with the first command (-a). As I mentioned, 
> I do have bitmaps on all my arrays, but you can't change that until you 
> rebuild the raidset.
> 
> I believe these comands will take care of everything. You shouldn't have 
> to do any diddling of the superblocks at a low level, and if the problem 
> is that bad, you might be best to backup and recreate the whole array or 
> engage the services of someone who knows how to muck with the data 
> structures on the disk. I've never had to use anything other than mdadm 
> to manage my raid arrays and I've never lost data with linux software 
> raid in the 10 or more years that I've been using it. I've found it to 
> be quite robust. Backing up is just a precaution that is a good idea for 
> anyone to take if they care about their data.
> 
> If these problems reoccur on a regular basis, you could have a bad 
> drive, a power supply problem or a cabling problem. Assuming your drives 
> are attached to SATA, SCSI or SAS controller, you can use smartctl to 
> check the drives and see if they are getting errors or other faults. 
> smartctl will not work with USB or firefire attached drives.
> 
> Nataraj
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   But God demonstrates his own love for us in this: 
 While we were still sinners, 
  Christ died for us.
--- Romans 5:8 (niv) --
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [SOLVED] more software raid questions

2010-10-23 Thread Nataraj 
fred smith wrote:
> On Thu, Oct 21, 2010 at 11:03:27AM -0700, Nataraj wrote:
>   
>> fred smith wrote:
>> 
>>> Thanks for the additional information.
>>>
>>> I'll try backing up everything this weekend then will take a stab at it.
>>>
>>> someone said earlier that the differing raid superblocks were probably
>>> the cause of the misassignment in the first place. but I have no clue
>>> how the superblocks could have become messed up, can any of you comment
>>> on that? willl I need to hack at that issue, too, before I can succeed?
>>>
>>> thanks again!
>>>
>>>   
>>>   
 Nataraj
 
 
>> I would first try adding the drives back in with:
>>
>> mdadm /dev/mdN -a /dev/sdXn
>>
>> Again, this is after having stopped the bogus md arrays.
>> 
>
> Nataraj, that worked fine, didn't need to --force it. Now I'm back to
> having two devices in md0 and two in md1, and they're the RIGHT two! :)
> Put the box in single-user mode to do the work, then after the array
> finished resyncing, rebooted and it came up with the right two md devices.
>
> I appreciate your tutoring me on this, you've been most helpful.
>
> Thanks a bunch!
>
> Oh, can you refer me to any good documentation on how to admin a
> software raid system? One aimed for people, like me, who are 
> computer literate, but have never trained as a sysadmin, and who
> don't know much about RAID...
>
> thanks again!
>
> Fred
>   
Hi Fred,

You might try this one, since it seems to be one of the more up to date:
https://raid.wiki.kernel.org/index.php/Linux_Raid

Also the mdadm man page and running "mdadm --help".

Oh, and there's this, however, some of the pages just happen to be in 
Chinese...
http://wiki.centos.org/Search?action=fullsearch&titlesearch=1&value=raid 


Nataraj



Nataraj


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos