Re: JavaLinux for servlets [off-topic]
>The comments regarding applets have nothing to do with C or JNI. Again I'm >trying to say that applets do not make sense in the context of HTML. It's >not Java's fault, it's just how things are. I don't see how this is true. HTTP is supposed to be a stateless, object- oriented protocol which simply uses HTML as one of its glue objects. Neither the protocol itself, nor the HTML spec state that the objects themselves must be stateless, nor does it attempt to define the objects. While I mistrust the embedded VM's in the browsers, and personally don't like applets, it is in no way the fault of HTML or HTTP. The browser VM's just typically suck. Used with a good VM, and in a secure/unrestricted area, applets can be a great tool. -- ([EMAIL PROTECTED]) Non-sequiturs make me eat lampshades.
Re: Wierd results using binfmt_misc
> Now for the wierd part. It all works just fine when I am logged in as > root. But when logged in as myself, java reports that it can't find my > class. What could cause this? I have loaded up my javawrapper script > with a bunch of echo statements and am convinced that it produces the > same output under both logins. Neither as root nor as myself do I have > a CLASSPATH variable defined. So what else could it be? Did you make sure that all your classes are o+rx, including the new classes that you have just built? > Or is it just a bad idea to use a package member class as the class > holding main()? I typically don't, but I don't see how that would cause this problem. -- ([EMAIL PROTECTED]) Mandrell: "You know what I think?" Doctor: "Ah, ah that's a catch question. With a brain your size you don't think, right?" -- Dr. Who -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Wierd results using binfmt_misc
> I do not, however, use my system under "root" *except* when absolutely > required (as in, when doing admin work). This is a good habit to be > in since it tends to reduce your chances of really getting messed up > or having some unwanted access into your system. It also helps > identify things like access rights issues in your directories and files > since non-root users actually are held to them. It is an especially bad idea to do development work on your system under root. Unless, of course, you enjoy re-entering all of your code, and re-installing your system every few hours ;-) -- ([EMAIL PROTECTED]) "And what will you do when you grow up to be as big as me?" asked the father of his little son. "Diet." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[email protected]
> However, even so, shouldn't class files as opposed to source > files normally be readable by anyone? That was not the case here. > My class files seem to be readable only by owner and group, not everyone. Your umask is probably set to 027. Check it by typing 'umask.' If it is set, you can make it less restrictive by doing 'umask 022.' This will give the owner read/write permissions, and group & other read permissions whenever you create a new file. -- ([EMAIL PROTECTED]) Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
