Slashdot Mirror

Palm/Pocket PC - Capabilities & Reality. Rebuttal from a CasioE100 Owner:

a) Don't compare processors... the Palm does everything quickly and efficiently with 16mhz. The Pocket PCs are 133mhz+....never intended to be an MP3 player.

I have run 'tests' with a coworker who runs a PalmIII/V, we did blanket searches on a 'word' contained in our PIM databases. I retrieved my data faster on every attempt, regardless of 'type'. My device has 16 megs (8RAM/8ROM) with about 5-6MB of PIM data. Admittedly NOT scientific, but it was enough to convince the both of us.

b) Palm Multi-platform friendly. The Pocket PC is all about Windows...iPaq can run linux, and Slashdot runs stories about it regularly).

I have CF Ethernet. To send files back/forth I simply use FTP/SMTP. The Pocket PC does not sync with any Non-Windows PC PIM Software (that I am aware of). I can move files to the CasioE100 without any trouble from _ANY_ TCP/IP capable box.

c) The Pocket PC has painfully little application support. VNC? SSH? Telnet?....generally more expensive than Palm.

VNC
Telnet
SSH

There is plenty of software available. More than I can even try.

d) No wireless support yet for Pocket PC...To me at least, there's no point getting a media rich Palm device if I can't use it to access the net.
CF Modem that I use togetherwith my phone

e) Cost, Cost, Cost. You can get Palms for as little as $149 ... NEW. Lower costs mean more accessibility to the geeks that write the code. :)

You might have me on this one.

CasioE100: $600
CF Modem: $69 (MS Rebate deal)
CF Ethernet: $180
2 x 96MB CFRAM: $300 ea.
Nokia Cell Phone: $200 (or so)
Having the most technically capable, multimedia, wireless, portable Palm/Pocket (whatever) PC/PIM: Priceless.

NOTE: I bought the device based on what it _CAN_ do by leveraging the OUTSTANDING hardware in a Palm/Pocket PC (at its time 10mos.) ago. I am not a great lover of M$, but their still is no comparing this device to _ANY_ Palm product. Please be realistic and leave the Anti-M$ zealotry out of your analysis.

College students need to write reports, create lab reports (embedding charts, diagrams, etc) and other larger projects.

In science and mathemetics, at least, this is usually accomplished with LaTeX. Diagrams are done with any tool that can generate EPS, like xfig or Graphviz. MS Word's equation editor sucks quite badly.

And there's a big difference between "you can embed diagrams" and "you can catch a virus". Yes, an exploit here or there is understandable. MS has made it quite clear that they're either clueless or careless when it comes to security, considering the sheer number and severity of exploits in their products. And their excuse that "there is no evidence that such activities are occurring" is even more unsettling. It reveals a whole attitude towards security akin to "the bank vault is secure until someone steals all the money".

here is the source for the first linux kernels:
linux0.1
Name: Linux 0.1
Date: 1991-09-17
Reference: http://www.memalpha.cx/Linux/Kernel/Master.html
Influenced by minix1.5.10

linux0.2
Name: Linux 0.3
Date: 1991-10-05
Reference: a printed calendar
Successor to linux0.1

greetings, eMBee.
--

VNC is not just a 'product name of sorts' for 'some company.' It is a GPL'ed cross platform solution for sharing desktops across TCP/IP that was developed by Olivetti Research Labs (later part of AT&T Research UK).

No license costs, the clients are small and there are versions for most Unices, all Windows including CE, MacOS, PalmOS, BeOS, and for Java web browsers. With Unix as host, VNC is multi user. Passwords are not clear text, but the data stream itself is not yet encrypted. However, it may be piped through ssh.

The program was usable from the start and there are now thousands of people using VNC Servers and Viewers, slowly taking over niches that were filled by PC Anywhere, or even X Windows. I have a feeling they are slowing down the number of WinFrame rollouts, too. But for multi user Windows, VNC is not the right solution.

Personally I never considered VNC a general term, unlike NC or Network Computer, which was the fashionable term for a while for what is now called thin client.

Anyhow, go get VNC if you haven't seen it yet..

I know this is flamebait-esque, but MacOS9 and below being secure is certainly an artifact of the OS just not doing that much.

UNIX has tended to run, as standard services, a much larger set of applications. Until recently Apples used only Appletalk to speak to one another, and TCP/IP to speak to the rest of the world (Or to NT boxen or Linux boxen which were willing to deal with them.) So there really wasn't any way to do anything to a Mac remotely.

MacOS is also a single-user operating system (Does that change in X?) with only a local login context. I'd guess there's a PC-Anywhere equivalent for it by now (Ah yes, VNC seems to be in beta) so there's another potential source of vulnerability. ph34r me as I hax0r your mac from my Wince handheld.

I subscribe to ATT@Home, and it's not bad. The speed could be more consistant, but I haven't experienced any downtime so far and overall I'm happy. After looking at the Comcast@Home Subscriber Agreement, I certainly hope that AT&T doesn't start making policy changes using Comcast as a model.

AT&T's policy is that you cannot run any servers, i.e. FTP, Telnet, News, etc. including VPN servers. They could care less whether or not I connect to work or elsewhere through VPN. The Terms of Service also say nothing about hosting a personal web site. It goes along with the upstream bandwidth limits, they want you to subscribe to their business services (which just happen to be significantly more expensive).

As far as sharing the internet connection goes (this is what I was told by the installation guy), the policy "we don't support home networks" really means "we're not going to set one up for you." I personally use a 2000 server configured as an internet router to share my connection. But he said he'd seen quite a few people with linux boxes or hardware routers. The companies just want you to buy more IP addresses from them (at $4-5 a month per IP address, it adds up).

I think Guillaume's nice discussion about some of the drawbacks of Gtk-- mixed memory management policy is fine as far as it goes, but I would like to add some points.

First, there are really many alternatives to choose to decide what kind of memory management to use for a C++ program. Telling is that the C++ standardization committee could only agree on one memory management class (auto_ptr<>). It uses gross hacks for ensuring the type checker does the right thing (And I'm not convinced it's right as it is).

Ok, to get to my real point, here is a list of all memory management policies I could remember having seen used in C++:

1) explicit deallocation (programmer responsible for deleting; e.g. C++ plain pointers)
2) strict ownership (e.g. a creation function returning a smart pointer )
3) transferrable ownership (e.g. auto_ptr)
4) Stack (objects created first are deleted last)
5) Static allocation (memory for object always exists)
6) no deallocation (sometimes you just can leave memory as leaks)
7) garbage collection (The garbage collector takes care of deallocation)
8) Cluster allocator (see "Ruminations on C++" by Andrew Koenig; basically objects are deallocated in clusters, and whenever the cluster is deallocated, all the objects in it are deallocated as well).
9) reference counting with explicit ref/unref.
10) Intrusive reference counting (the objects being pointed to contain a reference count)
11) Non-intrusive reference counting (the reference count is separate from the object, e.g. like boost shared_ptr template)
12) Handle-Body idiom (you write a specialized handle for managing memory for your class)
13) Container-managed (like Gtk-- manage())
14) Containment (like Gtk-- containment based solution)
15) Library-owned objects (library only returns references without ownership to users)
16) Distributed garbage collection
17) Evictor (the objects are maintained in a fixed size array, and the least used objects are deleted when new objects are created that would o verflow the array When the object is next needed after being deleted, it's re-created).
18) Copy semantics (you always do a copy)
19) Lazy copy semantics (you make a copy when you have to)
20) Reaper (The memory is scanned at fixed intervals for freed-up objects, and any objects marked to be deleted are freed).
21) Shared memory allocation
22) Persistent allocation (You mmap() some disk space for your objects, and leave it there to allow it to be used on subsequent invocations of your program)
23) Class allocator (overloading operator new and operator delete for allocating small objects efficiently)
24) Self-managed allocation (the object deallocates itself)
25) Singleton (The object is allocated when it's first used, and deallocated at the end of the program)
26) Mixture of several of the above policies

The design space for memory allocation of C++ objects is really HUGE. So it's no wonder there is some disagreement on what is the preferred way to handle memory management, especially as many of these alternatives are actually contradictory in that it is hard to combine many of these strategies.

I personally prefer auto_ptr combined with a non-intrusive reference counted pointer class and creation functions that return memory wrapped in auto_ptr. You do need some solution for putting references to objects in containers, plain auto_ptr doesn't work for that.

You may not always be safe in C++. (Acrobat format ;)
___

Besides being an expert cryptographer, Friedman was the world expert on the Voynich Manuscript, which is probably the closest thing in the real world to those weird books mentioned in Lovecraft's stories. Perhaps granting this patent is only the government's way of belatedly thanking Friedman for his work in preventing the Great Old Ones from returning.

Try it here. It takes into consideration the structure of XML for its compression model.

BTW, the exact redundancy depends on the kind of data you're compressing. But because you cannot use certain characters directly in XML (you have to escape certain things like the ampersand etc.), you will always be able to reduce XML files a bit.

Has anyone ever heard what C++ inventor Stroustrup thinks about the latest addition to the C family?!

Actually, this is in his FAQ. Since it is a short answer, I will carbon copy it here:

What do you think of C#?

I have no comments on C# as a language. It will take a lot to pursuade me that the world needs yet another proprietary language (YAPL). It will be especially hard to persuade me that it needs a language that is geared for a specific proprietary operating system.

Clearly, I'm no great fan of proprietary languages, and quite a fan of open, formal standards.
--

It's written in Perl, and works on Windows, Unix, and probably others. It establishes a proxy that you and others use, and it can pass requests on to other Crowds servers. This would still revolve around HTTP, I would guess.

tunneling vnc over ssh on *nix (use -c for compression) clients: http://www.uk.research.att.com/vnc/sshvnc.html and how to do it with a windows client http://www.uk.research.att.com/vnc/sshwin.html

tunneling vnc over ssh on *nix (use -c for compression) clients: http://www.uk.research.att.com/vnc/sshvnc.html and how to do it with a windows client http://www.uk.research.att.com/vnc/sshwin.html

Check out VNC. It does support ssh, and it doesn't have a lot of the overhead you'd expect it to.

Check out VNC. It does support ssh, and it doesn't have a lot of the overhead you'd expect it to.

Unfortunately I have not found a free MacOS X server which runs full-screen. With MacX, you can have an X root window in a Macintosh window (with its requisite title bar and menubar) or you can have a separate window for each X client and no root window.

I have also successfully run Debian on my IIci but it's kinda slow and it hung for some reason. I haven't gotten as far as installing X yet, because I can't seem to install anything with dselect or apt... it hangs while "resolving dependencies". Granted, the installation is maybe a year old, so maybe this is an old bug that's since been fixed.

Also worth checking out is VNC.

AT&T's Virtual Network Computing (VNC) is an excellent GPL licesned product to look at. When the server is run on UNIX systems, it allows you to run upto 99 independent sessions (more if you reconfigure/recompile it) on a single UNIX system. These sessions have their own window manager, programs, etc... tailored for the user running it. Essentially, you have a full X-Session running just like if the user was directly in front of the GUI console of the workstation. The user can then connect to the session from any VNC client, whether that client is MacOS, Windows, UNIX, DOS, Palm, etc...

Using VNC instead of a traditional X-Server on the PC side has several advantages. One is the fact that a user can disconnect and reconnect their viewer on another system and not have to logout. This also means that if the VNC viewer system (e.g., Windows) crashes, their entire X-Session is still running (and can be reconnected to). VNC also works fairly well over low-speed connections (as good as X11R6.3 extensions for low-speed connections), provided you minimize background images. An additional advantage is the fact that it runs on a single port (5900 + session #) which makes SSH tunneling extremely simple (side benefit: "low-cost, more secure" remote access than most "all ports open" commercial VPN software).

I work for a company whose applications are 90% UNIX based (Theseus Logic), and that's not likely going to change soon (as EDA tool vendors are choosing Linux over NT because of the true multiuser capabilities). We use Linux and Solaris sytems to run these applications. Although we are starting to dual-boot some of our NT Workstations on our desks with Linux (although my personal workstation and all our servers are 100% Linux ;-), most of our work is done via VNC over to our headless Linux and Solaris systems. With 512MB to 1GB of RAM, we can easily accomodate 10 engineers on each system with fairly intensive engineering applications running. This has additional benefits like accomodating node-locked licenses that normally won't remote display (to another system), but will work in a VNC session (because the VNC session appears simply as display "localhost:vncsession#.0").

VNC is also a great way to slowly move to Linux. Users can spend 6 months becoming familiar with Linux use via a remote VNC session, while still running Windows on their desktop. You can also use VNC to UNIX systems so any user can run those few (or many, like us ;-) UNIX applications when needed. Again, VNC is so simplistically powerful (especially on UNIX systems), you'll never run out of uses for it.

Again, instead of trying to deal with finding a costly terminal server program, or a PC-X-Server, evalute if you really need one. If your UNIX platform supports VNC (and I seriously doubt there is a major or even minor UNIX platform where it has not been ported to), just give your users a full UNIX session with all it's goodies. Best of all, with the VNC server and all its windows/apps running on the UNIX platform itself, you have 100% native execution.

[ Side Note: Unfortunately, since Windows is not a true multiuser system (and only a bastardized one with products like Terminal Server), you cannot use the VNC server in a reversed role (multiple users on a Windows NT system). Although you can use VNC like pcAnywhere (unified single session, remote and local user both see the same and control the keyboard/mouse simultaneously). And like pcAnywhere, VNC sessions can be shared, allowing remote training, etc... (even on UNIX, with multiple sessions running) ]

-- Bryan "TheBS" Smith

Office, admin, and even coding kinds of work can be done with VNC without a problem. That should satisfy your needs, should it not? I really hope you aren't trying to play games using a remote X display...

Food is not politics, and windowing is not a protocol, yet we have vegans and X.

IMO, tools like VNC obsoleted the "power" of X ages ago. 99% of the time, the X client and server are on the same system. The overhead is wasteful, and the terminology annoyingly confusing for newbies. I'm sure there would be significant performance and appearance improvements in GUI Un*x applications, especially games, if X were replaced with a standalone graphical system.

I'm a mac user. The significance comes in later. Anyway, I heard horror stories about slow install service from PacBell, so when I ordered extended (static-IP) service, I asked to do a self-install. This was about April 10. They said they normally don't allow that, but I assured the tech that I knew what I was doing (having installed a few ISDN modems before, and knowing DSL is much easier). Somehow I impressed the tech and he put my order through as a self-install. My line was set to be conditioned on April 25, and the modem was supposed to arrive soon after.

My line was conditioned as promised, but no modem arrived. I spoke to three diffrent techs on two consecutive days. Finally I tracked down the problem. I have a Mac. They don't allow self-installs on a Mac. I asked why, but they had no straight answer. The real reason is probably nobody on their staff knows how, so surely no customer does....

To aviod the whole shenanigan, I changed my order and asked them to have someone come out and install it for me. Now my install date was May 10. I crossed my fingers and hoped for the best. I really wanted the thing installed so I could start working from home via VNC. I couldn't wait to end my commuting.

Strangely, on May 5, I received a package from PacBell containing one DSL modem, one 10/100baseT NIC, 5 inline filters, a wall-mount filter, and one line splitter. "Hmmmm...," I thought. "It couldn't be as easy as plug and play, coult it?." The NIC was extraneous since I've got built-in 10bT ethernet (the DSL modem is only 10bT), so I plugged the DSL modem into the wall, and then ran a cable between it and the uplink port on my existing hub. I booted the Mac, entered the handily provided IP information and Voila! A quick trip to DSL Reports showed me downloading at over 1000kb/s. I couldn't have asked for a simpler install.

The funny thing is, I've since received two notices from PacBell in the mail -- the last via priority certified US Mail. They apologize for not yet getting to my DSL install. I wonder when, if ever, I'm going to be charged for my DSL service. :) Aside from clueless employees, I'm a curiously happy PacBell customer.

At the time I couldn't recall the one specific project I was thinking of, but a brief search dredged it up... AT&T's Crowds, a really nifty idea.

I had two mis-recollections from senior sem presentations I saw last year... I thought Anonymizer, wasn't a commercial project, but it turns out that it is. I'm not familiar with them at all, so I can't speak to their approach. I'd also thought that onion-routing was a little beyond the experimental stage, but I guess I was wrong.

I've said it before (so have others, in this very discussion) and I'll say it again:

You need VNC.

I run headless linux boxen here and access them from my (spit) NT workstation. Stuff I like:

• It's stateless, unlike X, so when your desktop machine goes belly-up your headless machines don't even notice.
• It's cross-platform. I can access my little penguins from my Palm, if I were inclined.
• It's virtual (on linux) - I don't even need a video card in the linux box, and I can run at any res (provided I've the memory for it). Which means that I can have massive desktops on the linux machines and view them on my 21" monitor. How many 21" monitors do you have? How many boxes do you have? Don't you wish all those boxes could have a large monitor? Now they can!
• It's Open Source. Dammit, it's GPL'd. Development is active and fast.
• It's stable. As a rock.
• It's ssh'able.

That's the last time I'm plugging VNC here. If you haven't tried it, it's your own fault.

You can find VNC, which is under the GPL, here:
http://www.uk.research.att.com/vnc/

--

As far as your last comment about tunnelling "... secure data through HTTP" goes, I think ATT&T Labs is working on a proxy system intended for anonymity. Although, I don't see anything addressing encryption, per se.

As far as your last comment about tunnelling "... secure data through HTTP" goes, I think ATT&T Labs is working on a proxy system intended for anonymity. Although, I don't see anything addressing encryption, per se.

The Chicagoland area is positively sprouting positions for technical workers. They're one of the fastest growing VC areas outside of Silicon Valley. There's a a huge technical corridor stretching from Joliet nearly to the Illinois/Wisconsin border.

Not to mention that Chicago's NAP sees more traffic coming through than ANYWHERE else on the planet.

Cablemodem and DSL services are emerging in the area (Ye God! There's so many DSL companies advertising out here now it's disgusting!) For cable, look at AT&T, MediaOne, and @Home. For listings of DSL providers, just hit 2Wire.com

How much you make depends on what you know. Decent wages for a tech support drone at an ISP is about $9-11(USC) an hour. Some positions down at the law firms downtown pay as much as $40K a year for people with basic techsup skills, some Unix experience, and some network experience.

Housing can be anywhere between $500-900 for a 1 bedroom apartment. Between $750-1200 for a 2 bedroom. (Not sure for 3.)

Depending on how far out you live, and what neighborhoods, actually buying a house may be cheaper. In Berwyn, the median price of a house is about $140K (some condos go for around $50K).

Further south in Downer's Grove/Darien, housing is in the $180-200K range, with condos going for between $60-100K.

If you live out further west in areas like Plainfield (starting to build up), housing starts around $120K and goes up from there.

The only major hassle in Chicago is the traffic. They have 5 major tollways, and 4 major freeways. And right now, they're working on most of them (hopefully to be done by the end of this year). For night-shift workers, this isn't too bad. For 9-5'ers and evening workers, it can be a big hassle.

Also, parking downtown is disgustingly expensive. Luckily there's a decent rail system in Chicago with several major lines (IIRC all of them are now open nearly 24/7).

There's two major airports for commuting (O'Hare and Midway). Midway is undergoing major construction right now to add a huge parking structure, and additional terminals.

Hope this helps.


Chas - The one, the only.
THANK GOD!!!

Setup the other machine and your machine with VNC and you will not have to "go to it".

The separate question is whether IHighway is big enough to be a peer or if they've got to buy transit service. Most of the Tier I providers will peer with other large nationwide carriers, but will treat local ISPs like they treat other non-ISP businesses, and charge money for service unless there's a really interesting traffic mix.

Just try taking advantage of platform-specific features from a Java program, or making a Java program work in a way that is expected by the users of native programs on each machine you might try to run it on.

Bjarne Stroustrup, inventor of C++, has much the same opinion in his statement about Java in his FAQ

.

There is no question that Plan 9 is more elegant and clean, but it also lacks a lot of functionality. Whether it's easier to add all that stuff to Plan 9 (and whether the result will still be elegant and clean), or whether it's easier to add Plan 9 ideas to Linux, to me, is still an open question. Both paths would lead to roughly the same end result: a complex system with better support for distributed computing.

Either way, the open source release of Plan 9 is a good starting point because it gets those ideas out into the mainstream.

CP

Pretty much anything related to software development. I mean you get a free (high quality) optimizing compiler, debugger, a whole load of libraries, etc.

Network servers. I hope I don't need to say any more about that.

Remote access. I can log into my computer at work from home, and do everything I could do if I was actually sitting in my office!

Mathematical typesetting. Nothing beats TeX and LaTeX when it comes to this. Sure, there's TeX for Macs, but (AFAIK) you have to buy it.

I admit that if I was building a system purely for free software development or as a network server, I wouldn't think of the Mac first. However, I don't think these are the kind of "applications" the original author had in mind (except maybe mathematical typesetting).

Emacs is the ultimate windowing system. I haven't gotten around to write a window manager in elisp yet, but I'm sure there's somebody out there that would do it. :)

Both gwm and the more recent Sawfish are extensible window managers which are implemented in an elisp-like language.

Somebody suggested, as a 'blue-sky' feature for GNOME a while ago, a kind of Emacs window manager where you have each app open in its own buffer and switch between them with C-x b, C-x o and so on. For the special case of shell buffers, we already have this. Something like a VNC-mode for XEmacs would probably allow you to implement this fairly easily.

With VNC (Virtual Network Computing) or something like it, any dropped connection means you just pick up where you left off when you get your connection back. This just follows the "ASP" (Application Service Provider) concept that Sun and Oracle have been pushing for a while.

I don't think you're really very tech-savvy. The difference is that Pascal and VB are languages for people incapable of understanding C, and shouldn't really be allowed to program at all. C++ is for people who are capable of understanding C, but choose to ignore things like code size and efficiency.

People who live in glass houses... Or maybe it's pots and kettles. Anyways you're description of the differences between the languages A) isn't funny (not just because I'm pedantic but because it's really not funny) and B) isn't accurate. I'm sorry to break this to you but C++ is as efficient and the code size is comparable to C. While propagating myths is fine and we all have our departure points from reality I believe you should attempt to rectify this inaccuracy in your own life.
Here are some helpful links to start you on your journey into knowledge:
Efficiency info
Bjarne's homepage
Bjarne answers a lot of the questions you might have on his page. That's where I would start.
None of this is in any way meant to state that the original poster wasn't a clueless troll, or that C++ is inherently better than C.
good luck. gid-foo

The ATT Crowds system shows how to build these kinds of distributed systems without traceability.

Of course, ZeroPaid's approach is also socially questionable and rather naive from a social point of view. The assumption that most people who download their files are "guilty" is a bad one. Many of them may be other people on the same mission as they are. Others may be automated programs or just promiscuous downloaders. Concretely, wouldn't you assume that the FBI is searching for and downloading just those files?

I checked crowds.org and its not regestered. crowds.com is owned by some German guy who hasn't put much of anything up. And crowds.net is also regestered.

Tip: use a search engine. I recommend Google. Try searching for "crowds proxy". You should find The Crowds Home Page.

• Electronic Content and Civilization's Discontent (1994)
• Fighting some of Slashdot's battles in 1996 by opposing some WIPO treaties
  

• 
  Some AT&T corporate PR outlining a few of the Library's Digital initiatives
• Remember when the GAO told him he wasn't authorised to disburse or use funds given by foreign libraries in cooperative projects?

• Withdrawing a travelling show of slavery-era photographs
  

__________

Also known as the Trojan Room Coffee Pot, which is located in the Trojan Room. It was around in 1991, but not connected to the internet (there wasn't one then) until later (see the biography).

A close relative (but much younger) is AT&T Laboratories Cambridge's Smart Beverage Dispenser. It, however, does not yet conform to rfc2324, Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), and rfc2325, Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2, "is not sufficiently flexible to represent the advanced multiple beverage dispenser". But, "Development of a revised MIB supporting multiple dynamic beverage options is under way". Hooray!

Also known as the Trojan Room Coffee Pot, which is located in the Trojan Room. It was around in 1991, but not connected to the internet (there wasn't one then) until later (see the biography).

A close relative (but much younger) is AT&T Laboratories Cambridge's Smart Beverage Dispenser. It, however, does not yet conform to rfc2324, Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), and rfc2325, Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2, "is not sufficiently flexible to represent the advanced multiple beverage dispenser". But, "Development of a revised MIB supporting multiple dynamic beverage options is under way". Hooray!

GraphViz is non interactive; instead you give feed it a text file containing a description of your (arbitrarily complex) graph and it spits out very nice output. I mean really nice. Check it out at the graphviz homepage.

As far as I know, Cygnus is still free, and you can access the original web pages, and cvs trees as normal at the old homepage of http://sourceware.cygnus.com.

Cygnus used to charge previously for the product as well; if you want nice manuals and stuff then you pay, which makes perfect sense.

To quote directly from the Cygnus webpage itself:


How does Red Hat's acquisition of Cygnus affect this site?
For now, very little. We thought about "conducting a process of re-engineering and re-branding with the aim of integrating our free software community outreach programs into our corporate objectives". But then we said "naah, let's just continue to have a great site to develop free software and work on making it even better".

In particular, we plan to be careful about changing the host name sourceware.cygnus.com or anything else which may require you to update your habits, CVS/Root files, etc. The name will have to change but before we go changing things around we'd kind of like to at least have a plausible guess about what we are going to change them to :-). We don't want you to have to switch over twice.



Incidentally, you may also want to check out AT&T's UWIN, at http://www.research.att.com/sw/tools/uwi n/ as well; very cool, does much the same thing.

HTH.
Anil

works quite well, thank you, other than the NT 3.51 desktop (won't handle some software that needs NT4). Costs a beejezus. To get a real command line I can work with on NT, I use VNC.

B.S.E.E., McSE

(i am not too familiar with VNC and definitely no experience with Citrix...await comments from pros, especially on how VNC compares with Citrix)

Assuming (as stated above) that the market for these devices is Fortune 1000, maybe Wyse/anybody can use VNC-Linux to solve this driver issue.

VNC already maps the local serial port, PS2 and keyboard to the VNC server. this is how it forwards the mouse/keyboard input to the VNC server (which can be Linux,Win9x,NT....)

VNC is open source, so Wyse could have hacked it to forward (+return path) the local thin client serial/parallel/whatever ports to an NT/Win machine running VNC server. the drivers for these devices (bar-code readers, scanners, printers etc) would be available on NT/Win. ....that's it.

btw, the VNC team is already quite advanced on this. Read about CORBA/Out going connections here.

having something like this available would open a lot of other interesting possibilities. an example of embrace and extend :)

(i am not too familiar with VNC and definitely no experience with Citrix...await comments from pros, especially on how VNC compares with Citrix)

Assuming (as stated above) that the market for these devices is Fortune 1000, maybe Wyse/anybody can use VNC-Linux to solve this driver issue.

VNC already maps the local serial port, PS2 and keyboard to the VNC server. this is how it forwards the mouse/keyboard input to the VNC server (which can be Linux,Win9x,NT....)

VNC is open source, so Wyse could have hacked it to forward (+return path) the local thin client serial/parallel/whatever ports to an NT/Win machine running VNC server. the drivers for these devices (bar-code readers, scanners, printers etc) would be available on NT/Win. ....that's it.

btw, the VNC team is already quite advanced on this. Read about CORBA/Out going connections here.

having something like this available would open a lot of other interesting possibilities. an example of embrace and extend :)

U/WIN from AT&T does this, se http://www.research.att.com/sw/tools/uwi n/.

This story got me to VNC and it has made a big difference to my working. Cannot recommend it enough.

Workspot is good for people to tryout/use Linux ...but for people who already have Linux ...VNC is THE thing to run.

I run VNC on my home DSL connected Linux PC. To take care of dynamic IP addresses on my DSL connection i use the superb DNS service from DHS, these guys are great!

Now, where ever i am, using VNC-SSH-DHS combo i can easily and securely reach my home Linux desktop with it's GB's of space and all the sw/code/tools that i have installed.

btw, a great SSH client for Windows without any crypto restrictions is TTSSH.

i have reached Nirvana (atleast for some time :)

Quantum cryptography is (assuming quantum theory is correct) an unbreakable cryptosystem. A basic primer of Q Cypto is here. This also gives details of how to implement Q. Crypto - test of quantum encrypted links of over 1km have already been demonstated: a far cry from "you can't develop [it] until you solve some general problems".

We need an "I am not a scientist" label (like IANAL) for posts like that one.