search for: linuxst

...ace to use in smb.conf file. This is rejected since the address of the interface is issued by the DHCP server, i.e., it changes frequently forcing me to change the smb.conf frequently. Solution #2: Fix /etc/hosts file as specified in GOTCHAS.txt. I changed the entry in /etc/hosts from 127.0.0.1 LinuxStation.ourdomain.com loopback to 127.0.0.1 loopback This resulted in nmbd spitting out errors about not being able to find the IP address of LINUXSTATION (the samba host's name). Since this is a DHCP device, there is no entry in /etc/host of the form 205.123.45.001 LinuxStation.ourdomain.com...

...se rsync to synchronise a Red Hat 7.2 Server and a RedHat 7.3 Server and they have different versions of rsync on them. I set up 2 x Red Hat 7.3 machines, both running rsync-2.5.4-2 and they work fine, transferring files via rsync with no problem. Here is my test rsyncd.conf on the server "linuxstation" [home] uid = root gid = root read only = no path = /tmp After placing the appropriate entries in the /etc/hosts files of all PCs, I created a single-line text file in /tmp on the workstation called "zz" and ran: rsync -avt /tmp/zz linuxstation::home It transferred fine....

...Exit: + return result; +} + +/* + * Cleans up VMCI components shared between guest and host + * driver. + */ +static void drv_shared_cleanup(void) +{ + vmci_event_exit(); + vmci_resource_exit(); +} + +static const struct file_operations vmuser_fops; +static struct vmci_linux_state linuxState = { + .misc = { + .name = MODULE_NAME, + .minor = MISC_DYNAMIC_MINOR, + .fops = &vmuser_fops, + }, + .activeContexts = ATOMIC_INIT(0), +}; + +/* + * Called on open of /dev/vmci. + */ +static int drv_driver_open(struct inode *inode,...

...Exit: + return result; +} + +/* + * Cleans up VMCI components shared between guest and host + * driver. + */ +static void drv_shared_cleanup(void) +{ + vmci_event_exit(); + vmci_resource_exit(); +} + +static const struct file_operations vmuser_fops; +static struct vmci_linux_state linuxState = { + .misc = { + .name = MODULE_NAME, + .minor = MISC_DYNAMIC_MINOR, + .fops = &vmuser_fops, + }, + .activeContexts = ATOMIC_INIT(0), +}; + +/* + * Called on open of /dev/vmci. + */ +static int drv_driver_open(struct inode *inode,...

I have so far been unable to get rsync to work properly in a test setup. Does anyone have any ideas? Both PCs are running RedHat 7.2. The Server: IP Address 192.168.0.202 Server Name: RH72TB hosts.allow ALL: 192.168.0.201 rsyncd.conf: [testmodule] path = /tmp The Client: IP Address 192.168.0.201 hosts file: 192.168.0.202 RH72TB I have run "rsync --daemon" on the server.

Does anybody know if the process of upgrading firmware on "Linksys SPA3102-NA" in Linux is the same as on Sipura 3K as described on voip-info.org http://www.voip-info.org/wiki/view/Sipura -- #Joseph GPG KeyID: ED0E1FB7

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * 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

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * 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

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 post.

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 post.

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 post.

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 post.