search for: uidgid

I'm a little unconfortable with the way the privsep user is created in the RedHat spec files. In particular the way a fixed UID is specified. Now it looks (from a glance at the apache/bind spec file) that it is 'the way it is done' - but is there a register of these numbers somewhere? Andrew Bartlett -- Andrew Bartlett abartlet at pcug.org.au

Hi All, How do you configure puppet nodes on the puppet master to allow SUing to root? I want to be able to ssh as a regular user then SU to root on client puppet servers. How do you configure the puppetmaster for this? Thanks in advance, -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi, my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC i386) crashes reproducibly when rsync-ing files to an NFSv4 share on the FreeBSD machine. The crash makes the system reboot. The crash creates files in /var/crash which may be obtained

....file 27 "/src/linux/include/linux" "rwsem-spinlock.h" > .file 28 "/src/linux/include/linux" "mm.h" > .file 29 "/src/linux/include/linux" "fs.h" > .file 30 "/src/linux/include/linux" "uidgid.h" > .file 31 "/src/linux/include/linux" "dcache.h" > .file 32 "/src/linux/include/linux" "seqlock.h" > .file 33 "/src/linux/include/linux" "list_bl.h" > .file 34 "/src/linux/in...

Hi ! I reproduced it on the file init/main.c The invocation, log and main.i / main.s is attached. -- Dipl.-Ing. Jan-Simon Möller jansimon.moeller at gmx.de Am Freitag, 16. Mai 2014, 14:25:47 schrieb Renato Golin: > On 16 May 2014 14:01, Jan-Simon Möller <dl9pf at gmx.de> wrote: > > A bisection points to > > > > git-svn-id:

...the hope that it will be useful, but + * WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY + * or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License + * for more details. + */ + +#ifndef __VMW_VMCI_API_H__ +#define __VMW_VMCI_API_H__ + +#include <linux/uidgid.h> +#include <linux/vmw_vmci_defs.h> + +#undef VMCI_KERNEL_API_VERSION +#define VMCI_KERNEL_API_VERSION_2 2 +#define VMCI_KERNEL_API_VERSION VMCI_KERNEL_API_VERSION_2 + +typedef void (vmci_device_shutdown_fn) (void *device_registration, void *user_data); + +bool vmci_device_get(u32 *api...

...the hope that it will be useful, but + * WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY + * or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License + * for more details. + */ + +#ifndef __VMW_VMCI_API_H__ +#define __VMW_VMCI_API_H__ + +#include <linux/uidgid.h> +#include <linux/vmw_vmci_defs.h> + +#undef VMCI_KERNEL_API_VERSION +#define VMCI_KERNEL_API_VERSION_2 2 +#define VMCI_KERNEL_API_VERSION VMCI_KERNEL_API_VERSION_2 + +typedef void (vmci_device_shutdown_fn) (void *device_registration, void *user_data); + +bool vmci_device_get(u32 *api...

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with