search for: faslink

----- Forwarded message from Jeremy Allison <jra@samba.org> ----- From: jra@samba.org (Jeremy Allison) Subject: [faslink@excite.com: FW: W2k wkstation no longer recognized by samba pdc] Date: Tue, 23 Jul 2002 12:02:21 -0700 To: samba@samba.org User-Agent: Mutt/1.2.5i Errand of mercy :-). Jeremy. ----- Forwarded message from "mitchbnj_removethis@excite.com" <faslink@excite.com> ----- Delivered-To:...

Errand of mercy :-). Jeremy. ----- Forwarded message from "mitchbnj_removethis@excite.com" <faslink@excite.com> ----- Delivered-To: jra@samba.org To: jra@samba.org Subject: FW: W2k wkstation no longer recognized by samba pdc X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 643734ca1432f536042764450a0cebdc Reply-To: faslink@excite.com...

...**(Nah) Have you tried writing to someone on the team? TRIED IT, NO RESPONSE One thing I'm sure of is that your problem is definitely Computer Trust Account related. I AGREE (GRIN) --- On Fri 08/16, mitchbnj_removethis@excite.com wrote: From: mitchbnj_removethis@excite.com [mailto: faslink@excite.com] To: trevor@systematic.co.za, faslink@excite.com Cc: lists@samba.org Date: Fri, 16 Aug 2002 10:45:10 -0400 Subject: 1st thought: was: help (Still) w2k pro no longer trusted by 2.2.3 pdc > Thanks for the suggestions Trevor. Reformatting in case someone else has > problem too:...

There is OBVIOUSLY something wrong somewhere. EITHER a WHOLE bunch of us are stupider than we thought, the documentation left off a step, or there is something SO blatently obvious that we are ALL staring it in the face and missing it inches in front of our faces. This is exactly what I've had, (BUT I *D*I*D* have it running ok ...) and I STILL havent figured it out yet,... Subject:

.... But I will plan to develop it for the future. If this is a general-type request, we may get many more of these in the future. If this is a way to "sell" TNG for development to the boss, then a slick pres. may be nice, I guess. dereck --- "mitchbnj_removethis@excite.com" <faslink@excite.com> wrote: > > Thanks Peter. But What I'm seeking (I guess?) is the > holy Grail? > Re: Samba 3.0 vs Samba TNG > > I asked: Can someone from the team(s) explain the > differences in the > current (v2.2x) version of Samba (as well as the > next (3.0)) &g...

...> > My numbers are something like: > > 1 pdb per obj file: link.exe takes ~15 minutes and 16GB of ram, > lld-link.exe takes 2:30 minutes and ~8GB of ram > around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, > lld-link.exe takes 1:30 minutes and ~6GB of ram > faslink: link.exe takes 40 seconds, but then 20 seconds of loading at the > first break point in the debugger and we lost DIA support for listing > symbols. > incremental: link.exe takes 8 seconds, but it only happens when very minor > changes happen. > > We have an non negligible number...

...w what kind of performance to expect? My numbers are something like: 1 pdb per obj file: link.exe takes ~15 minutes and 16GB of ram, lld-link.exe takes 2:30 minutes and ~8GB of ram around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, lld-link.exe takes 1:30 minutes and ~6GB of ram faslink: link.exe takes 40 seconds, but then 20 seconds of loading at the first break point in the debugger and we lost DIA support for listing symbols. incremental: link.exe takes 8 seconds, but it only happens when very minor changes happen. We have an non negligible number of symbols used on some runti...

...something like: >> >> 1 pdb per obj file: link.exe takes ~15 minutes and 16GB of ram, >> lld-link.exe takes 2:30 minutes and ~8GB of ram >> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, >> lld-link.exe takes 1:30 minutes and ~6GB of ram >> faslink: link.exe takes 40 seconds, but then 20 seconds of loading at the >> first break point in the debugger and we lost DIA support for listing >> symbols. >> incremental: link.exe takes 8 seconds, but it only happens when very >> minor changes happen. >> >> We have a...

...;> >>> 1 pdb per obj file: link.exe takes ~15 minutes and 16GB of ram, >>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, >>> lld-link.exe takes 1:30 minutes and ~6GB of ram >>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading at >>> the first break point in the debugger and we lost DIA support for listing >>> symbols. >>> incremental: link.exe takes 8 seconds, but it only happens when very >>> minor changes happen. >>&gt...

...t; 1 pdb per obj file: link.exe takes ~15 minutes and 16GB of ram, >>>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, >>>> lld-link.exe takes 1:30 minutes and ~6GB of ram >>>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading at >>>> the first break point in the debugger and we lost DIA support for listing >>>> symbols. >>>> incremental: link.exe takes 8 seconds, but it only happens when very >>>> minor changes hap...

...file: link.exe takes ~15 minutes and 16GB of ram, >>>>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, >>>>> lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading at >>>>> the first break point in the debugger and we lost DIA support for listing >>>>> symbols. >>>>> incremental: link.exe takes 8 seconds, but it only happens when very >>>>> m...

You probably don't want to go down the same route that clang goes through to write the object file. If you think yaml2coff is convoluted, the way clang does it will just give you a headache. There are multiple abstractions involved to account for different object file formats (ELF, COFF, MachO) and output formats (Assembly, binary file). At least with yaml2coff It's true that yaml2coff

...s and 16GB of ram, >>>>>>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, >>>>>>> lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading >>>>>>> at the first break point in the debugger and we lost DIA support for >>>>>>> listing symbols. >>>>>>> incremental: link.exe takes 8 seconds, but it only happens when ver...

...takes ~15 minutes and 16GB of ram, >>>>>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of ram, >>>>>> lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading at >>>>>> the first break point in the debugger and we lost DIA support for listing >>>>>> symbols. >>>>>> incremental: link.exe takes 8 seconds, but it only happens when very >>&g...

...m, >>>>>>>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of >>>>>>>> ram, lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading >>>>>>>> at the first break point in the debugger and we lost DIA support for >>>>>>>> listing symbols. >>>>>>>> incremental: link.exe takes 8 seconds, but it only happ...

...gt;>>>>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of >>>>>>>>> ram, lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of loading >>>>>>>>> at the first break point in the debugger and we lost DIA support for >>>>>>>>> listing symbols. >>>>>>>>> incremental: link.exe takes 8 seconds, but...

...lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>>>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of >>>>>>>>>>> ram, lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of >>>>>>>>>>> loading at the first break point in the debugger and we lost DIA support >>>>>>>>>>> for listing symbols. >>>>>>>>>>> incremental: link.e...

...gt;>> lld-link.exe takes 2:30 minutes and ~8GB of ram >>>>>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of >>>>>>>>>> ram, lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of >>>>>>>>>> loading at the first break point in the debugger and we lost DIA support >>>>>>>>>> for listing symbols. >>>>>>>>>> incremental: link.exe takes 8 s...

...minutes and ~8GB of ram >>>>>>>>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB >>>>>>>>>>>>> of ram, lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>>>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of >>>>>>>>>>>>> loading at the first break point in the debugger and we lost DIA support >>>>>>>>>>>>> for listing symbols. >>>>>>>>>>>>...

...takes 2:30 minutes and ~8GB of ram >>>>>>>>>>>> around 10 pdbs per folder: link.exe takes 1 minute and 2-3GB of >>>>>>>>>>>> ram, lld-link.exe takes 1:30 minutes and ~6GB of ram >>>>>>>>>>>> faslink: link.exe takes 40 seconds, but then 20 seconds of >>>>>>>>>>>> loading at the first break point in the debugger and we lost DIA support >>>>>>>>>>>> for listing symbols. >>>>>>>>>>>> increme...