search for: sabotaging

...t; been reminded before), this mailing list >>>> is about Samba and its components, about helping >>>> people to get the supported configurations working >>>> and about improving Samba and its components. >>>> >>>> So could you please stop sabotaging these efforts? >> We are helping, not sabotaging. > We? .... Is that you ... steves? Eh? Plural. We work as a team. It works that way.

So pretty sure one of my boxes has been owned. Just wanted some advise on what to do next. Obviously, i'll need to nuke the fecker and start over but it would be really nice to find out how they got in as its a CentOS 4.3 which is bang up to date. So i found: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 7052 apache 25 0 27320 5348 8 R 99.0 0.5

...not noticed (even tough you have >> been reminded before), this mailing list >> is about Samba and its components, about helping >> people to get the supported configurations working >> and about improving Samba and its components. >> >> So could you please stop sabotaging these efforts? We are helping, not sabotaging. Simply pointing out the facts and saving pain and time of those caught out by id mapping, and rfc2307. There _are_ solutions without winbind which work _now_ and that is a very important fact for many of the threads here which get palmed off with...

Hey all, As most of you know, I've been having problems (hopefully solved by now, won't know until friend is able to reshare his box) with SAMBA over the internet. On my local area network, I am using SAMBA for a one way connection just fine. my question is as follows. Can I make an fstab entry so I can mount the XP share whenever I boot? The reason I ask is because currently Wine

...Not sure about the support level... And if you have not noticed (even tough you have been reminded before), this mailing list is about Samba and its components, about helping people to get the supported configurations working and about improving Samba and its components. So could you please stop sabotaging these efforts? Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.samba.org/pipermail/samba/attachments/20151109/7d838d1c/signature.sig>

...you have > >>been reminded before), this mailing list > >>is about Samba and its components, about helping > >>people to get the supported configurations working > >>and about improving Samba and its components. > >> > >>So could you please stop sabotaging these efforts? > > We are helping, not sabotaging. We? .... Is that you ... steves? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.samba.org/pipermail...

I'm trying to compile LLVM with musl libc library. The compilation process fails on the following: x86_64-linux-musl-g++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter

> > >What do you recommend for keeping track of user >activities? For preserving bash histories I followed >these recommendations: > >http://www.defcon1.org/secure-command.html > Interesting reading but, as others have noted, of limited use. Keystroke logging can be disabled by - as others have noted - either spawning another (perhaps different) shell, using a remote

Hello there friends & foes, I've had if with M$ windows! Next week I'll sabotage my shop (how 'bout password protecting dualboots on WS) and force LINUX down my users' throats ;-) (oh, don't I like this tone... makes me feel Billy G.) Oops, showstopper! ACL enabled network filesystem, where is it? I can't go with alpha code nfs4, so is there a patch to the smb

What I've done so far: Studied man samba Connected to my parents XP box on my LAN (two different connections, even). root@omega-fleet root]# smbclient -L 64.131.112.121 added interface ip=192.168.1.11 bcast=192.168.1.255 nmask=255.255.255.0 added interface ip=192.168.1.10 bcast=192.168.1.255 nmask=255.255.255.0 session request to some.ip failed (Called name not present) session request to

On 09/11/15 21:35, Jeremy Allison wrote: > On Mon, Nov 09, 2015 at 12:55:23PM +0100, buhorojo wrote: >>>>>> So could you please stop sabotaging these efforts? >>>> We are helping, not sabotaging. >>> We? .... Is that you ... steves? >> Eh? Plural. We work as a team. It works that way. > Ah. OK. Can we please remove the 'buhorojo' > account from being allowed to post to the > mailing list ? > &...

...but I can?t understand a lot of your double standards ... On the one hand develop a proprietary product "CrossOver Linux", but at the same time cooperating with the project "Wine" that's free. Wine could be today better than CrossOver Linux, but who knows, perhaps you are sabotaging and delaying the Wine project. I Don?t understand why you don?t develop software 100% free and paid, also you can charge for the tecnical support. thanks for reading ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/...

...gt; > And if you have not noticed (even tough you have > been reminded before), this mailing list > is about Samba and its components, about helping > people to get the supported configurations working > and about improving Samba and its components. > > So could you please stop sabotaging these efforts? > > Michael > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 17, 2001 at 08:57:13PM -0600, Jack Moffitt wrote: > A man-in-the-middle attack is not easy to pull off. If you can show me > why some person would be incented to attack someone like this, then > maybe there is a case for it. > Two easy motivations. #1 is deliberate sabotage. Let's say my station is not doing so well in

> This is not sad. > Science marches on... The project was never about science, but about freedom. jack.

I have Ubuntu 8.04 and I am trying to run and old Windows 95/3.1 MPOG game called Legends Of Kesmai. The Game needs to be in the root directory i.e. C:\legends and also needs to be run in 16 bit color. I have managed to change my color to 16 bit via editing my xorg.conf and changing the 24's to 16's. However when I try to execute the lokclient.exe file, it just closes itself without any

Hi all. This is my first post here... sorry if this topic was already discussed, but I could not find anything related. In applications run with wine, especially games (but not only) one or more keys seem to be pressed. I mean, even if I don't even touch the keyboard, the program thinks I continuously press UP ARROW and/or RIGHT ARROW. This happens regardless of applications. Sometimes I can

On the face of it may sound like a useless thing to have, but a Win32 Samba client does have some merit. It would make the Samba server safe from sabotage by gratuitous protocol changes, and it opens the door to making performance improvements. I see the Samba win32 client sitting alongside whatever MS supply rather than replacing it, so that an MS client can talk to an MS server. However, when

This message is in MIME format --_=XFMail.1.3.p0.Linux:990413120342:8241=_ Content-Type: text/plain; charset=us-ascii R 0.64.0 on RedHat Linux 5.1 I decided to add a "make check" command in the R RPM spec file to ensure that R works properly before packaging it up. I found (by sabotaging one of the *.Rout.save files) that errors found by "make check" are ignored and do not cause make to exit abnormally. This means that there is no way for rpm to know that the checks have failed, and the RPM package gets built anyway. I changed this by removing the "-" flag in t...

This message is in MIME format --_=XFMail.1.3.p0.Linux:990413120342:8241=_ Content-Type: text/plain; charset=us-ascii R 0.64.0 on RedHat Linux 5.1 I decided to add a "make check" command in the R RPM spec file to ensure that R works properly before packaging it up. I found (by sabotaging one of the *.Rout.save files) that errors found by "make check" are ignored and do not cause make to exit abnormally. This means that there is no way for rpm to know that the checks have failed, and the RPM package gets built anyway. I changed this by removing the "-" flag in t...