Jump to content

chalex20

Members
  • Posts

    157
  • Joined

  • Last visited

Everything posted by chalex20

  1. Don't remove it. You do need its core. You are although not limited to its web-based interface. It's OK. If you do "ls -l /dev/printer", you see that it's just a symbolic link to /dev/lp0. If on the other hand it's not, just type "/dev/lp0" instead of "/dev/printer".
  2. I'm afraid you misinterpreted the meaning of "Location". It doesn't mean "driver location", but rather just describes to the users where the printer is physically located. For example, "Adjacent to John Doe's room" would give an excellent "Location". It says that a printer name may not contain spaces. You've given the printer the "HP OfficeJet" name, containing a space. Just give an alternative name, with no spaces. "HP_OfficeJet" would go nicely.
  3. You're correct, you need NVIDIA kernel module for version 1.0-8756. This "dkms-nvidia" is what would eventually become the NVIDIA kernel module. You need to obtain dkms-nvidia-8756, and to uninstall -7676, in addition to obtaining kernel-source.
  4. Krusader may be used for archiving as well. Select the files and choose the "pack" command. The same goes for Konqueror - select the files, right-click. "Compress", "Zip Archive".
  5. freely (well, almost) available to anybody who may decide to break into them... I'd rather prefer not...
  6. Audacity uses OSS by default and not ALSA. It should be compiled with some special parameters to use ALSA.
  7. chalex20

    Open office

    Recently, I've rebuilt and installed Cooker version of 2.0.2 on my "2006 with lots of recompiled Cooker packages" machine. I'd still refrain from calling its startup fast, but it's a lot faster than 2.0's startup.
  8. This option should be muted in case of analog speakers.
  9. Let's go even further :) This minimalistic bootstrapping part may actually replace BIOS, so the kernel would be pure Java ( heaven forbid )
  10. From purely theoretical point of view, (mostly) Java-based kernel is possible. Build some minimal kernel including Java VM, in C, write all the rest in Java, boot the minimal kernel, load all the rest and let it crawl along :) Bootstrapping at its best :)
  11. You're a good bit lucky. They're doing very good work, I personally use their packages, but nevertheless, there have been a lot of bugs in those packages.
  12. Open alsamixer or kmix or any else alsa-based mixer, and check that "Audigy Analog/Digital Output Jack" is muted if you've got analog speakers, or unmuted in case of digital ones.
  13. Got myself iRiver iFP 795 just yesterday, haven't got time to learn it fully yet. So, just several points : - If you purchase iRiver iFP, do your homework and purchase one that has UMS firmware available . There are Linux tools supporting iManager-based players, but I'm personally inclined to think that working with a regular USB drive would be preferable. - iRiver FPs play Oggs encoded with bitrate in 96K-225K range. No less, no more. Although, it may be some limitation of the UMS firmware, and the players may support a broader range of Oggs with their default one. - I've yet to see some more stupid user interface
  14. Not exactly "line by line" as seen on the screen. "urpmi.addmedia .... with hdlist.cz" is actually one command. So, you open a root terminal ( or "su" in your regular terminal), and then you feed in the commands you received, one by one ( you may unite them, as a matter of fact, but spotting errors is harder in this case).
  15. Well, "3" implies "1" and "2"... If the package is not installed ( and even not installable), there would be no way to run it. Now, that's serious :-( It seems that your urpmi/rpmdrake repositories are misconfigured a little bit. I've given you an answer about easyurpmi.zarb.org in "Installing Mandriva" forum. Go there, configure all the repositories ( you need "main", but all the rest wouldn't hurt as well). Try "urpmi kdevelop" or search for kdevelop in rpmdrake after completing the configuration. Alternatively : see if your installation CDs are configured as a repository in urpmi. Do configure them in, if needed. Explore them in any file manager, looking for "kdevelop*". If such files ( there should be around several dozens) exist, look for them in rpmdrake as well.
  16. UNIX-like systems keep some information about a process even after its exit / death, until the "parent process" of the given one asks about its state. "Zombie" is just that - a process that is actually not a process, but only a purely informational entry in the process table, "dead alive". http://easyurpmi.zarb.org Look for "source contrib".
  17. What do you exactly mean? Is it "you're not able to install it" or "you're not able to locate it in the start menu after successful installation"? For the first case : the package should be called "kdevelop". For the second case : the IDE is called "kdevelop". Try running "kdevelop" from a terminal window.
  18. Install KDevelop - this would bring you an IDE. Or read gcc / g++ documentation for options. You may be very interested in "-o" option ( meaning "what the output file would be"). This option gives you all the choice - both the folder and the file name. Gambas tries to create something resembling VB. VB and VB.net themselves - no dice. Windows only.
  19. The only GUI applications you've opened are Konsole and Mozilla. Other KDE components and console processes use their shares of memory as well. Pay attention to "buffers" and "cached" in the first line, and also to the second line. The matter is that Linux tries to use all of the memory it finds available, for system needs ( it would be pretty stupid to do otherwise; why pay for memory which would never be used?). "Buffers" and "cached" numbers reflect this very memory, used not by the applications but rather by Linux kernel itself. In case applications demand more memory, Linux will just use less memory for buffers. So, application-wise, "buffers" and "cached" memory should be considered "free", as it would be allocated to applications upon first demand. If you look at "-/+ buffers/cache" line, you would see exactly this picture : applications use 428244 K memory, and 607772 K memory are "free". As discussed above, about 500M of your RAM are taken by the Linux kernel for its own needs ( buffers and disk cache ). Almost all of them are still available for applications. 400M are taken by the applications themselves.
  20. I use the box mainly for office activities, with occasional video editing, learning some development tricks and very rarely play some simple game or two.
  21. It's exactly the other way around. libgtkhtml-2.so ( in development package ) points to libgtkhtml-2.so.0.0.0 ( in regular package). libgtkhtml-2.so is not a library per se, but a symlink. To formulate what I've said in a bit different way : one may use .so for development, but it is generally used for running applications. One doesn't generally use .a for running an application. So, .so may be present either in regular packages or in development packages, whereas .a are not generally present in regular packages, but are widely present in development packages.
  22. Where can I read about it? All I've read suggests me that you need .so files to run applications rather than to develop extensions for them. Just a little example : rpm -ql libgtkhtml2_0 /usr/lib/libgtkhtml-2.so.0 /usr/lib/libgtkhtml-2.so.0.0.0 rpm -ql libgtkhtml2_0-devel ... /usr/lib/libgtkhtml-2.a /usr/lib/libgtkhtml-2.la /usr/lib/libgtkhtml-2.so If someone argues that there is ".so" file in the devel- package, here it goes for him : ls -l /usr/lib/libgtkhtml-2.so lrwxrwxrwx 1 root root 21 Nov 5 22:47 /usr/lib/libgtkhtml-2.so -> libgtkhtml-2.so.0.0.0* This .so is but a symlink. So, what we see in this little example ? All the versioned .so files are in the regular package, while .la, .a and unversioned .so ( that are but symlinks) are in the -devel package.
  23. I believe you are very seriously mistaken here. *.so shouldn't mandatorily belong to -devel packages. It's exactly the other way around, they are a crucial part of regular packages. OTOH, *.a and maybe *.la belong to -devel.
  24. thats not true, i ave all the apckages i made yesterday installed and all runs smothly, and to remember that before packages go public all is first tested. There is some lib packages that dont exist anymore since some files were bad position since we did follwoed how mandriva put files but again all were wrong... Almost the same here : - System monitor applet is shown in "add applet" dialog, but can't be loaded - kdeaddons-akregator is there, but doesn't run - Search bar in konqueror is missing - libkdeaddons1-searchbar and libkdeaddons1-sidebar do not exist anymore Absence of problems on your computer doesn't guarantee absence of problems on other computers, you know.
×
×
  • Create New...