similar to: No subject

Displaying 20 results from an estimated 40000 matches similar to: "No subject"

2001 Nov 25
1
(no subject)
Hello all, Here is my situation: I have an existing linux box with 100+ users. This box run various services. Users do not have shell access. I have added samba to this box so users can share files and access their files from Windows. Samba installation and configuration went smoothly. Now, the problem is, I need to create entries in smbpasswd for these 100+ users. How would I go about creating
2001 Nov 26
2
Access denied from NT
Hi, I have a problem in accessing samba server from NT network neighbourhood. I can see the samba server icon on neighbourhood. But while trying to access then it's asking for user name & passowrd. I am not using local user & password from unix box rather it should be authenticated from NT PDC and accordingly I have modified the smb.conf file. Here is the sample of that. 103 flara %
2004 Sep 10
0
Java?
I'd be interested in helping too. I'm pretty new, but I think that JNI would be the easiest way to go. of course, never having done anything with JNI, what do I know :) Dave -----Original Message----- From: Josh Coalson [mailto:xflac@yahoo.com] Sent: Wednesday, November 28, 2001 5:19 PM To: Cain Brian-BCAIN1; dev Cc: Cracauer, David D. Subject: RE: [Flac-dev] Java? Decoding FLAC is
2001 Nov 24
1
lme or nlme
I'm trying to run a linear mixed effects model using nlme. It appears that lme is not available for R, but looks like I should be able to run linear models using nlme. What I tryed looks something like this: fit <- nlme (Y ~ A + B + C + D, fixed=list(A,B,C,D),random=Z). This didn't work. I got this error: Error in reStruct(random, REML = REML, data = NULL) : Object must be
2001 Nov 20
1
using samba to serve the whole tree of home directories
I'm trying to use samba to serve a number of home directories to other samba Linux clients on my network. ie. I have a set of client machines that want to use the /home directory that my samba server will provide I thought I could set up a share that goes something like this [homedirs] path = /home writable = true On a client machine, I smbmount //myserver/homedirs
2001 Nov 21
1
max. no of files(again)
Hello! A good day to you all. we've recently had some problems with samba (2.2.0) and sourcesafe. We had one particular project with over 700 files on it, and we've just recently encountered some problems with it, i.e. "corrupted" files from sourcesafe. i've read the archives, and someone mentioned that the number is actually unlimited(or 6.4million at the very least)...so
2013 Jan 02
0
Bug or strange behaviour or --output-prefix
Seems like what you really want is an --input-prefix parameter. You might also like a --create-output-directories option. In all cases except absolute paths, the input prefix must be assumed to be the current working directory. Therefore, any relative paths in input file names must be preserved on output to avoid collapsing multiple source directories into a single output directory, with
2001 Nov 29
3
Help me Please
Kind Attention: Andrew Tridgell Jeremy Allison Luke Kenneth Casson Leighton John H Terpstra Dear Sir, Good wishes. I am in big trouble. Please, help me. I am trying to setup and configure our college network. It comprises of the following: 1. RedHat Linux Server, Assembled PC, 20GB IDE, P-III, 400 MHz, 256 MB MM eth0: IP Address: 192.168.0.1,
2003 Dec 01
0
No subject
winbind primary group = 213478 winbind force primary = no // this is the default, but I just wanted to be explicit Stephen A Jazdzewski Steve@Jazd.com <<samba-2.2.4-forceprimarygrouprid.patch>> ------_=_NextPart_000_01C1FC4A.A7164AC0 Content-Type: application/octet-stream; name="samba-2.2.4-forceprimarygrouprid.patch" Content-Transfer-Encoding: quoted-printable
2007 Mar 30
0
Wine release 0.9.34
This is release 0.9.34 of Wine, a free implementation of Windows on Unix. What's new in this release: - Support for Xcursor. - A range of fixes for various installers. - New builtin xcopy tool. - The usual assortment of Direct3D fixes. - Lots of bug fixes. Because of lags created by using mirrors, this message may reach you before the release is available at the public sites. The
2003 Mar 13
2
Configuring firewall to allow Samba to work
Dear Folks, This is a note for all those people out there who had to turn off their firewalls (iptables) to get Samba to work. First start the GUI interface to the firewall by typing [somedir]# redhat-config-securitylevel Click on "Customize". Click the check box for your network adapter (usually "eth0"). Click on the checkboxes for any services you want to allow (I
2003 Mar 27
2
Problem with xcopy /d & samba
A problem has arisen with the way samba handles file creation dates compared to NT/win2k, which prevents xcopy /d from working correctly. On NT/Win2k, files copied from another NT machine using xcopy end up with the modified dates equal to the original modified date of the file, and the created and accessed dates become the date of the xcopy operation. On Samba, files copied from an NT
2004 Aug 06
2
improved error.log output --diff
diff -u --recursive icecast/src/admin.c icecast-new/src/admin.c --- icecast/src/admin.c 2003-07-18 16:29:23.000000000 -0400 +++ icecast-new/src/admin.c 2003-08-06 19:18:32.000000000 -0400 @@ -213,7 +213,7 @@ html_write(client, "HTTP/1.0 200 OK\r\n" "Content-Type: text/html\r\n" "\r\n"); - DEBUG1("Sending XSLT
2004 Sep 10
4
FLAC 1.0.1 source release out
The source release for 1.0.1 is finally up on sourceforge. If you are compiling for x86 make sure to read the note in in the README about automake 1.5. Josh __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com
2012 Dec 18
2
Bug or strange behaviour or --output-prefix
Hi all, I was busy programming a tool to automatically run some tests to update the FLAC comparison page (http://xiph.org/flac/comparison.html) when I stumbled across some weird behaviour of the flac program. So I compiled from git and it seems that this bug still is there. As I don't have any experience on coding C and don't know which bug-report facility to use, this seemed the
2019 Sep 17
1
[PATCH 2/6] drm/nouveau: fault: Widen engine field
On Tue, 17 Sep 2019 at 01:18, Thierry Reding <thierry.reding at gmail.com> wrote: > > From: Thierry Reding <treding at nvidia.com> > > The engine field in the FIFO fault information registers is actually 9 > bits wide. Looks like this is true for fault buffer parsing too. > > Signed-off-by: Thierry Reding <treding at nvidia.com> > --- >
2019 Sep 16
0
[PATCH 2/6] drm/nouveau: fault: Widen engine field
From: Thierry Reding <treding at nvidia.com> The engine field in the FIFO fault information registers is actually 9 bits wide. Signed-off-by: Thierry Reding <treding at nvidia.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/fault/gv100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/fault/gv100.c
2019 Sep 16
0
[PATCH 1/6] drm/nouveau: fault: Store aperture in fault information
From: Thierry Reding <treding at nvidia.com> The fault information register contains data about the aperture that caused the failure. This can be useful in debugging aperture related programming bugs. Signed-off-by: Thierry Reding <treding at nvidia.com> --- drivers/gpu/drm/nouveau/include/nvkm/subdev/fault.h | 1 + drivers/gpu/drm/nouveau/nvkm/engine/fifo/gk104.c | 3 ++-
2010 Oct 20
0
No subject
samba fails to allow this operation. 4.11. documentation ... ----------------------- In [8] there is very helpful tip to take migration using temporal root acco= unt. These two sentences was that break point... 4.12. Searching for root ------------------------ As stated in [7] net command operates on two servers, both of them is conne= cted using same account name. On other side DST account
2019 Sep 17
1
[PATCH 1/6] drm/nouveau: fault: Store aperture in fault information
On Tue, 17 Sep 2019 at 01:18, Thierry Reding <thierry.reding at gmail.com> wrote: > > From: Thierry Reding <treding at nvidia.com> > > The fault information register contains data about the aperture that > caused the failure. This can be useful in debugging aperture related > programming bugs. Should this be parsed for fault buffer entries too? > >