zero0w

Yeah, it means they can't attack Linux kernel anymore. Anyhow, SCO case against IBM is still flaky. :wink:

Here is the Novell CEO's letter to SCO, asking for clarification on ownership/issues of UNIX IP rights: http://www.theinquirer.net/?article=9724

Hey folks, Novell is now in the game too, but he's our friend, not the enemy for so far as he claimed: Novell Claims Ownership of UNIX System V http://slashdot.org/article.pl?sid=03/05/28/1252229

Well, it looks like SCO is going to get sued by Linuxtag - a German Linux lobbying group, for spreading baseless rumor against Linux (SCO still has not provided any clear, identifiable evidence/infringing code inside Linux kernel to public yet). German Software Group Threatens to Sue SCO on Linux

If this is indeed true, then this is indeed another good news for the open source community. EDIT: Another confirming news from The Inquirer.net: http://www.theinquirer.net/?article=9678

Sounds great.

Now the story goes on, and I suppose we will have to go to Court to settle this one: SCO CEO Says No Version of Linux Passes Legal Muster http://www.osnews.com/comment.php?news_id=3626 Note: As some of the posters pointed out in the comment, this could just be a pre-meditated speech to manipulate SCO's stock prices so that the shareholders can rip-off the new buyers ASAP .... :shock:

Great. As I have always thought, things should work on Linux as much as they can on Windows. It's probably harder to setup than Windows, but usually it's not impossible. You just have to figure things out anyhow. btw, I don't agree leeching unowned MP3 music :!: on any kind of P2P network, but it is obviously for another topic (if you want to discuss it please start a new thread in off-topic forum). Anyhow. -zero0w EDIT: Ok, since I believe this whole SB Extigy discussions should belong to one isolated topic on its own, I have asked the mod to move all Extigy related discussions to a new topic under the thread title 'SB Extigy configuration under ALSA', which I hope will serve SB Extigy users better and easier to find it (not to be wrapped under a SB Live related discussion, which would be unclear).

Checking over Makefile of the plugin source code, it doesn't look like it has such option to alter the header path location. :( No configure script either.

Yes, I did. You see, the thing is, the XMMS plugin compilation depends on <xmms/plugin.h>, which depends on <gtk/gtk.h> and <glib/glib.h>, which then again depends on other <gtk/*.h> and <glib/*.h>. The thing is I believe most Gtk programs out there are migrating Gtk-2.x, hence this trouble of defining <gtk> headers. What does <gtk/gtk.h> means now? How to tell it's a header for Gtk-1.x+ apps or Gtk-2.x apps? Now that I wonder, I've figured maybe a (very) dirty trick to get around this is possible. Well, just rename or re-locate the header directory during compilation, or use symlink to fake the directory to pretend it is in the correct path location. For eg. first rename /usr/include/gtk. After compilation, the symlink can be removed and the directory renamed back to their original naming. This trick sounds like an ancient lost art, but it might just work. I am going to try it later. I am not sure if there's an option to change the path of finding header files; maybe there's one, and hence what I am doing here :wink: .

I did. It's just that in compilation gcc complaint it can't locate the header files, which I suppose is because of a different path location. I believe it is that /usr/include/gtk will be assigned for header files for developing Gtk-1.2+ applications.

You should be able to disable it in the BIOS during system setup before booting.

I have come across some XMMS plugins which I need to compile myself, but they are based on Gtk-1.2+ widget; and since Mdk-9.0 the development libraries for Gtk-1.2+ are installed in the directory /usr/include/gtk/gtk-1.2. However, most source code headers are instead pointing to <gtk>, for eg.: #include <gtk/*.h>, so how can I work around this path difference to allow those Gtk-1.2+ programs to be compiled on Mdk-9.1? Your help is really appreciated.

Hi, I am using GAIM 0.62, I found that I can receive files on AIM but cannot send files, is there any firewall setting I need to tweak to make it working? btw, I am using shorewall.

Thac's Rosegarden-4 rpm and sfxload works fine on MDK 9.1 AFAIK. Oh, btw you need to load soundfont (eg. sfxload /opt/8MBGMSFX.SF2) to have RG-4 to playback MIDI/RG files.

Ok, let's clear things up first: 1) Did you disable the internal sound card inside your laptop? If not, does any sound coming from that? 2) For Kmix, have you tried: File > New Mixer Tab? See if the system can detect and generate a new mixer tab setting. 3) To have digital CD playback in XMMS, I guess today is your lucky day :D : > Download XMMS digital CD playback input plugin here cdparanoia-plugin-0.1-3mdk.i586.rpm (If this download link does not work, search google for the same filename, something similiar should come up) > Install this rpm, then run XMMS, go to Options > Preferences > In the input Plugin section: - Configure CD Audio Player 1.2.7: Disable it by removing the path in Device & Directory; leave them blank. - Then Configure CDDA Paranoia: modify the Directory to /mnt/cdrom, you may want to use Force Drive Speed if you find the CD playback quality to be jerky and skipping later. > In the output Plugin section: Make sure OSS driver 1.2.7 is used, I have tried ALSA Output plugin but it doesn't play nice with CDDA Paranoia :P . If all things go well, you should be able to hear music from your audio CD in XMMS using this digital playback plugin. However, considering it's a 0.1 version, you should regard this pretty much in beta quality. Good luck :) .

Two things: 1) I think KsCD use your CD analog audio playback instead of digital playback, so you can't really hear any CD audio because your CD-Rom drive analog output obviously isn't connected to the external SB Extigy device. Not sure if Grip or XMMS CD-player plugin uses digital playback though. 2) Seems that it all comes down to modifying 'modules.conf' now that you have installed the ALSA driver and have it running. Ok, here is my modules.conf: su cat /etc/modules.conf probeall scsi_hostadapter aic7xxx ide-scsi alias eth0 8139too above snd-emu10k1 snd-pcm-oss alias sound-slot-0 snd-emu10k1 probeall usb-interface usb-uhci alias /dev/nvidia* nvidia I think toaderxxix is right that the modules.conf is being parsed during boot time independent of the order of modules written in that file; it seems that the order of loading module was set internally by the system. In my case, I find that 'usb-uhci' modules was being loaded before the ALSA sound driver. In any case maybe you guys can post your modules.conf and see if we can figure out something here. :wink:

Yes, but ultimately the Court will decide 'the' perspective to be enforced, and this is what to be feared or felt stupid about :? , because it is being manipulated by legal and political tactics, not technical merit, much less for open source spirit.

I suppose compiling for GTK-1.2+ build will solve a lot of problems. Dragon Mage: About that symlink trick, use it ONLY for temporary, because it is known to break other programs. Perhaps I should have mentioned that (I thought Pete readme.txt does, if not, sorry about that .)

Unfortunately, looks like this news is true: http://slashdot.org/article.pl?sid=03/05/1...19/1055223&tid= Another source from WSJ http://biz.yahoo.com/djus/030519/0114000182_1.html Well it looks like the open source folks will have to fight this one. MS joining forces with SCO, I cannot imagine how the legal battle will turn out, or if IBM will decide to buy SCO eventually. I believe open source DOES have great impact such that these issues will make people vocal, and now, sue about it.

To install kernel source, in console, type the following command: su urpmi kernel-source Then insert Disc 3 into your CD-Rom drive and the installation will proceed. toaderxxix: you have a point. Modifying modules.conf might just work in william's situation. Since ALSA 0.9rc8 (which comes with Mdk 9.1) should handle 'snd-usb-audio' as well too. Detecting USB first and then detecting & setting up ALSA modules later could be a better path. However, I don't have experience of installing two soundcards on the same system running ALSA, so.... :wink: If you are successful modifying 'modules.conf', could you post the content of that file here? That might help william I believe. btw, I wonder, did you install usbmidi? I wonder how many MIDI devices are using USB ports nowadays.

I think you did not install the 'Development' category of packages (including gcc compilers and among a few others), which are needed to compile software for Mandrake Linux. Normally I do a full install with every categories (including Development) selected. It took some 1.8+ GB harddrive space to do that for Mandrake 9.1. Well, either you can manually install those packages needed, or do a full re-install and selecting 'Development' category as required. You can ask others about the details if you choose to manually adding development type of software/packages, but I will prefer a full re-install since, well, it probably took less time than to figure stuff out, what's needed or not...

Well, Sound Blaster Extigy is a very different beast from SB Live! or Audigy altogether. Nevertheless, you can follow the compilation procedure on the Soundblaster Extigy info page from the ALSA official site. Also, SB Extigy is using the module name as 'snd-usb-audio', not 'emu10k1'. According to the Soundblaster feature comparison chart here, SB Extigy does _not_ support soundfont (*.sf2 format file) at all. In this case this mini-how-to is not applicable for getting MIDI playback on your system. You will have to resort to software synthesizer approach such as TiMidity or FluidSynth. Hope this clears things up.

toaderxxix: I see, that could work. Actually Mandrake 9.1 by default loads OSS as sound driver using 'audigy' module, as many SB Live/Audigy users have experienced. Eugenia at OS News suggested you can switch between OSS and ALSA driver at Mandrake Control Center (MCC), here's how I did it for my SB Live: MCC > Hardware > HardDrake List Click the item under the 'Soundcard' entry. The info window will display the module name for the soundcard. You can click on the option: > Runconfig tool > Let me pick any driver If your soundcard has ALSA support, the module name (for SB Live/Audigy, it is 'snd-emu10k1') should be there on the list. Click on it, change and save the setting. You should then notice the ALSA module should have started and running in the service/daemon list located by MCC > System > DrakXService list. If ALSA is successfully started, you need to adjust the mixer setting since the default volume level is zero and no sound can be heard. You can adjust the volume & mixer settings in _both_ Aumix and Kmix (for KDE, which is what I am using). btw, there is a useful page for getting tips to configure your SB Live/Audigy under ALSA: emu10k1 http://alsa.opensrc.org/index.php?page=emu10k1

Many articles from http://linux.oreillynet.com/topics/linux/games Animation in SDL http://linux.oreillynet.com/pub/a/linux/20...5/sdl_anim.html SDL and Allegro http://www.gamecoding.org.uk/tutorials/ Focus on SDL > from Amazon Bookstore