The problem lies in the linux 2.{5,6}.x kernel headers. Try headers from a 2.4.x kernel. If you know C, what do you think about the following code from mod_devicetable.h (what happens, if __KERNEL_ is undefined?):
#ifdef __KERNEL__ #include typedef unsigned long kernel_ulong_t; #endif
#define PCI_ANY_ID (~0)
struct pci_device_id {
__u32 vendor, device;/* Vendor and device ID or PCI_ANY_ID*/
__u32 subvendor, subdevice;/* Subsystem ID's or PCI_ANY_ID */
__u32 class, class_mask;/* (class,subclass,prog-if) triplet */
kernel_ulong_t driver_data;/* Data private to the driver */ };
dosemu 1.1.99.1 has many improvements compared to Debians 1.0.2 (e.g. sound, dpmi) Reinhard
You have to run dosemu suid root to access devices and you have to enable device-access in dosemu.conf. I use dosemu to support APL2 programs. Codepages work fine using my Novell DOS. (Freedos has no support for codepages yet). dosemu 1.3.0 from CVS works extremly well with X and codepages! I could not do that in modern windows! Windows 2k does not support codepage 910 (APL Character set), dosemu does, even in X.
Neither United Linux nor SCO appear in the announcement. But relationships to the other two partners of United Linux (Conectiva and Turbolinux) are mentioned.
If I remember correctly, the main difference is that the german translation is only available to the translators and not available to everybody. The same thing was done with HP 4.
the file linux/drivers/partport/ieee1284_ops.c dosn't compile due to an undefined constant: IEEE1284_PH_DIR_UNKNOWN, the nearest match found is IEEE1284_PH_ECP_DIR_UNKNOWN in linux/include/linux/parport.h. I don't know, wether that is the right constant.
But the shortened version was meant with overview page.
But the question is: how to make (and to finance in this case) minority versions. It's the same problem with developing medicaments for diseases confined to Africa for example. There is no development as the pharmaceutical firms get no return on their investment.
In your case suse invested a lot in making the staroffice resourcefile. Should they have the exclusive right for some time to use it in their distribution? Maybe you get never a localized version, would that be better?
In the overviewpage was nothing stated about any of that.
In the translate FAQ was stated '... will not..', without any 'probably'. So what's the practical differnence for the private user between 'we will not contest' and 'free'?
But I don't like the action of suse. It starts eroding the free software, even if its looks quite innocent in the beginning.
According to other replies, the information is incomplete. As private user, you may use it legally. Some distributions (eg Debian) may use it starting at mar 1st, the rest starting june 1st. Suse is just seeking some reward for their work. I'm not sure if I like it, but it is not as bad as the first post stated.
Slashdot Mirror
The problem lies in the linux 2.{5,6}.x kernel headers.
/* Vendor and device ID or PCI_ANY_ID*/ /* Subsystem ID's or PCI_ANY_ID */ /* (class,subclass,prog-if) triplet */ /* Data private to the driver */
Try headers from a 2.4.x kernel.
If you know C, what do you think about the following code from mod_devicetable.h (what happens, if __KERNEL_ is undefined?):
#ifdef __KERNEL__
#include
typedef unsigned long kernel_ulong_t;
#endif
#define PCI_ANY_ID (~0)
struct pci_device_id {
__u32 vendor, device;
__u32 subvendor, subdevice;
__u32 class, class_mask;
kernel_ulong_t driver_data;
};
dosemu 1.1.99.1 has many improvements compared to Debians 1.0.2 (e.g. sound, dpmi)
Reinhard
You have to run dosemu suid root to access devices and you have to enable device-access in dosemu.conf.
I use dosemu to support APL2 programs. Codepages work fine using my Novell DOS. (Freedos has no support for codepages yet). dosemu 1.3.0 from CVS works extremly well with X and codepages! I could not do that in modern windows! Windows 2k
does not support codepage 910 (APL Character set), dosemu does, even in X.
Neither United Linux nor SCO appear in the announcement. But relationships to the other two partners of United Linux (Conectiva and Turbolinux) are mentioned.
If I remember correctly, the main difference is that the german translation is only available to the translators and not available to everybody. The same thing was done with HP 4.
no problem here, downloaded from ftp.kernel.org.
the file linux/drivers/partport/ieee1284_ops.c dosn't compile due to an undefined constant: IEEE1284_PH_DIR_UNKNOWN, the nearest match found is IEEE1284_PH_ECP_DIR_UNKNOWN in linux/include/linux/parport.h. I don't know, wether that is the right constant.
But the shortened version was meant with overview page. But the question is: how to make (and to finance in this case) minority versions. It's the same problem with developing medicaments for diseases confined to Africa for example. There is no development as the pharmaceutical firms get no return on their investment. In your case suse invested a lot in making the staroffice resourcefile. Should they have the exclusive right for some time to use it in their distribution? Maybe you get never a localized version, would that be better?
In the overviewpage was nothing stated about any of that. In the translate FAQ was stated '... will not..', without any 'probably'. So what's the practical differnence for the private user between 'we will not contest' and 'free'? But I don't like the action of suse. It starts eroding the free software, even if its looks quite innocent in the beginning.
According to other replies, the information is incomplete. As private user, you may use it legally. Some distributions (eg Debian) may use it starting at mar 1st, the rest starting june 1st. Suse is just seeking some reward for their work. I'm not sure if I like it, but it is not as bad as the first post stated.