It's used for more than gaming, but yeah I have a ton of games that use IPX and I am sure other people do as well. IPX is also lower-latency than TCP or UDP, but it only works on a LAN. I have often considered using IPX only on my LAN and using a Linux server between my DSL modem and LAN to convert the IPX data to TCP data and send it on its way, but never got around to implementing it. That'd make hacking my network rather difficult!
You are right about only root dealing with mounting, but my normal users can mount, unmount, read, and write NTFS drives both internal and external, as well as optical and flash media. They can also share files in their home directories using KDE. Not allowing IPX the same privilege and not having an easy way to do so is just bad design.
IPX and AMD64 not mixing?
Not trying to revive this thread, but I wanted to mention that in a last-ditch effort to make the kernel allow me to use IPX with Wine, I added my account to the root group, rebooted, logged in, and tried Wine. Still no go. I'd get as far as being allowed to type in a name for the server that I am attempting to create, but when I attempt creation, nothing happens. I don't know whether that means that Wine has an issue with IPX in a 64bit environment or what, but I wanted to post about it since I was physically in the root group and still unable to create an IPX game.
IPX and AMD64 not mixing?
On Fri, Apr 3, 2009 at 3:45 AM, Sephiroth <[email protected]> wrote:
The root group is just the root user's default group.
Adding a user in the root group will only give you additional
permissions on files / devices with root as their group and with
higher permission than "other".
It will not give you permissions unrelated to the file system.
You can add another user with UID 0 if you want another root user.
complete IP stack on the card. ARP might cause initial communication
between two hosts ta have slight latency and might not be needed for
IPX. (I'm not familiar with the mechanisms that IPX use if the AMC
address is not included in the network layer address..)
IPX is fully routable, but I do not know of any providers providing
IPX network access, which means that it need all kind of tunneling to
run over the IP internet. (If you supply your own IPX routeres you can
build an entire corporate network on IPX...)
Or you can try this:
http://support.novell.com/techcenter/ar ... 60902.html
Gert
Rooot is a user not a group.Not trying to revive this thread, but I wanted to mention that in a last-ditch effort to make the kernel allow me to use IPX with Wine, I added my account to the root group, rebooted, logged in, and tried Wine. Â Still no go. Â I'd get as far as being allowed to type in a name for the server that I am attempting to create, but when I attempt creation, nothing happens. Â I don't know whether that means that Wine has an issue with IPX in a 64bit environment or what, but I wanted to post about it since I was physically in the root group and still unable to create an IPX game.
The root group is just the root user's default group.
Adding a user in the root group will only give you additional
permissions on files / devices with root as their group and with
higher permission than "other".
It will not give you permissions unrelated to the file system.
You can add another user with UID 0 if you want another root user.
Tons of OLD games...It's used for more than gaming, but yeah I have a ton of games that use IPX and I am sure other people do as well.
Many modern LAN cards accelerate TCP / UDP and some even contain aIPX is also lower-latency than TCP or UDP, but it only works on a LAN.
complete IP stack on the card. ARP might cause initial communication
between two hosts ta have slight latency and might not be needed for
IPX. (I'm not familiar with the mechanisms that IPX use if the AMC
address is not included in the network layer address..)
IPX is fully routable, but I do not know of any providers providing
IPX network access, which means that it need all kind of tunneling to
run over the IP internet. (If you supply your own IPX routeres you can
build an entire corporate network on IPX...)
It would also require that you modify all your software to speak IPX...I have often considered using IPX only on my LAN and using a Linux server between my DSL modem and LAN to convert the IPX data to TCP data and send it on its way, but never got around to implementing it. That'd make hacking my network rather difficult!
Or you can try this:
http://support.novell.com/techcenter/ar ... 60902.html
Gert
You're right, I wasn't thinking that my common programs like Firefox might not even know what IPX is. Still, it would be one heck of a sweet setup if it was possible!
As for IPX being superior, it simply is. The problem is with range. I don't remember the specifics, but IPX doesn't travel very far for some reason. I do know that Intel (maybe IBM?) has a buried cable running from an office somewhere in the northwest USA to another office southwest and a state or so away. Why don't they use the Internet? They use IPX! They also have some hardware on that line every so many yards to clean up the signal and send it on its way again. I imagine it's very expensive, but they want to use IPX for some reason.
I also never tried using the root group before, so I honestly didn't know that it didn't grant root privileges. I've used Linux for years, but never had this sort of problem before, so I never tried such a bad thing. Thanks for the information though!
As for IPX being superior, it simply is. The problem is with range. I don't remember the specifics, but IPX doesn't travel very far for some reason. I do know that Intel (maybe IBM?) has a buried cable running from an office somewhere in the northwest USA to another office southwest and a state or so away. Why don't they use the Internet? They use IPX! They also have some hardware on that line every so many yards to clean up the signal and send it on its way again. I imagine it's very expensive, but they want to use IPX for some reason.
I also never tried using the root group before, so I honestly didn't know that it didn't grant root privileges. I've used Linux for years, but never had this sort of problem before, so I never tried such a bad thing. Thanks for the information though!
IPX and AMD64 not mixing?
Sephiroth wrote:
common use. There was a protocol that routed IPX over IP, but since IP
became the defacto protocol it is not used much.
BTW, IBM uses SNA to talk between some of their systems and it is very
touchy about delay.
James McKenzie
Interesting story, but IPX is not routable, that is why it is not inYou're right, I wasn't thinking that my common programs like Firefox might not even know what IPX is. Still, it would be one heck of a sweet setup if it was possible!
As for IPX being superior, it simply is. The problem is with range. I don't remember the specifics, but IPX doesn't travel very far for some reason. I do know that Intel (maybe IBM?) has a buried cable running from an office somewhere in the northwest USA to another office southwest and a state or so away. Why don't they use the Internet? They use IPX! They also have some hardware on that line every so many yards to clean up the signal and send it on its way again. I imagine it's very expensive, but they want to use IPX for some reason.
I also never tried using the root group before, so I honestly didn't know that it didn't grant root privileges. I've used Linux for years, but never had this sort of problem before, so I never tried such a bad thing. Thanks for the information though!
common use. There was a protocol that routed IPX over IP, but since IP
became the defacto protocol it is not used much.
BTW, IBM uses SNA to talk between some of their systems and it is very
touchy about delay.
James McKenzie
That's what the reason was. I had forgotten what the problem with IPX was that made it unacceptable for the Internet, but that was it. Still, I have a friend who worked for Intel and he once told me about that private line running between two big offices in separate areas. I'll ask him about it when I see him again.
IPX and AMD64 not mixing?
Sephiroth wrote:
The problem was that IPX was not designed to be routed through what is
now called the Internet. Thus you can have two very large installations
of IPX systems and they will talk to each other.
The real problem with using IPX on Linux is that the communications
interface is restricted to the root group, much like ICMP (Ping and like
programs). This is not a shortcoming of Wine. All Wine should do is
hand off requests to the protocol to the Linux processes that handle them.
James McKenzie
IPX can and is run at two different locations if they appear as one.That's what the reason was. I had forgotten what the problem with IPX was that made it unacceptable for the Internet, but that was it. Still, I have a friend who worked for Intel and he once told me about that private line running between two big offices in separate areas. I'll ask him about it when I see him again.
The problem was that IPX was not designed to be routed through what is
now called the Internet. Thus you can have two very large installations
of IPX systems and they will talk to each other.
The real problem with using IPX on Linux is that the communications
interface is restricted to the root group, much like ICMP (Ping and like
programs). This is not a shortcoming of Wine. All Wine should do is
hand off requests to the protocol to the Linux processes that handle them.
James McKenzie