similar to: Username Case Sensitivity vs. Lower Casing

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

From: Thierry Reding <treding at nvidia.com> As part of commit cfea88a4d866 ("drm/nouveau: Start using new drm_dev initialization helpers"), the initialization of the Nouveau DRM device was reworked and along the way the platform driver initialization was left incomplete. Add a call to nouveau_drm_device_init() to make sure all of the structures are properly initialized.

On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > Hi Thierry et al. > > > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > > Tegra124") graphics on Apalis TK1 is broken. During boot it fails > > loading the vic firmware: > > > > [

On Mon, Dec 10, 2018 at 03:20:19PM +0000, Marcel Ziswiler wrote: > Hi Thierry > > On Mon, 2018-12-10 at 12:00 +0100, Thierry Reding wrote: > > On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > > > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > > > Hi Thierry et al. > > > > > > > > I noticed that

Hi Thierry et al. I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on Tegra124") graphics on Apalis TK1 is broken. During boot it fails loading the vic firmware: [ 1.595824] tegra-vic 54340000.vic: Direct firmware load for nvidia/tegra124/vic03_ucode.bin failed with error -2 [ 1.606140] tegra-vic: probe of 54340000.vic failed with error -2 Subsequently Tegra HDMI

On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > Hi Thierry et al. > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > Tegra124") graphics on Apalis TK1 is broken. During boot it fails > loading the vic firmware: > > [ 1.595824] tegra-vic 54340000.vic: Direct firmware load for > nvidia/tegra124/vic03_ucode.bin failed with

Can anyone confirm that SID -> name lookup with a trusted domain is broken? Thanks Daniel

Dear Sir I been reading through your (?) samba-doc folder on Debian 2.2. The document DOMAIN-CONTROL.txt is dated 1996 and updated 1998. It mentions that SAMBA cannot be a PDC. This is not the case anymore isn't it? Thank you Warwick Chapman (Glenwood 1999) http://www.boatrace.co.za Assistant IT Manager Glenwood High School, Durban, South Africa 031 2055241 083 7797094

Hello folks, I am kinda confused as to how to get some values for ldap. For example, here is an ldif entry: dn: uid=gcarter, ou=people,dc=plainjoe,dc=org logonTime: 0 displayName: Gerald Carter lmPassword: 552902031BEDE9EFAAD3B435B51404EE primaryGroupID: 1201 objectClass: posixAccount objectClass: sambaAccount acctFlags: [UX ] userPassword: {crypt}BpM2ej8Rkzogo uid: gcarter uidNumber:

Hello! I have a query regarding the use of "encrypt passwords = yes" and is wondering if anyone can help me with it. If I recall correctly, when using "encrypt passwords = no" , Samba will lookup the username/password via the UNIX /etc/passwd file or equivalent. And as the password can have mixed-case passwords, the "password level = x" parameter is used to

Hi there, I'm running Samba 3.0.14a-sernet on Suse 9.1 using ldapsam. I've got an interdomain trust setup across a vpn connection with a 2k3sp1 domain (DOMB). The trust works. What is strange is that a user from DOMB can't access any shares until they browse a share on our domain controller, say netlogon, then samba creates a new posix account for them in the ou=users base. I have

Hello, I need an answer to the following problem: I have a Samba server with domain logons enabled and with encrypt passwords=no. So I don't use the smbpasswd file, only the Unix password files. When I try to logon with a Win95 client (client for Microsoft Networks, logging on to a domain), people with mixed-case passwords cannot logon to the Samba logon server. Those with a password in

Dear Andrew Tridgell and Samba Team, You have done a wonderful job in providing an excellent piece of software. I am interested in porting smbclient to Handheld device, mostly as a hobby. Please see my website http://vieka.com/. Because some of the Handheld OSs don't have the ability to access Windows share resource, specifically, the new Pocket PC by Microsoft, I would like to add this

Hello, I use cvs to download samba with pserver.samba.org i get the 2.0.4b version ! where can i get the last stable release (2.0.7) and alpha versions with cvs and anonymous ? Thanks Guy Roussin

Concur ... I reckon that you need a bunch of how tos, that you can sent these rude people. I think that you are a victim of your own success. Samba has hit the mainstream, and now you are paying the price :-) Still ........ I prefer these messages to those filled with hypertext ... or worse.... 2 Meg of mime formatted drivel :-) Has anybody thanked you recently for providing so much help on

hypothetically, i have 2 different textures, one names TX_Skin, another named tx_skin. a plugin calls TX_SKIN, which texture does it choose?

Hello, Some mischief happened and I have been asked if I can find out who was logged into their computers within a specific off-hours time frame. My logs for that time frame happened to be running at debug level 3, so I have been looking through them and trying to figure out how to recognize a workstation login. I find lines beginning with auth_check_password_send that seem like reasonably good

Hi Thierry On Mon, 2018-12-10 at 12:00 +0100, Thierry Reding wrote: > On Mon, Dec 10, 2018 at 11:21:47AM +0100, Thierry Reding wrote: > > On Sat, Dec 08, 2018 at 02:54:45PM +0000, Marcel Ziswiler wrote: > > > Hi Thierry et al. > > > > > > I noticed that since commit 3dde5a2342cd ("ARM: tegra: Add VIC on > > > Tegra124") graphics on Apalis

Hi, While testing the upgrade from 2.0.6 to 2.0.7 I found some kind of misbehaviour of inherit permissions. It was already known that the SGID bit on directories is only useable with "inherit permissions = yes". Most of my shares depend heavily on this (unix) feature. Today I found out I cannot change a file attribute to read-only from NT while "inherit permissions" is set

Hi, unfortunately I found a bug in Dovecot's ACL handling for shared mailboxes. It turns out Dovecot doesn't enforce lower casing the privileged username to whom the mailbox should be shared to. This results in a invalid configuration. Users get confused, since they passed on a valid email address in their ACL setup. /usr/local/www/default/mail/test at