|
|
| Author |
Message |
| 25 new of 124 responses total. |
keesan
|
|
response 25 of 124:
| 
Apr 7 15:36 UTC 1999 |
sdscan called it a partition table virus. It also infects the boot sector
of a floppy disk. It does spread by tape, too. Anti exe virus is what sdscan
calls it.
|
prp
|
|
response 26 of 124:
|
Apr 7 19:09 UTC 1999 |
re 24: On a hard disk the partition table is in the boot record.
Or rather the first boot record. There is one per disk plus one
per partition.
|
mcnally
|
|
response 27 of 124:
|
Apr 8 00:59 UTC 1999 |
re #26: I still don't understand what good it'd do putting virus code
in the partition table. It's not like the partition table is
executed the way the boot loader is.. If, by "partition table
virus" people mean a virus that overwrites the partition table
with stuff (virus code, garbage, or anything else..) then I
guess I understand the point of that (though it's a nasty thing
to do..) but it doesn't sound like that's what Cindi's talking about.
|
keesan
|
|
response 28 of 124:
|
Apr 8 04:25 UTC 1999 |
It hides there and attacks exe com and dll files. It is gone now, Kent fixed
it. Now Netscape often runs, but at 120 bytes per seco or less, as low as
30.
What has hit grex since midnight? Very slow.
|
mcnally
|
|
response 29 of 124:
|
Apr 8 06:41 UTC 1999 |
<sigh>
|
gull
|
|
response 30 of 124:
|
Apr 8 20:46 UTC 1999 |
Re #27: I'd guess that'd be the case. Bear in mind most people have no
clue about how their hard disks are *really* laid out.
|
keesan
|
|
response 31 of 124:
|
Apr 8 21:16 UTC 1999 |
Was there a grex problem from 12 to 12:20 or so this morning? If not, we have
some other phone or modem or computer problem. Please let me know. Our two
Netscape computers were running at as low as 68 bytes/sec and grex was waiting
10-15 seconds to display a word.
|
steve
|
|
response 32 of 124:
|
Apr 8 21:55 UTC 1999 |
Around 12:06am, Grex gets VERY busy for a bit, doing a bunch of nightly
things. There have been a few occaisons when I thought Grex was under
attack, it was so slow. This is something we should work on optimizing;
the work needs to be done, but hopefully we can alter the schedule such
that there isn't an emmense queue of things to do all at the same time.
|
keesan
|
|
response 33 of 124:
|
Apr 9 13:58 UTC 1999 |
What happens and where at 12:06? India is 10 1/2 hours different.
|
jazz
|
|
response 34 of 124:
|
Apr 9 16:14 UTC 1999 |
I'm not sure how that relates to what Steve said ... at all ...
|
steve
|
|
response 35 of 124:
|
Apr 9 16:40 UTC 1999 |
There is a program called cron which can run other programs at
a specified time, in order to do things like simple system maintenance,
and other things.
A bunch of log files get either updated or moved every night, among
other things. The way things have evolved, right at midnight a bunch
of things fire off at once, which wasn't by intent but has come about
that way, as we've added new things for cron to do. One example is
that Grex now makes copies of the all-important passwd and shadow files
six times a day in multiple locations, such that if the /etc directory
is ever damaged we have a copy of the passwd database no more than 4
hours old.
But all this takes a little time, and I think we're doing too much
at once right at midnight. We'll have to look at all the things that
are done, and work on rescheduling them a little bit such that we can
spread them farther apart.
|
keesan
|
|
response 36 of 124:
|
Apr 9 18:23 UTC 1999 |
re 34, I thought all the Indian grexers might be reading email at once.
|
gregb
|
|
response 37 of 124:
|
Apr 15 03:08 UTC 1999 |
Re. 33: Good point. Maybe time should Grex should use GMT as the std.
time reference.
|
rcurl
|
|
response 38 of 124:
|
Apr 15 04:28 UTC 1999 |
GMT no longer exists. Try UCT.
|
scg
|
|
response 39 of 124:
|
Apr 15 04:43 UTC 1999 |
Isn't GMT still the timezone Britain is in, even if it's not the official
timezome of the world anymore?
|
rcurl
|
|
response 40 of 124:
|
Apr 15 05:14 UTC 1999 |
Well, there isn't a standard clock at Greenwich anymore, for one thing.
Then, while GMT is now defined as UTC, it would not be called that
anywhere except in England - after, all, consider what UTC stands for (I
wrote it incorrectly in #38). Furthermore, time zones have been lettered,
and the correct time zone name for England is ZULU. (We are in the Romeo
time zone.) Try http://aa.usno.navy.mil/AA/faq/docs/world_tzones.html
for more information.
|
flem
|
|
response 41 of 124:
|
Apr 15 05:20 UTC 1999 |
poTAYto, poTAHto, IMO.
|
other
|
|
response 42 of 124:
|
Apr 16 00:51 UTC 1999 |
GMT = Grex Mean Time
|
prp
|
|
response 43 of 124:
|
Apr 16 01:36 UTC 1999 |
I heard that Greenwich went to BST year round. (BST=British Summer Time)
|
scg
|
|
response 44 of 124:
|
Apr 16 03:28 UTC 1999 |
Britain is not on daylight savings time in the winter. It was getting light
at 8 am and getting dark at 4 pm when I was in London a few months ago, so
noon was actual solar noon, just as it's supposed to be.
|
ec
|
|
response 45 of 124:
|
Apr 17 04:25 UTC 1999 |
Hiyez! Nice to see so many familiar names!
The newuser program and even the web interfaced version of it still
don't allow those of us with apostrophes in our names to have them stuck
in the gecos. :-(
Is this an okay place to whine about Backtalk? The
subscribe-to-conferences page doesn't actually list conferences at the
bottom as it says at the top it will.
Very spiffy interface overall, tho'! Maybe I'll telnet in for a
nostalgia trip sometime soon anyway.
Er, and I've typed an aliased name "Iain
O-apostrophe-really-is-allowed-here-'-see?-Cain" in the box next to my
login, but when I hit the "Preview" button, it shows my default name for
the conference.
Yous are badly in need of users who report bugs, hey?
|
ec
|
|
response 46 of 124:
|
Apr 17 04:26 UTC 1999 |
Yeah. Like that. So only the preview is broken.
I'll have to log in to see what my new uid is, won't I? :-)
|
mdw
|
|
response 47 of 124:
|
Apr 17 07:02 UTC 1999 |
Chfn should allow you to put a ' into your gecos field. Wonder how many
broken mail programs are out there?
|
mrmat
|
|
response 48 of 124:
|
Apr 17 21:40 UTC 1999 |
oops. Didn't mean to do THAT.
|
jep
|
|
response 49 of 124:
|
Apr 17 22:02 UTC 1999 |
Howdy, Iain! Good to see you back on-line.
|
