I always hated the 'MyThis, MyThat' nonsense. Always seemed to be a very immature naming convention.
Now if only MySQL can follow a fine example and find a better name. Although I wonder if the 'My' has been the best marketing idea to promote a software
product. Feels so much nicer to know that it's MINE !
Thanks for your insightful post. I now have a
different way to look at the Canada/Quebec issue.
I am from Western Canada and have roots in Quebec. I'd much rather keep my country whole vs. hacked apart. It's much better to acknowledge and embrace cultural differences.
Actually, we decided here ( a fairly large
installation) long ago to merge / and/usr.
Our main reason was simplification and this allows us the benefit of not worrying what is in/usr/bin and what is in/bin. (Actually, on Solaris,/bin is just a link to/usr/bin ). Everything in/usr and
/ should not be touched anyhow except through the
normal pkg management tools. We do of course maintain a separate/usr/local.
The main disadvantage is that a fsck would take longer because / is now a large filesystems. With the journaled filesystems of today, we don't see the concern. The other benefit is that we don't
need to worry about sizing / and/usr independantly and running out of space in/usr
when / still has lots (or vise versa).
Interestingly enough,/usr/openwin used to be a separate FS on SunOS long ago. The main reasoning was that disks back
then were small and you simply didn't have room to
place/usr/openwin in the/usr/ filesystem.
I would guess that others have merged/usr and /
too but I understand why it's a bit of a
controversial topic.
I do hold disregard for some of the defaults that
some Linux distros use where/var and / are merged
as well. In fact, the whole darn OS is in/.
The need for a separate/var should never go away
IMO.
Agreed, nobody forced me to do anything. I'm a
strong supporter of RH and a shareholder and a user.
At work, I am rolling out RH 3.0 and I'm happy with it.
However, I do feel like many others that RH left a hole in their product line. They're supporting Fedora and that's cool. But as a home user of Linux
(windoze free since 1997;) ), upgrading to fedora
didn't make sense. I want a stable box at home, not
a development release. I get the impression that Fedora is bleeding edge in that way.
I kept hearing that Mandrake was doing some great
things with their distro.
I was more than willing to keep paying 60$/yr
for RH 9, 10, and whatever.
For business, RH is great. But they are quite
clear in their approach that they are not interested in the home desktop so Mandrake gets my
60$ now. I just hope RH isn't shooting themselves in the foot somehow.
I was a linux fan from quite a while back and I decided to try FreeBSD to see the differences.
I installed it without much difficulty and poked around. I liked what I saw. I sorta shrugged my shoulders and said "Looks like a Unix system to me"
and continued using Linux.
I was using Redhat for the longest time before RHAT
forced me into migrating (Mandrake if you must know). I never really saw a reason to switch from
this distro to that distro unless the features were significantly different.
I think it's all what you get used to and prefer. I never understood the BSD/Linux platform wars. To me, we're on the same open source team. As long as I can download the code, I don't see a big problem. If SCO got their wish and asked me for 699$, you can bet I'd be hopping straight over
to FreeBSD. All the software I need is there anyhow.
After all, LinuxDistros/BSD aren't so different when they share the same features (KDE, openoffice, etc...)
Re:Next game please!
on
Human Pac Man
·
· Score: 0, Redundant
For us, releasing a production redhat server for a mission critical app would be a very tough sell in our organization. Our Unix team doesn't need support generally, but then there have been times when we've found a bug and were quite happy to open a case with Redhat and ask them to figure it out.
It's not really about needing support or not IMO, but rather the opportunity to pass off an issue to someone in a better position to investigate.
My experience with Redhat support has been very positive so far. The 'one who answers the phone' actually knows Unix/Linux well enough to do some preliminary research before escalating to back-line support.
For us, we're used to paying for Sun service at a silver level and while this includes hardware, 799$US per year for Redhat support is a good deal in our opinion.
I like the idea of limiting the lifespan of a cache. I think this has the potential of keeping everyone happy. Defining a lifespan of a cache would be hard though. Where I live, ecological impacts are small anyway, so it would be somewhat pointless to cap it at 1 year.
A workmate and I were just discussing this. What he suggested is that perhaps you might limit based on # of visits. This would have a more direct relation to soil erosion. Let's face it, geocaching is not random wandering through the forest. I imagine that there are new trails being made where perhaps there shouldn't be.
I have one of the older caches in Canada. It has received over 40 visits (this is alot for this area). Perhaps 50 visits should be a cap ? Then I can move it to avoid the specific site from being trampled too heavily ?
Seriously though, 27k is a nice size for an app that did so much. If only openoffice could lean down their suite a bit so it loads in less than 45seconds on my AMD K7-650. (Not trying to troll)
I recall tuning my DOS system to have Lotus 123 load in less than a second. Good days
Seriously. It's fine to say 'we should', we see that alot on slashdot (phone your political rep. etc.). Let's do something. Pick your favourite vendor that doesn't support linux yet, call them on April 23rd.
I think we (slashdot readers) have more influence than we often think we do.
Redhat has stated publically they do not like Sun marketing Solarisx86 and they consider it a competitor. My guess is redhat is willing to do a port if Sun cancels solarisx86 and eventually moved to redhat linux for their sparc machines.
I wonder if this is in fact related to Redhat
dropping their sparc port at 7.x ? Never thought of it
like that before.
It is kinda frustrating, we were hoping for that option as well.
I discussed this with RedHat and they suggested that we might license 1 or 2 critical servers with annual support, and the rest could be just the flat-rate 800$.
i.e. if you have 5 servers and they are all configured the same way and do very similar tasks, you can open a case against the one with support as the issue is likely to be applicable to any of the hosts.
Redhat recommended this and I Sun tolerates it too. Most of my software support calls to sun are tied to the O/S, not the particular instance of it. i.e If SEAM under Solaris 8 is broken, it's broken on all hosts, not just one.
The 800$ is only for the product, If you want support, that is 1500US/year for a 'silver' contract.
The product placement for AS is for Enterprise applications i.e. Oracle. For those of us considering moving Oracle from Sun to Redhat, this is a sweet deal.
Your comments about Microsoft pricing are valid, and I believe RedHat thinks so too. The new offering of ES, is I think 800$/yr for support.
If the right tool for the job is efficient, let them name-call all they want.
As far as I've seen, HTTP for FTP type operations is still somewhat new. While FTP has it's firewall and security issues, It is still used a whole lot more than HTTP IMHO.
If this is your first FTP application and you are already running HTTP alot, you might consider just using HTTP. If you plan to do alot of FTP hosting, I would suggest cracking the FTP server books.
Slashdot Mirror
I always hated the 'MyThis, MyThat' nonsense. Always seemed to be a very immature naming convention.
Now if only MySQL can follow a fine example and find a better name. Although I wonder if the 'My' has been the best marketing idea to promote a software product. Feels so much nicer to know that it's MINE !
*end rant*
What stops me from doing my taxes online is the fear that they don't secure their systems well (like many) and my data will have leaked/stolen.
Call it irrational, but I keep hearing of this kind of data leak time and time again.
In Canada, I pay 30$ for Quicktax and it's worth the extra peace of mind.
Thanks for your insightful post. I now have a different way to look at the Canada/Quebec issue. I am from Western Canada and have roots in Quebec. I'd much rather keep my country whole vs. hacked apart. It's much better to acknowledge and embrace cultural differences.
The 20$ toaster may last longer and be made by
your local economy. Nothing against overseas products, but shopping is a political choice.
Buying the toaster at wallmart for 2$ less
saves you money today, but what does that say about your concern for the future.
Even the crappiest toaster may last a few years. Saving 2$ over that time period is pointless.
Save the penny pinching for T.P.
( or is it )
Perhaps someone can explain to me the slight or not-so-slight bias against the French in the US I keep hearing about
Is it just good natured ribbing. What's the source ?
If 'The patriot' is any accurate indication of US history, I would've expected quite the opposite.
And yes, I realize this is off-topic.
But that's OK, cuz 'redundant' was put in twice.
Actually, we decided here ( a fairly large installation) long ago to merge / and /usr.
Our main reason was simplification and this allows us the benefit of not worrying what is in /usr/bin and what is in /bin. (Actually, on Solaris, /bin is just a link to /usr/bin ). Everything in /usr and
/ should not be touched anyhow except through the
normal pkg management tools. We do of course maintain a separate /usr/local.
The main disadvantage is that a fsck would take longer because / is now a large filesystems. With the journaled filesystems of today, we don't see the concern. The other benefit is that we don't need to worry about sizing / and /usr independantly and running out of space in /usr
when / still has lots (or vise versa).
Interestingly enough, /usr/openwin used to be a separate FS on SunOS long ago. The main reasoning was that disks back
then were small and you simply didn't have room to
place /usr/openwin in the /usr/ filesystem.
I would guess that others have merged /usr and /
too but I understand why it's a bit of a
controversial topic.
I do hold disregard for some of the defaults that some Linux distros use where /var and / are merged
as well. In fact, the whole darn OS is in /.
The need for a separate /var should never go away
IMO.
... and see if they nearly always end up with the side you flicked face up.
Seems to work at least 7 times out of 10. Makes for a fun bet on the unsuspecting ;)
Agreed, nobody forced me to do anything. I'm a strong supporter of RH and a shareholder and a user. At work, I am rolling out RH 3.0 and I'm happy with it.
However, I do feel like many others that RH left a hole in their product line. They're supporting Fedora and that's cool. But as a home user of Linux (windoze free since 1997 ;) ), upgrading to fedora
didn't make sense. I want a stable box at home, not
a development release. I get the impression that Fedora is bleeding edge in that way.
I kept hearing that Mandrake was doing some great
things with their distro.
I was more than willing to keep paying 60$/yr for RH 9, 10, and whatever.
For business, RH is great. But they are quite clear in their approach that they are not interested in the home desktop so Mandrake gets my 60$ now. I just hope RH isn't shooting themselves in the foot somehow.
I was a linux fan from quite a while back and I decided to try FreeBSD to see the differences.
I installed it without much difficulty and poked around. I liked what I saw. I sorta shrugged my shoulders and said "Looks like a Unix system to me" and continued using Linux.
I was using Redhat for the longest time before RHAT forced me into migrating (Mandrake if you must know). I never really saw a reason to switch from this distro to that distro unless the features were significantly different.
I think it's all what you get used to and prefer. I never understood the BSD/Linux platform wars. To me, we're on the same open source team. As long as I can download the code, I don't see a big problem. If SCO got their wish and asked me for 699$, you can bet I'd be hopping straight over to FreeBSD. All the software I need is there anyhow.
After all, LinuxDistros/BSD aren't so different when they share the same features (KDE, openoffice, etc...)
Human doom ?
I thought that's what paintball was for.
For us, releasing a production redhat server for a
mission critical app would be a very tough sell in our organization. Our Unix team doesn't need support
generally, but then there have been times when we've
found a bug and were quite happy to open a case with
Redhat and ask them to figure it out.
It's not really about needing support or not IMO, but rather the opportunity to pass off an issue to someone in a better position to investigate.
My experience with Redhat support has been very
positive so far. The 'one who answers the phone'
actually knows Unix/Linux well enough to do some
preliminary research before escalating to back-line support.
For us, we're used to paying for Sun service at
a silver level and while this includes hardware, 799$US per year for Redhat support is a good
deal in our opinion.
HTH
Eeeeehhhhh.... What's up Doc ?!
I like the idea of limiting the lifespan of a cache. I think this has the potential of keeping everyone happy. Defining a lifespan of a cache would be hard though. Where I live, ecological impacts are small anyway, so it would be somewhat pointless to cap it at 1 year.
A workmate and I were just discussing this. What he suggested is that perhaps you might limit based on # of visits. This would have a more direct relation to soil erosion. Let's face it, geocaching is not random wandering through the forest. I imagine that there are new trails being
made where perhaps there shouldn't be.
I have one of the older caches in Canada. It has received over 40 visits (this is alot for this area). Perhaps 50 visits should be a cap ? Then I can move it to avoid the specific site from being
trampled too heavily ?
I heard that the latest in Firewire attached drives
were high capacity as well as portable. Sorry, no
link, me too lazy.
You mean it's not available on Linux yet ? WTF?
Seriously though, 27k is a nice size for an
app that did so much. If only openoffice could
lean down their suite a bit so it loads in less than
45seconds on my AMD K7-650. (Not trying to troll)
I recall tuning my DOS system to have Lotus 123
load in less than a second. Good days
OK,
How does April 23rd sound ?
Seriously. It's fine to say 'we should', we see
that alot on slashdot (phone your political rep. etc.). Let's do something. Pick your favourite
vendor that doesn't support linux yet, call them
on April 23rd.
I think we (slashdot readers) have more influence
than we often think we do.
Redhat has stated publically they do not like Sun marketing Solarisx86 and they consider it a competitor. My guess is redhat is willing to do a port if Sun cancels solarisx86 and eventually moved to redhat linux for their sparc machines.
I wonder if this is in fact related to Redhat dropping their sparc port at 7.x ? Never thought of it like that before.
It is kinda frustrating, we were hoping for that option as well.
I discussed this with RedHat and they suggested that we might license 1 or 2 critical servers with annual support, and the rest could be just the flat-rate 800$.
i.e. if you have 5 servers and they are all configured the same way and do very similar tasks, you can open a case against the one with support as the issue is likely to be applicable to any of the hosts.
Redhat recommended this and I Sun tolerates it too. Most of my software support calls to sun are tied to the O/S, not the particular instance of it. i.e If SEAM under Solaris 8 is broken, it's broken on all hosts, not just one.
HTH.
The 800$ is only for the product, If you want support, that is 1500US/year for a 'silver' contract.
;)
The product placement for AS is for Enterprise applications i.e. Oracle. For those of us considering moving Oracle from Sun to Redhat, this is a sweet deal.
Your comments about Microsoft pricing are valid, and I believe RedHat thinks so too. The new offering of ES, is I think 800$/yr for support.
And I don't work for RedHat.
Sorry, But....
Our shop has been evaluating the purchase of AS for some time now. It's been 1500US/yr and 2500US/yr
for a few months at least.
This latest offering is only adding ES and WS for
those who still need/want support but don't want the
full enterprise price.
If the right tool for the job is efficient, let
them name-call all they want.
As far as I've seen, HTTP for FTP type operations
is still somewhat new. While FTP has it's firewall and security issues, It is still used a whole lot
more than HTTP IMHO.
If this is your first FTP application and you are already running HTTP alot, you might consider just
using HTTP. If you plan to do alot of FTP hosting, I would suggest cracking the FTP server books.
HTH.
.... they can create another Stuart Little movie.
Stuart Little: Look who's talking too ?
Off-topic:
A tip for remembering Antarctica:
Ant- (anterior, ie. south pole)
-arctic- (it's fscking cold down there)
-a ( *shrug* sounds better).
Not intended to be sarcastic, just thought it'd be useful. Cheers.
... confluence.org.
It's a good effort at a pseudo-random sampling of the earth using GPS.
It's amazing how difficult it is to find civilization pecking away at links at this site.