Theres already 'Internet Beat Time' or something. It's got 1000 'beats' a day, and '000' is 12:00 UTC+1. There are watches that have it, and web pages that have it (ever seen a @436 as a Timestamp somewhere? it's IBT).
It was designed so you could organise things on the internet where TZ's do/don't matter (depending on how you look at it)
One thing which I've not seen mentioned is the incentive for companies that sell computers (Such as IBM) in such a recycling effort. This gets older computers off the streets so they can put newer computers out there. Even if you only need a 486 to run your DNS servers, if there aren't enough computers you may need to go out and buy something more grunty and generate them more $$$:)
I used to run a program called 'Portal of Power', which would pick up my mail every so often. One of the "features" of this program was that you could press 'alt-L' and type in a password that needed to be reentered to unlock the computer's keyboard. It didn't do the sane "ask the question twice and check if they are the same" thing.
Twice I had my cat walk on the keyboard, left paw on "Alt" and right paw on "L", back paws on random other keys then sit down on 'enter', leaving me trying to figure out how to break into my computer.
I think it was when people started really pushing GCC for Intel based processors - gcc generates pretty good code for intel, but when you go to a less used platform you discover that some of the optimisations it makes are silly. GCC seems to put emphasis on keeping the number of registers it uses to a bare minimum, even on platforms that have lots of registers for it to use. I guess a lot of this is due to the fact that almost everyone has intel boxes, so that platform works, but noone has Alpha's/Sparcs and the time to dedicate improving their compilers.
Why not use something like IPsec for this? it encrypts the network traffic and requires no changes to the server, and gives you the same amount of protection.
The redundant links idea has been thrown around irc for years, and runs into some serious problems, for starters irc is very prone to 'desyncs', and many of the serverserver protocols aren't atomic with respect to a command, causing more desyncs. It basically ends up with you sending all the data multiple times which isn't really practical. And even if you could, if a servers unreachable, it's unreachable, no number of TCP connections will stop it from splitting. A lot of the splits on the major networks today are due to DDoS attacks against ISPs and/or the servers.
All IRC is, is a glorified multiplexor on steriods with delusions of grandeiur. If all the links are encrypted from clientsservers then how much security have you really gained? Noone can sniff your network, but do you trust the admin's of the servers not to patch the daemon and sniff your traffic? What about the local SS coming and forcing you to install those patches? You'd be far better to extend the CTCP (Client To Client Protocol) that runs over the top of irc to support encryption. IRC already has this in the 'SED' CTCP, which unfortunately isn't too secure. Someone with some spare time could easily hack this up.
The next point is how much cpu do you have? Encryption is all very fine, but having the servers do all the work causes all sorts of problems, when you hit 10k clients per server as some networks have done how much cpu are you going to need to use then?
this marks a file 'immutable' so that not even root can modify it. Then as I understand it using secure levels you can make it impossible to -i the file without a (logged) reboot.
I've been thinking about this for a while. The problem is you have several classes of files: Binaries - exported over a network readonly. Maybe arch independant. Data files, read only, or read write, may be on a network, machine local, or per user. Configuration, again, network, or local, or per user. The current fs layout is organised like this, so you can mount/usr readonly,/var read write, and mount/usr/share over a network. if you have/package// then you loose this.
After trying to emulate the linux shutdown message for a text adventure I was writing I was poking through the source code for init and friends and discovered that if your username is 'tyler' and the system is being rebooted you get an additional "Going down Mr Tyler?" as well as the normal 'System is going down for a reboot now' message.:)
True, but how many well used OSS compilers are there that aren't egcs/gcc ? Something like this could perpetuate a long time in the OSS world. Just make sure you put it somewhere in some code that doesn't change much....:)
Theres been a very famous back door in OSS software, one that was not visible by reading the source. It involved a compiler, and someone with a lot of spare time.
Basically it goes like this: You take a compiler, detect when your compiling login and insert a back door into login. You also detect when your compiling the compiler and add the code back. Read about it here
Speaking of easter eggs, I fell across one in shutdown the other day. if someone is logged in as 'tyler' they get a "Going down mr tyler?" message as the shutdown message as well as the standard message (System is going down for a reboot NOW)...
My all time favourite is a hearing about an isp that had a user which thought that sending attachments by email was a good idea. U/ling an.iso image to the local smtp server was fast, and at the other end it was fast to d/l it from the local pop server. Until one day he emailed an.iso image to a friend, and got a bounce message back with 'This would exceed mailbox limits, try again later'. ... including a full copy of his message (and the attachment). It then quite happily resent this bounce message after 4 hrs etc, up until 7 days. His ISP wasn't happy getting that many copies of the iso bounced back....
Google has started doing this now, you can sign up to maintain a branch, or just click through the trees that they've got their already. Google has the nice simple interface as always that works remarkably well in lynx. The people that run google say that they won't go into the "portal" business, which to me is a good thing. I just want to efficiently find information dammit!
Well, in regards to the time comments, we have 'internet beat time' that swatch(?) came up with. 1000 beats a day, 000 is always midnight GMT+1 no matter what time zone your in. Makes trying to organise events on the internet much much easier, and as a generic timestamp it's pretty good too, doesn't take up the space that 'HH:MM:SS' takes up in a logfile:)
As I understand it what is new is script kiddies breaking into hundreds of machines and installing a DoS 'client' on each of them. Now on command all of these 'DoS machines' all start smurfing/ pingflooding/synflooding/whatever the target. Now before it used to be difficult to trace back a smurf and find the originator. But now you've got to find a few hundred of them.... And if you close down even 1/2 of them, they'll find another 100 again tomorrow....
Well yes, color syntax highlighting, but I think that that tends to be bloatware anyway, ^G tells me if brackets match and the rest tends to be eye candy. Syntax highlighting has it's place, it is very useful at times, but it's not something I need continously. I use emacs when things just start to get too hairy, but thats maybe 1ce a year. Joe is lean, simple and usable, and I there is nothing I can point to and say: "I'd really like to change...."
I agree, Joe has simple key bindings that are common enough that (if only in the doze/dos world) most people don't have to relearn them. It's powerful enough for programming purposes, yet it doesn't masquarade as an entire operating system like some editors. It's small, fast, simple, and powerful enough for almost all tasks. What more can you ask for in an editor?
Slashdot Mirror
Theres already 'Internet Beat Time' or something. It's got 1000 'beats' a day, and '000' is 12:00 UTC+1. There are watches that have it, and web pages that have it (ever seen a @436 as a Timestamp somewhere? it's IBT).
It was designed so you could organise things on the internet where TZ's do/don't matter (depending on how you look at it)
a search on google seems to point to this release. Just a random guess.
One thing which I've not seen mentioned is the :)
incentive for companies that sell computers (Such
as IBM) in such a recycling effort. This gets
older computers off the streets so they can put
newer computers out there. Even if you only need
a 486 to run your DNS servers, if there aren't enough
computers you may need to go out and buy something
more grunty and generate them more $$$
I used to run a program called 'Portal of Power',
which would pick up my mail every so often. One
of the "features" of this program was that you
could press 'alt-L' and type in a password that needed
to be reentered to unlock the computer's keyboard. It didn't do
the sane "ask the question twice and check if they are the same" thing.
Twice I had my cat walk on the keyboard, left paw on "Alt"
and right paw on "L", back paws on random other keys then
sit down on 'enter', leaving me trying to figure out how to break into my computer.
I think it was when people started really pushing
GCC for Intel based processors - gcc generates
pretty good code for intel, but when you go to
a less used platform you discover that some of
the optimisations it makes are silly. GCC seems
to put emphasis on keeping the number of registers it
uses to a bare minimum, even on platforms that have
lots of registers for it to use. I guess a lot of
this is due to the fact that almost everyone has intel boxes, so that
platform works, but noone has Alpha's/Sparcs and the time to dedicate improving their compilers.
Why not use something like IPsec for this? it encrypts
the network traffic and requires no changes to the server,
and gives you the same amount of protection.
The redundant links idea has been thrown around irc for years,
and runs into some serious problems, for starters irc is very prone to 'desyncs', and
many of the serverserver protocols aren't atomic with respect to a command, causing more
desyncs. It basically ends up with you sending all the data multiple times which isn't really practical. And even if you could, if a servers unreachable, it's unreachable, no number of TCP connections will stop it from splitting.
A lot of the splits on the major networks today are due to DDoS attacks against ISPs and/or the servers.
All IRC is, is a glorified multiplexor on steriods
with delusions of grandeiur. If all the links are
encrypted from clientsservers then how much security have you really gained? Noone can sniff your network, but do you trust the admin's of the servers not to patch the daemon and sniff your traffic? What about the local SS coming and forcing you to install those patches? You'd be far better to extend the CTCP (Client To Client Protocol) that runs over the top of irc to support encryption. IRC already has this in the 'SED' CTCP, which unfortunately isn't too secure. Someone with some spare time could easily hack this up.
The next point is how much cpu do you have? Encryption is
all very fine, but having the servers do all the work causes all sorts of problems, when you hit 10k clients per server as some networks have done how much cpu are you going to need to use then?
chattr +i filename
this marks a file 'immutable' so that not even
root can modify it. Then as I understand it using
secure levels you can make it impossible to -i the
file without a (logged) reboot.
I've been thinking about this for a while. The /usr readonly, /var read write, and mount /usr/share over a network. /package// then you loose this.
problem is you have several classes of files:
Binaries - exported over a network readonly. Maybe arch independant.
Data files, read only, or read write, may be on a network, machine local, or per user.
Configuration, again, network, or local, or per user.
The current fs layout is organised like this, so you
can mount
if you have
IPv6 does support Mobile IP so you can actually be somewhere and have the internet route your IP to the correct place.
However it appears that at least for some distributions that that was the way the binaries were compiled.
After trying to emulate the linux shutdown message for a text adventure I was writing I was poking through the source code for init and friends and discovered that if your username is 'tyler' and the system is being rebooted you get an additional "Going down Mr Tyler?" as well as the normal 'System is going down for a reboot now' message. :)
True, but how many well used OSS compilers are there that aren't egcs/gcc ? Something like this could perpetuate a long time in the OSS world. Just make sure you put it somewhere in some code that doesn't change much.... :)
Theres been a very famous back door in OSS software,
one that was not visible by reading the source.
It involved a compiler, and someone with a lot
of spare time.
Basically it goes like this: You take a compiler,
detect when your compiling login and insert a
back door into login. You also detect when your
compiling the compiler and add the code back.
Read about it here
Speaking of easter eggs, I fell across one in
shutdown the other day. if someone is logged in
as 'tyler' they get a "Going down mr tyler?" message
as the shutdown message as well as the standard
message (System is going down for a reboot NOW)...
My all time favourite is a hearing about an isp .iso image .iso image
that had a user which thought that sending attachments
by email was a good idea. U/ling an
to the local smtp server was fast, and at the
other end it was fast to d/l it from the local
pop server. Until one day he emailed an
to a friend, and got a bounce message back with
'This would exceed mailbox limits, try again later'.
... including a full copy of his message (and the attachment). It then quite happily resent this bounce message after 4 hrs etc, up until 7 days.
His ISP wasn't happy getting that many copies of the iso bounced back....
Google has started doing this now, you can sign up
to maintain a branch, or just click through the
trees that they've got their already. Google has
the nice simple interface as always that works
remarkably well in lynx. The people that run
google say that they won't go into the "portal"
business, which to me is a good thing. I just
want to efficiently find information dammit!
Well, in regards to the time comments, we have :)
'internet beat time' that swatch(?) came up with.
1000 beats a day, 000 is always midnight GMT+1 no
matter what time zone your in. Makes trying to
organise events on the internet much much easier,
and as a generic timestamp it's pretty good too,
doesn't take up the space that 'HH:MM:SS' takes up
in a logfile
As I understand it what is new is script kiddies
breaking into hundreds of machines and installing
a DoS 'client' on each of them. Now on command
all of these 'DoS machines' all start smurfing/
pingflooding/synflooding/whatever the target. Now
before it used to be difficult to trace back a
smurf and find the originator. But now you've
got to find a few hundred of them.... And if you
close down even 1/2 of them, they'll find another
100 again tomorrow....
Well yes, color syntax highlighting, but I
think that that tends to be bloatware anyway,
^G tells me if brackets match and the rest tends
to be eye candy. Syntax highlighting has it's
place, it is very useful at times, but it's not
something I need continously. I use emacs when
things just start to get too hairy, but thats
maybe 1ce a year. Joe is lean, simple and usable,
and I there is nothing I can point to and say:
"I'd really like to change...."
I agree, Joe has simple key bindings that are
common enough that (if only in the doze/dos world)
most people don't have to relearn them. It's
powerful enough for programming purposes, yet it
doesn't masquarade as an entire operating system
like some editors. It's small, fast, simple,
and powerful enough for almost all tasks. What more
can you ask for in an editor?