Y, because history shows that complex systems composed of single-purpose, modular, and user-interchangeable/serviceable components are never desirable relative to opaque, monolithic, keep-your-hands-out-of-it-we're-the-experts systems.
Amazing...still doesn't get it after all of these years. What an ego.
I've been looking for a CRM solution for my company, Venn Technologies, Inc.. IMO, the best Open Source CRM out there right now is SugarCRM. I covers the basics at least. It doesn't have hooks for issue tracking and billing just yet but they are working on that. Currently, I'm evaluating SQL-Ledger and GNUCash for tracking the financials.
I ordered a small FM transmitter from Ramsey a
while back. It was good for some weekend playtime
and I still use it for broadcasting my MP3/OGG
connection around the yard. The instructions were
very paint-by-the-numbers though. The instruction
booklet had some decent information about RF basics
and FCC rules, but not much as far as basic
electronics. Can't say I really learned much from
the whole experience.
I remember one project that my father and I did
back when I was about 10. Crystal radio. I can't
say how your kids would react, but I was
amazed that you could pick up radio stations
without having to plug the bugger in. Crystal
radio has decent 'wow-factor'.
I would recommend starting with a crystal radio
kit and some basic electronics and RF and work
your way up to something a little more practical
like the Ramsey kits.
Do the base install on one machine. tar all of
the installed partitions and dump them onto an
NFS mount. Run "dpkg --get-selections > packages".
Copy packages file to NFS mounts. Get a boot
floppy that supports NFS(tomsrbt?). On each
yet-to-be-installed machine, partition disk and
untar the partitions dumps that live on the NFS
mount onto the local drive. Run lilo on newly
cloned machine. reboot. Run
"dpkg --get-selections
Most of that can be scripted in sh. I just wrote
it out so that the process is clear. It's really
easy to clone Debian machines quickly.
rip it apart and tinker with it at my discretion. I think that's my right as a consumer.
I saw a sig here on/. to the effect of "consumers
have wallets; citizens have rights." Too many
people use "consumer" where they should be using
something like "citizen". It plays right into the
mentality of people like the MPAA, RIAA, and IP
sharks/lawyers. It's subtle, but it's one of the
little things that got us to the place where this
stupid barcode thing is even an issue.
Yes, reboot. Not because the system needs it but because I like to know what is going to be running after an unattended reboot. Just in case the power goes out when I am on vacation I will still have piece of mind that I know *exaclty* what will be running because I sat there and *WATCHED* the boot messages the last time.
Yes, you could go so single user, but it's still not the same level of comfort because there are some things that can still be slightly different than after a reboot.
...but this article is very unfair to the major non-commercial distros. I can't say what Slackware's security is like since I don't use it, but Debian really gets the shaft... and undeservedly so. Kurt seems to go on the notion that any distro which ships software that hasn't been reved in 6 months or more is insecure. So in his eyes, Debian is not secure due to the long release cycles. I find that to be quite the opposite. Special apt-get security mirrors, security mailing lists, and patches that are usually available a couple of days after an exploit is announced....Debian does pretty well IMHO.
And it doesn't hurt that they don't ship with sendmail as their default MTA.;)
I've offered to write an article for securityportal on how to secure a Debian box from remote exploit, but I've not heard back from Kurt yet. I suppose he isn't in control of article submissions tho. They'll be suprised to see that the article is pretty much:
edit a couple of config files and reboot. Of course, local exploits are a whole nother story. That's true of most Unices tho...except for OBSD.
Anyway, anyone who hasn't used Debian...don't let this article turn you off to it. I don't think Kurt has really used Debian very much. I don't see how he could disregard it like that if he had. Disappointing from someone who writes the LASG.
>mind you the anti-MS block on >Slashdot will of course equate >Microsoft's involvement with the project to >mean that this is really about mind >control or the corporately financed return >of the plague, but what are ya gonna >do?
Poo poo. Hey! If you don't like the anti-MS slant around these parts then go post to some other web log. Damn, MS shills.
So does anybody know who this CmdrTaco fella is? We need to figure it out and break his virtual knees./. just isn't the same since all of those Windows-wienies started showing up around here.
>How is it that it is okay to inject totally >non-related riders into bills in this fashion? >Shouldn't > this kind of behavior be disallowed? > >Go ahead and try to draft a definition of >"substantionally related" that you can use to >restrict > which riders can be attached to which >bills. I dare you. And oh yeah, try to find a >constitutional > basis for striking down such riders by >the Supreme Court, which after all can only exert > judicial review over matters >concerning the constitution.
I agree that judging them by topic probably wouldn't work. But here is an easy solution: only the original authors of the bill can append additional riders. That would allow the original authors to make changes in order to get the bill passed without letting some jackass insert unrelated riders.
How is it that it is okay to inject totally non-related riders into bills in this fashion? Shouldn't this kind of behavior be disallowed? What about cross-referencing these riders? It must be a nightmare keeping track of what rider was in what totally unrelated bill. It's the governmental equivalent of spaghetti code. Someone please explain why our legistlative bodies haven't put a stop to this kind of thing?
Even tho they have been pretty succesfull petitioners in meat-space, there was some talk on the KY Greens list of doing this kind of thing to collect signatures for the petitions to put Ralph Nader on the presedential ballots. It was a little late in the game this time around, but maybe next election. So, yes, even tho they will probably be heavily abused given the non-technical lein of most people out there, there are some positive things one can do with dig. sigs.
FWIW, there is an elisp package that works pretty much the same way as IntelliSense except that the info shows up in the um....what is it called...the little area at the bottom in emacs. I had it working at one time but never really used it so I don't remember what it's called now. I'm sure you could find reference to it on Deja tho.
>BFD. They will know absolutely nothing, then, >about running all the other applications on that >box.
Who cares? I'm not talking about all of the *other* applications. I'm talking about a maximized SO on a machine that is used for email/www/office type work only. SO has the email and office covered and Netscape looks similar enough on every platform that that is pretty much covered as well. Essentially, re-learning/re-training time to jump to another platform is zilch. Hell, they even have an integrated file manager.
But then again, I'm not saying I prefer the WiW that SO uses. Just that I can see why they have chosen to go that route given the target audience.
Have you ever compared the X and Windows versions of StarOffice? They look pretty much identical. The buttons, scrollbars, menus, etc. I mean.
Most of the people who will use SO( assuming that it starts to get some share of the users at all ) will be the kind of people who could care less what OS/Windowing system they are running. They are office workers, home users, etc. A user who learns to operate SO on a Mac will *instantly* know what to expect when they sit down in front of a Windows, Linux, BSD, Solaris box running SO because the fullscreen WiW hides the underlying OS and windowing system completely. An initial learning curve and then no loss when moving to another platform. In some sense the WiW is good for people who would like to get Linux or some other alternative OS out of the server room and onto desktops. If the person who uses that desktop is a heavy office suite user, they probably wouldn't even know the difference.
That's not to say that I like the WiW. It's annoying to *nix-ites who are used to multiple desktops and terms spattered everywhere. I can just understand why they use WiW. It's there attempt to appease what they think will be the largest chunk of users.
Hey, how about that? Not only did he mention the fact that Linux is only a kernel and not the OS, but he actually mentioned a competing distro. Given, it wasn't a *commercial* distro but still pretty cool, IMHO.
The system that we have at Uni. is such that you may have root on the machine you are sitting at but you won't have the same priviliges on an NFS mounted filesystem. grep the NFS docs for the phrase "export root".
Slashdot Mirror
Keep reading that man page. That only comes into play if you are shredding a mount point/filesystem. Just shred the device file and you are golden.
Y, because history shows that complex systems composed of single-purpose, modular, and user-interchangeable/serviceable components are never desirable relative to opaque, monolithic, keep-your-hands-out-of-it-we're-the-experts systems.
Amazing...still doesn't get it after all of these years. What an ego.
I've been looking for a CRM solution for my company, Venn Technologies, Inc.. IMO, the best Open Source CRM out there right now is SugarCRM. I covers the basics at least. It doesn't have hooks for issue tracking and billing just yet but they are working on that. Currently, I'm evaluating SQL-Ledger and GNUCash for tracking the financials.
Thank you. That is so annoying but I have been :)
too lazy to try to figure out what was causing
it.
I ordered a small FM transmitter from Ramsey a
while back. It was good for some weekend playtime
and I still use it for broadcasting my MP3/OGG
connection around the yard. The instructions were
very paint-by-the-numbers though. The instruction
booklet had some decent information about RF basics
and FCC rules, but not much as far as basic
electronics. Can't say I really learned much from
the whole experience.
I remember one project that my father and I did
back when I was about 10. Crystal radio. I can't
say how your kids would react, but I was
amazed that you could pick up radio stations
without having to plug the bugger in. Crystal
radio has decent 'wow-factor'.
I would recommend starting with a crystal radio
kit and some basic electronics and RF and work
your way up to something a little more practical
like the Ramsey kits.
JMTC.
Can you tell me where/how you found out about the
additional rules for online broadcasters? It could be
relevant for a project I am working on.
http://kernelnewbies.org/~phillips/
Do the base install on one machine. tar all of
the installed partitions and dump them onto an
NFS mount. Run "dpkg --get-selections > packages".
Copy packages file to NFS mounts. Get a boot
floppy that supports NFS(tomsrbt?). On each
yet-to-be-installed machine, partition disk and
untar the partitions dumps that live on the NFS
mount onto the local drive. Run lilo on newly
cloned machine. reboot. Run
"dpkg --get-selections
Most of that can be scripted in sh. I just wrote
it out so that the process is clear. It's really
easy to clone Debian machines quickly.
rip it apart and tinker with it at my discretion. I think that's my right as a consumer.
/. to the effect of "consumers
have wallets; citizens have rights." Too many
people use "consumer" where they should be using
something like "citizen". It plays right into the
mentality of people like the MPAA, RIAA, and IP
sharks/lawyers. It's subtle, but it's one of the
little things that got us to the place where this
stupid barcode thing is even an issue.
I saw a sig here on
This is a really easy hack so perhaps you've
....
already seen it:
if( 4 = i )
will not compile but has the same semantics as
what you have. Get in the habit of putting making
the LHS something non-assignable.
>edit a couple of config files and reboot. Of
Yes, reboot. Not because the system needs it
but because I like to know what is going to be
running after an unattended reboot. Just in case
the power goes out when I am on vacation I will
still have piece of mind that I know *exaclty*
what will be running because I sat there and
*WATCHED* the boot messages the last time.
Yes, you could go so single user, but it's still
not the same level of comfort because there are
some things that can still be slightly different
than after a reboot.
...but this article is very unfair to the
;)
major non-commercial distros. I can't say
what Slackware's security is like since I don't
use it, but Debian really gets the shaft...
and undeservedly so. Kurt seems to go on the
notion that any distro which ships software that
hasn't been reved in 6 months or more is
insecure. So in his eyes, Debian is not secure
due to the long release cycles. I find that
to be quite the opposite. Special apt-get
security mirrors, security mailing lists, and
patches that are usually available a couple of
days after an exploit is announced....Debian
does pretty well IMHO.
And it doesn't hurt that they don't ship with
sendmail as their default MTA.
I've offered to write an article for
securityportal on how to secure a Debian box from
remote exploit, but I've not heard back from
Kurt yet. I suppose he isn't in control of article
submissions tho. They'll be suprised to see that
the article is pretty much:
apt-get remove rsh
apt-get install ssh
apt-get install portsentry
apt-get install aide
apt-get remove telnetd
apt-get remove ftpd
edit a couple of config files and reboot. Of
course, local exploits are a whole nother story.
That's true of most Unices tho...except for OBSD.
Anyway, anyone who hasn't used Debian...don't
let this article turn you off to it. I don't
think Kurt has really used Debian very much.
I don't see how he could disregard it like that
if he had. Disappointing from someone who writes
the LASG.
IMHO, of course.
Wow, this is so cool. Anybody have any
screenshots?
;)
>mind you the anti-MS block on
/. just isn't the same since all of those
>Slashdot will of course equate
>Microsoft's involvement with the project to
>mean that this is really about mind
>control or the corporately financed return
>of the plague, but what are ya gonna
>do?
Poo poo. Hey! If you don't like the anti-MS slant
around these parts then go post to some other
web log. Damn, MS shills.
So does anybody know who this CmdrTaco fella is?
We need to figure it out and break his virtual
knees.
Windows-wienies started showing up around here.
;)
>How is it that it is okay to inject totally >non-related riders into bills in this fashion? >Shouldn't
> this kind of behavior be disallowed?
>
>Go ahead and try to draft a definition of >"substantionally related" that you can use to >restrict
> which riders can be attached to which >bills. I dare you. And oh yeah, try to find a >constitutional
> basis for striking down such riders by >the Supreme Court, which after all can only exert
> judicial review over matters >concerning the constitution.
I agree that judging them by topic probably
wouldn't work. But here is an easy solution:
only the original authors of the bill can append
additional riders. That would allow the original
authors to make changes in order to get the
bill passed without letting some jackass insert
unrelated riders.
How is it that it is okay to inject totally
non-related riders into bills in this fashion?
Shouldn't this kind of behavior be disallowed?
What about cross-referencing these riders?
It must be a nightmare keeping track of
what rider was in what totally unrelated bill.
It's the governmental equivalent of spaghetti
code. Someone please explain why our legistlative
bodies haven't put a stop to this kind of thing?
Even tho they have been pretty succesfull
petitioners in meat-space, there was some talk
on the KY Greens list of doing this kind of thing
to collect signatures for the petitions to put
Ralph Nader on the presedential ballots. It was
a little late in the game this time around, but
maybe next election. So, yes, even tho they will
probably be heavily abused given the non-technical
lein of most people out there, there are some
positive things one can do with dig. sigs.
FWIW, there is an elisp package that works pretty
much the same way as IntelliSense except that
the info shows up in the um....what is it called...the little area at the bottom in emacs.
I had it working at one time but never really
used it so I don't remember what it's called now.
I'm sure you could find reference to it on Deja
tho.
>BFD. They will know absolutely nothing, then, >about running all the other applications on that >box.
Who cares? I'm not talking about all of the *other*
applications. I'm talking about a maximized SO
on a machine that is used for email/www/office type
work only. SO has the email and office covered and
Netscape looks similar enough on every platform
that that is pretty much covered as well. Essentially, re-learning/re-training time to jump
to another platform is zilch. Hell, they even
have an integrated file manager.
But then again, I'm not saying I prefer the WiW
that SO uses. Just that I can see why they have
chosen to go that route given the target audience.
Have you ever compared the X and Windows versions
of StarOffice? They look pretty much identical.
The buttons, scrollbars, menus, etc. I mean.
Most of the people who will use SO( assuming that
it starts to get some share of the users at all )
will be the kind of people who could care less
what OS/Windowing system they are running. They
are office workers, home users, etc. A user
who learns to operate SO on a Mac will *instantly*
know what to expect when they sit down in front
of a Windows, Linux, BSD, Solaris box running
SO because the fullscreen WiW hides the underlying
OS and windowing system completely. An initial
learning curve and then no loss when moving to
another platform. In some sense the WiW is good
for people who would like to get Linux or some
other alternative OS out of the server room and
onto desktops. If the person who uses that desktop
is a heavy office suite user, they probably
wouldn't even know the difference.
That's not to say that I like the WiW. It's
annoying to *nix-ites who are used to multiple
desktops and terms spattered everywhere. I can
just understand why they use WiW. It's there
attempt to appease what they think will be the
largest chunk of users.
IMHO.
Hey, how about that? Not only did he mention
the fact that Linux is only a kernel and not
the OS, but he actually mentioned a competing
distro. Given, it wasn't a *commercial* distro but
still pretty cool, IMHO.
Um, I would sell my left......
kidney for one!
Where can I send the check?
Ok, Dr. Dre. I'll pay up the money I "owe" *you* when you pay James Brown for all of those samples.
ATTN lawyers:
I don't actually listen to Dr. Dre...no CDs, no MP3's...so put that pen down and go chase an ambulance or something.
I'm sure he would be more than happy to answer
your question. Besides, nothing better than
getting your info directly from the FSF.
The system that we have at Uni. is such that you
may have root on the machine you are sitting at
but you won't have the same priviliges on an NFS
mounted filesystem. grep the NFS docs for the
phrase "export root".