Jump to content

dexter11

Members
  • Posts

    1559
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by dexter11

  1. I also had some problems with Opera in the past namely flash plug in didn't work right if I clicked another tab while it was playing, when I clicked back there was a grey block instead of the video. plus mplayer plug-in didn't work whatever I tried to do.

    So I decided to give it a try and I was glad I did it. First of all the installation. The guys made a Mandriva package so it was effortless. Just chose Mandriva from the list gave the root password and wait a few minutes. When the installation was finished it was right in the Internet menu.

    The first thing to notice is the new look. I like it. I1m sure there are hundreds more but I like the default.

    Now lets start with the problems. First page to visit is youtube.com. Flash player works. I start another tab with another video from Google video. I switch between the two tabs a few times, no grey block.

    Second plug in test. Visit java.com. Java plug-in works.

    Now let's see if mplayerplug-in works. So let's go to apple.com/trailers. Unfortunately mplayerplug-in seems to have a problem with playing Quicktime 7 videos. But finally I found one which wasn't in that format and it worked right in Opera too. So it looks to me the Opera developers worked for their money this time.

    Of course I can only find some problems with longer usage but the first impression is positive.

  2. For problem one: please post your /boot/grub/device.map and /boot/grub/menu.lst file here.

     

    For problem two: you don't have to install it from source. I'm sure Pidgin is in the Mandriva repositories. Visit http://easyurpmi.zarb.org Follow the steps there and then use your software installer utility to install software.

  3. Finally I've found something in my docs which could be useful to you. Beware in contains some command line magic.

     

    Hi,

     

    I made the mistake of installing kdevelop from the Software Management box. I merely wanted to play around with it a bit and do some testing. But installing it brought with it a whole gamut of dependencies and debuggers and took several hours to download almost a gig of packages.

     

    When I finally decided it was not for me (way too complicated for my needs) then I went back to Software Management and uninstalled it. But it uninstalled only kdevelop, and left behind not all the zillions of packages that came with it. What's with it?

     

     

    You can use the urpmi_rpm-find-leaves command in this situation. It lists all packages on your system which nothing else depends on. You have to be careful as some of them will be 'false positives' though - packages which you actually want.

     

    I actually had a similar situation to you the other day. This was my approach to dealing with it. It's not especially elegant, but it gets the job done, and it will teach you some neat shell stuff you may not already know. Smile

     

    rpm -qa --last lists all packages on your system in the order in which they were installed: most recent at the top, oldest at the bottom.

     

    the 'head' command is used to only display the top X lines of some output; you usually pipe other commands through it. So:

     

    rpm -qa --last | head -10

     

    displays the last ten packages installed. This much in principle is all you need if you haven't installed anything since kdevelop, but if you have, you can use tail, which does the opposite of head:

     

    rpm -qa --last | head -10 | tail -5

     

    displays from the tenth-last package you installed, to the fifth-last.

     

    So what I did was play with the value of head until I had the first package in the set of packages which came along together (in my case, it was KDE 4). Then, if you also installed packages since then, use tail as well, and play with the value of tail till you nail the last package in the group. (You should be able to see the packages that came along as a group from the timestamps).

     

    Now you have a nice clean list of the exact packages that came along as a group. You could, if you really wanted, painstakingly remove them all manually. That's no fun, though, and it's not teaching us anything new. Smile So let's do it the clever way.

     

    First we just want to have package names, so we need to strip the timestamps out of the output. Coincidentally, last week's Distrowatch Weekly covered this exact operation, in fact. You want to add the 'cut' command to our string. Cut lets you only display certain characters in each line of your output, with various different ways to identify exactly what you want. So you'll end up with something like:

     

    rpm -qa --last | head -10 | tail -5 | cut -d' ' -f 1

    the -f 1 puts cut in 'field' mode, where it considers each line of output as a set of fields, separated by a delimiter. -f 1 tells it to only display the first field. By default the delimiter is tab, but that's not what we want, so the -d' ' tells it to use space as the delimiter instead. (Space is a bit tricky to work with - that's really just a single space, in between ' quote marks so it can be properly parsed. If the delimiter were a normal character instead, the command would look less odd - it'd just be -da or something). You don't need to adjust this to your system, you can use it exactly as I wrote it:

     

    cut -d' ' -f 1

     

    is always right for this situation (getting just the package names out of the rpm -qa --last output).

     

    So this will give you something that looks a bit like this:

     

    [adamw@lenovo elisa-plugins-bad]$ rpm -qa --last | head -10 | tail -5 | cut -d' ' -f 1
    metacity-2.21.21-2mdv2008.1
    task-pulseaudio-2008.1-4mdv2008.1
    drakx-installer-stage2-10.8-1mdv2008.1
    graphviz-2.16.1-2mdv2008.1
    compositing-wm-common-2008.1-4mdv2008.1
    [adamw@lenovo elisa-plugins-bad]$

     

    which we can work with! The final step is to extend the command to feed that output back into rpm -e. You need to be root for this one:

     

    rpm -qa --last | head -10 | tail -5 | cut -d' ' -f 1 | rpm -e

    and boom, all the packages in the output get removed.

     

    Why rpm -e not urpme? Well, in this situation it provides insurance against mistakes. rpm -e will only work if removing the packages won't cause dependency issues for any others on the system, so if you got something wrong, rpm -e is likely to barf and not run. urpme , by comparison, will be 'helpful' and also offer to remove any packages which won't work if the packages in the group you specify aren't present, so if you screw up and feed it the wrong list of packages, it will ask you (Y/n)? and then happily remove a ton of stuff you probably wanted.

     

    Okay, so that might have been a bit more complex than you were prepared for, but it works, it's kinda cool, and you get to learn stuff Smile.

     

    We do actually have a system for letting you 'roll back' urpmi operations in a 'simple' way, but you need to set up a recovery point before hand. It's called urpmi.recover . I've not played with it myself, but RJ has. RJ, are you reading this thread? Can you let Bamm know how to use it?

  4. AFAIK Kerry and beagle searches for files. A package which has kde4 in its name does not necessarily contains files with kde4 in their name. Search for packages in the package manager.

  5. Urpmi.recover is not installed by default. Here's what rpmdrake writes about it:

    urpmi-recover - A tool to manage rpm repackaging and rollback​ 

    urpmi-recover is a tool that enables to set up a policy to keep trace of all packages that are uninstalled or upgraded on an rpm-based system, and to perform rollbacks, that is, to revert the system back to a previous state.

    It's 9KB so it shouldn't be a problem to install even on low bandwidth systems.
  6. Unfortunately uninstalling such a complex software like KDE is not straight forward. So I'd like to encourage everyone to use urpmi.recover before installing KDE4 or any other big piece of software. Your life will be much easier.

    As for uninstalling it now There is topic about just that somewhere in the club forum but I just can't find it. It includes some command line magic.

  7. Compiz-fusion is Compiz + Beryl together. They call it fusion because the two projects merged a couple of months ago. Beryl is not developed anymore as a standalone project.

    Mandriva has a backports repo for both main and contrib. If you need a newer version from a software try looking in them first. There is no real advantage using 3rd party repos like SOS anymore IMHO.

  8. There have been rumors since last year that Valve may be serious about porting Source games to Linux after Valve Software began seeking a senior software engineer with the responsibility of porting Windows-based games to the Linux platform.

     

    Valve Software has yet to officially announce Linux clients for any of its software, but Phoronix have received information confirming that Valve is indeed porting its very popular Source engine to the Linux platform.

     

    The rest of the article is here.

  9. If anyone is interested in multiplatform OpenGL development here then there is a new live CD aimed to do just that called myOSX11-GL. It's basically a stripped down Mandriva 2008. More info and the download is here.

     

    The original announcement in the Mandriva forum is here.

  10. Time to throw my 2 cents in though some of my thoughts were already mentioned by others.

    I tend to agree with Iphitus in a lot of things. My experience tells me that distro specific forums give better support since you can get better skills by learning one distro than learning multiple distros even if there are a lot of the same problems among distros.

    The official Mandriva support forum IS a good place for support especially since Adam arrived there. Though this forum may have lost from its user base the official forum has an increasing number of users. Mandriva may be not the first distro anymore but it's not going down. (Btw I proposed a few times in the official forum to use MUB as THE official Mandriva forum but the powers that might be decided against it).

    A lot of you mentioned an idea which would make distrostop.org different from other forums. I think this is the most important thing and I still fail to see that idea. Without it you have a bigger chance to fail than not. Just like making a movie starts (or should start) with a good script. If you don't have that your movie will most likely suck. So before doing anything I suggest you to find that idea.

    About splitting up the user base. I don't care if fewer newbies come here. But I do care if old time users like you Mysti or Paul have less time to visit this board. Old time users are the ones who keep this board alive.

    But since you seem to be determined to keep distrostop I wish you the best of luck.

  11. No Mandriva uses meta packages which are basically empty packages with a lot of dependencies. They are used in cases like this e.g. to install full KDE or Gnome etc desktops. The KDE 4 metapackage should be called something like task-kde4. There can be more than one. One for minimal and one for full KDE 4 installation.

  12. There is no big file (hdlist.cz) anymore. Mandriva is using a new XML based file format in 2008 Spring which is a way smaller than hdlist was. There should be an option in the GUI which sets up whether to download the info or not.

    When I saw this new feature in one of the betas it only downloaded the extra info when I clicked on "file list" or "description" etc drop-down lists.

    You have to ask for enhancements in Bugzilla just when you choose severity choose enhancement.

  13. herewith I have attached the dvd package list of both. please look at them.

     

    sorry it said "Upload failed. You are not permitted to upload this type of file"

    The forum engine will let you attach only a certain type of files. Add txt extension to the filename and you can add it to your post.
    I am posting the output of "rpm -qa | grep -i dvd | sort > dvd_package_list" of both

     

    mandriva 2008 powerpack

    --------------------------------

    dvd+rw-tools-7.0-3mdv2008.0

    libdvdcss2-1.2.9-3plf2007.0

    libdvdnav4-0.1.10-6mdv2008.0

    libdvdread3-0.9.7-4mdv2008.0

    lindvd-1.2.6-8mdv2008.0

    lsdvd-0.16-3mdv2007.1

     

    mandriva 2008 free

    -----------------------

    dvd+rw-tools-7.0-3mdv2008.0

    libdvdcss2-1.2.9-3plf2007.0

    libdvdnav4-0.1.10-6mdv2008.0

    libdvdread3-0.9.7-4mdv2008.0

    lsdvd-0.16-3mdv2007.1

    I am thinking about maybe you shouldn't add anything, maybe you should remove something. From the two package list the obvious choice is LinDVD. I have no explanation why a video player should affect mounting though so it's just a guess.

     

    1. Has this version of powerpack fixed some bugs that were reported when mandiva 2008 released, because it is long gap from that date.

    2. Does this version has updated kernel and xorg since it's very long duration from the date of mandriva 2008 release to the date when linux magazine distributed it free with the magazine.

    Mandriva is using the point release cycle meaning you'll only get bugfixes and security fixes after the released a version of the distro. Among the fixes are updated (but newer version) kernel packages too.

    But if you still want newer version packages then use the backports repos.

     

    With a distro like the Mandriva Powerpack (paid version), this would really be an insult to those who paid the full price.

    To be fair, by releasing the Powerpack to a magazine they have already insulted those that paid full price.

    No they didn't.

    First of all there is a lifcycle to every product. E.g. I can get a Pentium4 computer for much cheaper when it was released. Do computer manufacturers insult the users who bought it right after they were released? I don't think so.

    Second if Mandriva PP is released in a magazine that means that the magazine is paying for the printing of DVDs. So they can further reduce the price.

  14. I found this link in somebody's blog. It's freely downloadable now.

    It's pretty hardcore users' stuff so in case you're unsure if it applies to you or not here's the short TOC:

    Preface

    Chapter 1: Best Practices and Initial Investigation

    Chapter 2: strace and System Call Tracing Explained

    Chapter 3: The /proc Filesystem

    Chapter 4: Compiling

    Chapter 5: The Stack

    Chapter 6: The GNU Debugger (GDB)

    Chapter 7: Linux System Crashes and Hangs

    Chapter 8: Kernel Debugging with KDB

    Chapter 9: ELF: Executable and Linking Format

    A: The Toolbox

    B: Data Collection Script

×
×
  • Create New...