search for: cbrookes

Hello list. I've been running an old version of Samba (1.9.16p9) to give read-only access to my Digital UNIX 4.0B workstation hard drives (the share is called "rootdir"). It's worked great for over 2 years for that purpose. I finally want to give read-write access to 2 users (myself and my assistant). Her computer has NT 4.0 with Service Pack 3. Mine has NT 4.0 with Service

Hello everyone - I just upgraded from Samba 1.9.16p9 to 2.0.6 last week. Samba is running on my Digital UNIX 4.0E (aka Tru64 aka OSF1) workstation, and I have various Win'95, Win'98, and NT 4.0 (SP4 & SP6) computers accessing the Samba shares. One share is read-only, and one is read/write to specific users (I've included my smb.conf file below). If a users accesses the

Hello folks - back on April 2nd I asked why my NT 4.0 with SP4 computer wouldn't connect to my old copy of Samba (1.9.16p9), while my neighbour's NT 4.0 with SP3 computer did just fine. This was in the case of a read-write share that only myself and my neighbour had access to under our user names. A read-only share worked just fine on both our computers. Thanks to Herb Lewis & Jan

Hi everybody - Yesterday, I said that my Windows 98 & 95 computers couldn't connect to my Samba shares after upgrading from version 1.9.16p9 to 2.0.6, while my NT 4.0 (SP4 & SP6) computers could, even though I had the same user names & passwords on all the machines (UNIX, Win'9x, NT). I re-read the "What's New in Samba 2.0.6" document this morning, and found

On 16/11/05, Kip Macy <kip.macy@gmail.com> wrote: > The way the initial memory space gets setup there is no way MFS could work. > It wasn''t an anticipated use. I guess somewhere either in FreeBSD GNATS or > xen''s bugzilla there should be i386-xen FreeBSD bugs filed for me to track. I intend to file a bug report sooner or later, but in the meantime I decided to

1.6.2.0-rc1. I am having trouble with voice mail intermittently not working correctly on CHANUNAVAIL. (it may happen for other statuses too, haven't checked). Basically here's what happens: -- Executing [1651xxxxxx at mydids:1] Macro("SIP/ipkall-trunk-14838bc8", "phone,1651xxxxxx") in new stack -- Executing [s at macro-phone:1]

I''ve currently got a Xen 2 system running on a CL10000 VIA system. I''d like to upgrade to Xen 3 and make use of the hardware virtualization support in Xen (sometimes). My requirements then: 1) Cheap CPU. AMD or Intel. Must have Xen3 hardware VM support. Any speed. 2) Lower power consumption from the CPU 3) Cheap mobo to support the chip. 4) Decent raid-1 SATA support on the