In other news, Terrence Philip, a manager for a well-known Canadian company was arrested yesterday. He was accused of possessing a dangerous computer virus.
Philip claims that he didn't know about the virus and his computer was merely infected by it.
"Bullshit, ", said officer Barbrady, who've searched the offender's machine, "his box was full of this stuff - nobody keeps so many viruses without wanting to do evil things with them".
I tend to disagree with claims that primitive types should be taken away. But regardless of that, integer (byte, int, etc.) types, both primitive and object-wrappers, should receive their unsigned versions - currently there are only signed ones. So e.g. C style following declarations should be possible:
unsigned int foo; unsigned byte bar;
and additional wrapper classes should be present:
UnsignedByte quux = new UnsignedByte(231);
When coding my own base64 encoder, I had to do lots of bit-juggling that wouldn't have been requred if I've had unsigned types in Java.
For example, I've needed patch-innobase_include_univ_i to compile any recent MySQL to compile on OpenBSD 3.1. That patch is quite funny:
#define UNIV_INLINE __inline #else /* config.h contains the right def for 'inline' for the current compiler */ -#if (__GNUC__ == 2) -#define UNIV_INLINE extern inline -#else -/* extern inline doesn't work with gcc 3.0.2 */ +/* mysql people don't understand extern inline */ #define UNIV_INLINE static inline
When installing MySQL 4.0.2 I've applied all of those patches, and then configured, compiled and made make install.
The database new MySQL daemon started up and operated fine (with previous version's data files), but mysql 4 client were unable to connect (I've got an "ERROR:" error message. Tells much, doesn't it?).
So, to summarize, wait some more time, at least until they release a beta.
Stealing cell phones is already illegal, yet cell phones are getting stolen. Do you really think that criminals are more likely to abide by a law that prohibits changing a GSM phone's IMEI number, than a law that already prohibits stealing them?
"If your not ready to answer these questions, then your not ready to
pass this legislation."
And so on....
Man, you could really use correct grammar and spelling. It really matters here. Those mistakes are clearly visible even for me, English not being my primary language...
The problem with this approach (which Microsoft, Apple, etc. recognized back in the '80s but we still haven't caught up with) is the notion that text is not the only thing that needs to be cut, copied and pasted among and across applications.
Thus, there is inherently a different semantic involved when transferring objects other than text, because X doesn't know how to handle those.
X knows nothing of moving a picture between a charting application and a word processor, for instance. Nor should it.
One of the really cool, yet rarely used, features of the selection mechanism is that it can negotiate what data formats to use. It's not just about text. When one application asks another for the selection, part of their communication involves the requester asking the owner for the list of types in which they are capable of delivering the selection data; then the requester picks the format they like best, and asks for it that way.
As a simple example, suppose there is a program displaying text in multiple fonts. When pasting that into a text-only program, you'd want to paste only the text. But when pasting that into a word processor, you'd want to keep the font information: if both applications spoke HTML, they could use that as the intermediate format by which they transferred the data.
More complex things are possible, too: for example, when an image is selected on a web page, the web page displayer could offer to serve that up as raw image bits; or as JPEG data; or as the original URL of the image. When trying to copy and paste an image into a text editor that can't do images, the text editor might decide that the next best thing would be to paste the filename of the image, or the URL.
The content negotiation mechansim is very powerful, and I wish more applications would take advantage of it.
For examples of how to use it, see the files select.el and/or x-select.el from any XEmacs distribution. There are some utility functions in there that will let you experiment with content negotiation with other apps, see what types the apps are capable of converting to, etc. For example:
(x-get-selection-internal 'PRIMARY 'TARGETS) ==> [ TARGETS TIMESTAMP TEXT STRING LENGTH FILE_NAME OWNER_OS HOST_NAME USER CLASS NAME CLIENT_WINDOW PROCESS COMPOUND_TEXT]
> 10. No easy way to configure X - especially change > resolution on the fly. > Actually, it couldn't be easier to change > resolutions on the fly. Hold ctrl and alt, then > hit - or + on the numberic key pad. This cycles > you through all your selected resolutions, on the > fly. Just make sure you selected all the ones you > want when you setup x (Red Hat users use > Xconfigurator to select resolutions).
I think what the original poster had in mind was the ability to change the resolution AND the size of the desktop on the fly, lik in MS Windows.
Currently it's impossible in XFree. With XFree, you have to exit X, edit XF86Config, and launch X again.
When you press CTRL - ALT - +,-, what you get is a different size of window through which you look at the desktop. And the desktop is still the same size. For example, if you are currently working in 1024X768 and press CTRL - ALT - -, your display will switch to 800X600, but the desktop is still 1024x768! You are only looking at your big desktop through a smaler window. When you move the cursor beyond the edge of your display, it will scroll.
Such behaviour is almost completely useless, very uncomfortable, but still resolution switching works only in this way since the infant times of XFree!
In MS Windows, when you switch to a different resolution, the desktop is resized too, icons are automatically laid out to fit to the new size of desktop, and you see the whole desktop regardless of what resolution you work in. If you work in 800X600, the desktop is 800X600. If you switch to 640X480, the desktop is resized to 640X480. No stupid scrolling and such nonsense.
> Compressing such images with JPEG will give you > ugly "ringing" artifacts, since the lines are > essentially infinite-frequency "spikes" which you > can't capture completely.
The occurence of those artifacts is called the Gibb's effect.
solution for projects' main FTP sites
on
KDE 3.0 is Out
·
· Score: 3, Informative
There's a solution for that different nonprofit projects' FTP main sites that don't want to be hammered before mirrors catch up.
Junkies posting stories to Slashdot use ftp. Mirrors use rsync.
So just make it so that rsync and ftp processes access the release directory as different users on the server. Don't allow access to the FTP user on the new release directory for some time until all mirrors update through rsync. Only then chmod the latest release directory to let anonymous ftp users in. Chmod only takes a fraction of second to execute. So in addition, there will be no poor soul that in a hurry would download a partially copied, uncomplete file...
X Window system is flawed. The client-server model is inversed in some bizarre way that a user runs the server and he needs to connect the apps he starts to this server (the only benefit of this, being that the user can in one session start apps that display on different devices/workstations that run separate X severs - almost totally useless...). If the server exits, all apps have to exit too.
Only one user can use the server at the same time because the X server is bound th a single, static set of physical display device(s) and input devices... No shared sessions for presentations/courses etc are possible.
Then there comes (my favourite, but still lacking) AT&T's Virtual Network Computing (VNC) which on UNIX-alikes is basically a wrapper that is run on the same machine that applications and acts as a X server for them, while at the other end accepting connections from VNC clients. This way sessions can be shared between users, and one can disconnect from the vnc server (the apps still run uninterrupted, attached to the X11 end of VNC server) then connect later, or from a different machine. So VNC is basically a great step forward. But its development went into stagnation (It hasn't been updated in long, long time) while it lacks many features:
a standard for session management: a VNC server session has to be started locally from the inside of the machine where VNC server and (usually) most clients will run, so one first has to SSH there. You can't just fire off the VNC client, type in the host address, then connect and see a list of active VNC sessions/servers to choose from/kill them/create new active sessions. Of course at system startup you can fire off several VNC servers that run constantly with Gnome/KDE/whatever sessions, but creating 10 of them is enough to bring a P3 666/512 MB RAM to its knees. And users don't need access 24 hrs/a day, so that is just a waste of precious computrons... And if a session gets messed up (you'd be surprised how often it happens with KDE and Gnome, or if someone tries to start an app that users OpenGL or hardware overlays), there's no easy way for users to kill/restart it
data compression. there are zlib patches, but one has to do lots of customization to make everything work (patching the server, patching the clients... You get the idea. Someone at AT&T should have long time ago taken the best compression patch and integrated it into the official package, but it seems noone is maintaining VNC anymore...
session recording/playback capabilities (which are essential for e-learning solutions and demos/presentations). Again there are patches, but they require messing around...
Shared sessions don't have a notion of per-user permissions, every user connected to a session has privileges that allow moving the mouse pointer, sending keystrokes etc.
If you run an online course/demo/presentation and someone starts fooling around... You get the idea.
Berlin project is still in its infancy and far from being complete.
I haven't tried Linux Terminal Server Project, but it is, well, Linux only:(
Besides, it seems to me as being only a thin, networked X-terminal. Can someone elaborate on its capabilities pertaining to sharing sessions between users/connecting from different machines to the same session, disconnecting from sessions without killing them etc?
Unfortunately for GPLed software, Microsoft's remote resktop solutions offer most of what I've enumerated here, and Citrix Metaframe is even better...
So closed-source software is at an advantage here.
> Shooting people is something where, if a vest is > not worn, can be expected to cause serious > injury or death. Even if a vest is worn, the > outcome can be injury, and death has been known > to happen. > A more accurate analogy would be tapping someone > on the shoulder to see if they are alive. But you > don't expect that one in tens of thousands happens > to have a very sore shoulder, and this tapping > causes great pain.
What about if you tap someone on the shoulder and scare them to death?
Just installed OpenBSD 3.0 today.
The new Packet Filter' syntax is somewhat backwards-compatible with IPFilter, the most significant difference being that with PF you now must specify protocol when specifying ports, so for example if with IPF you had:
block in on fxp0 from any to any port = 137
with PF you have to change it to:
block in on fxp0 proto { udp, tcp } from any to any port = 137
And you place the default donfiguration in/etc/pf.conf, not/etc/ipf.rules.
>Did anyone notice that one of those products did
>really change to the worse (besides the ads in ICQ,
>which is ok I guess because they are not that
>annoying)?
>
>No, no one noticed, because they didn't.
You must have forgotten about enforced license managment for WMA audio in Winamp?
Slashdot Mirror
In other news, Terrence Philip, a manager for a well-known Canadian company was arrested yesterday. He was accused of possessing a dangerous computer virus.
Philip claims that he didn't know about the virus and his computer was merely infected by it.
"Bullshit, ", said officer Barbrady, who've searched the offender's machine, "his box was full of this stuff - nobody keeps so many viruses without wanting to do evil things with them".
But it still doesn't support user-defined (in PL/SQL) functions that are able to operate on and return row sets.
What about a better name: Personal License Migration Service futility ?
I tend to disagree with claims that primitive types should be taken away.
and additional wrapper classes should be present:But regardless of that, integer (byte, int, etc.) types, both primitive and object-wrappers, should receive their unsigned versions - currently there are only signed ones. So e.g. C style following declarations should be possible:
When coding my own base64 encoder, I had to do lots of bit-juggling that wouldn't have been requred if I've had unsigned types in Java.
Not to mention that things that are politically correct now may stop being p-correct in the future...
Hypocrisy, not Hypocracy.
Please, learn to spell important words properly. Or use a spellchecker, you do need it.
Yes, effecting service to your customers would be a disaster... You can do better without them ;)
I've tried compiling MySQL version 4.0.2 on OpenBSD.
First of all, to even get this thing compiled, you'll probably need to apply patches from the ports. See http://www.openbsd.org/cgi-bin/cvsweb/ports/databa ses/mysql/patches/ for OpenBSD ports patches.
For example, I've needed patch-innobase_include_univ_i to compile any recent MySQL to compile on OpenBSD 3.1.
That patch is quite funny:
When installing MySQL 4.0.2 I've applied all of those patches, and then configured, compiled and made make install.
The database new MySQL daemon started up and operated fine (with previous version's data files), but mysql 4 client were unable to connect (I've got an "ERROR:" error message. Tells much, doesn't it?).
So, to summarize, wait some more time, at least until they release a beta.
Stealing cell phones is already illegal, yet cell phones are getting stolen.
Do you really think that criminals are more likely to abide by a law that prohibits changing a GSM phone's IMEI number, than a law that already prohibits stealing them?
Hand out a thousand Region-free copies of the Matrix? My God, doesn't this person have any morals?
"Is it compatable with my circuit?"
"If your not ready to answer these questions, then your not ready to pass this legislation."
And so on....
Man, you could really use correct grammar and spelling. It really matters here. Those mistakes are clearly visible even for me, English not being my primary language...
This is not true.
See this article by Jamie Zawinsky: http://www.jwz.org/doc/x-cut-and-paste.html
The interesting part:
One of the really cool, yet rarely used, features of the selection mechanism is that it can negotiate what data formats to use. It's not just about text. When one application asks another for the selection, part of their communication involves the requester asking the owner for the list of types in which they are capable of delivering the selection data; then the requester picks the format they like best, and asks for it that way.
ICCCM:As a simple example, suppose there is a program displaying text in multiple fonts. When pasting that into a text-only program, you'd want to paste only the text. But when pasting that into a word processor, you'd want to keep the font information: if both applications spoke HTML, they could use that as the intermediate format by which they transferred the data.
More complex things are possible, too: for example, when an image is selected on a web page, the web page displayer could offer to serve that up as raw image bits; or as JPEG data; or as the original URL of the image. When trying to copy and paste an image into a text editor that can't do images, the text editor might decide that the next best thing would be to paste the filename of the image, or the URL.
The content negotiation mechansim is very powerful, and I wish more applications would take advantage of it.
For examples of how to use it, see the files select.el and/or x-select.el from any XEmacs distribution. There are some utility functions in there that will let you experiment with content negotiation with other apps, see what types the apps are capable of converting to, etc. For example:
The full technical documentation for this stuff is in the X11R6 Inter-Client Communication Conventions Manual, section 2: ``Peer-to-Peer Communication by Means of Selections.''
> 10. No easy way to configure X - especially change
> resolution on the fly.
> Actually, it couldn't be easier to change
> resolutions on the fly. Hold ctrl and alt, then
> hit - or + on the numberic key pad. This cycles
> you through all your selected resolutions, on the
> fly. Just make sure you selected all the ones you
> want when you setup x (Red Hat users use
> Xconfigurator to select resolutions).
I think what the original poster had in mind was the ability to change the resolution AND the size of the desktop on the fly, lik in MS Windows.
Currently it's impossible in XFree. With XFree, you have to exit X, edit XF86Config, and launch X again.
When you press CTRL - ALT - +,-, what you get is a different size of window through which you look at the desktop. And the desktop is still the same size.
For example, if you are currently working in 1024X768 and press CTRL - ALT - -, your display will switch to 800X600, but the desktop is still 1024x768! You are only looking at your big desktop through a smaler window. When you move the cursor beyond the edge of your display, it will scroll.
Such behaviour is almost completely useless, very uncomfortable, but still resolution switching works only in this way since the infant times of XFree!
In MS Windows, when you switch to a different resolution, the desktop is resized too, icons are automatically laid out to fit to the new size of desktop, and you see the whole desktop regardless of what resolution you work in. If you work in 800X600, the desktop is 800X600. If you switch to 640X480, the desktop is resized to 640X480. No stupid scrolling and such nonsense.
When those guys are going to run out of superlatives?
> I mean, I'm stuck at home running an animation
> rendering, so, um, I have an excuse. But what
> about the rest of you!
The excuse for the rest of us is that we are in different time zones.
> Compressing such images with JPEG will give you
> ugly "ringing" artifacts, since the lines are
> essentially infinite-frequency "spikes" which you
> can't capture completely.
The occurence of those artifacts is called the Gibb's effect.
There's a solution for that different nonprofit projects' FTP main sites that don't want to be hammered before mirrors catch up.
Junkies posting stories to Slashdot use ftp.
Mirrors use rsync.
So just make it so that rsync and ftp processes access the release directory as different users on the server.
Don't allow access to the FTP user on the new release directory for some time until all mirrors update through rsync. Only then chmod the latest release directory to let anonymous ftp users in.
Chmod only takes a fraction of second to execute.
So in addition, there will be no poor soul that in a hurry would download a partially copied, uncomplete file...
See Hexonet's RFB software page, I just discovered them thanks to their package being included in Mandrake 8.2 (rfb-0.1.2-7mdk.i586.rpm).
Seems like a good follow-up to (seemingly dead) AT&T's VNC project...
BTW, if you have Mandrake 8.2, be sure to check out the rfbdrake utility (rfbdrake-0.8.2-13mdk.i586.rpm)! It looks awesome!
But it only works with SSH, not SFTP... If I disallow shell logins for a user, iXplorer is of no use.
X Window system is flawed. The client-server model is inversed in some bizarre way that a user runs the server and he needs to connect the apps he starts to this server (the only benefit of this, being that the user can in one session start apps that display on different devices/workstations that run separate X severs - almost totally useless...). If the server exits, all apps have to exit too. Only one user can use the server at the same time because the X server is bound th a single, static set of physical display device(s) and input devices... No shared sessions for presentations/courses etc are possible.
Then there comes (my favourite, but still lacking) AT&T's Virtual Network Computing (VNC) which on UNIX-alikes is basically a wrapper that is run on the same machine that applications and acts as a X server for them, while at the other end accepting connections from VNC clients. This way sessions can be shared between users, and one can disconnect from the vnc server (the apps still run uninterrupted, attached to the X11 end of VNC server) then connect later, or from a different machine. So VNC is basically a great step forward. But its development went into stagnation (It hasn't been updated in long, long time) while it lacks many features:
Berlin project is still in its infancy and far from being complete.
I haven't tried Linux Terminal Server Project, but it is, well, Linux only :(
Besides, it seems to me as being only a thin, networked X-terminal. Can someone elaborate on its capabilities pertaining to sharing sessions between users/connecting from different machines to the same session, disconnecting from sessions without killing them etc?
Unfortunately for GPLed software, Microsoft's remote resktop solutions offer most of what I've enumerated here, and Citrix Metaframe is even better... So closed-source software is at an advantage here.
> Shooting people is something where, if a vest is
> not worn, can be expected to cause serious
> injury or death. Even if a vest is worn, the
> outcome can be injury, and death has been known
> to happen.
> A more accurate analogy would be tapping someone
> on the shoulder to see if they are alive. But you
> don't expect that one in tens of thousands happens
> to have a very sore shoulder, and this tapping
> causes great pain.
What about if you tap someone on the shoulder and scare them to death?
> Sony: Tell you what. We'll Rochambeau you for it. ...
That's Roshambeau (see this node @ everything2).> MS: What's Rochambeau?
If so, then it comes out Bill Gates was right !
Just installed OpenBSD 3.0 today.
/etc/pf.conf, not /etc/ipf.rules.
The new Packet Filter' syntax is somewhat backwards-compatible with IPFilter, the most significant difference being that with PF you now must specify protocol when specifying ports, so for example if with IPF you had:
block in on fxp0 from any to any port = 137
with PF you have to change it to:
block in on fxp0 proto { udp, tcp } from any to any port = 137
And you place the default donfiguration in
>Did anyone notice that one of those products did
>really change to the worse (besides the ads in ICQ,
>which is ok I guess because they are not that
>annoying)?
>
>No, no one noticed, because they didn't.
You must have forgotten about enforced license managment for WMA audio in Winamp?