similar to: Can't connect to shares w/2.0beta3 on OSF1

Previously if you were root, and you tried to change directory into a directory which was not owned by you and not readable (eg. 0700 bin:bin), it would fail. This doesn't fail on regular directories because when you are root the kernel just ignores permissions. Although libguestfs in general tries not to duplicate kernel code, in the case where we emulate the FUSE access(2) system call,

>Date: Tue, 8 Dec 1998 11:00:42 -0500 (EST) >From: Rob Naccarato <rob@sheridanc.on.ca> >To: samba@samba.org >Subject: Can't connect to shares w/2.0beta3 on OSF1 > > >I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to >give 2.0beta3 a try. For some reason, I cannot connect to any of the >server's >shares or even get a list of

mainly question for the intel folks, any chance to rerun the ltp testsuites to see how we are doing these days with all the changes ? thanks :) Wim

Problem is apparently with locking issues, disabled oplocks in the [general] section, and the problem actually got worse... Here's what happens: User-A part of group1, opens Excel file off of share, saves, exits... User-B (or even User-A for that matter) tries to re-open same file, get error stating it's locked and can only open for read-only access... Both users in the same group, and

Enable stereoscopic output for HDMI and DisplayPort connectors on NV50+ (G80+) hardware. We do not enable stereoscopy on older hardware in case there is some older board that still has HDMI output but for which we have no logic for setting the Vendor InfoFrame. With this, I get an obvious 3D output when using the "testdisplay" program from intel-gpu-tools with the "-3"

On Tue, Apr 11, 2017 at 1:32 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater > <alastair.bridgewater at gmail.com> wrote: > > + /* HDMI 3D support */ > > + if ((disp->disp.oclass >= NV50_DISP) > > You probably meant G82_DISP. Although I don't know if there were any > G80's

skeet@Bridgewater.EDU wrote: > > > Basically what it looks like to me is that an smbd process is spawning a > child which goes defunct for some reason I have yet to determine and the > smbd process hangs out there waiting for the child. Of course the child is > never going to answer being defunct, so the parent smbd process sticks > around and keeps its oplocks. > That

This is an initial implementation of HDMI 3D mode support for the nouveau kernel driver. It works on all of the hardware that I have available to test at the moment, but I am unsure as to the overall approach taken for setting HDMI InfoFrames, there's no support for g84 or gf119 disps, and the criteria for enabling stereo support for an output seems a bit iffy. The first four patches arrange

Store the ELD correctly, not just enough copies of the first byte to pad out the given ELD size. Signed-off-by: Alastair Bridgewater <alastair.bridgewater at gmail.com> --- drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c

On Mon, Mar 27, 2017 at 05:57:57PM -0400, Alastair Bridgewater wrote: > HDMI 3D mode support, round two. Revisions include no longer dealing > with audio InfoFrames, passing infoframe data to NVKM as bags of bytes > rather than as data pre-packed for the hardware, more-normal return > value checking for drm_hdmi_*_infoframe_from_display_mode() results, > Frame-Packing mode support,

Full_Name: Michael Hoffman Version: 2.0.0-beta-20041001 OS: OSF1 V5.1 Submission from: (NULL) (193.62.199.8) Hello. Building R 2.0.0-beta-20041001 on OSF1 V5.1 failed because the default configure sets R_XTRA_CFLAGS to "-std1 -ieee_with_inexact." The bzip2 directory includes C99 code that requires -std1 to not be set in order to compile. This halts the overall build process.

This was v3 patch 2/22, reworked to address the confusion about how a structured reply header is read in two pieces before getting to the payload portion. I'm still working on rebasing the rest of my v3 series (patches 1, 3-22) from other comments given, but this seemed independent enough that it's worth posting now rather than holding it up for the rest of the series. Eric Blake (4):

http://bugzilla.mindrot.org/show_bug.cgi?id=319 Summary: Privilege Separation failing on OSF1 v5.1 Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

I am stuck in the installation of "R" on ALPHA runing OSF1/V5.1 for individual use. When I ran "./configure CC=cc F77=f77 Make=gmake ", the following message came out, 506426:/usr/users/1/mwang2/R/R-2.1.1/bin/exec/R: /sbin/loader: Error: libreadline.so.4: symbol "tgetflag" unresolved 506426:/usr/users/1/mwang2/R/R-2.1.1/bin/exec/R: /sbin/loader: Fatal Error: Load

I tried configuring Samba 2.0.7pre4 on a OSF1 machine (actually a DEC Alpha running Digital Unix 4.0d) with --with-utmp. The autoconf system sets the variable HAVE_UTMPX_H The linking of smbd aborts with the message ---------------------------------------------------------- ld: Unresolved: getutmpx utmpxname updwtmpx *** Exit 1 ---------------------------------------------------------- If I

Dear R-users, I currently have trouble in trying to compile R-1.3.0-patched on Compaq OSF1. -------- >uname -a OSF1 adenine.fysik.dtu.dk V4.0 1229 alpha -------- The 'configure' step ended seemingly corretly: ----------------------- R is now configured for alphaev6-dec-osf4.0f Source directory: . Installation directory: /home/adenine/sysman/laurent/share/ C

I'm still playing with ideas on how to split rstate from wstate (so that we can send a request without waiting for POLLIN to complete a pending reply), but this is some preliminary refactoring I found useful. I also fixed a couple of bugs while in the area (already pushed). There's a question of whether we want nbd_handle to be nearly 5k, or if we should instead keep it small and add one

I'm having trouble compiling and installing R as a shared library on Alpha/OSF1. I used ./configure --enable-R-shlib SHLIB_CXXLDFLAGS=-L/lib/cmplrs/cxx (Using configure with --enable-R-shlib alone generated "Could not determine SHLIB_CXXLDFLAGS" errors.) make and everything else were done as specified in the documentation. It compiled everything without visible problems, but on

Hi, I have a problem with Samba on an OSF1 v4.0d machine. I get an "INTERNAL ERROR" and a core dump when trying to connect to a share from an NT 4.0 SP3 or W95 machine. I configured Samba to use encrypted password and I set the parameter "security=user". My Samba server is in a workgroup on its own, no PDC and BDCs around. I can see it in my Computer Neighborhood from the NT

This isn't quite finished because not all of the tests or examples have been updated, but it demonstrates an idea: Should we forget about the concept of having multiple connections managed under a single handle? In this patch there is a single ‘struct nbd_handle *’ which manages a single state machine and connection (and therefore no nbd_connection). To connect to a multi-conn server you must