similar to: novice - samba3+; suse linuxpro9.1

Hi, armed with Samba-3 -by example I proceeded to test my 2 linux lan [suselinux pro 9.1 with Samba 3.0.9-2.6-suse]. I followed instructions and made the smb.config as small as possiblw: [global] workgroup = snj server string = Samba Server guest ok = yes [orb] comment = removable 2.2 gb hd path = /orb browsable = yes read only = no However, I was stumped practically immediately as you can

Hi, I got the validation to work. scn@west:~> smbclient -L west -U% Domain=[SNJ] OS=[Unix] Server=[Samba 3.0.9-2.6-SUSE] Sharename Type Comment --------- ---- ------- orb Disk removable 2.2 gb hd IPC$ IPC IPC Service (Samba Server) ADMIN$ IPC IPC Service (Samba Server) Domain=[SNJ]

Hi, I have posted to this list once before without any reply. It would be nice if some reply could indicate why the posting was not appropriate and some indication as to what one should do - the last time I included my smbconf. This time I have reworked my questions, limited their scope , and put them in two emails. I have two essentially identical linux computers [east and west] both running

hi, I'm new to Samba. I use Suse linux 9.1pro & kde on a small network with Samba 3.0.9. I tried the testparm from the Official Samba -3 howto. Unfortunately the book, etc. does not address the error msg given, follows. Can somebody help? scn@scn:~> testparm -s -v | egrep "(lp|print|spool|driver|ports|\[)" Load smb config files from /etc/samba/smb.conf Processing section

HI, I guess I did sth wrong with the optional argument in the program. but I don't know how should I make it. in my main program: source("getelasticity_overPB.r") crossprice<-getelasticity(mydata,mydatao,"nest")$cross_p is same with crossprice<-getelasticity(mydata,mydatao)$cross_p I don't know why???? In ""getelasticity_overPB.r": I have the

Hi the list. Is there a bug in mmlcr package ? The following code does not compile: mmlcrTest <- function(dataW){ dataL <- reshape(dataW,idvar="id",timevar="T",varying=list("T0","T1","T2"),direction="long",v.names="score") resultR <- mmlcr(outer= ~ 1 | id, components = list(list(formula =

Hi, John, thanks for replying. I am fully aware that this is a volunteer effort and do appreciate it very much. I really didn't expect an automatic answer - I was suggesting an automatic response which could indicate the objection[s]? I have downloaded the S3be `book' and ordered it from amazon. I was puzzled by your comment: `Please do not refer to smbfs's friends as Samba. The

Hi All, In XCore backend, I saw “ …... EVT VT = Op.getValueType(); SDValue Data = DAG.getNode(XCoreISD::CRC8, DL, DAG.getVTList(VT, VT), Op.getOperand(1), Op.getOperand(2) , Op.getOperand(3)); SDValue Crc(Data.getNode(), 1); SDValue Results[] = { Crc, Data }; return DAG.getMergeValues(Results, 2, DL); “ which is used to lower an

Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts on guest request. When active, host->guest notifications will be handled via global_indicator -> queue indicators instead of queue indicators + subchannel I/O interrupt. Indicators for virtqueues may be present at an offset. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/s390x/css.c |

Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts on guest request. When active, host->guest notifications will be handled via global_indicator -> queue indicators instead of queue indicators + subchannel I/O interrupt. Indicators for virtqueues may be present at an offset. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/s390x/css.c |

On Fri, 5 Apr 2019 01:16:15 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Virtio-ccw relies on cio mechanisms for bootstrapping the ccw device. Well, a ccw device is, by definition, using cio mechanisms ;) Better say: "As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor." Or something like that. > Thus we

As virtio-ccw devices are channel devices, we need to use the dma area within the common I/O layer for any communication with the hypervisor. Note that we do not need to use that area for control blocks directly referenced by instructions, e.g. the orb. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An

As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. This patch addresses the most basic stuff (mostly what is required for virtio-ccw), and does take care of QDIO or any devices. An interesting side effect is that virtio structures are now going to get allocated in 31 bit addressable storage. Signed-off-by: Halil Pasic <pasic at

From: Halil Pasic <pasic at linux.ibm.com> As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

From: Halil Pasic <pasic at linux.ibm.com> As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

Currently I only have one machine backing up to another. I am backing up to a filesystem that is mounted as nosuid. The syncing process works perfectly except it fails on files that are suid. Example proc/ root/ tmp/ mknod tmp/mysql.sock : Invalid argument mknod tmp/orbit-daud/orb-12573780511489051058 : Invalid argument mknod tmp/orbit-daud/orb-139425434385535813 : Invalid argument mknod

Move base / limit accessors into desc.h, where they properly belong. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/include/asm-i386/system.h =================================================================== --- linux-2.6.13.orig/include/asm-i386/system.h 2005-08-08 17:58:03.000000000 -0700 +++ linux-2.6.13/include/asm-i386/system.h 2005-08-08 18:01:31.000000000 -0700

Move base / limit accessors into desc.h, where they properly belong. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/include/asm-i386/system.h =================================================================== --- linux-2.6.13.orig/include/asm-i386/system.h 2005-08-08 17:58:03.000000000 -0700 +++ linux-2.6.13/include/asm-i386/system.h 2005-08-08 18:01:31.000000000 -0700

Move base / limit accessors into desc.h, where they properly belong. Patch-base: 2.6.13-rc5-mm1 Patch-keys: i386 desc cleanup Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/include/asm-i386/system.h =================================================================== --- linux-2.6.13.orig/include/asm-i386/system.h 2005-08-09 20:17:26.000000000 -0700 +++

Move base / limit accessors into desc.h, where they properly belong. Patch-base: 2.6.13-rc5-mm1 Patch-keys: i386 desc cleanup Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/include/asm-i386/system.h =================================================================== --- linux-2.6.13.orig/include/asm-i386/system.h 2005-08-09 20:17:26.000000000 -0700 +++