What are your reasons for running the old standby suite over
the Firefox/Thunderbird combo?
Quite simply, it's a better browser. The killer feature for me is searching.
I hate the wasted real estate in Firefox from having a separate location
and search box, and ease of use is dramatically better in Mozilla than in
Firefox. In Mozilla, I just hit Ctrl-L, type my search commands, hit
up arrow and enter. I haven't found any way of achieving the same thing in
Firefox, and I hate the small size of the box I'm given to enter my search
terms.
For email, I don't use either. Until something else comes close to the power
of mh, I see no reason to change. But I also found out a major
failing in Thunderbird yesterday. My other third uses it, and it turns out
it can only get mail from a POP3 or IMAP server. It can't read from a local
mbox file. How braindead is that?
Subsequent republican groups never targeted individuals due to their religion- sectarian violence has always been the preserve of loyalist (protestant) terrorists.
Whereas the IRA are just completely indiscriminate,
and blow people up simply for being British?
That's obvioualy
so much better. Having been caught
by the blast (though fortunatly not injured) of
the Canary Wharf bomb, I can tell you it's not much
fun...
If X isn't selected at install time
(and it really shouldn't be on a server),
then RH doesn't add the rhgb parameter,
and defaults to a text only boot anyway.
Either way I'd expect to be able to disable it if I so choose (like I'm running a server) with a kernel arguement, recompile option, or boot loader preference change.
RH passes the rhgb kernel parameter, which
enables the "Red Hat Graphical Boot". Omit that,
and you'll get a regular text only boot.
You can also control it by changing the line:
GRAPHICAL=yes
in/etc/sysconfig/init (as well as
controlling how verbose the text boot is,
which can come in handy when you're trying to
debug a boot time fault).
There are (supposedly) a gazillion out of work or underemployed computer scientists. The idea that they can't find what they want here in the states is just preposterous.
A gazillion out of work and a gazillion that I'd
want to employ are two very different
things. I have a hard enough time recruiting for
a department of 15, let alone trying to do it at
the sort of scale he's talking about. The truth is
that Sturgeon's Law holds just as well for IT
staff as for anything else. In fact, if my
experiences are anything to go by, he was being
optimistic...
Somehow, they don't seem to realize that by forcing me into the situation where I *can't* have a password that is both obscure and easy for me to remember, they are making the system LESS secure, rather than nore secure.
I'm glad someone else understands this. I've
successfully fought against mandatory password
changes at my company, but it rears its head
again every few months, as some bright spark in
management (usually in our parent company) thinks
it would be a good idea, and it's "standard best
practice" in the IT industry.
I can't recall that many uses for a D10 in D&D/AD&D.
Errr... initiative? Admittedly, it was d6 in D&D, but by AD&D 2e, it had changed to a d10. Yikes. I've been playing 2e for so long that
I'd almost forgotten it used to be anything other
than d10.
Does anyone remember early issues of Wired magazine. Hippest and Coolest magazine ever at the time -- awesome ads and graphics.
Yep. Absolutely hated it. It was pretty much utterly
devoid of content, the layout and presentation were
appalling, and it was incredibly poorly written by
people that didn't understand the subject,
and probably still
don't[1].
It was a wannabe magazine, aimed at people who
aspired to a hacker lifestyle
without having the technical skills to achieve it.
Strictly for the script kiddies (who seemed to lap it up).
[1] A trait that's sadly all too common in IT
journalism even today. As the saying goes, "Those
who can, do. Those who can't, teach" (and by
extension, write about it).
Smart is manufactured and marketed in Europe by an unaffiliated party and made US/CA compliant by DMC.
That "unaffiliated party" is Mercedes Benz (and
hence ultimately, Daimler Chrysler). I wonder why
they don't seem to want to market it themselves,
and are relying on Zap instead. Worried about it
being a flop in the US and not wanting to damage
their reputation, perhaps?
Really? I never heard of anyone having a problem
with it, save for with insecure software[1], and I'd
advise anyone running windows to upgrade to SP2
ASAP. From those I have contact with, this seems
to be by far the prevailing wisdom.
[1] And personally, I'd rather my software stopped
working rather than kept running in an insecure
manner. Besides, I haven't yet found a program
that doesn't work with SP2. I'm sure they exist,
but they're rare.
TCP just doesn't make sense for everything, e.g. real-time apps (including games) where retransmissions are counterproductive.
Correct, which is why they should (and most do)
use UDP, which is unreliable by design,
specifically for the type of situations you cite.
Trying to make UDP reliable is totally counter
productive. You'll just end up with TCP.
RPM still sucked massively and was fragmented between RedHat, SuSE, and Mandrake so badly that they couldn't use each others' RPMs.
Sigh. RPM didn't suck at all. The sole reason for your problems is RPMs
popularity. If Ubuntu
or Progeny or whoever acquires enough market share,
I can guarantee
you'll start to see the same issues cropping
up with dpkg systems. Initially, it won't be a
problem, just as Caldera and SuSE RPMs used to work
fine on Red Hat and vice versa -- everyone strived
to maintain compatibility with Red Hat. But as soon as
a distribution ies to do something different,
in an attempt to differentiate itself from the
others, then you're headed down the same path
that RPM has gone. There is nothing
intrinsically better about dpkg than RPM, and
dpkg systems' saving grace to date has simply
been their comparative
lack of success. I wish more people could see
the reason things work well under Debian,
rather than just blindly claiming RPM sucks.
As the sainted Lindsay Marshall pointed out to ESR
at a conference some years ago, cathedrals (which
we know a bit about in Europe) weren't built like
ESR thinks. They were built over the course of
generations, by a sequence of random people
All of which is completely irrelevant, as ESR was
discussing how they're run, not how they were built.
What planet are you living on. Maybe for watching porn CRT's are better because the color is more, um, vibrant. For real work, coding, hacking, chatting, or anything where you have to look at words on the screen, LCD's blow CRT's away.
Wrong. It comes down to personal opinion, and mine,
in common with that of many others, is that CRT gives far superior picture quality. For prolonged
viewing, I couldn't recommend anything else. LCDs
are just a recipe for headaches if you use them
long enough. I'm sure that in time, flat screen
technology will improve to the point where it can
rival CRTs. Indeed, it's been getting far better
in the last couple of years. But it's not there
yet, and probably won't be for at least another
4 or 5 years.
Actually, even Wikipedia can't spell it right,
that fact alone hinting at the lack of wisdom
of using Wikipedia to be a credible
source of data. OK, so DNS can't support
the æ ligature needed to get the correct
spelling: Wikipædia. But they could at least have used the
A and E as separate characters: Wikipaedia.
Bad management, unrealistic schedules, artificial deadlines
A friend of mine writes games for a living. He
was recently told by his management that they
needed him to work overtime[1] -- the
project plan had allocated 150% of their available
developer man hours to hit their (artificial)
deadlines. Unfortunately, this is far from
uncommon.
[1] The stupid thing is, the coders voluntarily
worked overtime a lot of the time
before the crunch because they
enjoyed what they were doing. But when it came down
to management insisting they did it every day, it
just drained morale. They're all burned out, and none of them are putting
any effort into the product any more. Everyone
loses, yet they still do it, just as they did
with their last failed project. And as they will
do with their next one when this one fails.
What if somebody hacks your primary machine and erases your data? This would propagate to your backup server as well.
The syncs are delayed, so I have an overnight sync
to a local disk in my main machine, weekly
backups offsite, and 4 weekly backups from that
to another offsite machine. Thus I have 28 days in which to
spot the deleted data and restore from backup
(actually, I don't need to spot it manually --
AIDE tells me when a file disappears from my machine).
Eventually, I'll get around to implementing
a backup strategy using rsync with hard links
to do incremental backups, which we do at work.
See rsnapshot.
But for home use, what I have is more than
sufficient.
Or rather, dispense with the concept of permanent
media altogether. I realised a few years ago that
the only sane way to protect my data was to have
it all online all the time. I store my data on
redundant arrays
of disks in two geographical locations (my house
and my parents' house, synced nightly via rsync).
This is IMHO a far better solution than backing
up to tape or CD/DVD. LVM makes the process of
moving the data to bigger disks trivial. Where
it falls down is for really large volumes of
data. Places like CERN that generate terabytes
of data per day are going to struggle in the not
too distant future. Archived data will become a
real problem (even more than it is now).
If you believe that mbox is an obscure format, I suggest you need to read up on the subject before commenting on it...
Quite simply, it's a better browser. The killer feature for me is searching. I hate the wasted real estate in Firefox from having a separate location and search box, and ease of use is dramatically better in Mozilla than in Firefox. In Mozilla, I just hit Ctrl-L, type my search commands, hit up arrow and enter. I haven't found any way of achieving the same thing in Firefox, and I hate the small size of the box I'm given to enter my search terms.
For email, I don't use either. Until something else comes close to the power of mh, I see no reason to change. But I also found out a major failing in Thunderbird yesterday. My other third uses it, and it turns out it can only get mail from a POP3 or IMAP server. It can't read from a local mbox file. How braindead is that?
Whereas the IRA are just completely indiscriminate, and blow people up simply for being British? That's obvioualy so much better. Having been caught by the blast (though fortunatly not injured) of the Canary Wharf bomb, I can tell you it's not much fun...
If X isn't selected at install time (and it really shouldn't be on a server), then RH doesn't add the rhgb parameter, and defaults to a text only boot anyway.
RH passes the rhgb kernel parameter, which enables the "Red Hat Graphical Boot". Omit that, and you'll get a regular text only boot. You can also control it by changing the line:
inA gazillion out of work and a gazillion that I'd want to employ are two very different things. I have a hard enough time recruiting for a department of 15, let alone trying to do it at the sort of scale he's talking about. The truth is that Sturgeon's Law holds just as well for IT staff as for anything else. In fact, if my experiences are anything to go by, he was being optimistic...
I'm glad someone else understands this. I've successfully fought against mandatory password changes at my company, but it rears its head again every few months, as some bright spark in management (usually in our parent company) thinks it would be a good idea, and it's "standard best practice" in the IT industry.
Movies (much like computer games) are largely unprofitable. The makers rely on a few big hits to cover the losses made by the rest.
Errr... initiative? Admittedly, it was d6 in D&D, but by AD&D 2e, it had changed to a d10. Yikes. I've been playing 2e for so long that I'd almost forgotten it used to be anything other than d10.
Yep. Absolutely hated it. It was pretty much utterly devoid of content, the layout and presentation were appalling, and it was incredibly poorly written by people that didn't understand the subject, and probably still don't[1]. It was a wannabe magazine, aimed at people who aspired to a hacker lifestyle without having the technical skills to achieve it. Strictly for the script kiddies (who seemed to lap it up).
[1] A trait that's sadly all too common in IT journalism even today. As the saying goes, "Those who can, do. Those who can't, teach" (and by extension, write about it).
That "unaffiliated party" is Mercedes Benz (and hence ultimately, Daimler Chrysler). I wonder why they don't seem to want to market it themselves, and are relying on Zap instead. Worried about it being a flop in the US and not wanting to damage their reputation, perhaps?
My userid would seem to imply otherwise :-)
I run a Mac, and even I know that SP2 will give a substantial number of Windows boxes the Hershey Squirts.
We've rolled it out on several hundred desktops here, and to date we haven't had a single problem with it.
Really? I never heard of anyone having a problem with it, save for with insecure software[1], and I'd advise anyone running windows to upgrade to SP2 ASAP. From those I have contact with, this seems to be by far the prevailing wisdom.
[1] And personally, I'd rather my software stopped working rather than kept running in an insecure manner. Besides, I haven't yet found a program that doesn't work with SP2. I'm sure they exist, but they're rare.
Correct, which is why they should (and most do) use UDP, which is unreliable by design, specifically for the type of situations you cite. Trying to make UDP reliable is totally counter productive. You'll just end up with TCP.
Sigh. RPM didn't suck at all. The sole reason for your problems is RPMs popularity. If Ubuntu or Progeny or whoever acquires enough market share, I can guarantee you'll start to see the same issues cropping up with dpkg systems. Initially, it won't be a problem, just as Caldera and SuSE RPMs used to work fine on Red Hat and vice versa -- everyone strived to maintain compatibility with Red Hat. But as soon as a distribution ies to do something different, in an attempt to differentiate itself from the others, then you're headed down the same path that RPM has gone. There is nothing intrinsically better about dpkg than RPM, and dpkg systems' saving grace to date has simply been their comparative lack of success. I wish more people could see the reason things work well under Debian, rather than just blindly claiming RPM sucks.
All of which is completely irrelevant, as ESR was discussing how they're run, not how they were built.
Wrong. It comes down to personal opinion, and mine, in common with that of many others, is that CRT gives far superior picture quality. For prolonged viewing, I couldn't recommend anything else. LCDs are just a recipe for headaches if you use them long enough. I'm sure that in time, flat screen technology will improve to the point where it can rival CRTs. Indeed, it's been getting far better in the last couple of years. But it's not there yet, and probably won't be for at least another 4 or 5 years.
Actually, even Wikipedia can't spell it right, that fact alone hinting at the lack of wisdom of using Wikipedia to be a credible source of data. OK, so DNS can't support the æ ligature needed to get the correct spelling: Wikipædia. But they could at least have used the A and E as separate characters: Wikipaedia.
Both :-) The do their own ADSL, and they rebrand
NTL's cable service as "AOL Broadband".
Huh? Then what were they doing? At least here in the UK, that's pretty much all they do, and it's the main focus of all their advertising.
A friend of mine writes games for a living. He was recently told by his management that they needed him to work overtime[1] -- the project plan had allocated 150% of their available developer man hours to hit their (artificial) deadlines. Unfortunately, this is far from uncommon.
[1] The stupid thing is, the coders voluntarily worked overtime a lot of the time before the crunch because they enjoyed what they were doing. But when it came down to management insisting they did it every day, it just drained morale. They're all burned out, and none of them are putting any effort into the product any more. Everyone loses, yet they still do it, just as they did with their last failed project. And as they will do with their next one when this one fails.
Tripwire, its main competitor, is in much the same state. But since both are mature enough to do the job, the lack of updates isn't a problem.
The syncs are delayed, so I have an overnight sync to a local disk in my main machine, weekly backups offsite, and 4 weekly backups from that to another offsite machine. Thus I have 28 days in which to spot the deleted data and restore from backup (actually, I don't need to spot it manually -- AIDE tells me when a file disappears from my machine). Eventually, I'll get around to implementing a backup strategy using rsync with hard links to do incremental backups, which we do at work. See rsnapshot. But for home use, what I have is more than sufficient.
Or rather, dispense with the concept of permanent media altogether. I realised a few years ago that the only sane way to protect my data was to have it all online all the time. I store my data on redundant arrays of disks in two geographical locations (my house and my parents' house, synced nightly via rsync). This is IMHO a far better solution than backing up to tape or CD/DVD. LVM makes the process of moving the data to bigger disks trivial. Where it falls down is for really large volumes of data. Places like CERN that generate terabytes of data per day are going to struggle in the not too distant future. Archived data will become a real problem (even more than it is now).
Right here.