[CentOS] Where can I get the source package of the RPM alsa-driver-1.0.20-78.el5.i386.rpm

[jasonwen]

Hi all,

    I want to get the the source codes of the RPM package
alsa-driver-1.0.20-78.el5.i386.rpm, but I can not find it, anyone knows
that?



thanks a lot
Jason Wen



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

Re: [CentOS] web filtering for remote computers

[Steven Vishoot]

- Original Message 
> From: Dhaval Thakar 
> To: CentOS mailing list 
> Sent: Thursday, May 21, 2009 11:55:15 PM
> Subject: Re: [CentOS] web filtering for remote computers
> 
> 
> John R Pierce wrote:
> > Dhaval Thakar wrote:
> >  
> >> Hi,
> >>
> >> I am using Squid for local users since two years & is working fine.
> >> I am trying to implement web filtering for remote computers e.g few 
> >> laptops & 
> branch / franchise computers on dynamic ips.
> >>
> >> I do not want to use Squid proxy for it, if all remote computers will use 
> Squid from my public ip, bandwidth utilization will increase.
> >> Need valuable suggestion to achieve this.
> >>  
> >>
> >
> > how are these remote computers connected to the network, and what OS are 
> > they running?
> >
> >  
> all are windows clients
> connecting through internet using dynamic ips.
> > filtering, by necessity, has to be between the user and the thing you 
> > want to filter.
> >  
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

well i think we get the hint!!!

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

Re: [CentOS] Fixing to bite the dust?

[nate]

sam wrote:
> I dunno Nate,
>
> It started all this extraenous logging stuff after kicking memory
> from a paltry 256m up to 2 Gigs. The system has on occasion crashed with
> little else in the log files that would indicate any kind of other
> hardware problem, so with all the rejected packets or partial entries
> (none which showed up on this particular snippett leads me to believe
> it's dropping sync somehow.  I'll watch the further logs and stuff to
> see if I can find something more definitive.

System crashes often do not log anything.. if possible connect
a serial console to the system and configure it to put the console
on the serial port, then connect that to another system or terminal
server..

Or you can run something like memtest86, though it can take a while
sometimes to trace memory errors(days). There is a burn-in test
suite that a lot of vendors use created by VA Linux a long time
ago called Cerberus (ctcs), you can find it on sourceforge, in
my experience if the hardware is bad ctcs will crash the system
in a matter of hours every time(assuming motherboard/cpu/ram),
and it helps catch bad disk controllers as well as disks too,
putting the system under incredible strain.

nate


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

Re: [CentOS] Fixing to bite the dust?

[sam]

I dunno Nate,

It started all this extraenous logging stuff after kicking memory 
from a paltry 256m up to 2 Gigs. The system has on occasion crashed with 
little else in the log files that would indicate any kind of other 
hardware problem, so with all the rejected packets or partial entries 
(none which showed up on this particular snippett leads me to believe 
it's dropping sync somehow.  I'll watch the further logs and stuff to 
see if I can find something more definitive.

Thanks..

Sam


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

Re: [CentOS] Fixing to bite the dust?

[Lanny Marcus]

On Fri, May 22, 2009 at 4:35 PM, sam  wrote:
> I've been getting LOTS of messages like the below in the daily log, and
> from all indications, it appears to all be related to the cpu;
> the machine is just over a year old, and was the old vortex.wa4phy;net
> server from the downtown co-lo site.  Aside from huge log files, and
> lots of other fluff, numerous problems of other nature have started
> cropping up.  Anyone have any suggestions as to what to do besides make
> a boat anchor out of it?  It's all greek to me, so I'm totally at the
> mercy of those folks who understand the bits and bites (lit) that have
> run amok in things.  Any suggestions as a possible fault other than the
> cpu just becoming more toasty brown? :)

To me, it looks like the messages all have to do with communications.
What are the other problems that you say "have started cropping up"?
Are those things in the logs or the box rebooting by itself or some
other issue?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] USB issues

[Michael A. Peters]

Jerry Geis wrote:
> I am using centos5.3 x86_64 on a gigabyte GA-MA78GM-US2H motherboard.
> 
> When I insert a USB thumbdrive its detected with dmesg, I mount it and 
> start to copy files.
> Then I start getting errors:
> sdd: assuming drive cache: write through
>  sdd: sdd1 sdd2
> sd 7:0:0:0: Attached scsi removable disk sdd
> sd 7:0:0:0: Attached scsi generic sg4 type 0
> usb-storage: device scan complete
> usb 1-5: reset high speed USB device using ehci_hcd and address 5
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: reset high speed USB device using ehci_hcd and address 5
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: reset high speed USB device using ehci_hcd and address 5
> usb 1-5: device not accepting address 5, error -110
> 
> I have also tried connecting a USB hub into my computer and using that.
> Then plugging the thumbdrive into the hub. I get the same results.
> 
> I have never had USB issues before - any ideas?

I had the same issue on my asus board (nvidia chipset).
Moving the UPS to a different USB port allowed it to function and moving 
the monitor hub to a different USB port allowed it to function again.

I'm not sure if it is a bad port or what, the ports that caused issue 
with my UPS and my display did not have the issue in Fedora with the 
CentOS problem devices and work for other things in CentOS.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fixing to bite the dust?

[nate]

sam wrote:
> I've been getting LOTS of messages like the below in the daily log, and
> from all indications, it appears to all be related to the cpu;
> the machine is just over a year old, and was the old vortex.wa4phy;net
> server from the downtown co-lo site.  Aside from huge log files, and
> lots of other fluff, numerous problems of other nature have started
> cropping up.  Anyone have any suggestions as to what to do besides make
> a boat anchor out of it?  It's all greek to me, so I'm totally at the
> mercy of those folks who understand the bits and bites (lit) that have
> run amok in things.  Any suggestions as a possible fault other than the
> cpu just becoming more toasty brown? :)

Those messages don't look particularly bad, is the system
crashing or something?

It seems like some sort of packet logging, perhaps iptables log
rules or something?

I get messages like this in my logs all the time, no harm done:
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00 SRC=125.89.73.173
DST=209.90.228.140 LEN=40 TOS=0x00 PREC=0x00 TTL=104 ID=256 PROTO=TCP
SPT=6000 DPT=3306 WINDOW=16384 RES=0x00 SYN URGP=0
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00 SRC=74.160.133.83
DST=209.90.228.140 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=14491 DF PROTO=TCP
SPT=4664 DPT=139 WINDOW=64512 RES=0x00 SYN URGP=0
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00 SRC=74.160.133.83
DST=209.90.228.140 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=15210 DF PROTO=TCP
SPT=4664 DPT=139 WINDOW=64512 RES=0x00 SYN URGP=0
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00 SRC=95.67.143.212
DST=209.90.228.140 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=6209 DF PROTO=TCP
SPT=4604 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00 SRC=95.67.143.212
DST=209.90.228.140 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=6884 DF PROTO=TCP
SPT=4604 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00
SRC=207.183.171.254 DST=209.90.228.140 LEN=52 TOS=0x00 PREC=0x00 TTL=51
ID=1415 DF PROTO=TCP SPT=14669 DPT=139 WINDOW=60352 RES=0x00 SYN URGP=0
IN=eth0 OUT= MAC=00:0c:29:68:2f:4a:00:0b:bf:73:84:1b:08:00
SRC=207.183.171.254 DST=209.90.228.140 LEN=52 TOS=0x00 PREC=0x00 TTL=51
ID=2157 DF PROTO=TCP SPT=14669 DPT=139 WINDOW=60352 RES=0x00 SYN URGP=0

nate


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

[CentOS] Fixing to bite the dust?

[sam]

I've been getting LOTS of messages like the below in the daily log, and 
from all indications, it appears to all be related to the cpu; 
the machine is just over a year old, and was the old vortex.wa4phy;net 
server from the downtown co-lo site.  Aside from huge log files, and 
lots of other fluff, numerous problems of other nature have started 
cropping up.  Anyone have any suggestions as to what to do besides make 
a boat anchor out of it?  It's all greek to me, so I'm totally at the 
mercy of those folks who understand the bits and bites (lit) that have 
run amok in things.  Any suggestions as a possible fault other than the 
cpu just becoming more toasty brown? :)

Thanks...
Sam

Begin log snip

 - Kernel Begin  

 
 1 Time(s):  PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s):  URGP=0 
 1 Time(s):  WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 0 PREC=0x00 TTL=49 ID=37550 DF PROTO=TCP SPT=388 DPT=53395 
WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 0 PREC=0x00 TTL=49 ID=56466 DF PROTO=TCP SPT=388 DPT=53395 
WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 0 SRC=216.104.158.222 DST=165.91.140.32 LEN=52 TOS=0x00 PREC=0x00 
TTL=64 ID=16424 DF PROTO=TCP SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK URGP=0 
 1 Time(s): 04.158.222 LEN=1500 TOS=0x00 PREC=0x00 TTL=49 ID=48422 DF PROTO=TCP 
SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 0x00 TTL=49 ID=4348 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 
RES=0x00 ACK URGP=0 
 1 Time(s): 1.140.32 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=19772 DF PROTO=TCP 
SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK URGP=0 
 1 Time(s): 20:20:08:00 SRC=165.91.140.32 DST=216.104.158.222 LEN=1500 TOS=0x00 
PREC=0x00 TTL=49 ID=32346 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 
ACK URGP=0 
 1 Time(s): 22 LEN=1500 TOS=0x00 PREC=0x00 TTL=49 ID=60844 DF PROTO=TCP SPT=388 
DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 2860 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 48 RES=0x00 ACK URGP=0 
 1 Time(s): 48:2e:69:48:00:01:97:00:20:20:08:00 SRC=165.91.140.32 
DST=216.104.158.222 LEN=1500 TOS=0x00 PREC=0x00 TTL=49 ID=49338 DF PROTO=TCP 
SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 500 TOS=0x00 PREC=0x00 TTL=49 ID=44842 DF PROTO=TCP SPT=388 
DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 63 RES=0x00 ACK URGP=0 
 1 Time(s): 890 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): 91.140.32 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=47322 DF PROTO=TCP 
SPT=53395 DPT=388 WINDOW=2263 RES=0x00 ACK URGP=0 
 1 Time(s): 9:48:00:01:97:00:20:20:08:00 SRC=165.91.140.32 DST=216.104.158.222 
LEN=1500 TOS=0x00 PREC=0x00 TTL=49 ID=43080 DF PROTO=TCP SPT=388 DPT=53395 
WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): :00:20:20:08:00 SRC=165.91.140.32 DST=216.104.158.222 LEN=1500 
TOS=0x00 PREC=0x00 TTL=49 ID=12262 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 
RES=0x00 ACK URGP=0 
 1 Time(s): :08:00 SRC=165.91.140.32 DST=216.104.158.222 LEN=1500 TOS=0x00 
PREC=0x00 TTL=49 ID=12384 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 
ACK URGP=0 
 1 Time(s): :30:48:2e:69:48:00:01:97:00:20:20:08:00 SRC=165.91.140.32 
DST=216.104.158.222 LEN=52 TOS=0x00 PREC=0x00 TTL=49 ID=40706 DF PROTO=TCP 
SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): < PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): < SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <0 ACK URGP=0 
 1 Time(s): <00 TTL=49 ID=39518 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 
RES=0x00 ACK URGP=0 
 1 Time(s): <165.91.140.32 DST=216.104.158.222 LEN=1500 TOS=0x00 PREC=0x00 
TTL=49 ID=57258 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <4 ID=24199 DF PROTO=TCP SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK 
URGP=0 
 1 Time(s): <5.91.140.32 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=9616 DF PROTO=TCP 
SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK URGP=0 
 1 Time(s): <7
 1 Time(s): <7 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <7.104.158.222 DST=165.91.140.32 LEN=52 TOS=0x00 PREC=0x00 TTL=64 
ID=49890 DF PROTO=TCP SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK URGP=0 
 1 Time(s): <7.91.140.32 DST=216.104.158.222 LEN=52 TOS=0x00 PREC=0x00 TTL=49 
ID=51756 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <7104.158.222 DST=165.91.140.32 LEN=52 TOS=0x00 PREC=0x00 TTL=64 
ID=38046 DF PROTO=TCP SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK URGP=0 
 1 Time(s): <7140.32 DST=216.104.158.222 LEN=1500 TOS=0x00 PREC=0x00 TTL=49 
ID=43334 DF PROTO=TCP SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <722 DST=165.91.140.32 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=34918 DF 
PROTO=TCP SPT=53395 DPT=388 WINDOW=2534 RES=0x00 ACK URGP=0 
 1 Time(s): <7222 LEN=1500 TOS=0x00 PREC=0x00 TTL=49 ID=37676 DF PROTO=TCP 
SPT=388 DPT=53395 WINDOW=1448 RES=0x00 ACK URGP=0 
 1 Time(s): <72e:69:4

Re: [CentOS] USB issues

[Benjamin Smith]

Thumb drives are pretty much problem free, in my experience, unless there's a 
problem with the drive itself.

Have you tried with a different drive?  

On Friday 22 May 2009 13:33:06 Jerry Geis wrote:
> I am using centos5.3 x86_64 on a gigabyte GA-MA78GM-US2H motherboard.
>
> When I insert a USB thumbdrive its detected with dmesg, I mount it and
> start to copy files.
> Then I start getting errors:
> sdd: assuming drive cache: write through
>  sdd: sdd1 sdd2
> sd 7:0:0:0: Attached scsi removable disk sdd
> sd 7:0:0:0: Attached scsi generic sg4 type 0
> usb-storage: device scan complete
> usb 1-5: reset high speed USB device using ehci_hcd and address 5
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: reset high speed USB device using ehci_hcd and address 5
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: device descriptor read/64, error -110
> usb 1-5: reset high speed USB device using ehci_hcd and address 5
> usb 1-5: device not accepting address 5, error -110
>
> I have also tried connecting a USB hub into my computer and using that.
> Then plugging the thumbdrive into the hub. I get the same results.
>
> I have never had USB issues before - any ideas?
>
> Jerry
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

[CentOS] USB issues

[Jerry Geis]

I am using centos5.3 x86_64 on a gigabyte GA-MA78GM-US2H motherboard.

When I insert a USB thumbdrive its detected with dmesg, I mount it and 
start to copy files.
Then I start getting errors:
sdd: assuming drive cache: write through
 sdd: sdd1 sdd2
sd 7:0:0:0: Attached scsi removable disk sdd
sd 7:0:0:0: Attached scsi generic sg4 type 0
usb-storage: device scan complete
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: device descriptor read/64, error -110
usb 1-5: device descriptor read/64, error -110
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: device descriptor read/64, error -110
usb 1-5: device descriptor read/64, error -110
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: device not accepting address 5, error -110

I have also tried connecting a USB hub into my computer and using that.
Then plugging the thumbdrive into the hub. I get the same results.

I have never had USB issues before - any ideas?

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

Re: [CentOS] Video on (video-capable digital) still camera not accessible

[Jeff]

On Fri, May 22, 2009 at 1:00 PM, MHR  wrote:
> On Fri, May 22, 2009 at 10:33 AM, Scott Silva  wrote:
>>
>> Renaming a file does not change its makeup. Just because you rename a .vob
>> file to .jpg, doesn't make it a jpeg. It just makes it a mis-named vob file.
>>
>
> Realizing this, I would love to have the opportunity to rename the
> files (they're .mov files - quicktime format, I believe), but the
> problem is that they don't show up in the Import Photos app, and
> they're otherwise (so far) completely inaccessible.
>
> I tried using my card reader again (I may have said this already), but
> the "drives" won't mount (the reader shows up as 2 drives - CF and MM,
> which is similar to SD) under CentOS, and my WinXP guest also can't do
> anything with them - XP recognizes that  is there, but
> nothing shows up in the explorer (or My Computer), and all I can do is
> dismount the  s.
>
> I _can_ play the videos on the camera, but when I try to do that while
> connected to the computer, the camera blanks out and powers off.  I
> even tried to dd from /dev/sdd and /dev/sdd1 (based on the dmesg
> output), and it says there's no such file.  I put in fresh batteries -
> nothing.
>

Indeed, file names and formats are a bit off the mark if you can't
even mount the drive.

Have you tried connecting to a completely different PC? Maybe your USB
port or motherboard is flaky or some other hardware problem is getting
you. If you know it's not a problem with the camera or card, then you
can focus on your PC issues.

I recently had an SD card that I could not access in my card reader.
Windows thought that it needed to be formatted, but it worked just
fine in the camera. And it had always worked fine in the card reader
too before that incident. I had to connect directly to the camera with
USB to download my pictures just that one time. I got lucky. Sadly,
that solution did not work for you. But the point is that just because
it works within the confines of the camera, does not guarantee that
everything is hunky dory with the camera or the card. The camera's
built-in firmware is probably not as strict about device and file
system standards.

Try a completely different PC, and if that doesn't work, you need to
call Canon. If it does work, then start checking out different USB
devices and flash cards on your computer to try to pinpoint the issue.
Heck, sometimes one USB port works and another doesn't. Have  you
tried different ports yet?

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

Re: [CentOS] Samba Question

[Fabian Arrotin]

Bo Lynch wrote:
> Hopefully very easy question to answer. I am trying to migrate data of of
> a samba server that is using winbind joined to a windows domain to another
> box. What samba or winbind files do I need so that this will resolve to
> names rather than UID and GID. For example
> drwxr-x--- 1049  10926  10005 36864 May 15 11:46 Student
> 
>

If you mean that you migrate data from one samba server to another *non* 
samba machine it depends how your newly machine is/will be configured. 
Is the samba domain ADS based ? have you used the idmap_rid feature ? (a 
*must* when having multiple linux/unix machines using winbind in a AD 
domain to have a consistent id/sid mapping accross all the samba 
machines instead of the 'first come, first serve' id from from idmap pool) .
If not, don't forget that even if you configure winbind/samba the same 
way it was on the old machine, the uid/gid map will never be the same 
(except when using idmap_rid directly)
So my advice is just to backup the permissions on the old machine (with 
getfacl) , rsync the data, join the new machine to the domain, and 
restores permissions back (with setfacl --restore)

-- 
--
Fabian Arrotin
  idea=`grep -i clue /dev/brain`
  test -z "$idea" && echo "sorry, init 6 in progress" || sh ./answer.sh
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Video on (video-capable digital) still camera not accessible

[Lanny Marcus]

On Fri, May 22, 2009 at 1:00 PM, MHR  wrote:
> On Fri, May 22, 2009 at 10:33 AM, Scott Silva  wrote:
>>
>> Renaming a file does not change its makeup. Just because you rename a .vob
>> file to .jpg, doesn't make it a jpeg. It just makes it a mis-named vob file.
>
> Realizing this, I would love to have the opportunity to rename the
> files (they're .mov files - quicktime format, I believe), but the
> problem is that they don't show up in the Import Photos app, and
> they're otherwise (so far) completely inaccessible.

Mark: As I just replied to Scott, possibly you can look in the
Advanced manual for your camera, to see if they permit you to change
the settings, so you save the video files in another format, such as
.avi If you do not see anything in the manual, maybe look on the
Canon web site tech support area or send them an email, to see if
that's somehow possible. Lanny
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Video on (video-capable digital) still camera not accessible

[Lanny Marcus]

On Fri, May 22, 2009 at 12:33 PM, Scott Silva  wrote:
> on 5-22-2009 7:22 AM Lanny Marcus spake the following:
>> On Wed, May 20, 2009 at 1:16 PM, MHR 
>>  wrote:
>>> I'm looking for any intelligent commentary on this - it may be a
>>> little off topic, but I'm wondering if anyone knows about this. �This
>>> isn't short, so bear with me.
>>>
>>> Yesterday, I tried to download a video off of one of my digital still
>>> cameras that also takes videos (Canon Powershot SX10 iS) on my CentOS
>>> x86_64 5.3 system. �When I plugged the camera into a USB port and
>>> turned it on, it showed no images available, AND no device showed up
>> 
> Renaming a file does not change its makeup. Just because you rename a .vob
> file to .jpg, doesn't make it a jpeg. It just makes it a mis-named vob file.

I know that, but when we changed the extensions from .vob to .jpg we
were able to upload the videos to youtube and they worked fine.
:-)

That doesn't help Mark, since he can't see the video files on his
digital still camera. If the camera settings permit, maybe he can
change the video file type, in the camera, to .avi or something that
will be seen by Linux.  I think he said his camera saves video files
in .mov   Ours saves them in .avi
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Video on (video-capable digital) still camera not accessible

[MHR]

On Fri, May 22, 2009 at 10:33 AM, Scott Silva  wrote:
>
> Renaming a file does not change its makeup. Just because you rename a .vob
> file to .jpg, doesn't make it a jpeg. It just makes it a mis-named vob file.
>

Realizing this, I would love to have the opportunity to rename the
files (they're .mov files - quicktime format, I believe), but the
problem is that they don't show up in the Import Photos app, and
they're otherwise (so far) completely inaccessible.

I tried using my card reader again (I may have said this already), but
the "drives" won't mount (the reader shows up as 2 drives - CF and MM,
which is similar to SD) under CentOS, and my WinXP guest also can't do
anything with them - XP recognizes that  is there, but
nothing shows up in the explorer (or My Computer), and all I can do is
dismount the  s.

I _can_ play the videos on the camera, but when I try to do that while
connected to the computer, the camera blanks out and powers off.  I
even tried to dd from /dev/sdd and /dev/sdd1 (based on the dmesg
output), and it says there's no such file.  I put in fresh batteries -
nothing.

?

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

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Scott Silva]

on 5-22-2009 10:17 AM Peter Hopfgartner spake the following:
> JohnS wrote:
>> On Fri, 2009-05-22 at 09:44 +0200, Peter Hopfgartner wrote:
>> 
>>   
   
   
>>> Would it make sense to install the kernel from CentOS 5.2? Any 
>>> contraindications?
>>>
>>> Regards,
>>>
>>> Peter
>>> 
>> ---
>> Now why in the world would you want to do that??? You running 5.3 as per
>> your earlier post and your uname shows you running the Xen Kernel.
>> Always run the newest kernel *unless* there are very good reasons not to
>> and I do not see that for your situation. Use the latest 5.3 NON Xen
>> Kernel to test it with.
>>   
> A random kernel reboot on a production machine is a good reason, at 
> least from my POV. It run fine for months with 5.2 and has now problems 
> running with 5.3. If it is not able to run XEN, then I have to trash the 
> whole thing, since the ASp services hosten on the machine are within XEN 
> guests. No XEN - no business. And id DID run fine before the update.

If the system was upgraded from 5.2, the 5.2 kernel should still be there. I
would just run with the 5.2 zen kernel long enough to see if the problem goes
away. If it does, then there is something in the new kernel that just doesn't
aggree with your server and its hardware configuration. If the problem
persists, then you have a good case for trying a power supply, but you could
also have another card going south and generating NMI's. Sometimes it just
isn't easy.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Video on (video-capable digital) still camera not accessible

[Scott Silva]

on 5-22-2009 7:22 AM Lanny Marcus spake the following:
> On Wed, May 20, 2009 at 1:16 PM, MHR 
>  wrote:
>> I'm looking for any intelligent commentary on this - it may be a
>> little off topic, but I'm wondering if anyone knows about this. �This
>> isn't short, so bear with me.
>>
>> Yesterday, I tried to download a video off of one of my digital still
>> cameras that also takes videos (Canon Powershot SX10 iS) on my CentOS
>> x86_64 5.3 system. �When I plugged the camera into a USB port and
>> turned it on, it showed no images available, AND no device showed up
> 
> Our  digital still camera is a very low end Canon PowerShot A460. Your
> camera may employ different technology, so YMMV.  A few minutes ago, I
> made 3 test videos, each a few seconds in length.  I am using CentOS
> 5.3 (32 bit, fully updated) and the GNOME Desktop. After I connected
> the camera to a USB port and I turned on the camera, it was detected,
> immediately, by the same Ap that imports still photos from the camera.
>  I imported the 3 .avi files and was able to play each of them,
> perfectly, using the Totem Movie Player. Your camera is producing
> video files with a different file extension? Our Samsung DVD Camcorder
> produces .vob files and in order to upload them to YouTube, I had to
> rename them to .jpg or .jpeg or something. But if you cannot download
> the video files from your digital still camera to your PC, you do not
> have the opportunity to convert them to another file format or rename
> them to a different file extension. GL
Renaming a file does not change its makeup. Just because you rename a .vob
file to .jpg, doesn't make it a jpeg. It just makes it a mis-named vob file.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Mathew S. McCarrell]

Nope, all of my adapters are Intel.
0f:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet
Controller (Copper) (rev 01)
0f:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet
Controller (Copper) (rev 01)
20:04.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet
Controller (rev 05)

Matt

--
Mathew S. McCarrell
Clarkson University '10

mccar...@gmail.com
mccar...@clarkson.edu


On Fri, May 22, 2009 at 1:20 PM, Peter Hopfgartner <
peter.hopfgart...@r3-gis.com> wrote:

> The guys on the Dell PowerEdge ML seem to be attracted by the idea that
> it is a driver problem of the network adapter. In this case, lspci gives
> me:
>
> 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
>
> Does this match your adapter?
>
> Regards,
>
> Peter
>
> Mathew S. McCarrell wrote:
> > Actually, I've also been experience this issue on a two identical
> > custom built systems running 5.3 x64 with Xen.  I experienced the
> > issue under the same kernel that Peter is running and the first kernel
> > released with 5.3.
> >
> > In my particular instance, I'm attributing these random crashes to
> > hardware problems since I'm only experiencing the issues on these two
> > systems and not an older Dell PowerEdge 850 which is set up with the
> > same software configuration.
> >
> > Matt
> >
> > --
> > Mathew S. McCarrell
> > Clarkson University '10
> >
> > mccar...@gmail.com 
> > mccar...@clarkson.edu 
> >
> >
> > On Fri, May 22, 2009 at 10:26 AM, Michael A. Peters  > > wrote:
> >
> > JohnS wrote:
> >
> > >
> > > My sejustion is unplug everything hooked to it but the power and
> > network
> > > cabling. Open it up while it is running, and shake the cables
> > lightly
> > > ( don't jerk on them). External disk array, unplug it also. USB
> > floppies
> > > and cd drives unplug emmm all.
> > >
> > > Is it under a heavy load? High cpu usage? Some times when there is
> a
> > > power supply on the verge of dying you don't really know until
> > disk I/O
> > > climbs real high thus pulling loads of wattage.
> >
> > That's my guess.
> > I'd swap out the power supply.
> >
> > My personal experience with ram issues is either kernel panic or
> > filesystem funnyness (sometimes resulting in filesystems being
> > remounted
> > read only). My experience with disk I/O issues is that forcing fsck
> > reveals filesystem errors with high frequency.
> >
> > Rebooting machines in my experience is almost always a failing power
> > supply (or faulty power source - check your UPS, when they start to
> go
> > bad they can cause issues).
> >
> > If it was a kernel issue, I suspect more people would be experiencing
> > (unless it is caused by a third party kmod)
> > ___
> > CentOS mailing list
> > CentOS@centos.org 
> > http://lists.centos.org/mailman/listinfo/centos
> >
> >
> > 
> >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
>
>
> --
>
> Dott. Peter Hopfgartner
>
> R3 GIS Srl - GmbH
> Via Johann Kravogl-Str. 2
> I-39012 Meran/Merano (BZ)
> Email: peter.hopfgart...@r3-gis.com
> Tel. : +39 0473 494949
> Fax  : +39 0473 069902
> www  : http://www.r3-gis.com
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Peter Hopfgartner]

The guys on the Dell PowerEdge ML seem to be attracted by the idea that 
it is a driver problem of the network adapter. In this case, lspci gives me:

09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 
Gigabit Ethernet (rev 12)

Does this match your adapter?

Regards,

Peter

Mathew S. McCarrell wrote:
> Actually, I've also been experience this issue on a two identical 
> custom built systems running 5.3 x64 with Xen.  I experienced the 
> issue under the same kernel that Peter is running and the first kernel 
> released with 5.3.
>
> In my particular instance, I'm attributing these random crashes to 
> hardware problems since I'm only experiencing the issues on these two 
> systems and not an older Dell PowerEdge 850 which is set up with the 
> same software configuration.
>
> Matt
>
> --
> Mathew S. McCarrell
> Clarkson University '10
>
> mccar...@gmail.com 
> mccar...@clarkson.edu 
>
>
> On Fri, May 22, 2009 at 10:26 AM, Michael A. Peters  > wrote:
>
> JohnS wrote:
>
> >
> > My sejustion is unplug everything hooked to it but the power and
> network
> > cabling. Open it up while it is running, and shake the cables
> lightly
> > ( don't jerk on them). External disk array, unplug it also. USB
> floppies
> > and cd drives unplug emmm all.
> >
> > Is it under a heavy load? High cpu usage? Some times when there is a
> > power supply on the verge of dying you don't really know until
> disk I/O
> > climbs real high thus pulling loads of wattage.
>
> That's my guess.
> I'd swap out the power supply.
>
> My personal experience with ram issues is either kernel panic or
> filesystem funnyness (sometimes resulting in filesystems being
> remounted
> read only). My experience with disk I/O issues is that forcing fsck
> reveals filesystem errors with high frequency.
>
> Rebooting machines in my experience is almost always a failing power
> supply (or faulty power source - check your UPS, when they start to go
> bad they can cause issues).
>
> If it was a kernel issue, I suspect more people would be experiencing
> (unless it is caused by a third party kmod)
> ___
> CentOS mailing list
> CentOS@centos.org 
> http://lists.centos.org/mailman/listinfo/centos
>
>
> 
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>   


-- 
 
Dott. Peter Hopfgartner
 
R3 GIS Srl - GmbH
Via Johann Kravogl-Str. 2
I-39012 Meran/Merano (BZ)
Email: peter.hopfgart...@r3-gis.com
Tel. : +39 0473 494949
Fax  : +39 0473 069902
www  : http://www.r3-gis.com

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

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Peter Hopfgartner]

JohnS wrote:
> On Fri, 2009-05-22 at 09:44 +0200, Peter Hopfgartner wrote:
> 
>   
>>>   
>>>   
>> Would it make sense to install the kernel from CentOS 5.2? Any 
>> contraindications?
>>
>> Regards,
>>
>> Peter
>> 
> ---
> Now why in the world would you want to do that??? You running 5.3 as per
> your earlier post and your uname shows you running the Xen Kernel.
> Always run the newest kernel *unless* there are very good reasons not to
> and I do not see that for your situation. Use the latest 5.3 NON Xen
> Kernel to test it with.
>   
A random kernel reboot on a production machine is a good reason, at 
least from my POV. It run fine for months with 5.2 and has now problems 
running with 5.3. If it is not able to run XEN, then I have to trash the 
whole thing, since the ASp services hosten on the machine are within XEN 
guests. No XEN - no business. And id DID run fine before the update.
> My sejustion is unplug everything hooked to it but the power and network
> cabling. Open it up while it is running, and shake the cables lightly
> ( don't jerk on them). External disk array, unplug it also. USB floppies
> and cd drives unplug emmm all. 
>
> Is it under a heavy load? High cpu usage? Some times when there is a
> power supply on the verge of dying you don't really know until disk I/O
> climbs real high thus pulling loads of wattage. Pentium 4 and up cpus
> are bad about this also.
>   
No heavy load, it crashes even at times when tere is almost noload at 
all. The power supplies are rwedundand and hardware monitoring tells me 
they are both fine, as is the rest of the hardware of the machine.
> Run memtest86 for a few hours not just a min or two and say ahh it's ok.
> It takes time. Is there gaps in your log files like white space?
>   
No gaps. Simply the machine restarts at a given moment. No shutdown, no 
traces of a kernel panic
> Hardware raid controller updated to latest firmware release?
Indeed, updating firmware and maybe some drivers from Dell's support 
site will be the next actions.

>  Ok I guess
> others can tack onto my list here as well.I wouldn't get to discouraged
> because sometimes it can take days to find the problem.
>
>
>   
Thank you for the infos,

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


-- 
 
Dott. Peter Hopfgartner
 
R3 GIS Srl - GmbH
Via Johann Kravogl-Str. 2
I-39012 Meran/Merano (BZ)
Email: peter.hopfgart...@r3-gis.com
Tel. : +39 0473 494949
Fax  : +39 0473 069902
www  : http://www.r3-gis.com

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

Re: [CentOS] Gnome terminal oddity

[Beartooth]

On Fri, 22 May 2009 12:49:43 -0400, James B. Byrne wrote:

> I have the following gnome terminal profile settings:
> 
> Backspace  = ASCII DEL
> Delete Key = Escape Sequence
[] 
> I am fairly confident that the delete key worked in the same fashion for
> my usual user id up until quite recently.  Does anyone know of why or
> how this behaviour could differ between two separate users in the same
> terminal window?

I have my gnome-terminal (under Fedora, not CentOS) set to 
Control-H and Escape Sequence; that works fine for all users here, and 
does what I'm guessing you want.

-- 
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.

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

[CentOS] Gnome terminal oddity

[James B. Byrne]

I have the following gnome terminal profile settings:

Backspace  = ASCII DEL
Delete Key = Escape Sequence

If the logged in session in the terminal window is my own user id
then the delete key does nothing.  If however, I su -l in the same
terminal window then the delete key removes the character under the
cursor and left shifts the rest of the line.

I am fairly confident that the delete key worked in the same fashion
for my usual user id up until quite recently.  Does anyone know of
why or how this behaviour could differ between two separate users in
the same terminal window?


-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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

Re: [CentOS] Firefox 3, Sun jre1.6.0_12_x86_64 and enabling a plugin

[James B. Byrne]

On: Fri, 22 May 2009 16:26:45 +0200, Lorenzo Quatrini
 wrote:

  http://wiki.centos.org/TipsAndTricks/PluginsFor64BitFirefox

Thank you.

-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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

[CentOS] CentOS-announce Digest, Vol 51, Issue 9

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2009:0329 Important CentOS 3 i386 freetype - security
  update (Tru Huynh)
   2. CESA-2009:0329 Important CentOS 3 x86_64 freetype - security
  update (Tru Huynh)
   3. CESA-2009:1059 Important CentOS 3 i386 pidgin -   security
  update (Tru Huynh)
   4. CESA-2009:1059 Important CentOS 3 x86_64 pidgin - security
  update (Tru Huynh)


--

Message: 1
Date: Fri, 22 May 2009 16:02:05 +0200
From: Tru Huynh 
Subject: [CentOS-announce] CESA-2009:0329 Important CentOS 3 i386
freetype -  security update
To: centos-annou...@centos.org
Message-ID: <20090522140205.ga24...@sillage.bis.pasteur.fr>
Content-Type: text/plain; charset="us-ascii"

CentOS Errata and Security Advisory CESA-2009:0329

freetype security update for CentOS 3 i386:
https://rhn.redhat.com/errata/RHSA-2009-0329.html

The following updated file has been uploaded and is currently syncing to
the mirrors:

i386:
updates/i386/RPMS/freetype-2.1.4-12.el3.i386.rpm
updates/i386/RPMS/freetype-devel-2.1.4-12.el3.i386.rpm

addons/i386/RPMS/freetype-demos-2.1.4-12.el3.i386.rpm
addons/i386/RPMS/freetype-utils-2.1.4-12.el3.i386.rpm

source:
updates/SRPMS/freetype-2.1.4-12.el3.src.rpm

You may update your CentOS-3 i386 installations by running the command:

yum update freetype\*

Tru
-- 
Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance)
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://lists.centos.org/pipermail/centos-announce/attachments/20090522/b45dde1d/attachment-0001.bin
 

--

Message: 2
Date: Fri, 22 May 2009 16:03:10 +0200
From: Tru Huynh 
Subject: [CentOS-announce] CESA-2009:0329 Important CentOS 3 x86_64
freetype- security update
To: centos-annou...@centos.org
Message-ID: <20090522140310.gb24...@sillage.bis.pasteur.fr>
Content-Type: text/plain; charset="us-ascii"

CentOS Errata and Security Advisory CESA-2009:0329

freetype security update for CentOS 3 x86_64:
https://rhn.redhat.com/errata/RHSA-2009-0329.html

The following updated file has been uploaded and is currently syncing to
the mirrors:

x86_64:
updates/x86_64/RPMS/freetype-2.1.4-12.el3.i386.rpm
updates/x86_64/RPMS/freetype-2.1.4-12.el3.x86_64.rpm
updates/x86_64/RPMS/freetype-devel-2.1.4-12.el3.x86_64.rpm

addons/x86_64/RPMS/freetype-demos-2.1.4-12.el3.x86_64.rpm
addons/x86_64/RPMS/freetype-utils-2.1.4-12.el3.x86_64.rpm

source:
updates/SRPMS/freetype-2.1.4-12.el3.src.rpm

You may update your CentOS-3 x86_64 installations by running the command:

yum update freetype\*

Tru
-- 
Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance)
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://lists.centos.org/pipermail/centos-announce/attachments/20090522/d5f2e95b/attachment-0001.bin
 

--

Message: 3
Date: Fri, 22 May 2009 16:04:17 +0200
From: Tru Huynh 
Subject: [CentOS-announce] CESA-2009:1059 Important CentOS 3 i386
pidgin -security update
To: centos-annou...@centos.org
Message-ID: <20090522140417.gc24...@sillage.bis.pasteur.fr>
Content-Type: text/plain; charset="us-ascii"

CentOS Errata and Security Advisory CESA-2009:1059

pidgin security update for CentOS 3 i386:
https://rhn.redhat.com/errata/RHSA-2009-1059.html

The following updated file has been uploaded and is currently syncing to
the mirrors:

i386:
updates/i386/RPMS/pidgin-1.5.1-3.el3.i386.rpm

source:
updates/SRPMS/pidgin-1.5.1-3.el3.src.rpm

You may update your CentOS-3 i386 installations by running the command:

yum update pidgin

Tru
-- 
Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance)
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://lists.centos.org/pipermail/centos-announce/attachments/20090522/8269ce1f/attachment-0

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Mathew S. McCarrell]

Actually, I've also been experience this issue on a two identical custom
built systems running 5.3 x64 with Xen.  I experienced the issue under the
same kernel that Peter is running and the first kernel released with 5.3.
In my particular instance, I'm attributing these random crashes to hardware
problems since I'm only experiencing the issues on these two systems and not
an older Dell PowerEdge 850 which is set up with the same software
configuration.
Matt

--
Mathew S. McCarrell
Clarkson University '10

mccar...@gmail.com
mccar...@clarkson.edu


On Fri, May 22, 2009 at 10:26 AM, Michael A. Peters  wrote:

> JohnS wrote:
>
> >
> > My sejustion is unplug everything hooked to it but the power and network
> > cabling. Open it up while it is running, and shake the cables lightly
> > ( don't jerk on them). External disk array, unplug it also. USB floppies
> > and cd drives unplug emmm all.
> >
> > Is it under a heavy load? High cpu usage? Some times when there is a
> > power supply on the verge of dying you don't really know until disk I/O
> > climbs real high thus pulling loads of wattage.
>
> That's my guess.
> I'd swap out the power supply.
>
> My personal experience with ram issues is either kernel panic or
> filesystem funnyness (sometimes resulting in filesystems being remounted
> read only). My experience with disk I/O issues is that forcing fsck
> reveals filesystem errors with high frequency.
>
> Rebooting machines in my experience is almost always a failing power
> supply (or faulty power source - check your UPS, when they start to go
> bad they can cause issues).
>
> If it was a kernel issue, I suspect more people would be experiencing
> (unless it is caused by a third party kmod)
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Firefox 3, Sun jre1.6.0_12_x86_64 and enabling a plugin

[Lorenzo Quatrini]

JohnS ha scritto:
> On Thu, 2009-05-21 at 16:40 -0400, James B. Byrne wrote:
>> SOMEbody on this list must have this combination working by now.
>>
>> How does one enable the firefox jre plugin for Sun's x86_64
>> distribution?  Every site that I can find refers to making a link to
>> a now non-existent plugins directory under the jre installation
>> directory.  The official firefox plugin pages refers to the
>> existence of a Sun x86_64 jre but provides no details on how to
>> enable it.  The Sun site speaks only about installing i386 versions.
>>  Most other web sites that I have found are for distributions other
>> than CentOS.
>>
>> Help?
> ---
> http://wiki.centos.org/TipsAndTricks/PluginsFor64BitFirefox?highlight=(java)
> 
I noticed that there is an open bug...

http://bugs.centos.org/view.php?id=3574

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

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Michael A. Peters]

JohnS wrote:

> 
> My sejustion is unplug everything hooked to it but the power and network
> cabling. Open it up while it is running, and shake the cables lightly
> ( don't jerk on them). External disk array, unplug it also. USB floppies
> and cd drives unplug emmm all. 
> 
> Is it under a heavy load? High cpu usage? Some times when there is a
> power supply on the verge of dying you don't really know until disk I/O
> climbs real high thus pulling loads of wattage.

That's my guess.
I'd swap out the power supply.

My personal experience with ram issues is either kernel panic or 
filesystem funnyness (sometimes resulting in filesystems being remounted 
read only). My experience with disk I/O issues is that forcing fsck 
reveals filesystem errors with high frequency.

Rebooting machines in my experience is almost always a failing power 
supply (or faulty power source - check your UPS, when they start to go 
bad they can cause issues).

If it was a kernel issue, I suspect more people would be experiencing 
(unless it is caused by a third party kmod)
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Video on (video-capable digital) still camera not accessible

[Lanny Marcus]

On Wed, May 20, 2009 at 1:16 PM, MHR  wrote:
> I'm looking for any intelligent commentary on this - it may be a
> little off topic, but I'm wondering if anyone knows about this.  This
> isn't short, so bear with me.
>
> Yesterday, I tried to download a video off of one of my digital still
> cameras that also takes videos (Canon Powershot SX10 iS) on my CentOS
> x86_64 5.3 system.  When I plugged the camera into a USB port and
> turned it on, it showed no images available, AND no device showed up

Our  digital still camera is a very low end Canon PowerShot A460. Your
camera may employ different technology, so YMMV.  A few minutes ago, I
made 3 test videos, each a few seconds in length.  I am using CentOS
5.3 (32 bit, fully updated) and the GNOME Desktop. After I connected
the camera to a USB port and I turned on the camera, it was detected,
immediately, by the same Ap that imports still photos from the camera.
 I imported the 3 .avi files and was able to play each of them,
perfectly, using the Totem Movie Player. Your camera is producing
video files with a different file extension? Our Samsung DVD Camcorder
produces .vob files and in order to upload them to YouTube, I had to
rename them to .jpg or .jpeg or something. But if you cannot download
the video files from your digital still camera to your PC, you do not
have the opportunity to convert them to another file format or rename
them to a different file extension. GL
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Double packages

[Karanbir Singh]

On 05/21/2009 07:06 PM, Eduardo Silvestre wrote:
>   thanks but i know that. I just want keep im my system packages x86_64. Why 
> yum return packages i386 when $basearch is x86_64?

There are many apps that are still 32bit, and work fine under a x86_64 
host - also, there are many apps that are better run 32bit irrespective 
of what arch you are running on the host. Yum facilitates that, its a 
choice you can control ( as many have already pointed out to you ).


-- 
Karanbir Singh : http://www.karan.org/  : 2522...@icq
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] web filtering for remote computers

[Jake]

On Fri, May 22, 2009 at 12:55 AM, Dhaval Thakar
 wrote:
>
> John R Pierce wrote:
>> Dhaval Thakar wrote:
>>
>>> Hi,
>>>
>>> I am using Squid for local users since two years & is working fine.
>>> I am trying to implement web filtering for remote computers e.g few laptops 
>>> & branch / franchise computers on dynamic ips.
>>>
>>> I do not want to use Squid proxy for it, if all remote computers will use 
>>> Squid from my public ip, bandwidth utilization will increase.
>>> Need valuable suggestion to achieve this.
>>>
>>>
>>
>> how are these remote computers connected to the network, and what OS are
>> they running?
>>
>>
> all are windows clients
> connecting through internet using dynamic ips.
>> filtering, by necessity, has to be between the user and the thing you
>> want to filter.
>>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

Good morning:

If your needs are simple (e.g. you are able to apply one filtering
policy to roughly all users at the same time and you aren't concerned
with per-user reporting on usage for accountability, etc.) you can try
OpenDNS. I just use this service for normal name resolution but they
have a filtering service as well.
http://www.opendns.com/solutions/enterprise/filtering/

Of course you can get around this filtering scheme but then no web
filtering technique is fool-proof...and blocking outbound dns requests
to all resolvers except the IP addresses of OpenDNS (there are just
two to put in your firewall) would go a long way towards preventing
users from escaping the filter.

-- 
Jake Paulus
jakepau...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Double packages

[Jim Perrin]

On Thu, May 21, 2009 at 2:06 PM, Eduardo Silvestre
 wrote:
> Hello Johan,
>
>  thanks but i know that. I just want keep im my system packages x86_64. Why 
> yum return packages i386 when $basearch is x86_64?

In some cases you can get away with nuking all of them immediately
following install. This can be done with a simple 'yum remove *.i386'
followed by the exclude in yum.conf mentioned earlier. This will not
work in all cases because some 3rd party applications just flat out
require i386 packages to be used.


-- 
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] web filtering for remote computers

[Dhaval Thakar]

John R Pierce wrote:
> Dhaval Thakar wrote:
>   
>> Hi,
>>
>> I am using Squid for local users since two years & is working fine.
>> I am trying to implement web filtering for remote computers e.g few laptops 
>> & branch / franchise computers on dynamic ips.
>>
>> I do not want to use Squid proxy for it, if all remote computers will use 
>> Squid from my public ip, bandwidth utilization will increase.
>> Need valuable suggestion to achieve this.
>>   
>> 
>
> how are these remote computers connected to the network, and what OS are 
> they running?
>
>   
all are windows clients
connecting through internet using dynamic ips.
> filtering, by necessity, has to be between the user and the thing you 
> want to filter.
>   

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

Re: [CentOS] Random server reboot after update to CentOS 5.3

[JohnS]

On Fri, 2009-05-22 at 09:44 +0200, Peter Hopfgartner wrote:

> >   
> Would it make sense to install the kernel from CentOS 5.2? Any 
> contraindications?
> 
> Regards,
> 
> Peter
---
Now why in the world would you want to do that??? You running 5.3 as per
your earlier post and your uname shows you running the Xen Kernel.
Always run the newest kernel *unless* there are very good reasons not to
and I do not see that for your situation. Use the latest 5.3 NON Xen
Kernel to test it with.

My sejustion is unplug everything hooked to it but the power and network
cabling. Open it up while it is running, and shake the cables lightly
( don't jerk on them). External disk array, unplug it also. USB floppies
and cd drives unplug emmm all. 

Is it under a heavy load? High cpu usage? Some times when there is a
power supply on the verge of dying you don't really know until disk I/O
climbs real high thus pulling loads of wattage. Pentium 4 and up cpus
are bad about this also.

Run memtest86 for a few hours not just a min or two and say ahh it's ok.
It takes time. Is there gaps in your log files like white space?
Hardware raid controller updated to latest firmware release? Ok I guess
others can tack onto my list here as well.I wouldn't get to discouraged
because sometimes it can take days to find the problem.


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

Re: [CentOS] Double packages

[A. Kirillov]

> Hello Johan,
> 
>  thanks but i know that. I just want keep im my system packages x86_64. Why 
> yum return packages i386 when $basearch is x86_64?
> 
> Regards,
> ---
> Eduardo Silvestre
> nfsi telecom, lda.
> 
> eduardo.silves...@nfsi.pt
> Tel. (+351) 21 949 2300 - Fax (+351) 21 949 2301
> http://www.nfsi.pt/
> 
> - Original Message -
> From: "Johan Swensson" 
> To: "CentOS mailing list" 
> Sent: Wednesday, May 20, 2009 4:42:07 PM GMT +00:00 GMT Britain, Ireland, 
> Portugal
> Subject: Re: [CentOS] Double packages
> 
> yum install ncurses-devel.x86_64
> 
> 
> - Original Message -
> From: "Eduardo Silvestre" 
> To: "CentOS mailing list" 
> Sent: Wednesday, May 20, 2009 5:33:08 PM GMT +01:00 Amsterdam / Berlin / Bern 
> / Rome / Stockholm / Vienna
> Subject: [CentOS] Double packages
> 
> 
> 
> 
> Hello, 
> 
> i'm trying install some packages with x64_86 architecture and got same 
> packages doubling (32 and 64 bits). 
> How can i force yum just install packages x64_86 based? 
> 
> [r...@www pfqueue-0.5.6]# yum install ncurses-devel 
> Loading "fastestmirror" plugin 
> Loading mirror speeds from cached hostfile 
> * base: mirrors.nfsi.pt 
> * updates: mirrors.nfsi.pt 
> * addons: mirrors.nfsi.pt 
> * extras: mirrors.nfsi.pt 
> Setting up Install Process 
> Parsing package install arguments 
> Resolving Dependencies 
> --> Running transaction check 
> ---> Package ncurses-devel.x86_64 0:5.5-24.20060715 set to be updated 
> ---> Package ncurses-devel.i386 0:5.5-24.20060715 set to be updated 
> --> Finished Dependency Resolution 
> 
> Dependencies Resolved 
> 
> = 
> Package Arch Version Repository Size 
> = 
> Installing: 
> ncurses-devel x86_64 5.5-24.20060715 base 1.7 M 
> ncurses-devel i386 5.5-24.20060715 base 1.6 M 
> 
> Transaction Summary 
> = 
> Install 2 Package(s) 
> Update 0 Package(s) 
> Remove 0 Package(s) 
> 
> Total download size: 3.3 M 

Add exclude=*.i?86 to /etc/yum.conf
You may still need some i386 packages on x86_64.
When you do, use
yum --disableexcludes=all ...
HTH


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

Re: [CentOS] Send syslog to a remote server

[Ralph Angenendt]

hce wrote:
> The rsyslog.conf in FC 9 is much easy to be configured, just enable
> the InputTCPServerRun and ModLoad. It is not the problem in FC 9
> rsyslog server, it is the problem in CentOS syslog, no messages
> sending to FC9 when I checked with tcpdump on port 514 on FC9.
> 
> Has anyone made CentOS 5 syslog work to send messages to remote syslog
> server? Or, I am wondering if it has never worked on CentOS 5?

syslog or rsyslog?

Have you "tcpdumped" udp or tcp?

Ralph


pgpJtCJpC74kh.pgp
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Peter Hopfgartner]

Ralph Angenendt wrote:
> Lanny Marcus wrote:
>   
>> It would have been helpful, if the error message told you which system
>> software.  :-)   The Upgrade from 5.2 to 5.2 seems to have been
>> problematic for some people on this list.  When you did the Upgrade,
>> did you follow this sequence, per the CentOS 5.3 Release Notes?
>> yum clean all && yum update glibc\* && yum update
>> If not, that may or may not have anything to do with the reboots and
>> error messages you have received.
>> 
>
> No, it would not have to do anything with the spontaneous reboots. The 
> problem with glibc only concerns rpm, as the release notes clearly state.
>
> Ralph
> 
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>   
Would it make sense to install the kernel from CentOS 5.2? Any 
contraindications?

Regards,

Peter

-- 
 
Dott. Peter Hopfgartner
 
R3 GIS Srl - GmbH
Via Johann Kravogl-Str. 2
I-39012 Meran/Merano (BZ)
Email: peter.hopfgart...@r3-gis.com
Tel. : +39 0473 494949
Fax  : +39 0473 069902
www  : http://www.r3-gis.com

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

Re: [CentOS] Random server reboot after update to CentOS 5.3

[Peter Hopfgartner]

William L. Maltby wrote:
> On Thu, 2009-05-21 at 20:07 +0200, Ralph Angenendt wrote:
>   
>> Lanny Marcus wrote:
>> 
>>> It would have been helpful, if the error message told you which system
>>> software.  :-)   The Upgrade from 5.2 to 5.2 seems to have been
>>> problematic for some people on this list.  When you did the Upgrade,
>>> did you follow this sequence, per the CentOS 5.3 Release Notes?
>>> yum clean all && yum update glibc\* && yum update
>>> If not, that may or may not have anything to do with the reboots and
>>> error messages you have received.
>>>   
>> No, it would not have to do anything with the spontaneous reboots. The 
>> problem with glibc only concerns rpm, as the release notes clearly state.
>> 
>
> Since nobody else mentioned it to th OP, ...
>
> Let us not forget that often the hardware chooses to act up around the
> same time that some kind of (software) upgrade is performed. I've wasted
> a lot of time in the past *assuming* that because the hardware was
> rock-solid in the past, it must have been some change (I made) to the
> software.
>
> I suggest running diagnostics, or manually re-seating everything
> (especially if you had occasion to move the unit or open it recently).
>
> Memory used to age, does it still? Memtest*86 might be in order.
>
>   
The machine has ECC RAM and extensive hardware logging build in. It 
should be quite uncommon that the build in server logging would not 
notice a memory failure. The server diagnostics from Dell do not show 
any hardware failure at all, only a software problem. In my experience, 
memory problems lead in most cases to application instability,  but I've 
never seen a reboot like this, that leaves absolutely no trace in the 
Linux logs. Taking the reboot, that happened tonight:

The Dell utility says:

Severity  : Critical
Date and Time : Thu May 21 21:16:16 2009
Description   : System Software event: run-time critical stop was asserted

 From /var/log/messages:

May 21 10:58:38 servernew auditd[18962]: Init complete, auditd 1.7.7 
listening f
or events (startup state enable)
May 21 21:18:58 servernew syslogd 1.4.1: restart.
May 21 21:18:58 servernew kernel: klogd 1.4.1, log source = /proc/kmsg 
started.
May 21 21:18:58 servernew kernel: Bootdata ok (command line is ro 
root=LABEL=/)
May 21 21:18:58 servernew kernel: Linux version 2.6.18-128.1.10.el5xen 
(mockbuil
d...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) 
#1 SMP T
hu May 7 11:07:18 EDT 2009
May 21 21:18:58 servernew kernel: BIOS-provided physical RAM map:

Reassuming: nothing happens for hours and then, zack!, boom!, the server 
restarts.


Regards,

Peter
>> Ralph
>> 
>> 
>
> HTH
>   


-- 
 
Dott. Peter Hopfgartner
 
R3 GIS Srl - GmbH
Via Johann Kravogl-Str. 2
I-39012 Meran/Merano (BZ)
Email: peter.hopfgart...@r3-gis.com
Tel. : +39 0473 494949
Fax  : +39 0473 069902
www  : http://www.r3-gis.com

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