Jump to content

chris z

  • Posts

  • Joined

  • Last visited

Everything posted by chris z

  1. open MCC (Mandrake Control Center)->software management->media manager. insert the Cd into the drive. mount it if neccessary. click the "add" button. choose "removable device". give it a name (IE: 10.1 CD, or whatever you like). use the browse button to browse to the CD location. (should be something like /mnt/cdrom) leave the "relative path........." blank. click "ok" in the dialogue box. it will add the CD source. click "ok" in the media manager box. as LZ cautioned, check what dependencies OOo wants before you blindly install it. i would think that it wouldn't need anything that would conflict with your 10.0 install, but just be wary of that. mixing 10.1 system files with 10.0 could land you in trouble. if everything installs OK, i would go back to media manager & either disable, or remove that source, just to be safe for further app installs. Chris
  2. in terminal as root do............. urpmi libfreetype (enter). i'm not sure of the exact version for MDK10.1, but the package will be something like libfreetype6-devel-<version number>mdk. liborgX11 needs that as a dependency. Chris
  3. did you restart X, restart your DE, reboot after uninstall/reinstall? since they're X screensavers, you'll need to do one of those. Chris
  4. chris z


    to read all about fsck, you can go HERE. it's basically the manpage in an easy on the eyes html format. or, if you like plain text, just do man fsck in a terminal. IMHO, you shouldn't need worry about checking the system with fsck on any kind of regular basis. Linux handles things differently than Windows, so there's no need for Windows like routine maintenance, such as defragging, scandisc, cleaning temp folders, etc. fsck is set to run as a startup service in Mandrake by default, after X amount of reboots (usually something like 20-30) or after a forced/unclean shutdown. if you are going to use it, please read the info carefully. fsck can actually f*ck up your system if you're not careful with it. (IE: it needs to be run on an unmounted partition, for starters.) i'd say, as long as your system is running smoothly, don't worry about disk maintenance. at the most, you might want to occassionally look into cleaning up .log files in /var/log because they can get quite large over time. to do that, just simply delete any .log files that are taking up too much space, or if you want to turn logging off, just type service syslog stop (or, service syslogd stop) in terminal as root. Chris
  5. Nominated Screenshot MDK10.0, KDE, running Superkaramba themes tmon_liquid (highly modified) & liquid_weather (slightly modified), transparent Konsole w/ iceWM style, Kleardock Kicker replacement, an assortment of desktop icons from various iconsets, and my very first attempt at desktop wallpaper, made in Gimp2 from a severely tweaked fractal template. (click image for larger view) Chris
  6. ok................ you can't remove kicker. it needs to be running. but.......... you can hide the ugly little bugger, like you see (or don't see, as the case may be) in my screenie. it looks like you have Kleardock running now (right? wrong?). anywho, to hide Kicker, do the following......... (note: Kicker will still be accessible after doing this. you just need to hover your mouse over where it's hidden.) right click the star in kicker->panel menu->configure panel. on the "arrangement" tab, click one of the position buttons for where you want it located. (hint........ position it somewhere that you don't have desktop icons, else it will overlap the icons if you mouse hover over it.) you can also adjust the panel length & size settings here if you want. (i have mine set to the smallest settings.) next, click the "hiding" tab. check the "hide automatically" box & set it to "immediately" after the cursor leaves the panel. in "panel-hiding buttons", uncheck both boxes ("show left/right panel-hiding"). uncheck the "animate panel hiding" box. click "apply"->"ok".......... walla! Kicker be gone! Chris
  7. AFAIK, none of the monitoring apps out there (superkaramba, grkllm, etc) have any kind of setting/switch to shut down your PC due to overheating. you may be able to write some type of script & link it somehow, but if so, i have no idea how you'd do that. you also might be able to accomplish that using lm_sensors, but again, if so i have no idea how. (big help i am, huh?) you should, however, be able to set a high temp/auto shutdown in your BIOS. i know mine has such a feature (don't know how well it works because i've never had a temp go over the threshold). so, unless somebody else has a way to use the monitoring app itself to shut you down, i'd check the BIOS settings. Chris
  8. maybe this would be something you'd be interested in, too........... Kleardock Kleardock in action.............. (click below image/link for full screen view) that's Kleardock on the bottom. kicker is running (it has too), but it's completely hidden at the top of my screen. it will only appear if i mouse hover over it. Chris
  9. chris z


    not offended at all. just a pet peeve of mine & i'm cranky this morn. thank YOU for responding & posting this RESOLVED. Chris
  10. chris z


    thanks AussieJohn. i sorta forgot about this thread. but, i see ChrisM hasn't responded, so maybe he either figured it out or gave up on it. [minor rant] (hint, hint.......... please mark your threads SOLVED or RESOLVED if your problem has been solved!) [/minor rant] Chris
  11. a brief tute on GPG keys (from how i understand it)............ every package is signed with a GPG key to assure the user (downloader) that the file hasn't been tampered with (IE: the server was hacked and all the files were replaced by bogus ones, virus infected files, badly compiled files, etc.). to read the key, you (the user) need the public GPG key. the main public GPG key for Mandrake repositories is installed with the distro so that's why you won't get errors installing apps from the Mandrake CD's. files from other repositories usually link to a public GPG key on their website or keep it in the root of the repository. you can download and import that key with the command "gpg --import (name of file)". for instance, if you go to This PLF Repository, you'll see the file "pubkey" listed. that contains all the GPG keys for the PLF apps on that site. so, for instance, you could do gpg --import ftp://ftp.free.fr/pub/Distributions_Linux...ake/10.0/pubkey in terminal as root to put those GPG keys on your system. then, when you go to install an app from that source, the keys will match & you won't get the "invalid sig" error. if you don't have the key, you will get that error. but, since it's highly unlikely that official Mandrake (or PLF, or Contrib, or Cooker, etc.) files have been tampered with, you can ignore the "bad key" message and go ahead and install the programs without fear. they'll work fine. if you want the added security of knowing all the keys match & all of your downloads are certified, then you'll have to add a key for all of your sources & keep them all up to date. a bit too much to go through, IMHO, but the choice is yours. as for the Quota support in the kernel......... i don't use Quota(s), so i have no idea. maybe Arthur, or somebody else could answer that or elaborate more. Chris
  12. if the source is reliable, ignore the "bad signature........" message & install it. it's just telling you that it can't match any known GPG keys becuase you probably don't have them downloaded on your computer. i (& many others) do it all the time. it will install fine without the GPG key match. if the RPM is borked for some reason, then it will will error out during the install & won't install at all. also note, the quota-3.09-1mdk rpm is available on the MDK CD's or from a "main" source. if you'd do urpmi quota in terminal as root you shouldn't get that error at all. Chris
  13. chris z


    i'm not at the Linux box right now, but there is an option to store your password in the "configure kmail" tool. i think it's in the user accounts (sending/receiving) somewhere. poke around & look for a setting that lets you to enter your e-mail account password & save it for auto login, or something to that effect. if nobody gives you the exact instructions, i'll do so when i get home tonight & can look at it. Chris
  14. devries......... no, the bar is from an app called Kleardock. it's a Kicker replacement that you can make totally transparent. Kicker is still running, but hidden at the top of my screen. and, the red Opera "O" is not a Kleardock icon. i've checked into that already. the "O" also appears as the oogly red one in kicker if i have it unhidden. thanks for answering, though....... Chris
  15. they are highly modified Superkaramba themes. the CPU info, etc. stuff is called keramik t monitor. the weather app is liquid weather. the weather theme is pretty much stock, with a few modifications by me. the t-monitor theme, on the other hand, looks nothing like it does out of the box. i had to edit alot of the theme. and, to get the various monitors to work you need lm_sensors installed & a computer capable of sensor detection. Chris
  16. chris z


    i dunno, moskal. i don't (never have) played Quake, so i don't know how Quake display settings relate to normal display settings. something you may want to check into, though. in your original post you say you're trying to set the display to 1280x720. i don't see those monitor display settings anywhere in your XF86 file. and, if i'm not mistaken, based on the display modes given under the "monitor" "subsection display" settings, your monitor doesn't support 1280x720 mode. so, is there a way you can try setting it to 1280x1024 or something that's supported for your monitor? please keep in mind, i'm just guessing here. i don't know if this is a definite solution or not. just thought i'd throw that out since nobody else has come up with anything yet. Chris
  17. i'm getting a bit confused, as to your partition set up. could you please post the partition set up for each hard drive? IE: hdb=/boot/hdb1, /root/hdb2, etc. Chris
  18. thanks for replying, Ip, but it's not that one either. i forgot to metion /pixmaps in my original post, but i've changed that one too, with no luck. that's what's driving me crazy. i did a find / -name opera.* & changed every opera icon/pixmap/image that was the red "O" to the silver "O" & it still stays the same. there's gotta be a way............ Chris
  19. AFAIK, you wouldn't need to put anything in your current /boot partition. you simply install whatever distro you're thinking of on the other HDD, give it it's own /boot, then edit your current fstab & lilo to mount the new distro (if you want it to be accesible from MDK) & boot into it. you could edit fstab manually for the mounting part, but it's much easier using Mandrake Control Center->mount points->partitions. click on each partition you want to mount, name it, mount it. when you're done, allow it to write the changes to fstab. as for lilo........... open lilo.conf with your favourite text editor, & add an entry for the new distro, making the image= point to the new /boot partition. for example, if you installed DsitroX on hdX & you named it DistroX, your lilo entry would look something like........... image=/dev/hd(X)/DistroX/boot/vmlinuz label="DistroX" root=/dev/hd(X)(number) initrd=/dev/hd(X)/boot/initrd.img append="devfs=mount splash=silent acpi=ht resume=/dev/hd(X)(number)" vga=788 read-only ............then run lilo -v to make changes stick, reboot. Chris
  20. could you please post the complete error you're getting? if it says something like "failed to retrieve........curl blah, blah......." it could be as simple as changing to a different update source mirror. sometimes mirrors go down & are unavailable. in lieu of something else right now, try a different mirror. Chris
  21. ok, here's something for ya'll to chew on, if ya like......... (click image for full screen view, to better see what i'm talking about.) my question is about the red Opera "O" (with the grey shadow) in the lower right of the tray. it's the icon that shows when you have Opera open. it's horrible. the edges are jagged & looks awful, especilly when you mouse over it & it enlarges. i want to replace that damn thing, or at least clean it up. but, no matter where i look for Opera icons on my computer, no matter which ones i change, that oogly red "O" still remains. i have tried editing/replacing the opera.png & opera.xpm files in the following locales in all icon sizes (16x16,22x22,32x32, etc.)........ /usr/share/icons, /usr/share/icons/crystalsvg (which is the current icon set i'm using), & /usr/share/opera/images. i've looked at the /opera & /.kde directories in /home/me but there's nothing in those relating to that icon. it doesn't reflect the silver Opera "O" launcher icon on the left of the tray, so it's gotta be coming from somewhere else. i've also checked the Opera rpm for where image files are stored. they're all stored in /usr/share/opera/images & i've changed all of them to no avail. this is driving me crazy! any ideas where else i could/should look? i just can't figure out for the life of me where that icon eminates from. i tried Opera Community help & faq's & there's nothing about it there. Chris
  22. as Ix said, run the k3bsetup. the last dialogue screen will give you an option to add users for burning/writing privileges. to answer your questions......... 1. yes, that should fix the problem. all the Linux CD burning apps i've come across (so far) don't allow normal user's to burn, for security purposes. see 3. for more......... 2. see my very first statement up yonder......... 3. for a stand alone, home PC, used by yourself &/or family/people you trust, there is nothing wrong with allowing normal users burning privileges with burning apps, IMHO. it's kinda silly, i think. but, i can see how this default behaviour could be a benefit in a work place scenerio, where you might not want to allow employees access to burn company critical things to a CD for removal from the premises. Chris
  23. see This Topic, "The Nvidia Mandrake 10.1 tutorial" link. Chris
  24. ok........... what version of Mandrake are you running? and, where you you getting the update mirrors from? are you using Mandrake Control Center to select mirrors, or are you using Easy Urpmi? if it's Easy Urpmi, are you sure you're selecting mirrors for your version of Mandrake? IE: 10.1 update mirrors won't work with 10.0 & vice versa. and, if you are using 10.1 & choosing the correct mirrors, from what i've been reading, it seems that 10.1 mirrors are closed right now due to major updates. if that' the case, you'll just have to wait until the mirror updates are complete. how long will that take? i dunno. Chris
  25. that sounds to me like a mirror is currently down, unavailable, or updating itself. does this occur every time, with every mirror, over a period of time (like from one day to the next) or just over a period of several minutes, selecting one mirror after another? if it's the latter, i'd say wait for several hours or a day, then try again. Chris
  • Create New...