similar to: Can ONLY log in as root-console perms problem

Hi, How do I get a libraw1394 kernel module loaded? I tried # /sbin/modprobe raw1394 FATAL: Module raw1394 not found. # rpm -qa | grep 1394 libraw1394-devel-1.2.1-1.fc6 libraw1394-1.2.1-1.fc6 libdc1394-2.0.0-0.1.pre7.el5.rf libavc1394-0.5.3-1.fc6 # uname -r 2.6.18-8.1.6.el5 Thanks, Shawn

Hi all! I'm trying to use my first-ever firewire device, and just OOB I'm not getting very far, so advice would be appreciated. When I plug in the device I see some entries in /var/log/messages: Jul 27 14:50:30 fcshome kernel: firewire_core: phy config: card 0, new root=ffc1, gap_count=5 Jul 27 14:50:31 fcshome kernel: firewire_core: created device fw1: GUID 0003f300118123f9, S100

Hello, Having a problem getting Centos to see my firewire connected camcorder. Here what I have thus far; Installed the kernek fron centos-plus and checked that libraw1394.x86_64 and libraw1394_8.x86_64 are installed Kernel i'm running is 2.6.9-34.106.unsupported here are some outputs from my machine; ~ $ lspci | grep -i firewire 00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE

Hi Gang! I've got this (now old) Gigabyte motherboard (GA-7N400 Pro2), I've had it for just over 3 years. I use it, so far, with only PATA devices. I'm toying with the idea of buying a matched pair of SATA drives and when I install Centos 5 (hopefully soon), building it with software raid (using the two drives as mirrors of each other). Now, I wouldn't have ever even thought of

Hi List I have a Gygabyte GA-7N400 PRO2 with a 2.6 mHz Athlon cpu. I want to set up a central file storage for 2/3 users using 6/7 machines. A mixture of win2k, XP and various Linux distros (my home network). It will be used to store files, (docs, music and DVD ) for all of these machines, print server, (two ink-jets), mail server and later on a myth tv set up. Would SAMBA be the best option

Hello everybody, After going through multiple posts on Internet and trying different things I can't seems get zaptel wcfxo loaded on the server correctly. I run dual P3 500 Mhz box. After reading README.udev I put a file 60-zaptel.rules /etc/udev/rules.d # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer",

Hi all, i need to use openbsd 3.9 as domU. So I downloaded an image and used my standard config file: kernel = "/boot/vmlinuz-2.6.16.18-xenU" memory = 128 name = "openbsd.3-9" disk = [''file:/xen/openbsd/disk,sda1,w''] root = "/dev/sda1 ro" but when I start the domU and attach the console I only see following lines befor it crashs. Any

Having done my fresh 5.0 install a couple months ago I'm slowly getting things back in to working condition. Decided last night to try setting up lmsensors. Got it all set up (modules, etc taken care of) and it runs and reports values, but some of 'em a clearly wrong with the default sensors.conf Trying to use the old sensors.conf I used on Centos 4 produces even more whacked-out results,

Hi everybody, I need help to install driver for video card. I have physically installed two video capture card on two different computers. Both running Linux CentOS release 4.4 (final), and kernel 2.6.9-42.0.3.ELsmp. The first computer is Pentium D 3.00 GHz, 1Gbyte RAM. The second computer is AMD Athlon 2800+, 1 Gbyte RAM. I succesfully installed opencv-0.9.7 on both computers with gtk+ 2.x,

The subject's a little misleading really, but I was looking for some clarification of my thoughts... In Windows, one can use both share permissions and NTFS permissions to control access to files. I would normally use share permissions to control a connection (allow/deny), and use NTFS to control access. I would never use share permissions to control access whilst NTFS was capable of

I would expect that the sending rsync would only send the perms provided modified by the --chmod. I wouldn't expect the receiver to even know the other permissions. On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote: > Thank you for the feedback, I'm glad to see that different people see > the issue > differently. As a followup question, what would you expect this to do:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on dovecot launch, 'dovecot.log' is created as: -rw------- 1 root testuser 271 2006-09-11 07:58 dovecot.log which causes an apparent perms prob with exim using dovecot's LDA ... what/how do i define/change the LOG's ownership/perms with? it seems to ignore the dovecot.conf umask setting, etc. thx. richard - -- /"\ \

Using --existing, I would like to transfer files created by root to home dirs, where the files would be updated, but leave the user,group and perms as they were. ie root creates a new file on the sending system, rsyncs it to the home dir of the user, leaving the perms untouched. Seems there is no option for this - the users are not defined on the sending system. I cant do it backwards due to

Permissions don't require super. Any place where permissions can't be stored certainly can't handle xattrs either. So, I wouldn't expect --fake-super to affect --perms at all. On 3/12/20 12:46 PM, Dimitrios Apostolou via rsync wrote: > rsync --perms -M--fake-super src dst > > For me, this command means that rsync should save the original perms in the > xattr, and

Why does --xattrs imply --perms (according to the man page)? Unlike --acls, --xattrs is not logically a superset of --perms (since system.* xattrs are ignored). I might conceivably want to copy some user xattrs that I set on my files while allowing the destination permissions to take the default value. Matt

https://bugzilla.samba.org/show_bug.cgi?id=3253 Summary: Feature request - Sync perms/ownership/time etc but with no file transfer Product: rsync Version: 2.6.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

I don't believe it is possible. I think the misunderstanding stems from the fact that the permissions are even stored in the xattr. They don't need to be there but they may as well be. They don't take much space. The real question would be when rsync reads the file to restore it and the file perms are different than the ones in the xattr which set does it use? On 3/16/20 10:01 AM,

rsync --perms -M--fake-super src dst For me, this command means that rsync should save the original perms in the xattr, and leave the real file mode to the umask default. Currently it also modifies the real file mode, and there is no way to store something different in the xattr. According to an old bug report that I found, more people would like --fake-super to be a complete attribute

Hi Dumb question i think but how can i make devices permissions persist after a reboot. I dont think i have come across this issue before but i have some SAN disks that need to be oracle:dba as their perms but after a reboot they reset back to brw------- 1 root root 120, 49 Nov 30 10:40 /dev/emcpowerd1 any thoughts? thanks

Hello, My wiki username: cormander URL requesting perms for: http://wiki.centos.org/HowTos/Nagios Thanks