![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Eero Ahonen wrote:
> When wires are disconnected and the user heads for mobile environment,
> "broadband" means pretty far "anything that connects"...
Anything an order of magnitude faster than the previous generation of
technology is "broadband"? :-)
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 06 Jun 2008 13:10:37 +0100, Invisible wrote:
> Possibly my poudest achievement was splitting my OS disk across two
> floppies. This required me to completely require the boot script so that
> it rewired all the search paths dynamically, so half the files were on
> the boot floppy and half on another one, but the OS could still find all
> of them immediately. It's a lot more work than it sounds, but it worked
> magnificantly.
>
> [Again, I suppose theoretically you could do the same thing to a Linux
> distro with enough symlinks. But since I have absolutely NO CLUE how
> Linux actually works and this does not appear to be documented
> anywhere........]
man ln
Thing is, there's no need in Linux to boot off multiple diskettes for
Linux - you can do a bootable CD that has everything you need *if* it
doesn't fit on a floppy. But there are distributions (Damn Small Linux
for one, Puppy Linux for another IIRC) that are entirely contained on a
single diskette.
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 06 Jun 2008 12:56:01 -0400, Warp wrote:
> Jim Henderson <nos### [at] nospam com> wrote:
>> In Europe, yes. In the US, no. I got an upgrade recently (for free)
>> to 3 Mbps from 1.5. It's amazing that that still qualifies as
>> "broadband" here in the US.
>
> I think "broadband" is a marketing term which means "anything faster
> than ISDN".
Quite possibly. But here in the US, compared to the rest of the "first
world", broadband speeds are quite slow, generally speaking.
I live in a major metropolitan area and my DSL speed won't go above 3
Mbps because of "technical limitations" (distance from the telco CO).
And it's only been in the last year that I got 3 Mbps, it used to be 1.5.
I *could* pay for Comcast cable and get - I think it is - a whopping 6-8
Mbps, but then I'd be subject to their bandwidth caps and throttling = I
pay for 6-8, but I can't *use* it if I so desire. Their TOS (when I
selected my current provider) didn't allow for hosting services, either,
and I need remote access into my network. If you wanted that (at that
time, no idea if it's changed now), you had to pay something like $250 a
month for a *business* connection.
There's no way my employer would reimburse for that. They'd sooner have
me drive 45 miles to sit in an office rather than work from home.
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 06 Jun 2008 10:16:06 -0500, Mueen Nawaz <m.n### [at] ieee org>
wrote:
>--
>"I think not," said Descartes, and promptly disappeared.
LOL
--
Regards
Stephen
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> [Jesus, and I don't even have a sound card...]
>
> Then you missed most of it.
A feel glad about this! o_O
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> Possibly my poudest achievement was splitting my OS disk across two
>> floppies. This required me to completely require the boot script so that
>> it rewired all the search paths dynamically, so half the files were on
>> the boot floppy and half on another one, but the OS could still find all
>> of them immediately. It's a lot more work than it sounds, but it worked
>> magnificantly.
>>
>> [Again, I suppose theoretically you could do the same thing to a Linux
>> distro with enough symlinks. But since I have absolutely NO CLUE how
>> Linux actually works and this does not appear to be documented
>> anywhere........]
>
> man ln
I'm sure if you knew enough about Linux, you could do this kind of thing
pretty easily. I don't have the knowledge required.
> Thing is, there's no need in Linux to boot off multiple diskettes for
> Linux - you can do a bootable CD that has everything you need *if* it
> doesn't fit on a floppy. But there are distributions (Damn Small Linux
> for one, Puppy Linux for another IIRC) that are entirely contained on a
> single diskette.
I *have* such a thing. It's a little Linux boot disk that allows you to
access an NTFS partition and rewrite the SAM DB. [The thing that stores
the local administrator password.] Very damn useful too! ;-)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 06 Jun 2008 19:40:39 +0100, Orchid XP v8 wrote:
>>> Possibly my poudest achievement was splitting my OS disk across two
>>> floppies. This required me to completely require the boot script so
>>> that it rewired all the search paths dynamically, so half the files
>>> were on the boot floppy and half on another one, but the OS could
>>> still find all of them immediately. It's a lot more work than it
>>> sounds, but it worked magnificantly.
>>>
>>> [Again, I suppose theoretically you could do the same thing to a Linux
>>> distro with enough symlinks. But since I have absolutely NO CLUE how
>>> Linux actually works and this does not appear to be documented
>>> anywhere........]
>>
>> man ln
>
> I'm sure if you knew enough about Linux, you could do this kind of thing
> pretty easily. I don't have the knowledge required.
That's a far cry from "doesn't appear to be documented".
>> Thing is, there's no need in Linux to boot off multiple diskettes for
>> Linux - you can do a bootable CD that has everything you need *if* it
>> doesn't fit on a floppy. But there are distributions (Damn Small Linux
>> for one, Puppy Linux for another IIRC) that are entirely contained on a
>> single diskette.
>
> I *have* such a thing. It's a little Linux boot disk that allows you to
> access an NTFS partition and rewrite the SAM DB. [The thing that stores
> the local administrator password.] Very damn useful too! ;-)
Yep. I've got a copy of that one around here somewhere as well from my
days working on Win2K Server. Pity it didn't work on the domain
controller I was having problems with, though - W2Ks had a problem where
if the administrator password got corrupted (that's the best guess
Microsoft had about the issue), you couldn't even boot into safe mode.
The utility disk at the time didn't understand AD DCs (indeed, since it
was a DC, it wasn't the SAM but the AD database that needed to be
accessed, and it wasn't designed for that).
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> this had real processing capabilities vaguely moddelled after Unix
>
> AmigaOS was farther from being UNIX-like than DOS 2.0 was. The two had
> absolutely nothing in common.
>
> Let me rephrase: What did you think was common about the two of those?
> About the only thing I can think of is they both had pre-emptive
> interrupts.
I always wondered why the hell AmigaDOS provided this lame little "more"
command. Or why it had "type". I was even more perplexed by "ed" - a
program that lets you edit a text file one line at a time by typing in
utterly cryptic instructions. And I often wondered why the "dir" command
has a "SHOW=" option.
...and then I read about Unix for the first time, and I realised that
that's where all this stuff comes from. That "ed" thing is for scripted
editing of text files. The "SHOW=" option allows you to write
scripts-that-write-scripts. "type" is basically the Unix "cat" program.
And "more" is there because it's there in Unix.
[On top of that AmigaDOS allows scripts to have multiple parameters
(with default values), local environment variables, uses variable
expansion, and generally does a number of things similar to what various
Unix shells give you. It also has pipes, launching background processes,
etc.]
Obviously there's also a truckload of ways AmigaOS is *different* from
Unix. [There are no device files, pathnames have a syntax more like
MS-DOS, configuration is always stored in binary files not text files...]
>> [Again, I suppose theoretically you could do the same thing to a Linux
>> distro with enough symlinks. But since I have absolutely NO CLUE how
>> Linux actually works and this does not appear to be documented
>> anywhere........]
>
> I saw a distro that used symlinks to completely "fix" the legacy layout
> of files. So their Linux had a /Programs and a /Library and a /Users and
> so on, not unlike OSX apparently has.
Now I would suspect that would tend to break horribly as soon as some
new application is added that expects everything to be in the normal
locations...
[Basically I have absolutely no clue how the traditional Unix file
layout is supposed to work. I don't know why, for example, we have /bin,
/root/bin, /usr/bin, /usr/sbin, /usr/share/bin...]
>> Ooo, ooo, and... TOKEN RING! Remember that?? Trying to get MS-DOS
>> powered PCs to talk to each other over a token ring network... Never
>> tried it personally, but I watched first-hand, and it wasn't pretty.
>
> I didn't have any trouble with that, except for the amount of RAM it
> took. Left little for the actual applications.
They had trouble. Somebody walked past and the T-adaptor on their PC
fell apart, breaking the ring. That and the constant AUTOEXEC.BAT
editing required to set up new programs or devices on PCs...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> When you wanted to start
>> windows you wrote "win".
>
> Except for one person I know who renamed it to "lose.com". You can guess
> his opinion.
OMG, lose.com is so full of win!
[Did you see what I did there?]
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> OTOH, 24 Mbit/s ADSL is completely normal
>
> In Europe, yes. In the US, no. I got an upgrade recently (for free) to
> 3 Mbps from 1.5. It's amazing that that still qualifies as "broadband"
> here in the US.
Really? I'd heard it was the other way round...
My company grudingly signed a 3-year lease with BT for our Internet. My
boss really wants to shop around for better deals.
(Er, HELLO? Are you not getting this? BT OWN ALL THE WIRES IN THE
GROUND. THERE ARE NO OTHER TELECOMS PROVIDERS IN THE UK [except in
London]. No matter who you pay the bills to, the wires under the ground
are still being provided by the same people... WTF?)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |