I'm not very knowledgable on *nix security, so please help me out here. Why could you not simply do this trick to any program? IE: make a fake libc.so that erases all the files on the hard drive on a call to fopen(), and then run a program that has suid root?
root or setuid root generally ignores LD_PRELOAD as a rule on most unixen. Made it hell for Sun on their initial rollout of Sunrays, which used an LD_PRELOAD hack on yes, libc.
The Windows NT security model is far, FAR superior to anything Unix has. The design of the thing is fabulous. The problem is, it's hardly ever used, it's been made practically or totally impossible to use by an admin by using the interface, and of course, there's the bugs, bugs, bugs...
Couldn't something like IMAX restore the cinema's advantage over television? Even the real early adopters don't have an IMAX screen in their living room. A pity that more films aren't made in a suitable large-screen format.
If you think Hollywood is bad... The president of IMAX recently came out criticizing a "scary" 3D haunted-house IMAX fim, saying that it went against the family-oriented fare that IMAX wanted to promote. This wasn't slasher flick stuff either, it was just especially gooey looking "ooga booga" ghosts and monsters and such. Long as this company controls the distribution to the theaters using this format, you will see nothing on IMAX but their standardized 40 minutes of pablum consisting largely of roller coaster style first person views and helicopter shots. Add to this the fact that IMAX theaters by their nature can't have the same amount of seating (the seats have to be steeply raked), and let's say I wouldn't put bets on them displacing the megaplex.
Start by reading every book you can get your hands on about designing user interfaces for the common user.
Then burn them. In a big roaring bonfire. Okay, don't -- donate them somewhere, but pretend you burned them. Picture 'em burning in your mind.
You are not designing an interface for the common person. Those are designed to be immediately accessable, with a slow gradual learning curve, with lots of consistent easy to grasp metaphor. That is the mac, and usually they do pretty well at it. Metaphors and graduality will drive your power users insane, and you're designing an app for them.
You want something more like emacs. Or, if you're doing CAD, you want something more like AutoCAD. You want an interface with power. You want one with usability. You want consistency, you still want to keep things like Fitt's Law in mind, but by no means should you feel compelled to make the damn thing intuitive. Neither vi nor emacs are in the least bit intuitive, but boy are they usable, meaning the interface really squeezes maximum use out of itself.
If I did have to throw in one piece of pithy advice, I'd say that since you're probably going to have to implement some sort of language to express the actions of the interface in, make the API self-documenting, like emacs. I can't tell you how amazingly useful the apropos command is in emacs, how it just searches through the names and documentation of every function and every var in the system, and I don't have to rely on compiled API documentation that may or may not tell me what I need.
Konqueror's integration is completely different from IE's integration. IE isn't just integrated into the desktop, but is wired deep into the bowels of the OS, using interfaces not available for other apps.
Funny thing, is that Duct tape is almost completely worthless on heating ducts
Yep. The stuff was originally called -- or nicknamed anyway -- "Duck Tape", not "Duct Tape", owing to its waterproof properties. It was made for the army, to seal ammunition cases. The military still uses awesome quantities of the stuff for just about everything to this day.
They gave up on the client end and created cvsup for distribution instead (which was meant to replace sup, but turns out to beat cvs in terms of reliability). Many private branches use Perforce
> To me, the real question is: what is going wrong with Linux kernel development that CVS is not sufficient?
Why don't you ask Linus? He's tired of answering, but now and then, he will give you a *big* rant on what he hates about CVS. Let's start with the fact that you can't even rename a file in CVS without losing its history. Or the fact that you can't make one changeset (in CVS terms, a tag) depend on another. Or that you can't even back out individual changesets -- history in CVS is entirely linear when going backward. The reason this worked for Linux before was because Linus did it all by hand, and now he's tired of it.
ad nauseum. Not chapter titles, not section titles, the literal words chapter and section. Multiply this by hundreds of sections.
How. Completely. Useless.
Until I can find an XML editor with some bloody sense to its structure navigator, I would rather use word. And no, I don't really want to use a WYSIWYG editor, because I want to know what XML it generates for my custom xslt snippets (which I might add I also have similar problems navigating with these brain dead editors)
> In your opinion, what are the main strengths of Access? I don't know all that much about its extended capabilities.
It's integrated. You design a schema, do data entry, define queries, run ad hoc queries, design forms and reports, all in one place. It can now use SQL Server as a native backend -- a real database -- or continue using ODBC to other databases, with basic functionality. From the perspective of a DBA, it's still a steaming pile of excrement. Using the SQL server backend makes it a passable front end to a sql server db, but it's definitely not something you'd do heavy lifting with. But as far as desktop data solutions go, it's surpassed only by Filemaker.
I personally use it to edit stored procedures on a SQL server db. The syntax hilighting of the SQL editor is pretty nice.
"All geeks like open-source. If you are against open-source, then you aren't a geek."
Actually that's perfectly valid (assuming that to be "against" something is not to like it). It's just not necessarily sound because the first premise is in doubt.
Valid means all the logic connects together. Sound means making a formally valid argument with true premises.
Circular reasoning is the act of restating of one of the premises as the conclusion. It's invalid because it simply makes the point of the argument one of your items of proof.
The problem with FOX and FLTK is that they don't use native widgets, whereas wxWindows has wxWin, wxMotif, wxMac, wxGTK, and wxUniversal (the last renders its own widgets).
FOX certainly looks a lot like windows... which isn't so hot when you run it on Linux.
FLTK looks like it combined the colors of CDE with the polish and smoothness of Windows 3.1. Hard to beat it for size though...
Furthermore, the self-proclaimed "embedded" windowing systems for handhelds often do worse than X11. X servers running on the Agenda or Zaurus take 1.3Mbytes of memory. This is a fraction of what, for example, Qt/Embedded takes.
That's an X server with no toolkit. Doing everything in raw xlib, are you?
> Their main public relations problem seems to be the use of an adult language, C++.
It may be in C++, but there's all sorts of bindings for different languages, including perl, python, ruby, and lua. I'm really in love with wxPython myself, though the introductory material and documentation is really poor, deferring entirely to the C++ version for the API docs. Right now I'm trying to figure out how to unbind an event in wxPython, and have to go straight to the C++ docs for it and hope the concepts translate. I'd really love it that situation were improved.
As for the matter of overcharging (not in regard to the parent post, so much as those above), define "overcharge".
Companies do not conspire to fix prices in order to keep them artificially low now, do they? Even Ayn Rand considered such anticompetitive behavior to be outright villany.
Grim Fandango, Black and White, Neverwinter Nights, Quake 3, the list goes on. There was never a golden age. You are simply forgetting the long list of games that sucked, then as now.
Not that I'm saying that DeleteFile is fast or anything, but mke2fs doesn't take as long as rm -rf /... One just wipes out the superblocks and lays new ones down, the other iterates through every file and makes several system calls for each.
I'd imagine NTFS makes managing windows partitions from linux a whole lot harder...
Look, buddy -- I use P2P clients because I'm too damn cheap to buy a $15 dollar CD. What makes you think I'm going to spend hundreds on virtual pc or vmware?
Well, you can always warez vmware from those same P2P networks... I really draw a hard line there -- vmware inc doesn't engage in price-fixing, deception, bribery of legislators, or otherwise declare war on its own customers.
Isn't vmware for linux only around a hundred bucks?
Why do you think the IBM PC exploded at home, when it SUCKED at Games/Graphics/Sound up until the mid-late 90s??
Because the market was radically different then, and the games basically sucked, appealing only to the same intellectual professionals who bought them in the first place. PC's are largely bought as entertainment devices these days, a fact that you ignore at your peril.
Be sure to include OggDS so they can play their.ogg files in Windows Media Player (yes I know "everwicked.com" looks bad, google for oggds if you don't believe the link)
I can see that you might not care about exposing people to the CLI toolchain, but... X runs under cygwin, and there's a growing library of X app ports on cygwin -- including KDE.
Even in CLI land, there's some CLI tools that power users will love, like wget. If you have room on the CD, I suggest a "power users" section, that includes cygwin. Here's a suggestion:
(I call it 'suck', perhaps you want a more genteel name). These are just standard options to wget that I use to suck down a site from the command line. It's trivial enough to integrate this with some sort of clipboard monitor, and you have a web site downloader that unlike most of their brethren for windows, actually *works*.
The clincher for including cygwin is: you want to distribute an open source CD. How about a compiler to make that source actually useful? gcc perhaps? Welcome to cygwin (or mingw if you use -mno-cygwin)
craigslist.org for bay area
on
Honest Job Sites?
·
· Score: 3, Interesting
not that i've gotten a job from anything i've sent through craigslist, but the postings there seem rather more like actual existing job openings than the "let's send out our weekly advertisement on hotjobs" listings.
Your newspaper's classifieds are indicative of the market. Don't see any tech jobs in there? Then there probably aren't any -- at least none they're considering unsolicited candidates for. Start looking at temping and be prepared to take some truly crappy and short-term jobs in that field...
Got modded down as flamebait. I got karma to burn. So here it is again. Extending my middle finger to fuckwit moderators everywhere:
Every couple of years, Microsoft completely changes their computing paradigms to ape what they perceive is a threat from some other company, and when the threat is gone, they just drop the initiative and move on to the next thing.
Who the fuck mods this blather up as insightful?
I can still run 16 bit DOS programs on windows. I can still use DDE for IPC. COM and COM+ haven't gone away with.NET. The Win32 API seems to have grown quite a few "Ex" appendages to API calls, but it hasn't changed since Win32s -- a forward compatibility hack for Win16 that still works even now. Why don't you present just some trivial little shred of evidence that you have any idea what you're talking about? -- Obviously it is Allah's will that I throw the unix box out the window. I submit to the will of Allah.
Slashdot Mirror
I'm not very knowledgable on *nix security, so please help me out here. Why could you not simply do this trick to any program? IE: make a fake libc.so that erases all the files on the hard drive on a call to fopen(), and then run a program that has suid root?
root or setuid root generally ignores LD_PRELOAD as a rule on most unixen. Made it hell for Sun on their initial rollout of Sunrays, which used an LD_PRELOAD hack on yes, libc.
The Windows NT security model is far, FAR superior to anything Unix has. The design of the thing is fabulous. The problem is, it's hardly ever used, it's been made practically or totally impossible to use by an admin by using the interface, and of course, there's the bugs, bugs, bugs...
Couldn't something like IMAX restore the cinema's advantage over television? Even the real early adopters don't have an IMAX screen in their living room. A pity that more films aren't made in a suitable large-screen format.
... The president of IMAX recently came out criticizing a "scary" 3D haunted-house IMAX fim, saying that it went against the family-oriented fare that IMAX wanted to promote. This wasn't slasher flick stuff either, it was just especially gooey looking "ooga booga" ghosts and monsters and such. Long as this company controls the distribution to the theaters using this format, you will see nothing on IMAX but their standardized 40 minutes of pablum consisting largely of roller coaster style first person views and helicopter shots. Add to this the fact that IMAX theaters by their nature can't have the same amount of seating (the seats have to be steeply raked), and let's say I wouldn't put bets on them displacing the megaplex.
If you think Hollywood is bad
Start by reading every book you can get your hands on about designing user interfaces for the common user.
Then burn them. In a big roaring bonfire. Okay, don't -- donate them somewhere, but pretend you burned them. Picture 'em burning in your mind.
You are not designing an interface for the common person. Those are designed to be immediately accessable, with a slow gradual learning curve, with lots of consistent easy to grasp metaphor. That is the mac, and usually they do pretty well at it. Metaphors and graduality will drive your power users insane, and you're designing an app for them.
You want something more like emacs. Or, if you're doing CAD, you want something more like AutoCAD. You want an interface with power. You want one with usability. You want consistency, you still want to keep things like Fitt's Law in mind, but by no means should you feel compelled to make the damn thing intuitive. Neither vi nor emacs are in the least bit intuitive, but boy are they usable, meaning the interface really squeezes maximum use out of itself.
If I did have to throw in one piece of pithy advice, I'd say that since you're probably going to have to implement some sort of language to express the actions of the interface in, make the API self-documenting, like emacs. I can't tell you how amazingly useful the apropos command is in emacs, how it just searches through the names and documentation of every function and every var in the system, and I don't have to rely on compiled API documentation that may or may not tell me what I need.
Konqueror's integration is completely different from IE's integration. IE isn't just integrated into the desktop, but is wired deep into the bowels of the OS, using interfaces not available for other apps.
Name just one such interface.
Funny thing, is that Duct tape is almost completely worthless on heating ducts
Yep. The stuff was originally called -- or nicknamed anyway -- "Duck Tape", not "Duct Tape", owing to its waterproof properties. It was made for the army, to seal ammunition cases. The military still uses awesome quantities of the stuff for just about everything to this day.
> GNU Hurd is being developed with CVS.
It's being developed?
> BSD is.
They gave up on the client end and created cvsup for distribution instead (which was meant to replace sup, but turns out to beat cvs in terms of reliability). Many private branches use Perforce
> To me, the real question is: what is going wrong with Linux kernel development that CVS is not sufficient?
Why don't you ask Linus? He's tired of answering, but now and then, he will give you a *big* rant on what he hates about CVS. Let's start with the fact that you can't even rename a file in CVS without losing its history. Or the fact that you can't make one changeset (in CVS terms, a tag) depend on another. Or that you can't even back out individual changesets -- history in CVS is entirely linear when going backward. The reason this worked for Linux before was because Linus did it all by hand, and now he's tired of it.
But seriously, don't take it from me, ask Linus.
> Did you mean, a "Brave GNU World"? I'm sorry Mr. Huxley, but it's just so appropriate.
GNU's monthly e-zine is, in fact, named Brave GNU World
But the structure navigator in every single bloody XML editor I have ever tried, free or commercial, tends to look like this:
book
|
+--chapter
+--chapter
| |
| +--section
| +--section
|
|--chapter
ad nauseum. Not chapter titles, not section titles, the literal words chapter and section. Multiply this by hundreds of sections.
How. Completely. Useless.
Until I can find an XML editor with some bloody sense to its structure navigator, I would rather use word. And no, I don't really want to use a WYSIWYG editor, because I want to know what XML it generates for my custom xslt snippets (which I might add I also have similar problems navigating with these brain dead editors)
> In your opinion, what are the main strengths of Access? I don't know all that much about its extended capabilities.
It's integrated. You design a schema, do data entry, define queries, run ad hoc queries, design forms and reports, all in one place. It can now use SQL Server as a native backend -- a real database -- or continue using ODBC to other databases, with basic functionality. From the perspective of a DBA, it's still a steaming pile of excrement. Using the SQL server backend makes it a passable front end to a sql server db, but it's definitely not something you'd do heavy lifting with. But as far as desktop data solutions go, it's surpassed only by Filemaker.
I personally use it to edit stored procedures on a SQL server db. The syntax hilighting of the SQL editor is pretty nice.
"All geeks like open-source. If you are against open-source, then you aren't a geek."
Actually that's perfectly valid (assuming that to be "against" something is not to like it). It's just not necessarily sound because the first premise is in doubt.
Valid means all the logic connects together. Sound means making a formally valid argument with true premises.
Circular reasoning is the act of restating of one of the premises as the conclusion. It's invalid because it simply makes the point of the argument one of your items of proof.
(the preceding was circular reasoning)
The problem with FOX and FLTK is that they don't use native widgets, whereas wxWindows has wxWin, wxMotif, wxMac, wxGTK, and wxUniversal (the last renders its own widgets).
... which isn't so hot when you run it on Linux.
FOX certainly looks a lot like windows
FLTK looks like it combined the colors of CDE with the polish and smoothness of Windows 3.1. Hard to beat it for size though...
Furthermore, the self-proclaimed "embedded" windowing systems for handhelds often do worse than X11. X servers running on the Agenda or Zaurus take 1.3Mbytes of memory. This is a fraction of what, for example, Qt/Embedded takes.
That's an X server with no toolkit. Doing everything in raw xlib, are you?
> Their main public relations problem seems to be the use of an adult language, C++.
It may be in C++, but there's all sorts of bindings for different languages, including perl, python, ruby, and lua. I'm really in love with wxPython myself, though the introductory material and documentation is really poor, deferring entirely to the C++ version for the API docs. Right now I'm trying to figure out how to unbind an event in wxPython, and have to go straight to the C++ docs for it and hope the concepts translate. I'd really love it that situation were improved.
As for the matter of overcharging (not in regard to the parent post, so much as those above), define "overcharge".
Companies do not conspire to fix prices in order to keep them artificially low now, do they? Even Ayn Rand considered such anticompetitive behavior to be outright villany.
I don't give a damn
Full stop, that sums it up pretty well. If you really don't give a damn, don't whine when big corps and governments choose Windows.
MS doesn't have a problem with the BSD license, because it allows for incorporation into proprietary applications, like the TCPIP code in Windows.
Doesn't matter how many times you repeat it, it doesn't make it true. The only BSD code in MS's TCP/IP stack is the header file.
Grim Fandango, Black and White, Neverwinter Nights, Quake 3, the list goes on. There was never a golden age. You are simply forgetting the long list of games that sucked, then as now.
Not that I'm saying that DeleteFile is fast or anything, but mke2fs doesn't take as long as rm -rf / ... One just wipes out the superblocks and lays new ones down, the other iterates through every file and makes several system calls for each.
I'd imagine NTFS makes managing windows partitions from linux a whole lot harder...
Look, buddy -- I use P2P clients because I'm too damn cheap to buy a $15 dollar CD. What makes you think I'm going to spend hundreds on virtual pc or vmware?
Well, you can always warez vmware from those same P2P networks... I really draw a hard line there -- vmware inc doesn't engage in price-fixing, deception, bribery of legislators, or otherwise declare war on its own customers.
Isn't vmware for linux only around a hundred bucks?
Why do you think the IBM PC exploded at home, when it SUCKED at Games/Graphics/Sound up until the mid-late 90s??
Because the market was radically different then, and the games basically sucked, appealing only to the same intellectual professionals who bought them in the first place. PC's are largely bought as entertainment devices these days, a fact that you ignore at your peril.
Be sure to include OggDS so they can play their .ogg files in Windows Media Player (yes I know "everwicked.com" looks bad, google for oggds if you don't believe the link)
I can see that you might not care about exposing people to the CLI toolchain, but ... X runs under cygwin, and there's a growing library of X app ports on cygwin -- including KDE.
/winOSS/powertools/suck
Even in CLI land, there's some CLI tools that power users will love, like wget. If you have room on the CD, I suggest a "power users" section, that includes cygwin. Here's a suggestion:
cat >>
#!/bin/sh
wget --continue --timestamping --recursive --level=inf --convert-links --dont-remove-listing --no-parent $*
^D
(I call it 'suck', perhaps you want a more genteel name). These are just standard options to wget that I use to suck down a site from the command line. It's trivial enough to integrate this with some sort of clipboard monitor, and you have a web site downloader that unlike most of their brethren for windows, actually *works*.
The clincher for including cygwin is: you want to distribute an open source CD. How about a compiler to make that source actually useful? gcc perhaps? Welcome to cygwin (or mingw if you use -mno-cygwin)
not that i've gotten a job from anything i've sent through craigslist, but the postings there seem rather more like actual existing job openings than the "let's send out our weekly advertisement on hotjobs" listings.
Your newspaper's classifieds are indicative of the market. Don't see any tech jobs in there? Then there probably aren't any -- at least none they're considering unsolicited candidates for. Start looking at temping and be prepared to take some truly crappy and short-term jobs in that field...
Got modded down as flamebait. I got karma to burn. So here it is again. Extending my middle finger to fuckwit moderators everywhere:
.NET. The Win32 API seems to have grown quite a few "Ex" appendages to API calls, but it hasn't changed since Win32s -- a forward compatibility hack for Win16 that still works even now. Why don't you present just some trivial little shred of evidence that you have any idea what you're talking about?
Every couple of years, Microsoft completely changes their computing paradigms to ape what they perceive is a threat from some other company, and when the threat is gone, they just drop the initiative and move on to the next thing.
Who the fuck mods this blather up as insightful?
I can still run 16 bit DOS programs on windows. I can still use DDE for IPC. COM and COM+ haven't gone away with
--
Obviously it is Allah's will that I throw the unix box out the window. I submit to the will of Allah.
Where the hell is Taco when you really need him?