Open Sores Software.

So, I've spent the last several weeks fighting with various bits of free software in a vain attempt to make things that once worked, work again.

This morning, I gave up. You win. Congratulations.

I submitted a PO for a Network Appliance this morning with CIFS and NFS capability. Sure, this will cost close to 50k by the time I have the UPS, Veritas plugin, wall power, and the actual NetApp itself, but you know what?

I don't fucking care.

I got the latest version of Samba to compile, finally got it using Kerberos 5 without pitching a fucking fit, and while it still won't join AD properly, falling back to RPC, it'll at least use NTLMv2 to pass credentials now. The moderator at the samba-technical list apparently didn't feel that my submission for help in getting it to stop spitting out krb5 errors when it tried was justified, so I didn't get any. In fact, my missive never even showed up on the list. Fuck you too.

I figured, fuck it, I'll just use it as is, it's good enough for now, but I need to do one last recompile because CUPS and Impressario conflict, and since I have an Impressario license, and it doesn't suck a diseased goat like CUPS, guess who gets to stay? So I recompile Samba one last time, this time without CUPS for two reasons: a) it won't run without a constant stream of errors about not being able to talk to the cups daemon on localhost (no shit, I'm not running it, and I explicitly told you in your goddamned config file to use sysv printing, so why are you even fucking trying you self important piece of bloated shit?) and b) because it won't start without CUPS being installed because it was linked against the shared object libraries that are no longer there. New compilation using the exact same compilers, options, prerequisites, etc. The only difference is that it no longer finds and compiles the bits for CUPS support, and doesn't link against those shared objects.

I have a question for you software types, because I REALLY fucking want to know, and I'm pretty sure I already know the answer, but enlighten me anyway:

What kind of insane, crack addled, no talent, braindead idiot ties FILE LOCKING to an optional printing subsystem?

Mar 21 13:16:46 4A:dragon unix: WARNING: oplock 0xa80000004cf30d80: timed out
...
Mar 21 13:17:16 3D:dragon smbd[12694]: [2006/03/21 13:17:16, 0] smbd/oplock.c:(375)
Mar 21 13:17:16 3D:dragon smbd[12694]: Oplock break failed for file Outlook Folders/Space Breakfast.pst -- replying anyway


These are new, and they lead to file corruption like you wouldn't believe, and I'd bet a whole fuckload of money that if I reinstall CUPS, thereby breaking printing that works right now, and recompile Samba, again, in the exact same way, these will go away. Of course, I'll have syslog so over loaded with smbd CUPS errors again that if anything important ever happens I'll never see it, but why would I want to? In the mean time, I can either have my SGIs print, or I can have the users capable of moving data transparently between their Windows desktops, and the Unix machines they do analysis on. But not both.

Fuck you, I don't need this shit. I'm going to start attending conferences that the people who write this crap present at, just so I can throw feces at them. If they're going to code like monkeys, then I fully intend to treat them as such.

Open Sores Software.

So, I've spent the last several weeks fighting with various bits of free software in a vain attempt to make things that once worked, work again.

This morning, I gave up. You win. Congratulations.

I submitted a PO for a Network Appliance this morning with CIFS and NFS capability. Sure, this will cost close to 50k by the time I have the UPS, Veritas plugin, wall power, and the actual NetApp itself, but you know what?

I don't fucking care.

I got the latest version of Samba to compile, finally got it using Kerberos 5 without pitching a fucking fit, and while it still won't join AD properly, falling back to RPC, it'll at least use NTLMv2 to pass credentials now. The moderator at the samba-technical list apparently didn't feel that my submission for help in getting it to stop spitting out krb5 errors when it tried was justified, so I didn't get any. In fact, my missive never even showed up on the list. Fuck you too.

I figured, fuck it, I'll just use it as is, it's good enough for now, but I need to do one last recompile because CUPS and Impressario conflict, and since I have an Impressario license, and it doesn't suck a diseased goat like CUPS, guess who gets to stay? So I recompile Samba one last time, this time without CUPS for two reasons: a) it won't run without a constant stream of errors about not being able to talk to the cups daemon on localhost (no shit, I'm not running it, and I explicitly told you in your goddamned config file to use sysv printing, so why are you even fucking trying you self important piece of bloated shit?) and b) because it won't start without CUPS being installed because it was linked against the shared object libraries that are no longer there. New compilation using the exact same compilers, options, prerequisites, etc. The only difference is that it no longer finds and compiles the bits for CUPS support, and doesn't link against those shared objects.

I have a question for you software types, because I REALLY fucking want to know, and I'm pretty sure I already know the answer, but enlighten me anyway:

What kind of insane, crack addled, no talent, braindead idiot ties FILE LOCKING to an optional printing subsystem?

Mar 21 13:16:46 4A:dragon unix: WARNING: oplock 0xa80000004cf30d80: timed out
...
Mar 21 13:17:16 3D:dragon smbd[12694]: [2006/03/21 13:17:16, 0] smbd/oplock.c:(375)
Mar 21 13:17:16 3D:dragon smbd[12694]: Oplock break failed for file Outlook Folders/Space Breakfast.pst -- replying anyway


These are new, and they lead to file corruption like you wouldn't believe, and I'd bet a whole fuckload of money that if I reinstall CUPS, thereby breaking printing that works right now, and recompile Samba, again, in the exact same way, these will go away. Of course, I'll have syslog so over loaded with smbd CUPS errors again that if anything important ever happens I'll never see it, but why would I want to? In the mean time, I can either have my SGIs print, or I can have the users capable of moving data transparently between their Windows desktops, and the Unix machines they do analysis on. But not both.

Fuck you, I don't need this shit. I'm going to start attending conferences that the people who write this crap present at, just so I can throw feces at them. If they're going to code like monkeys, then I fully intend to treat them as such.

Open Sores Software.

So, I've spent the last several weeks fighting with various bits of free software in a vain attempt to make things that once worked, work again.

This morning, I gave up. You win. Congratulations.

I submitted a PO for a Network Appliance this morning with CIFS and NFS capability. Sure, this will cost close to 50k by the time I have the UPS, Veritas plugin, wall power, and the actual NetApp itself, but you know what?

I don't fucking care.

I got the latest version of Samba to compile, finally got it using Kerberos 5 without pitching a fucking fit, and while it still won't join AD properly, falling back to RPC, it'll at least use NTLMv2 to pass credentials now. The moderator at the samba-technical list apparently didn't feel that my submission for help in getting it to stop spitting out krb5 errors when it tried was justified, so I didn't get any. In fact, my missive never even showed up on the list. Fuck you too.

I figured, fuck it, I'll just use it as is, it's good enough for now, but I need to do one last recompile because CUPS and Impressario conflict, and since I have an Impressario license, and it doesn't suck a diseased goat like CUPS, guess who gets to stay? So I recompile Samba one last time, this time without CUPS for two reasons: a) it won't run without a constant stream of errors about not being able to talk to the cups daemon on localhost (no shit, I'm not running it, and I explicitly told you in your goddamned config file to use sysv printing, so why are you even fucking trying you self important piece of bloated shit?) and b) because it won't start without CUPS being installed because it was linked against the shared object libraries that are no longer there. New compilation using the exact same compilers, options, prerequisites, etc. The only difference is that it no longer finds and compiles the bits for CUPS support, and doesn't link against those shared objects.

I have a question for you software types, because I REALLY fucking want to know, and I'm pretty sure I already know the answer, but enlighten me anyway:

What kind of insane, crack addled, no talent, braindead idiot ties FILE LOCKING to an optional printing subsystem?

Mar 21 13:16:46 4A:dragon unix: WARNING: oplock 0xa80000004cf30d80: timed out
...
Mar 21 13:17:16 3D:dragon smbd[12694]: [2006/03/21 13:17:16, 0] smbd/oplock.c:(375)
Mar 21 13:17:16 3D:dragon smbd[12694]: Oplock break failed for file Outlook Folders/Space Breakfast.pst -- replying anyway


These are new, and they lead to file corruption like you wouldn't believe, and I'd bet a whole fuckload of money that if I reinstall CUPS, thereby breaking printing that works right now, and recompile Samba, again, in the exact same way, these will go away. Of course, I'll have syslog so over loaded with smbd CUPS errors again that if anything important ever happens I'll never see it, but why would I want to? In the mean time, I can either have my SGIs print, or I can have the users capable of moving data transparently between their Windows desktops, and the Unix machines they do analysis on. But not both.

Fuck you, I don't need this shit. I'm going to start attending conferences that the people who write this crap present at, just so I can throw feces at them. If they're going to code like monkeys, then I fully intend to treat them as such.