Displaying 7 results from an estimated 7 matches for "tremont".
Did you mean:
premont
2006 Nov 22
1
Confused about Active Directory, Winbind, and Kerberos
...been documents my efforts:
http://michael.susens-schurter.com/interop/
and on my blog:
http://michael.susens-schurter.com/blog/
Thanks in advance,
Michael Schurter
Relevant system info:
Debian Etch, 2.6.17 kernel, Samba 3.023c-4, MIT Kerberos 1.4.4-4
### relevant smb.conf lines ###
workgroup = TREMONT
realm = TREMONT.LOCAL
security = ADS
auth methods = winbind
obey pam restrictions = Yes
idmap uid = 10000-20000
idmap gid = 10000-20000
template shell = /bin/bash
winbind enum users = Yes
winbind enum groups = Yes
winbind use default...
2006 Nov 27
1
Samba 3.0.23d & /etc/krb5.keytab
...re of it?
Sorry if these are elementary questions, but the Samba HOWTO didn't help
me understand Samba's interaction with Kerberos.
My /etc/krb5.keytab looks like this:
KVNO Principal
----
--------------------------------------------------------------------------
1 host/schurter3-linux.tremont.local@TREMONT.LOCAL
0 host/schurter3-linux.tremont@TREMONT.LOCAL
0 host/schurter3-linux.tremont@TREMONT.LOCAL
0 host/schurter3-linux.tremont@TREMONT.LOCAL
0 host/schurter3-linux@TREMONT.LOCAL
0 host/schurter3-linux@TREMONT.LOCAL
0 host/schurter3-linux@TREMONT.LOCAL
0 schurter3-...
2006 Dec 06
2
Samba + Win2k works, Win2003 fails
...long as I hack my /etc/hosts
and /etc/samba/lmhosts files to trick Samba into always using my
networks Windows 2000 Active Directory Server. The second a Samba
command finds and attempts to use the 2003 server, it fails.
Workstation: Debian Sid, Samba 3.0.23d (pam_winbind, MIT kerberos)
Domain: TREMONT
Realm: tremont.local
AD Servers:
thsdc1/192.168.100.4 (Windows 2000)
thsdc2/192.168.100.6 (Windows 2003)
So both my hosts & lmhosts files point thsdc2 to thsdc1's IP address
which seems to trick Samba into always using thsdc1. thsdc1 is also
what I set all the appropriate /etc/krb5.conf...
2019 Mar 23
2
Generating object files more efficiently
Johannes,
I tried the last one and it gave me this:
error: unknown target CPU 'XYZ'
note: valid target CPU values are: nocona, core2, penryn, bonnell, atom,
silvermont, slm, goldmont, goldmont-plus, tremont, nehalem, corei7,
westmere, sandybridge, corei7-avx, ivybridge, core-avx-i, haswell,
core-avx2, broadwell, skylake, skylake-avx512, skx, cascadelake,
cannonlake, icelake-client, icelake-server, knl, knm, k8, athlon64,
athlon-fx, opteron, k8-sse3, athlon64-sse3, opteron-sse3,...
2019 Mar 23
4
Generating object files more efficiently
...: via llvm-dev
Subject: Re: [llvm-dev] Generating object files more efficiently
Johannes,
I tried the last one and it gave me this:
error: unknown target CPU 'XYZ'
note: valid target CPU values are: nocona, core2, penryn, bonnell, atom,
silvermont, slm, goldmont, goldmont-plus, tremont, nehalem, corei7,
westmere, sandybridge, corei7-avx, ivybridge, core-avx-i, haswell,
core-avx2, broadwell, skylake, skylake-avx512, skx, cascadelake,
cannonlake, icelake-client, icelake-server, knl, knm, k8, athlon64,
athlon-fx, opteron, k8-sse3, athlon64-sse3, opteron-sse3,...
2019 Mar 23
2
Generating object files more efficiently
...ect files more efficiently
>
>
>
> Johannes,
>
>
> I tried the last one and it gave me this:
>
>
> error: unknown target CPU 'XYZ'
> note: valid target CPU values are: nocona, core2, penryn, bonnell, atom,
> silvermont, slm, goldmont, goldmont-plus, tremont, nehalem, corei7,
> westmere, sandybridge, corei7-avx, ivybridge, core-avx-i, haswell,
> core-avx2, broadwell, skylake, skylake-avx512, skx, cascadelake,
> cannonlake, icelake-client, icelake-server, knl, knm, k8, athlon64,
> athlon-fx, opteron, k8-sse3, athlon64...
2019 Mar 23
2
Generating object files more efficiently
Currently I compile my C code in 2 steps in order to generate .o files
clang -emit-llvm -c foo.c -o foo.bc
llc -march=XYZ foo.bc -filetype=obj
Is there a way to generate either .o or .elf files in just 1 command?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190323/da9b3c18/attachment.html>