search for: oaky

I'm not sure if this has already be answered, but when I try to mount something using smbmount I get an error that smbfs needs mount version 6. I am running kernel 2.2.16-3 I was running 2.2.14-5.0 and I was still having the same problem. Is there a fix to this. Or is it a bug. I have not been able to find any documentation on the exact problem, just other people with the same problem.

...ype::Verify >>> DIType::Verify >>> that try to access the context link: >>> if (getContext() && !getContext().Verify()) >>> return false; >>> >>> And the Verify functions are called from 10+ files. >>> >>> If we are oaky with not calling getContext().Verify(), option a) appears much better to me. >>> For printing | debugging purpose, we agree that not being able to trace the pointer is okay. >>> >>> Let me know your thoughts, >>> Manman >>> >>> On Jun 21, 2013...

Some scoping for option a: There are a few Verify functions DISubprogram::Verify DICompositeType::Verify DIType::Verify that try to access the context link: if (getContext() && !getContext().Verify()) return false; And the Verify functions are called from 10+ files. If we are oaky with not calling getContext().Verify(), option a) appears much better to me. For printing | debugging purpose, we agree that not being able to trace the pointer is okay. Let me know your thoughts, Manman On Jun 21, 2013, at 5:01 PM, Eric Christopher wrote: > On Fri, Jun 21, 2013 at 4:59 PM, D...

I need some help. I can map the NetApp filer, but when I do a 'ls' in the directory I get errors. Saying that the file or directory does not exist and I know the directories and files do, you can see them when you map the NetApp with NT. If you know the name of the directory you can change into it. I can also map NT with samba just fine with no problems. The NetApp is running a CIFS server

...ram::Verify >> DICompositeType::Verify >> DIType::Verify >> that try to access the context link: >> if (getContext() && !getContext().Verify()) >> return false; >> >> And the Verify functions are called from 10+ files. >> >> If we are oaky with not calling getContext().Verify(), option a) appears >> much better to me. >> For printing | debugging purpose, we agree that not being able to trace the >> pointer is okay. >> >> Let me know your thoughts, >> Manman >> >> On Jun 21, 2013, at 5...

...IType::Verify >>>> that try to access the context link: >>>> if (getContext() && !getContext().Verify()) >>>> return false; >>>> >>>> And the Verify functions are called from 10+ files. >>>> >>>> If we are oaky with not calling getContext().Verify(), option a) appears >>>> much better to me. >>>> For printing | debugging purpose, we agree that not being able to trace the >>>> pointer is okay. >>>> >>>> Let me know your thoughts, >>>>...

On Fri, Jun 21, 2013 at 12:33 PM, Manman Ren <mren at apple.com> wrote: > > On Jun 21, 2013, at 11:56 AM, Eric Christopher wrote: > >> On Fri, Jun 21, 2013 at 11:50 AM, Manman Ren <mren at apple.com> wrote: >>> >>> On Jun 21, 2013, at 11:35 AM, Eric Christopher wrote: >>> >>>> On Thu, Jun 20, 2013 at 10:52 PM, Manman Ren <mren at