Slashdot Mirror


RPM Package Manager

Things have changed quite a bit since we last posted about the state of Linux Package Management. Over the few months ago, we saw the Connectiva release, which was a RPM front-end to apt-get [?] . Now, for those of you running RH6.x, there are a new program called Aduva Manager. It's kinda like using apt-get update/apt-get dist-upgrade, but checks dependecies and such for RH6.x based systems. They've got screenshots as well as a FAQ/download site. It's designed more for new users, but it looks like a step in the right direction for RPM.

180 comments

  1. sounds like up2date by xcyber · · Score: 1

    up2date from rawhide is more or less from apt-get

    --
    xcyber """"""Complexity for the sake of complexity is not a solution, neither is simplicity for the sake of simplicity
    1. Re:sounds like up2date by Anonymous Coward · · Score: 1

      up2date doesn't do not even a bit of what this program does. Among other features it's got:

      * kernel upgrade - not an RPM upgrade, but entire compilation - with 2 clicks
      * dependecy problem - no more. Just upgrade or install - without depenedency headache
      * Upgrade entire trees in single click - want to upgrade all your development enviroment? select the branch - and click "upgrade now"
      * Hardware support - newer driver comes out? you couldn't install driver or didn't find it? the Manager will do this for you.
      * 1 place to download your software - no need to look for RPM's - the program is connected to their server and download what you want from there - with support to broken connection and proxies.
      * Built in search engine for RPM's - no need to guess RPM names
      * Completely depend from your Desktop enviroment/Winidow manager - whatever you run KDE/GNOME/Enlightment/twm/fvwm/you-name-it - it doesn't need anything
      * Its totally free and soon the source will be out..

      Now - can you compare those features to any other package management or other solutions available for Linux?

    2. Re:sounds like up2date by xcyber · · Score: 1

      from non-technical sides how about the price?

      --
      xcyber """"""Complexity for the sake of complexity is not a solution, neither is simplicity for the sake of simplicity
    3. Re:sounds like up2date by Menthos · · Score: 1

      up2date is free (as in speach).

      --

      GNU/Linux. The Freshmaker.

    4. Re:sounds like up2date by Menthos · · Score: 1
      up2date from rawhide is more or less from apt-get

      No, up2date does not share a single piece of code with apt-get.

      --

      GNU/Linux. The Freshmaker.

    5. Re:sounds like up2date by Menthos · · Score: 1
      * Its totally free and soon the source will be out..

      Unless the source is already out, it does not even begin to fulfill the criteria for free software.
      up2date is GPL and fully free.

      --

      GNU/Linux. The Freshmaker.

    6. Re:sounds like up2date by Menthos · · Score: 1

      up2date is a GPL:d free software program, and can be used freely against Red Hats servers, and anonymously. So no, you don't have to pay for using up2date unless you want to (and want to get access to Red Hat Network, RHN).

      --

      GNU/Linux. The Freshmaker.

  2. Package Managers by GW+Hayduke · · Score: 3

    It's been my humble opinion that packaging managers are good for "users" of OS's I just started using debian on my workstations after a co-worker showed me the ease of applying new dependancies. However without getting into a distro jihad here, I still say that for the tried-and-true, the only REAL way to understand and comprehend services on a production box, you really need to compile the source yourself.
    How else are you going to be able to troubleshoot or modify any tweaks/perks/or problems that may occur.
    Or take for example the debian debacle of a couple weeks ago. I did an upgrade then an install of a couple things only to find out that X was going to crap the bed on me... If I had been less lazy (yes I know that goes against EVERY netadmin's fibre) and had compiled the programs myself I could have saved a couple hours of time in the long run.
    But as far as getting *nix out to the masses I applaud RH and Debian for attempting to ease the installation of software for new users.

    --
    -- Life: Hate the Game... Love the cereal
    1. Re:Package Managers by SquadBoy · · Score: 2

      This assumes that you can and do *read* the source. I know that for me to type ./configure make make install does not give me any more understanding and control then does typing apt-get install foo. For many of us admin types who can code a little but at nowhere near the level we would have to in order to really use the code it is worthwhile to let the fine folks of the Debian project take care of the details. And BTW I have never ever seen stable randomly break things that did not end up being my fault in the end so if you are running unstable well you should know better.

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    2. Re:Package Managers by GW+Hayduke · · Score: 2

      granted and point well taken. I guess I'm attacking the issue from a different angle. more along the line of the other dependancies that are installed during certain apt-gets.
      and generally depending on where you get the source from, there seems to be more documentation (README's, INSTALL, what have you) to help you out with.
      Yes, I wholeheartedly agree with you that the debian developers who forget more on a daily basis than I will ever learn about their own products have a much better understanding of the tweaks/peeks of the OS and therefore will be able to "fix" any problems long before the majority would even figure out that there WAS a problem.

      --
      -- Life: Hate the Game... Love the cereal
    3. Re:Package Managers by Servo · · Score: 1

      While learning the internals of the environment, by doing things the hard way, has always been the best way in my book, but when it comes to system administration, having Debian's package manager is extremely helpful. 1st, if you run more than one box (which I run 12 servers at work, 1 for my LUG, 5 for a local freenet, plus my "personal" server on my home DSL line) managing software becomes a nightmare. I'm not really crazy about Sun's package manangement, but without it (and thank god for patch clusters) it would be next to impossible to manage the 12 systems at work. The rest of the systems all run Debian, and it really does work better than Redhat's releases. Do you know what I hate? Reading Redhat's ERRATA page on a constant basis to see if a package has been updated. With Debian, I just "apt-get update; apt-get upgrade" to grab the latest updates.

      It's always been my opinion that Slackware is the best (and hardest) distribution of Linux to start out with, because you learn HOW to do things the hard way. This is an important step in the learning process. The next step is to learn how to do it BETTER. I do not recommend Debian to new users unless they are coming over from Solaris or other commercial Unix. Its not for novices trying to learn with, its for Linux users who have a job to do.

      --
      A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin
    4. Re:Package Managers by Phexro · · Score: 2

      "the only REAL way to understand and comprehend services on a production box, you really need to compile the source yourself."

      i agree; that's how i learned *nix system administration. but it gets old pretty quick, when you have to download, configure, compile, install and tweak a dozen or so programs just to have a system that does what you need it to.

      once you have reached the level where you understand what is going on, you will start looking for a way to remove that drudgery. for me, debian was the way. most packages install and work out of the box, so most system admin tasks involve customizing your setup, e.g. to make apache do a bunch of virtual hosts.

      as for your problem with X, what do you expect when you run the unstable distribution? if you want a rock-solid system, use potato.

      oh, and X takes several hours to compile. so you wouldn't have saved that much time anyways.

      --

    5. Re:Package Managers by johnnyb · · Score: 2

      That's good for installation, but what about removal? What about dependency checking during removal? ./configure won't help you there. The only way ./configure works in a sensible way is if it is used in conjunction with encap or stow.

    6. Re:Package Managers by Bruce+Perens · · Score: 1
      Yes, I built stuff from sources on 4BSD in 1981. It's 20 years later and frankly I really do appreciate apt and the hundreds of Debian folks who consistently get things right, even in unstable so that I can run an automatic upgrade from there every few days and very rarely see anything go wrong.

      Thanks

      Bruce

    7. Re:Package Managers by lemox · · Score: 2

      I've use Slackware before with no problems, and I think the whole idea that Slackware is "hard" is largely outdated. Yes, Slackware used to be more difficult to pick up than something like Redhat, but recently Slackware is not any more difficult or more educational than anything else. Really, is './configure && make && make install' that much more difficult than 'rpm -Uvh' or 'apt-get install'? Slackware even has it's own package management system now too.

      Sure, it's supposed to be the most "UNIX-like" distribution, but what is really UNIX nowadays; with Sun's own CEO calling Solaris "Sun's implementation of Linux"?

      --

      "We obviously need a new moderation category: (-1, Woo-fucking-hoo)" --Mr. AC

    8. Re:Package Managers by Servo · · Score: 1

      I wasn't meaning that Slackware was hard, maybe I should word that differently. I probably should have said that its the least easiest. And yes, ./configure && make && make install' is more difficult for the new users. There's more to it than just that.

      Sure, you and I have no problem doing these things, but to a new user, having a consistant interface for installation is important. Say you want to install a program that requires another library, and a perl module. Each builds differently, and come from a different location.

      For me, doing it "the hard way" taught me the fundamentals for finding and working with all parts of the system. I think this is an important step. If you take the easy way out, and just know how to do it via the GUI, when something breaks you don't know how to fix it.

      I still find it amazing that some people who started out with Redhat, and used the prepackaged modulerized kernels, years later can't even begin to tell you how to compile a kernel. They can't tweak or modify the kernel now because of that.

      --
      A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin
  3. Yet another reason for... by Zecho · · Score: 1

    ...a standards comittee!

  4. Could someone enlighten me please... by Kiss+the+Blade · · Score: 1
    ...regarding why Red Hat use RPM, and not Debs? I thought there was a great consensus that the debs system is superior to the RPM system, and considering that Red Hat need not worry about copyright infringement, why do they continue to use RPMs? Is it because they have a perhaps misguided feeling of pride regarding their package management system?

    I suppose some will argue that it is because RPM is the 'standard', but the fact is that the standard is pretty much whatever Red Hat decrees it to be.

    I just don't understand why Red Hat are continuing to use an arguably outdated system.

    KTB:Lover, Poet, Artiste, Aesthete, Programmer.

    --

    KTB:Lover, Poet, Artiste, Aesthete, Programmer.
    There is no

    1. Re:Could someone enlighten me please... by bero-rh · · Score: 2

      RPM is not at all outdated. .deb packages have a lot of things that are an advantage and a disadvantage at the same time, such as the post-install configuration. We don't want this type of stuff because it makes installation unnecessarily complicated. The only real advantage of debs compared to rpms is apt-get, which has now been implemented for rpms as well. So why switch to anything else?

      --
      This message is provided under the terms outlined at http://www.bero.org/terms.html
    2. Re:Could someone enlighten me please... by blakestah · · Score: 2

      How is .deb better then .rpm?


      Apt-get.

      Cleaner dependencies.

      More package maintainers.

      More packages in the standard tree - fewer compiled by other people who are not part of the distribution.

      More testing.

      Debconf.

      No backward compatibility break between rpm-3 and rpm-4 for debs.

      Nuff said.

    3. Re:Could someone enlighten me please... by Flabdabb+Hubbard · · Score: 1
      You've hit the nail on the head there. The great claim of open source development is that the best solution survives while the weaker ones go to the wall.

      This may be true when your user base is elite CS Grads at Berkerly, but you have to wonder if these days Linuxs user base is not as tech-savvy as it once was, back in the good old days of v1.119

      Honestly, this might sound a bit dumb, but I don't see what is so difficult about using gzip, tar and gmake. I mean, if you cannot figure out a few simple commands, maybe you shouldn't be using Linux in the first place !!! Its not for joe average, its for people who like to get under the hood and tinker around.

    4. Re:Could someone enlighten me please... by Uri · · Score: 1

      ".deb packages have a lot of things that are an advantage and a disadvantage at the same time, such as the post-install configuration. We don't want this type of stuff..."

      Erm, actually RPM has had optional pre- and post- install/uninstall script capabilities for a while now. At the moment they're mainly used for running ldconfig, though I have seen them used for generating post-install SSH keys, and for setting an SQLd password interactively from the shell prompt.

      I wonder how well GnoRPM would cope with that, though...

    5. Re:Could someone enlighten me please... by brandonj · · Score: 2

      >>>if you cannot figure out a few simple commands, maybe you shouldn't be using
      >>>Linux in the first place !!! Its not for joe average, its for people who like to get under the hood and tinker around.

      I disagree... It may have been that way before, but more and more windows users are moving to linux, probably just because of the hype so they are curious. But the easier it is for any user to install and maintain packages, the more users will stay with linux. Sure sometimes its a good idea to compile the sources, but if there's already a package out there, it's just a waste of time. Ideally, no user should ever have to compile the sources- just have it there in case they want it. The thing that is keeping that from happening is the lack of a standard packaging system. RPM works fine, but I really like the apt-get feature of debs. But now that apt is being ported to rpm, then I think I'll just stick with rpm. In the meantime, whoever makes package management easier has got my support.

      But on a side note, I think the interface for this piece of software is ugly and is poor UI design. I personally cant wait for RedCarpet from Helix to be available - that looks like the best bet right now for package management.


      -Brandon

    6. Re:Could someone enlighten me please... by HeUnique · · Score: 2

      As I said in another post - the GUI will be skinnable and you will have the option to use the Aduva Manager with a standard GUI.

      --
      Hetz (Heunique)
    7. Re:Could someone enlighten me please... by bero-rh · · Score: 2

      The strict policy for Red Hat RPMs (and those of any other RPM based distribution I'm familiar with) is not to demand user interaction in %post, %pre and the likes. debs have a very different philosophy there (or at least used to, haven't checked out the latest Debian yet). We generally use %pre and %post to autogenerate stuff, not to prompt users.

      --
      This message is provided under the terms outlined at http://www.bero.org/terms.html
    8. Re:Could someone enlighten me please... by shallot · · Score: 1
      Feel free to relativize every difference between the packaging format. But I doubt you can do that with the endless hard work Debian maintainers invest in their packages.

      FWIW. (I'd put a disclaimer here, being a maintainer of about forty .deb packages, but the above post didn't have one ;)

    9. Re:Could someone enlighten me please... by JabberWokky · · Score: 2
      He original question: How is .deb better then .rpm?

      Apt-get.
      Which is an update program, and not a package program. Mandrake has MandrakeUpdate (along with stable and cooker sources), and I'm sure most other rpm based distros have similar tools.

      BUT - this has squat to do with .deb versus .rpm.

      Cleaner dependencies.
      Is that a function of the format or the package maintainers?

      More package maintainers.
      Again, has nothing to do with .deb file format versus .rpm.

      More packages in the standard tree - fewer compiled by other people who are not part of the distribution.
      Again, squat to do with deb versus rpm. And for that matter, Mandrake's Cooker has most of what I want, being an open submission of Mandrake rpms.

      More testing.
      Hunh? I'm not sure what that means, but I don't think you're referring to rpm versus deb as packages.

      Debconf.
      Okay now THATs more like it - can a somewhat less zealot debian user explain debconf? I'm seriously interested in deb versus rpm (Corel's distro for a two month period was as close as I got to debian).

      No backward compatibility break between rpm-3 and rpm-4 for debs.

      Bzzzt. Thank you for playing. It works fine on my system.

      Nuff said.
      Not only did you manage to sidestep the direct question (rpm versus deb as packages, leaving package managers/updaters out of the scope of the discussion), you merely named a whole bunch of utilities that would only be recognizable to debian users, who, presumably, would not need the information.

      Any debian AND rpm user out there care to take a crack at explaining the difference and pros and cons between the package formats?

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    10. Re:Could someone enlighten me please... by Enahs · · Score: 2

      RPM == Red Hat Package Manager

      Seriously, the reason Debian doesn't use RPM is because R=="Red Hat" IMHO. That's the vibe I get from some folks who're involved in Debian. "Ick, that's a RH thing," I've heard more than once. :-) You could make a system (now :-) as easy to use, and as coherent, and as logically laid out, package-wise, as Debian and use RPM. Hell, now, you can even use apt-get with this mythical RPM-based system.

      --
      Stating on Slashdot that I like cheese since 1997.
    11. Re:Could someone enlighten me please... by RelliK · · Score: 1
      Seriously, the reason Debian doesn't use RPM is because R=="Red Hat" IMHO.

      Nice troll. Debian packages have been around far longer than rpm's. When RedHat got started, they made their own package manager, even though there was one already available.
      ___

      --
      ___
      If you think big enough, you'll never have to do it.
    12. Re:Could someone enlighten me please... by blakestah · · Score: 2

      Apt-get.
      Which is an update program, and not a package program. Mandrake has MandrakeUpdate (along with stable and cooker sources), and I'm sure most other rpm based distros have similar tools.

      Ever tried to use those tools ??

      You are right though - this is not strictly a deb vs rpm issue.

      More packages in the standard tree - fewer compiled by other people who are not part of the distribution.
      Again, squat to do with deb versus rpm. And for that matter, Mandrake's Cooker has most of what I want, being an open submission of Mandrake rpms.

      Actually this has a ton to do with reliability. The entire point of having a distribution is that they will ensure that packaging is reliable and consistent. When third party vendors start offering Redhat RPMs, or Mandrake RPMs, or you start using contrib RPMs, package dependencies get less consistent, and the machine is just not as clean.

      I get everything I need at debian.org in woody non-us and non-free, all packaged by debian maintainers.

      Debconf.
      Okay now THATs more like it

      Debconf is a little scripting conf that allows packages to pop up questions in console windows during the package installation that ask you if you would like to clobber your existing configuration files with new ones or not. The default is always do not clobber. Or, a package can pop up a reminder about a configuration issue associated with a package, and either show or do not show the reminder in the future. Lastly, they have help hints if you cannot resolve a dependency that tell you what to do !! These have helped me a few times.

    13. Re:Could someone enlighten me please... by teg · · Score: 2

      Red Hat (and almost all the other distributions) use RPM because it works well and is a better and more flexible package format than deb. You're probably confusing "rpm being superior to deb" (package format) with "apt is cool" (distribution of packages)

      RPMs, in contrast to .deb, has cryptographically signed packages (and has had so for ages), flexible and reproducible building method (look at a spec file, they really tell you how to build a package), separated patches(I've seen people claim than .deb can do this, but as long as the packages distributed with Debian don't seem to do this I'll believe that as an urban legend). Take a look at a SRPM and a Debian source package - there's really no competition.

    14. Re:Could someone enlighten me please... by blakestah · · Score: 2

      Actually this has a ton to do with reliability. The entire point of having a distribution is that they will ensure that packaging is reliable and consistent. When third party vendors start offering Redhat RPMs, or Mandrake RPMs, or you start using contrib RPMs, package dependencies get less consistent, and the machine is just not as clean. I get everything I need at debian.org in woody non-us and non-free, all packaged by debian maintainers.


      Really? Mmm... Do you also purchase only Microsoft software, avoiding those nasty "other" vendors that prevent you from having a "reliable and consistent" experience? Because you could replace "Debian" with "Microsoft" there and have a sentence that could come from any number of idiot NT admins that I've run into.



      Point well taken, but the environment is completely different. Everything I need under linux is free (as in speech), and can be packaged by a single party. And the single party is not a vendor with a monetary incentive to lock me in, but a collaboration of hundreds of volunteers.

      There is nothing preventing RedHat from packaging everything that is packaged as RPMs for RedHat from third party vendors. The packaging basically consists of taking the installation files, and wrapping them together, setting sane dependencies, and pre/post install/uninstall scripts where appropriate.

      Put another way, in a Microsoft world one of the single largest sources of OS trouble is third party software clobbering system dlls. If Microsoft could package that software properly, Windows would work much better. Of course, in a Windows world the third party software is actually competition, so this would never work.

      In free software the third party software is a welcome addition to strengthen the distro. See the difference yet ??

      The .deb/.rpm battle ended a long, long time ago. RPM won. How many people do you see coming out with .debs of their software? Sure, they *exist*...but at a 1:20 ratio to RPM producers.

      This may surprise you, but Debian as a distribution is still growing rapidly. And the net number of people converting from RPM based systems to deb based systems is substantial.

      But that is beside the point. Debian will continue. Its volunteer packaging force is growing rapidly, as is its user and testing base. There is no monetary bottom line affecting the distribution - only the joy of having free software that works the way it should. As long as the packagers keep packaging, the distro will continue. As long as the userbase keeps expanding, it will grow stronger and stronger.

    15. Re:Could someone enlighten me please... by shallot · · Score: 1
      Oh, the maintainers of .rpms do their stuff. They just don't do it with the care .deb maintainers do. Does every RH .rpm have to abide to all the stuff like Debian Policy and Packaging Manual describe? Would they have releases twice a year if they did?

      Of all the moments in history, your friend had to switch from Debian to Red Hat now that Red Hat made some of their biggest fsckups (RH7), and now that Debian made some of their biggest advances (2.2, plus `testing')? Honestly, I find that quite hard to believe.

      Microsoft software hardly ever upgrades properly when the installation procedure is invoked manually. I fear the day `Windows update' becomes automatic... unless of course I get to work in some windoze tech support company. The consultants are going to make big money on fixing up all that crap. :>

      You ought to actually _try_ current Debian before tossing off such snide remarks. The `stable' tree isn't wildly outdated, not at all. I'm a developer, and although I'm quite capable of handling the breakages in unstable, I only upgraded a dozen packages over 2.2 on three of my machines, those that I use daily (the others still run pure stable). Additionally, there exists a new tree now, it's called `testing', that is considerably more stable than `unstable', and has more of the new, shiny stuff than `stable' does.

    16. Re:Could someone enlighten me please... by Rakarra · · Score: 1
      Honestly, this might sound a bit dumb, but I don't see what is so difficult about using gzip, tar and gmake.

      I know how to use them fairly well, but I'll usually go for a package instead. Why? Because the work has been done for me already. I don't want to go through a hastle that pretty much is a waste of time if there's a package available. I mean, if you know how to use it, why not go for the package? (Unless there are some compile-time customizations you want to make) I just don't have the time otherwise.

    17. Re:Could someone enlighten me please... by blakestah · · Score: 2

      No backward compatibility break between rpm-3 and rpm-4 for debs.
      Not an issue for at least RH and, presumably, other RPM-based distros (though I don't know, so I can't swear to it). RH just runs out and makes an rpm-4 compatible version of rpm that runs on old distros. Easy. Fun. Besides, presumably all the reinstalls you've had to do when the unstable Debian tree breaks your system add up to at least some form of "upgrade", hence lack of backward compatibility? :-)

      If you don't want to have to fuss with it, simply use the stable tree - that is what it is there for.

      If you don't mind the occasional manual futzing with your box, the Debian unstable tree is for you.

      And if you want a real pain in the ass, use a RedHat *.0 release. Totally unstable compared to Debian unstable. And RedHat calls it a production release.

      Don't get me wrong - I administer RH and Debian boxes. I find I spend much less time screwing with the Debian boxes, and the initscripts and cron jobs (slocate, man) do more intelligent things. Like, for example, wiping /tmp clean on every boot. And /var/run.

      Basically, I tried Debian as an experiment. It was slink, and a royal pain to install (potato is supposed to be much easier). Then it was a pain to get everything the way I liked it, as I didn't know much of apt and dpkg. Then, I used the box. And over a few months, I realized the Debian box was running more smoothly, and upgrading more easily, than the Redhat box. And this is mainly due to clean packaging and apt and debconf.

      From Debconf's own description: "It's a way to get rid of all those annoying questions Debian packages often ask when they are installed; or a way to present them to the user via a varierty of UI's.". Gee. That's just swell. Instead of auto-detecting things like most RPMs do (following a Red Hat convention) and then letting you customize things if you want something special (rpm -i blah.src.rpm, edit .spec, rpm -bb .spec), you get to manually enter stupid info that could be auto-detected 99% of the time. Lovely.

      Really, it does things like
      1) install XFree 4.0
      2) Prompt you whether you want to make XFree 4.0 the default
      3) Remind you that Debian XFree 4.0 uses the binary /usr/X11R6/bin/Xfree86 instead of /usr/X11R6/bin/X, and the new config file is /etc/X11/XF86Config-4. The new install doesn't conflict with the old one that way (since 4.0 currently doesn't work for a lot of people).
      4) Ask if you want to autoconfigure XF86COnfig-4 or use the existing version.

      So you can see, you have multiple options, all of which any reasonable user might choose. With redhat you only get a broken system until you can hack up a new config file.

      And for another example, for gdm, the debconf entry asks if you want to keep or overwrite the gdm.conf file.

      More testing.
      Again, not a .rpm-.deb issue. This is a distribution issue. If you're claiming that .debs inherently get more testing than .rpms, than I claim that you're full of it. To be fair, if you're slamming RH 7.0, you're on target.

      Really, this is critical. Debian packages get a little testing by the maintainers, and sometimes others who download them from a web page. Then, they get placed in unstable. Thousands upon thousands download unstable (since apt works so well), and an open bug reporting system checks all the bugs. The package is changed again and again until it is assumed everyone in stable can use the package without issue. Then it is moved to stable.

      Redhat is trying something similar with rawhide, but it gets a few orders of magnitude less testers.

  5. Isn't freshmeat supposed to do this? by Lally+Singh · · Score: 2
    Hmm, when did slashdot start taking over for freshmeat? I though they were the ones listing new software releases. Perhaps part of a hostile takeover within the andover ranks?

    --

    --
    Care about electronic freedom? Consider donating to the EFF!
  6. I'm so sick of... by uradu · · Score: 3

    ...these organic GUIs. Why do we need to have widgets that look like automobile clay models or stuff you'd find if you slit open your guts? What's wrong with good old 3D widgets, which took us like 10 years to get to?

    1. Re:I'm so sick of... by ghoti · · Score: 2

      I don't have a problem with "organic" UIs, but I think that this program has a pretty bad UI, organic or not. The parts don't fit together, some are 2D, some 3D, buttons and scrollbars are lit from different directions, and the text is hard to read because you can't find any structures for orientation. So the problem here is IMHO not the organic layout, it's just that the UI is not very well thought out, and done mostly for the effect (and maybe for looking good in computer magazines), not for making the program usable.

      --
      EagerEyes.org: Visualization and Visual Communication
    2. Re:I'm so sick of... by HeUnique · · Score: 3

      It will be skinnable in newer versions, so you will have this GUI, as well as the standard GUI that you're used too.

      --
      Hetz (Heunique)
    3. Re:I'm so sick of... by waldoj · · Score: 1

      Amen. I was hoping that those screenshots were skinned, but they're not. How about a little unity? X will not be usable to the average consumer until these programs stop looking so damned different. Control-F4 to close a program, or Alt-W? Should the close button be top left or top right? Isn't the architecture of Gnome (or KDE) such that people don't specify how these things work, but the window manager figures that out? 'Cuz this shit is *dumb*.

      -Waldo

    4. Re:I'm so sick of... by Drone-X · · Score: 1

      X will not be usable to the average consumer until these programs stop looking so damned different. Control-F4 to close a program, or Alt-W?

      Gotta hurt when you try to go to console 4 ;). I'd suggest stricking with Ctrl+W or Ctrl+Q as is now done in most Gnome programs (what's up with the difference anyway, it's probably confusing for beginners).

    5. Re:I'm so sick of... by SYS2066 · · Score: 1
      I completely agree with you. A good keyboard controlled UI is really what's needed, it can still be graphical of course, but every function should be able to reach keyboard-wise. Either using the menus (ALT-) or a regular shortcut. Many of the "organic" interfaces don't even seem to have a menubar, and no keyboard shortcuts either (I'm not sure how this application works, it might be nice, but it looks like many other organic apps).

      Apple: Having an UI that makes users want lick on their screen is not only good. The screen can get dirty ;-) // Simon

  7. Dept of Redund Dept by OlympicSponsor · · Score: 1

    "RPM Package Manager"? Is that anything like "scuba apparatus"?
    --
    MailOne

    --
    Non-meta-modded "Overrated" mods are killing Slashdot
    (Hey Ryan! Here's your proof!)
    1. Re:Dept of Redund Dept by Zecho · · Score: 1

      You'd be correct if the files handled by the Package Manager were of the type R. However the actual file extension/file type being RPM the correct term would be RPM package manager. Going along your train of thought, deb package manager would also be incorrect.

    2. Re:Dept of Redund Dept by Shadowlion · · Score: 1

      Or ATM machine, or PIN number...


      --

    3. Re:Dept of Redund Dept by egregious · · Score: 1

      Or NIC card, Or RPMs...

    4. Re:Dept of Redund Dept by egregious · · Score: 1

      You'd be correct if the files handled by the Package Manager were of the type R. However the actual file extension/file type being RPM the correct term would be RPM package manager. Going along your train of thought, deb package manager would also be incorrect.

      Um... Yeah. Redhat package manager package manager? "deb" isn't an acronym, "rpm" is.

    5. Re:Dept of Redund Dept by egregious · · Score: 1

      Or NIC card, Or RPMs...

      Yeah, mea culpa: RPMs like the engine term... Or, revolutions per minutes?

    6. Re:Dept of Redund Dept by tssm0n0 · · Score: 1

      Don't ferget FAT Tables!

      Man, that's one phat table...

  8. It's about bloody time by TWX_the_Linux_Zealot · · Score: 1

    I like my rpm based distro, SuSE. I like how they have implemented booting, system changes, etc. I like what options they give at install. I don't like trying to change it ever after it's on there though, because it makes upgrading impossible because the downloaded tar.gz's don't work the same way as they otherwise would have. Maybe in the next six months to a year something will FINALLY be done... Debian is a nice distro, but it's definitely not easy to install...

    "Titanic was 3hr and 17min long. They could have lost 3hr and 17min from that."

    --

    IBM had PL/1, with syntax worse than JOSS,
    And everywhere the language went, it was a total loss...
    1. Re:It's about bloody time by Zecho · · Score: 1

      Debian is definitely not an easy distro to install, especially for beginners. But, IME the debian system keeps better track of installed components and dependancies, which could possibly make eveyday (un)installing much easier and streamlined for the average newbie.

    2. Re:It's about bloody time by SquadBoy · · Score: 2

      This has been bugging me lately and you are near and the first one I saw this morning but Where does this idea that Debian is hard to install come from and really how long do you spend installing a system. Now granted before 2.2 maybe it was kind of hard because you had to go to dselect to do it. But the 2.2 install is cake. I will give a walkthrough. Boot, tell it what keyboard you want to use, partition, set up your swap partition, mount the rest of your partitions, install the kernel, choose modules (drivers) for your hardware, install the base system, set up networking and time, install lilo, reboot, give it a root password and make another user, choose simple and choose the tasks you want to install, pay a little attention to what packages are installed by default note any you would like to get rid of, let it install what it needs to, answer some basic config questions if not sure the defaults are really sensible, apt-get remove anything you don't want (I just hate XDM) apt-get install anything you want (Netscape and Mozilla are both good) Run xf86config (If this is hard for you maybe you really should be running RH)and you are done. Now really what was so hard about that? Could somebody please tell me just what is so hard about installing Debian?

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    3. Re:It's about bloody time by Zecho · · Score: 1

      What I took from the original comment, was that the installation of a Debian system is a lot more involved and complex than the installation of (yes)Red Hat or Mandrake or the like. With the importance of the term User-Friendly in the effort to take linux to the common desktop environment and build a user base that consists of more than tech-savvy geeks, Debian lacks a lot to be desired. I can bring copies of windows, the aforementioned RedHat and Mandrake and possibly a few other distros home to my parents house and they can install either without any input from me. The chances of them going to bestbuy, purchasing a Debian CD set, coming home and installing and actually becoming a member of the slowly growing list of *nix users are less than slim.

    4. Re:It's about bloody time by thue · · Score: 1

      Linux mandrake autodetected all my hardware. Debian autodetected none of it. It was a bit of a pain to try to figure out which driver my ethernet card needed, and dusting of the monitor manual for refresh rates. And manual mouse and video card configuration is a pain, except I had tried those before so they ddin't really take long.
      And now I am at it, I had to download a lot of drivers etc. before I could start on the network install. I can't see why it couldn't just put all the essentials on one floppy and then get the rest of the base system over the network.
      Oh, and dselect is a horrible user interface. They really need a good graphical one under X. (I use apt currently)

      But when installed debian is really nice and robust. After all, why else would I use it? :)

    5. Re:It's about bloody time by SquadBoy · · Score: 1

      Yes you install it and then you are done then you need to maintain it. Now lets see you get the all the new updates for Mandrake with two commands. Keep in mind you spend ~1 hour installing a system and after you have done it the first few times it gets really easy then you spend the lifetime of the hardware maintaining it and for that it does not get better the Debian.

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    6. Re:It's about bloody time by TWX_the_Linux_Zealot · · Score: 1

      If I'm going to use an OS that I'm going to have to wrangle with all of the time simply to have good package management, I'm going to use FreeBSD. It has a much better tool than dselect, one called 'sysinstall', which will let one manage packages and check dependencies and all that jazz, and it'll install via FTP or HTTP Proxy. I don't have to worry about having a packages list onhand later if I want to add stuff, it'll retrieve it and display it for me when I load sysinstall. In a way, the current FreeBSD has some of the better features of the various linuxes without the crap. I just wish that they were better on the unstable development.

      "Titanic was 3hr and 17min long. They could have lost 3hr and 17min from that."

      --

      IBM had PL/1, with syntax worse than JOSS,
      And everywhere the language went, it was a total loss...
    7. Re:It's about bloody time by TWX_the_Linux_Zealot · · Score: 1

      I'm not even concerned with an 'easy' install, I'm just looking for a 'not a pain in the ass' install. When the installer crashes (which may just be a problem I have, but I've had it a lot with debian), I get mad, especially if I'm trying to do anything on a deadline. I had a problem with this at work and had to install via FTP via HTTP Proxy, which took a very long time, and I'm constantly finding pieces missing, because it skipped that nice 'what kind of computer do you want today?' menu, and I had to select packages by hand, with dselect.

      "Titanic was 3hr and 17min long. They could have lost 3hr and 17min from that."

      --

      IBM had PL/1, with syntax worse than JOSS,
      And everywhere the language went, it was a total loss...
    8. Re:It's about bloody time by Zecho · · Score: 1

      First to Squadboy, try re-reading my original post.
      Second, there is a GUI running under Gnome, named appropriately Gnome-Apt, that does a somewhat decent job of maintaining Debian packages. However, you'd be hard pressed to convince me that dpkg, yast, whatever is simpler for INSTALLATION than an RPM based system.

    9. Re:It's about bloody time by SquadBoy · · Score: 1

      Yes I understand and it was not really about your original post but more a answer to the mandrake user. I guess I just don't get the focus on installation. Something you do once per box as opposed to maintaince something you do every day after the install. Yea installing Debian you have to think and pay attention. I don't know maybe some people spend hours and hours installing just does not make alot of sense to me.

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
    10. Re:It's about bloody time by Zecho · · Score: 1

      The point I was trying to make is that if you can't install it, maintaining it is a moot point. I have many times (in a crunch for .. well time) totally wiped a drive of Debian and installed a Mandrake or RedHat system just because it's easier to stick in an auto-install floppy and wait an hour for the install than to try and rebuild a Debian system from scratch.

    11. Re:It's about bloody time by technomancerX · · Score: 1
      Umm, how about a few mouse clicks and a password? Click the updates icon conveniently located on your X desktop, enter the root password, click OK (or hit enter), click Update List, click Select All (or individually select the updates you want/need), and click Do updates... The Update tool in Mandrake 7.2 is really sweet...

      .technomancer

      --
      .technomancer
    12. Re:It's about bloody time by lunatik17 · · Score: 1
      However, you'd be hard pressed to convince me that dpkg, yast, whatever is simpler for INSTALLATION than an RPM based system.

      First of all, YaST is RPM-based. Secondly the difficulty, perceived or otherwise, comes from the target audience for Debian; namely, not newbies. Corel Linux was Debian based, and installed easier than any other distro I've seen. It's certainly possible to make Debian easy, but that's not the priority. There are many different types of people who use Linux, and ease of use is not a top priority for all. If you're having trouble installing Debian, use something else. No big deal.

      As for maintainance, let's compare them:

      RPM: rpm -ivh package.rpm
      DEB: dpkg -i package.deb
      RPM: rpm -Uvh package.rpm
      DEB: apt-get install package
      Pretty much the same, although apt-get really does kick ass. It's good to see RPM users can use it now too.

      --

      Here's my DeCSS mirror, where's yours?

    13. Re:It's about bloody time by SquadBoy · · Score: 1

      Bah that means that I have to install X :) Sounds better than RH. In any case I really agree with the above about user friendly not really being that important just figured out why I don't get it thanks all. I'm not pissed off anymore.

      --

      Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
  9. The shifting sands of Linux by Kiwi · · Score: 3
    I am sure a number of people will reply by complaining that this does not work with RedHat 7. The fact that it does not work with RedHat 7 highlights what is both a good thing and a bad thing for Linux:
    • Linux is in a constant state of change.
    A slick program like this takes many man hours to develop. Due to the constant changes done to Linux, developers not only have to do all the effort involved with developing their program, but also have to expend a lot of effort keeping track of every single change to the Linux distributions thrown their way.

    There is a lot of excitement in the Linux community about getting the latest distribution of (Debian/RedHat/SuSE/Slackware/whatever). This excitement oftentimes results in neglect of older, oftentimes more stable releases of Linux systems.

    To RedHat's credit, RedHat still supports releases as far back as RH5.2, in the sense they still releases security upgrades for RH5.2. About a year ago, RedHat silently stopped releasing security upgrades for RH4.2. Since I still run a RH5.2 server (too far away and too mission-critical for me to conveniently upgrade), I dread the day no more security patches are made available for RH5.2.

    I know that the people at Linux Weekly News have been making somewhat of a stink over the fact that Debian announced that they would not make available security patches for 2.1 bugs immediately after releasing Debian 2.2.

    Anyway, the point being: The "latest and greatest" is not always the best solution.

    - Sam

    --

    The secret to enjoying Slashdot is to realize that it should not be taken too seriously.

    1. Re:The shifting sands of Linux by stefanlasiewski · · Score: 1
      I am sure a number of people will reply by complaining that this does not work with RedHat 7

      What's ironic is that RedHat's up2date service doesn't support RH 7 either (At least, there is no rhl-7.0 directory under ftp://ftp.redhat.com/pub/up2date ).

      --
      "Can of worms? The can is open... the worms are everywhere."
    2. Re:The shifting sands of Linux by Syberghost · · Score: 3

      They've also been promising an up2date that works through firewalls "in a couple of weeks" since at least October.

      They won't respond to emails inquiring about this, either; not even to say "we don't have a time estimate yet".

      So, I just continue to report to my Fortune 100 employer that RedHat doesn't have an auto-update solution yet, and doesn't respond to email.

      -

    3. Re:The shifting sands of Linux by Sc00ter · · Score: 2

      That's probably because RH7 has it's own update manager that looks like it's derived from the Helix Gnome updater
      --

    4. Re:The shifting sands of Linux by Bruce+Perens · · Score: 2
      Supporting back releases of Debian is probably within the purview of a commercial Debian derivative, not the Debian organization itself. However, Debian supported LIBC 4 long after they needed to. LIBC 5 is still supported. Debian releases aren't like Red Hat 7.0 (or Red Hat 6.0), they are a good deal more tested and when they are finally released, users should upgrade.

      Thanks

      Bruce

    5. Re:The shifting sands of Linux by mrdlinux · · Score: 1

      Why in the world would you use Redhat if you need a distribution that can auto-update? Debian's APT is far more versatile, and its been around longer. Let your Fortune 100 employer chew on that.

      --
      Those who do not know the past are doomed to reimplement it, poorly.
    6. Re:The shifting sands of Linux by teg · · Score: 2

      It has been released for some time now - look for up2date 2.1.7

      As for emails, who did you send them to?

    7. Re:The shifting sands of Linux by Syberghost · · Score: 1

      It has been released for some time now - look for up2date 2.1.7

      A week isn't a very good match for "some time" but thanks for the info!
      -

    8. Re:The shifting sands of Linux by Syberghost · · Score: 1

      Why in the world would you use Redhat if you need a distribution that can auto-update?

      Exactly my point.
      -

  10. Recursive? by Gothmolly · · Score: 1

    RPM Package Manager, isn't that like ATM Machine, or VIN Number?

    --
    I want to delete my account but Slashdot doesn't allow it.
  11. Re:all linux users are criminals by chissad · · Score: 2

    That's not humorous at all. Please make way with your parody on such sensitive issues.

    --


    -root is lord.
  12. Re:all linux users are criminals by Jedi+Alec · · Score: 2

    Please do not reply to the idiot. Giving him/her/it* attention will only make it worse. Just adjust your threshold.

    * Underline appropriate option. Multiple options may be valid.

    --

    People replying to my sig annoy me. That's why I change it all the time.
  13. The Two Cultures once again by dmorin · · Score: 2
    Things like this (and helix-update, another neat toy) are vital if we ever expect to get Joe User working with Linux. I bang my head against the screen every time someone says "Package? Why don't you just compile the source?" Say it with me...the majority of the population are not programmers....if you make an OS that is only for programmers, then you will never get market share...

    Besides, anybody who says that compiling their own source automatically makes them better understand their machine must not ever execute those "make install" scripts. If an automated process puts 100 files across 12 directories on your machine, and you tell me you can keep track of them all in your head for 100 software packages, I don't believe you.

    1. Re:The Two Cultures once again by elegant_dice · · Score: 1

      dmorin, you have said what I have been yelling at my screen while reading earlier posts, but in a much nicer way!

      Go the binary, get the .deb/.rpm, and you have a (mostly stable, especially with potato) working program straight away. if theres a problem, talk to the author or go get the source... 99.9% of the time there is no problem.

      running 'make install' won't help you understand anything about the source, you must spend time to read and track the source. considering i have over 800 packages installed, the compile-all approach would only work will on a 486 with a 100mb hd.

  14. Hey,autoslack ,anyone? by xcyber · · Score: 1
    http://www.userlocal.com/interviews/cantrell121800 /cantrell2.shtml

    in all the way that most distro is adopting what apt-get doing@

    DEBIAN ROCKS

    --
    xcyber """"""Complexity for the sake of complexity is not a solution, neither is simplicity for the sake of simplicity
  15. Hierarchical package display by dpilot · · Score: 2

    My pet peeve is the silly hierarchical package display. You have to figure out exactly where in the hierarchy the developer chose to stick the silly thing. Often a package can logically go in one of several places, and it seems that almost as often, yet a different place was chosen.

    I like xrpm, which gives a flat view of installed packages or rpms in a directory. A long list, but no hiding in odd mislabeled corners.

    Unfortunately, my RH 6.2 has 'aged' too much. I'm seeing too many things that pretty much require me to turn it into RH 7 with prerequisites, so I may as well take the faster route. Then get the updates on, etc.

    RPM is handy for a user, as opposed to a developer. Though I try to understand more of the nuts and bolts of what's happening, my computer is more of a tool than a programming machine.

    --
    The living have better things to do than to continue hating the dead.
    1. Re:Hierarchical package display by HeUnique · · Score: 2

      The program got a built-in search engine, and from GUI aspect, I think a collapse tree is very confusing. The tree is "folded", so you can either "open" the tree or use the search engine..

      --
      Hetz (Heunique)
  16. Will it ever get the backing of Redhat? by miahrogers · · Score: 2

    Warning, I am a debian user.

    I don't think that redhat will ever give an automated-updating package manager their full support. It's a pain to get all of the little dependencies for RPM(this depends on that, which depends on those 8 packages, two of which require a new version of pacakge q), which helps them sell cds.

    This is not at troll, but honestly, redhat has to sell cds, and I belive they have held back support for automatically updating package managers because they would rather have their users go out and buy redhat cds.

    Now Eazel and I belive helixcode are gearing up to offer subscription(money)-based automatic system updaters, and I remember hearing something similar from redhat at one point. But I doubt they will ever support one for free. It's a sad fact that often technology advances are held back because a company needs to make money.

    An interesting thing to try would be to make it so you could do bug-fixing upgrades (1.0 to 1.1) but not feature upgrades (1.0 to 2.0). And in order for that upgrade you would have to be running the new version of Redhat. "6.0 lets you upgrade from 1.0 to 1.1, but to get the added functionality of 2.0 you need to buy version 7!".

    1. Re:Will it ever get the backing of Redhat? by tweedle99 · · Score: 1

      Well... Aduva Manager, unlike Helixcode and Eazel is for free and will remain that way...

    2. Re:Will it ever get the backing of Redhat? by Enahs · · Score: 1

      /*
      I don't think that redhat will ever give an automated-updating package manager their full support.
      */

      I started to disagree for some odd reason, but you're entirely correct. Doing Debian-like apt-getting would kill RH's CD sales. People like me would still buy CDs, since I live in Bumfuzzle USA with my blazing-fast 56k analog modem connection, but I tend to go the Cheap-Bytes route.

      /*
      Now Eazel and I belive helixcode are gearing up to offer subscription(money)-based automatic system updaters, and I remember hearing something similar from redhat at one point. But I doubt they will ever support one for free.
      */

      One nice thing about Red Hat is that they make their distribution (at least the free software) available for download. You can pull a Mandrake and simply re-release RH with apt-get, YUP or whatever automatic dependency management you wish.

      If I could find a server to throw stuff on, I wouldn't mind seeing this done. :-) I personally have a bit of a problem with Debian; too many people wanting to set community policy. Yes, thank you, I'm too stupid to know whether or not software is truly Free and I might accidentally use some non-Free software in a situation that violates the license. I'm entirely too stupid to read the license, so yes, thank you for making that decision for me. Thinking makes my brain hurt! ;-)

      --
      Stating on Slashdot that I like cheese since 1997.
    3. Re:Will it ever get the backing of Redhat? by teg · · Score: 2

      We already ship tools for automac update (up2date), and has done so for some time.

  17. So ugly by dwlemon · · Score: 2

    Those screenshots are terrible. I hope that's a GTK theme or something, because I'd hate to have THAT on my desktop. I'm probably wrong. It's probably all hard-coded ugliness. Or even worse, they went ahead and wrote a whole theming engine for their one app while Qt or GTK already have the ability to make your desktop as ugly as you want.

    I thought web sites were supposed to look more like applications in order to be more usable, not the other way around.

    Who designs this crap?

    1. Re:So ugly by sharkey · · Score: 1

      Boy, I'll second that. It looks like it was put out by Netscape.

      --

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    2. Re:So ugly by tweedle99 · · Score: 1

      Well... you'll have to admit it is innovative:) Next version will be themable.

    3. Re:So ugly by Nodatadj · · Score: 1

      Bullshit.
      Bryce, anything from metacreations.

  18. It will support 7. by bero-rh · · Score: 2

    I've talked with Aduva people a while ago, their plans are to add support for 7 in a while.

    As for "silently" dropping 4.2, it's not really true. We have always supported the end-of-line releases for the last 2 major versions, meaning 4.2 was dropped when 7 was released, 5.2 will (unless our policy changes) be dropped when 8 will be released. I'm quite sure this information is publically available somewhere.

    --
    This message is provided under the terms outlined at http://www.bero.org/terms.html
  19. Aduva Manager... by jmccay · · Score: 1

    Anyone check out the Licenses attatched to it? There are a lot. Also mentioned in the licenses:

    ADUVA RESOLVE LIBRARY BETA TEST LICENSE AGREEMENT
    Section 1.
    "a limited, non-exclusive license and right to non-commercial use of one copy of the Program on your desktop computer or on a portable computer, all for the purpose of testing the Program."

    This leads me to believe this will not always be free. You could end up paying for this "service" (the use of their database). Doesn't that violate some of the previous Licenses? After glancing at this, I doubt I will use this. Sounds to sketchy to me.

    --
    At the next eco-hypocrisy-meeting, count the private jets used to get to the meeting. Should be interesting to see that
    1. Re:Aduva Manager... by mixerfix · · Score: 1

      There is no intent to fleece the private users. In fact, it is probably not profitable. However, the way the program works, if for some reason the user grows tired of the Aduva Mangler - all that needs to be NOT done is run the program. C'est touts. :-)

  20. Re:Dept of Redund Dept-OT IGNORE by Zecho · · Score: 1

    AC who would have guessed? LMAO

  21. this will be taken as a flame. by small_dick · · Score: 1

    but it isn't. i really wish redhat would drop their distro and go with debian.

    in fact, i wish all the distros would re-center around debian.

    how much energy has been spent here, supposedly making "rpm as good as debian", when debian is already the standard of excellence?

    imagine redhat's prowess at making Linux easier...applied to debian. really, all these offshoots seem to be a waste of creative energies.

    --


    Treatment, not tyranny. End the drug war and free our American POWs.
    See my user info for links.
    1. Re:this will be taken as a flame. by bruns · · Score: 1

      Dont care how much people tell me, no dist is perfect, Debian is far from perfect, like Redhat, Slackware, etc are also.

      Use what you want, but dont try to convince someone else that their dist is so inferior to yours. The major advantage of Linux is choice. No one vendor, no one controlling group.

      --
      Brielle
    2. Re:this will be taken as a flame. by banky · · Score: 1

      Red Hat GNU/Linux? Not bloody likely. The Stormix people have tried to be the Red Hat of Debian, as did Corel, and it seems to have stalled and failed, respectively.

      Red Hat can't hardly afford to just up and drop RPM in favor of dselect/apt. Talk about the mother of all breakings! Seems like the work needed to bridge the gap is better spent fixing RPM. Its probably an equally herculean task.

      --
      ZOMG I WOULD LOVE TO KNOW ABOUT YOUR FEELINGS ON MACINTOSH VERSUS WINDOWS, VI VERSUS EMACS, AND HOW YOU'RE NOT A DORK
  22. I'm with you there dude! by Greyfox · · Score: 2

    The first thing I thought when I looked at the screenshots was "Looks like Lotus Notes 5.0. Ugh." The program sounds cool in concept, but I wish they'd stick to GTK so the program looks like everthing else on my desktop (except Netscape and Emacs.)

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:I'm with you there dude! by paulbd · · Score: 1

      There's actually some evidence that they are using GTK. Don't assume that by using GTK you are forced into the disgustingly boring looking GUI's that we see all the time with Linux apps. I have several apps that use GTK to do heavily pixmap-based GUI's, and I happen to think they are much better for it. I don't want my software to look like everything else on your desktop, though I do let you use GTK themeing to alter its appearance without recompilation.

    2. Re:I'm with you there dude! by HeUnique · · Score: 2

      > There's actually some evidence that they are using GTK...

      Nop. QT 2 is being used.

      --
      Hetz (Heunique)
  23. it's a step, but in the wrong direction by SuperQ · · Score: 1

    this is still a step in the WRONG direction. It's the same problem that mandrake has.. it's pretty, it's GUI, but it's not capeable of being used for automation.. there MUST be a backend library, like apt, to do the real work.. if I can't use it with a CLI, in a shellscript, I can't use it for my network automation. these GUI's are great for users, useless for companies with large network installs of boxes... I don't want to go back to rsync'ing boxes. looks like I get to stay with debian for now. (conectiva's apt port is the right way of doing it.. they are on my list of good distro's now)

    1. Re:it's a step, but in the wrong direction by mixerfix · · Score: 1

      The standard aduvizor RPM should include ttyzor which runs on the command line. It is quite stupid, IIRC, but at least does not require a running X11 ;-). M

    2. Re:it's a step, but in the wrong direction by PollMastah · · Score: 1

      Ermmm....

      It is not a step in the wrong direction. It gives normal desktop users something they want; if you don't like it, you already have Debian anyway. Remember, Linux is about choice. People keep moaning and groaning about how we need a standard package manager, how redhat sucks and debian rulez and we should standardize on debian, and how debian sucks and redhat rules and we should standardize on redhat, etc. etc.. They're all missing the point, which is that Linux is about choice.

      If there were a single, "standard" Linux, it'd look frighteningly like M$ to me. But here we have different Linux distros, each of which offers different advantages, and are learning from each other (eg., adding apt-get-like features to RPM). This is a sign of health.

      --

      Poll Mastah

  24. "RPM Package Manager" by Phexro · · Score: 2

    i guess "rpm" now means "redundant package manager".
    --

  25. Re:Uh, fellas... by xcyber · · Score: 1

    come on,he is a graduate of computer science don't demand too much

    --
    xcyber """"""Complexity for the sake of complexity is not a solution, neither is simplicity for the sake of simplicity
  26. Licensing by egon · · Score: 5

    Did anybody see the licensing on this? Read on...

    12. Access to the ADUVA Server

    Aduva provides at present free of charge access to the ADUVA Server and to the
    ADUVA KNOWLEDGE BASE. Aduva may charge in the future for access to the ADUVA
    Server and/or the ADUVA KNOWLEDGE BASE. The information and/or any other data
    received from the ADUVA Server is the sole property of Aduva and is protected
    by copyright and other rights.

    I wonder if they have a privacy policy...
    --
    Give a man a match, you keep him warm for an evening.

    --
    Give a man a match, you keep him warm for an evening.
    Light him on fire, he's warm for the rest of his life
    1. Re:Licensing by xcyber · · Score: 1
      ADUVA is not a free software boycott it

      apt-get is superior

      --
      xcyber """"""Complexity for the sake of complexity is not a solution, neither is simplicity for the sake of simplicity
    2. Re:Licensing by update() · · Score: 3
      Aduva provides at present free of charge access to the ADUVA Server and to the ADUVA KNOWLEDGE BASE. Aduva may charge in the future for access to the ADUVA Server and/or the ADUVA KNOWLEDGE BASE.

      Is this different from the policies for the Eazel and Helix Code updaters? They're planning to eventually charge for use of their databases as well. (Hint: That's how they might conceivably make money.)

      The real question is whether the Aduva source will be released -- and according to the license page it will be, under the GPL.

    3. Re:Licensing by bluebomber · · Score: 1

      Except maybe to the Communists (RMS?), it should seem perfectly legit to make money off home users... or have I missed something?
      -bluebomber

    4. Re:Licensing by tweedle99 · · Score: 1

      Yes, it is different from the policies of Eazel and Helixcode: Home users won't pay! Not for services, not for access to the KB not for the application. Both Eazel and Helixcode will charge for services regrdless if you are a home user or a commercial one. The source will be released pretty soon...

    5. Re:Licensing by angelo · · Score: 1

      Well, if HelixCode charges, they better upgrade their pipe.. It's actually slower than the main us debian servers, if that were possible! (note: of course, thise depends on time of day, release schedule, etc. Your mileage may vary)

    6. Re:Licensing by GrenDel+Fuego · · Score: 2

      Helixcode gives you a list of download sites. Which are you choosing?

    7. Re:Licensing by angelo · · Score: 1

      Spidermonkey. It's currently the only apt-get choice.

    8. Re:Licensing by tweedle99 · · Score: 1

      Well as far as I understood helixcode's future business model - they will charge. I'll be glad to find I was wrong on this one. Tweedle99 does want Linux look good:)

    9. Re:Licensing by tweedle99 · · Score: 1

      You missed the point! I'm being payed by aliens to conquer the world. common...

    10. Re:Licensing by tweedle99 · · Score: 1

      to start with, you might want to enter their websites and read carefully everything as I did before writing...

    11. Re:Licensing by tweedle99 · · Score: 1

      Right you are, but one point you miss is that none-commercial users won't ever have to pay for any of these features. Aduva will not charge money from home users.

  27. bero by gimpboy · · Score: 1

    whats your opinon of aduva?

    use LaTeX? want an online reference manager that

    --
    -- john
  28. Re:But does it have support for... by mixerfix · · Score: 1

    not yet. we may be adding support for beowulf, depending on demand. Let's see demand, eh? Easier to canvass resources if the community raves for it, no? ;-). M

  29. Do any of these leave the packages locally? by PRR · · Score: 1

    One of the things I like about the Helix updater is that it gives you the option to leave all the packages in a local /tmp directory (which could be useful if I had to do some over, or if the connection stalled in the middle, or whatever)

    Do these RPM manager installers give you this option also?

    Just curious, does Debian apt-get have that option too?

    And do these rpm (and deb) tools do all the downloading first, then install all ... or do they install each package immediatly after it's downloaded before downloading the next?)

    1. Re:Do any of these leave the packages locally? by tweedle99 · · Score: 1

      1. Yes, the Aduva Manager gives you the option to leave all the packages in a local directory. 2. The Aduva Manager asks you whether you care to install all and then it downloads and install all, not one by one. 3. Debian has this option as well.

    2. Re:Do any of these leave the packages locally? by AYEq · · Score: 1

      Debian's apt seems to keep all of the dowloaded deb's in /var/cache/apt. It seems to keep even older versions which came in handy when exim broke on one of the updates in the unstable tree

  30. What all Linux Package Managers Lack... by uslinux.net · · Score: 5

    Unfortunately, all the Linux package managers (apt/dpkg, rpm, etc) lack one vital feature that all the big guys (IBM, Sun, HP) have included for years - the ability to install, but not commit a package.

    One of the things "enterprise" Unices have is the ability to upgrade a package, while the system backs up your old package. If the package upgrade breaks something, it's simple to roll back to the prior state. If everything goes OK, it can be run through it's paces for a while, and then eventually "committed", whereby the old information is deleted.

    Until some flavor of Linux adds this to their package management, Linux WILL NEVER be able to take over the corporate world (yeah, there's a lot of other things it needs to, like 32-bit UIDs and a journaling filesystem, but at least they're on their way).

    1. Re:What all Linux Package Managers Lack... by mixerfix · · Score: 1

      actually, debian dows provide debian-repack which _could_ be used to a-priory back up a package before replacement ;-). Space concerns are another issue, YMMV.

    2. Re:What all Linux Package Managers Lack... by bluebomber · · Score: 2

      Right. Because Windows has provided "install, but don't commit" functionality for YEARS. Give me a break.
      -bluebomber

    3. Re:What all Linux Package Managers Lack... by shallot · · Score: 1

      Although this would undoubtedly be a great feature, Debian works around the lack of it by having packages that actually upgrade without major problems. Sure, it's the harder route, and the rule does have exceptions (98% of which happen only in unstable, and we all know nobody in their right mind upgrades Perl every day on a production machine), but it's (being) done. Feel free to try it :)

    4. Re:What all Linux Package Managers Lack... by TV-SET · · Score: 1

      Well, actually there is a kind of attempt in RPM to save something. Ocasionally, the configuration files are backed up into filename.rpmsave, though I have not found any trend so far...

      ...sometimes it works, sometimes it does not...that's life ;)

      --
      Leonid Mamtchenkov ...i don't need your civil war...
    5. Re:What all Linux Package Managers Lack... by Bruce+Perens · · Score: 1
      I've seen demonstrations of apt's "downgrade" logic, probably close to two years ago. Perhaps Jason abandoned it, I'm not sure.

      Thanks

      Bruce

    6. Re:What all Linux Package Managers Lack... by ErikSev · · Score: 1

      I haveta disagree. While I haven't put a ton of effort into it, my debian system right now refuses to upgrade almost 20 packages because something somewhere is screwed up. Probably some more of the perl bullshit it took me a while to track down last time. Even if this isn't a business machine that costs me tons of money if it screws up, it's still a pain in the @$$ sometimes to run unstable on it. An option like the parent suggested would be well worth it.

      Erik

    7. Re:What all Linux Package Managers Lack... by lemox · · Score: 1

      You're running UNSTABLE, what the hell did you expect?!?! Stability?!

      I love it when people bitch about how "unfriendly" Debian is when they are explicity told that things will "randomly break" when running unstable. That's why unstable is not released.

      The worst part is that you're getting the better end of the deal running unstable Debian. Try running Mandrake Cooker or Rawhide... then you'll have something to complain about.

      --

      "We obviously need a new moderation category: (-1, Woo-fucking-hoo)" --Mr. AC

    8. Re:What all Linux Package Managers Lack... by 6j3 · · Score: 1
      uselinux.net wrote:
      Unfortunately, all the Linux package managers (apt/dpkg, rpm, etc) lack one vital feature that all the big guys (IBM, Sun, HP) have included for years - the ability to install, but not commit a package.

      One of the things "enterprise" Unices have is the ability to upgrade a package, while the system backs up your old package.

      bluebomber wrote:
      Right. Because Windows has provided "install, but don't commit" functionality for YEARS. Give me a break.

      Funny?

      Would have been if Windows was considered enterprise class for *YEARS*. Or if it was mentioned in the original post.

      But, but... MaAAHum, I wanted to moderate the /. moderaters.
      Don't worry, Eric. You'll get your turn.

  31. Licensing by egon · · Score: 2

    Received the following:

    Date: Wed, 27 Dec 2000 22:31:05 +0200
    From: Ury Segal
    To: egon@tuininga.org
    Subject: Aduva Manager Privecy issue

    [ The following text is in the "windows-1255" character set. ]
    [ Your display is set for the "ISO-8859-1" character set. ]
    [ Some characters may be displayed incorrectly. ]

    Hi!

    I am Ury Segal from Aduva.

    I just wanted to say, in advance to the answers to your question you'll
    probably get tomorrow ( It's 22:27 here ), that your privacy is kept, and
    Aduva Manager does not send the inventory of your computer to our
    servers. All we have is your IP ( and what you asked to download -
    but that's just any FTP site can do. )

    We are making the sources ready for GPL, and then you'll be able
    to check my claim, but till then - you can either sniff the packets and
    see for yourself, or just believe me :-)

    (The stream is SSLed, but it's sniffable if you are
    on one end )

    --
    Ury Segal
    Aduva INC

    Phone: +972-3-7534300
    Fax: +972-3-7534343

    --
    Give a man a match, you keep him warm for an evening.

    --
    Give a man a match, you keep him warm for an evening.
    Light him on fire, he's warm for the rest of his life
  32. Integration by redhog · · Score: 3

    This program is just one of many coming out lately that does the same error as Microsoft: Merging functionality and user interface. A package tool should consist of either one (or both) of a) a library b) a command line tool. Merging UI and functionality makes it very hard to change the UI (bringing it to a web-based administration, automation, etc) in the future, if needed.

    Unfourtunately, this have been done a lot lately, mainly by KDE developers (No offense, you make a really good GUI, and some really nice functionalities, but could you please separate the two?):

    * KMail have functionality to download mails and filter mails to different mailboxes (It should have used fetchmail and procmail for that, and provided only a graphical configuration tool for those two backends).

    * QT contains both basic datastructures (Linked lists, hash-tables, etc) and GUI widgets (Buttons, listboxes, etc). In GNOME, those two parts are separated in Gtk+ (GUI widgets) and glib (basic datastructures).

    * KDE contains a virtual filesystem that enables the user to transparently use files on remote sites using any KDE application. This functionality should have been in the operating system filesystem layer (There are several projects to achive this (portable): Podfuk, Alex, etc) VirtualFS), since as it is now, only KDE applications benefit. Here I might add that GNOME are unfourtunately heading for the same, developing the gnome-vfs (which stems from the Midnight Commander VFS).

    --
    --The knowledge that you are an idiot, is what distinguishes you from one.
    1. Re:Integration by redhog · · Score: 1

      You missunderstund. I want to have a GUI, which uses the backend. The newbie uses the GUI, but a hacker can still use the functionality without the GUI.

      --
      --The knowledge that you are an idiot, is what distinguishes you from one.
  33. I wish they'd all just can rpm and use Debian... by aquarian · · Score: 1

    Redhat and rpm sucks. Debian's packaging system is way better. Mandrake does the best job bundling and configuring their distribution, but alas, it's rpm-based. What I really wish is that Mandrake was Debian based, or that someone would build something as well thought out as Mandrake using Debian. Maybe this new thing will bring Debian-class ease of administration to rpm-based systems, that is, if it actually works.

  34. www.adbusters.org by SubtleNuance · · Score: 2

    This 'Aduva system' stinks of a pay-for-play service of some kind....

    What is the Aduva business-model? What are they planning on doing to feed themselves? Does anyone know?

    1. Re:www.adbusters.org by mixerfix · · Score: 1

      This is, to the best of my limited knowledge (I work in Aduva), not the plan. Pay-for-play for users is, as I said in a previous post, not the plan and, prabably, not very profitable, either ;-).

  35. A Couple of Points of Clarification... by KenCrandall · · Score: 2


    There seems to be some confusions as to what a "package manager" really is. This isn't an 'RPM front-end to apt-get" as Hemos put it. This is a port of apt to support RPM's as a package format. Debian packaging is done through 'deb' packages, which are almost identical to RPM's in form and functionality. Both have evolved to be very good package building, deployment, and retraction tools for software.

    What this, Helix-Update, Eazel Services, apt, and up2date really do is function as package distribution channels. They resolve dependencies, check package location/availability against host-side maintained repositories and download the appropriate packages, once all the dependencies are figured out and resolved. They do not install the packages -- the package manager (RPM, dpkg) does this part. (Well, technically they can, but this would be through either re-writing, or linking to the library form of the package manager.)

    While noone can argue that Debian had this capability first, and probably (currently) does it best due to having time to mature, it's natural that this capability will come to other distros and package formats precisely because it works so well.

    Cheers,
    Ken Crandall

    1. Re:A Couple of Points of Clarification... by KenCrandall · · Score: 1

      Ack...I was a bit vague. The this I spoke of in the first paragraph is Connectiva's work, not the Aduva stuff.

      The this in the second paragraph is the Aduva stuff... Cheers,
      Ken

  36. Doing it yourself... by manyoso · · Score: 1

    I've spent enough time with all these distributions... Seems the only way i can get the linux system i want is to do it myself.

    1. Re:Doing it yourself... by Zecho · · Score: 1

      That link should read
      http://www.linuxfromscratch.org/
      And personally, I'm very much in favor of this for advanced/experienced users. I think I might just re-do the front page of radicalmatter.com to include something where people can rate and comment about distros. Maybe we can line them up, rate them from newbie to bleeding edge, and review what's best and worst about each.

  37. Why can't we all use INST? by the_tsi · · Score: 1

    It's the best all-in-one package tool there is. Sure, it has cryptic file names and horribly difficult-to-use packaging tools (see swpkg(1)), but you get one-of-a-kind features you can't find elsewhere, like the ability to have uniform installation sets across multiple machines (oh, gee, rpm and deb have that, too)! Remote unattended installations (I guess debian can do that, whoops)! And above all else, you get the wonderful "showprods" command that is easy to decrypt and includes its own paging tool which seems oddly like "| more".

    -Chris
    ...More Powerful than Otto Preminger...

  38. Skinnable? *sigh* by TrentC · · Score: 5

    It will be skinnable in newer versions

    I really hope that by "skinnable" you mean that it will use the widget set that your window manager & desktop environment provides, or at the very least provide that as an option.

    That last thing in the world we need are 500 "desktop-ready" applications, each with their own skin format. I already use four different applications that have separate theme formats: XMMS, Nautilus, Mozilla and gkrellm. Combined with GTK and Sawmill, that's 6 different theme formats I have to keep track of. (Well, that's kind of a lie; I have Mozilla installed so I can use Galeon...)

    I don't need a themeable package manager, ICQ client, mailreader, image editor, web server, and SETI@Home client. Desktop environments provide those widget sets for a reason...

    Jay (=

  39. Debian stuff by TWX_the_Linux_Zealot · · Score: 2

    Hey, I got Debian 2.2r1 to install on my 68040 based Mac Centris 660AV, so I'm not saying it's impossible. I've just never had it EVER go as it was 'supposed to'... I've had problems with installing the X Server (in the 2.0 release that I was playing with, the console would cease to respond when working with the X servers and i'd have to manually kill-9 it and try again), I've had problems with dselect, with applications seg faulting on good hardware, and with certain pieces of hardware that worked back in Slackware on the 2.0.0 kernel not work in Debian 2.2r2. Maybe this is being picky, but lots of stuff just gets on my nerves.

    Yes, RedHat, SuSE, Mandrake, etc are easy to install, very easy, like i can put the disk in, boot, select the shiny red button for 'install' (figuratively speaking) and it'll set all the defaults and select all the basic, normal packages. I don't have to do much. Sometimes, like with that Mac, I don't mind a challenge, but when it's just giving me a headache because I want to be able to play sounds or talk to my NIC, it's quite annoying.

    Just my two cents worth...

    "Titanic was 3hr and 17min long. They could have lost 3hr and 17min from that."

    --

    IBM had PL/1, with syntax worse than JOSS,
    And everywhere the language went, it was a total loss...
  40. Re:Dept of Redund Dept-OT IGNORE by Zecho · · Score: 1

    Yeah me too!

  41. Re:Dept of Redund Dept-OT IGNORE by Zecho · · Score: 1

    Try rereading my post again! Uh huh!

  42. props for Conectiva by SomeOtherGuy · · Score: 1

    I for one got all excited when I heard Conectiva had ported apt to work with RPM's. I had to install it and give it a go. A week later, not to bad I must say. The only negative thing I have to say is that Conectiva's web site does not seem to get updated very often (no security update list or FAQ, or Knowledge base, no nothing...) However -- the most important is the distribution -- and so far it rocks!!! It seems like the best of both worlds so far. Cross my fingers. (Will Madrake convert to this for 7.3? -- I wonder)

    --
    (+1 Funny) only if I laugh out loud.
    1. Re:props for Conectiva by pandora-br · · Score: 1

      Unfortunately, the main site (www.conectiva.com) is well behind the portuguese site, but all the updates can be found at http://distro.conectiva.com.br/atualizacoes/ (just select english on the right top menu to see these in english).

    2. Re:props for Conectiva by Captain+Zion · · Score: 2

      Most of the content in Conectiva's site is in http://distro.conectiva.com.br, including news, projects, updates, security annoucements and a webcam.

    3. Re:props for Conectiva by Captain+Zion · · Score: 2
      You can't do that with third-party .deb packages as well, unless the packager follows the distributor's packaging policies. So, if these packages are built in a sensible way and posted in a apt-enabled repository, there's no reason to believe it wouldn't work.

      For example, building packages depending on obsolete packages, or packages conflicting with the distro's official packages, is a good way to break apt-get in both Debian and Conectiva.

  43. NetBSD Package System by daniell · · Score: 1
    I just thought I'd point out, while everyone's arguing how much better than RPM the dpkg system is, that NetBSD's Package System (pkgsrc) is a particularly great system that has the capacity to hide most everything from you, or not. It works particularly well with source packages, which if you like you can configure with particular options yourself, and it also has a good variety of prebuilt packages.

    -Daniel

  44. Profit, that's why! by erotus · · Score: 2

    Because it's more profitable. How's that you ask? RPM is a for-profit company that relies on you buying new releases of their distro for profit while debian, on the other hand, is not.

    If one could apt-get distupgrade a Redhat box ad infinitum you could buy their distro once and upgrade from that point forward. Debian is a non-profit organization and does not worry about cashing in on the next point release. Debian users upgraded from 2.1 to 2.2 by issuing a simple command. Redhat users sometimes have to deal with dependency problems if they want to upgrade a package and you can imagine what could happen with hundreds of packages.

    Redhat benefits when people buy their distro. They might benefit if they could provide an apt-get frontend with a subscription based service. Although I would love to see an apt-get front end thats free to all, I bet the suits at Redhat corp won't let this happen. I could be wrong, but I think the use of a tool like apt-get and especially doing a distupgrade on a Redhat box is about profit and nothing more.

  45. Re:Licensing - This is not free software! by Carl · · Score: 2
    It is worse then that. Read the following two clauses:

    2.You may install the program yourself, but you must do so in accordance with Aduva's instructions. The Program is licensed, not sold. This license does not confer you title or ownership in the Program. The Program is not subject to any General Public License and is in whole or part the proprietary property of Aduva. You are specifically prohibited from reverse engineering the Program.

    7.Confidentiality. All elements of the Program, the servers it attaches to, the manner of operation thereof, the code thereof and the information relating thereto are considered confidential information and you agree to maintain such information absolutely confidential and not to disclose such information to any third party whatsoever without first obtaining Aduva's prior written consent.

    More (including a nasty termination clause) can be found on http://www.aduva.com/mason/new/licenses.html

  46. nice! by Anonymous Coward · · Score: 2

    I just downloaded it and tried it on a machine which I did not touch since I installed Redhat 6.2 on it (it sits here as a printer server), and here is what the program did:

    1. compiled and added sound support for my ES1371 (I didn't know that I have sound card onboard, heh)
    2. Upgraded my Netscape to 4.76 - security update (thats nice!)
    3. updated my gtk

    Then I selected the kernel and clicked Upgrade Now - and it downloaded and compiled kernel 2.2.17 quite nicely..

    Overall - I really like the program - I just really hope that they'll replace the BUTT UGLY GUI and add the option to let me resize the window (it looks very small on EXCEED on my NT when I'm running 1600x1280)

    Good work Aduva!

    YoGi

  47. Re:Aduva: free for non-commercial use only (per FA by pandora-br · · Score: 1
    For connectiva package management - you'll need THEIR RPM'S

    apt is GPL, and so is the port to RPM. Any RPM-based distro is free to use it as it pleases. And many people already used it to upgrade Redhat systems, for example.

  48. Re:Aduva: free for non-commercial use only (per FA by Captain+Zion · · Score: 2
    For connectiva package management - you'll need THEIR RPM'S! - I wish you all the best luck to go out and find your favourite RPM in their format.
    Not quite, apt-get is works fine with Red Hat as well, and possibly Mandrake. Check the apt-rpm mailing list archives for success reports.
  49. +5 Insightful by pohl · · Score: 1

    I'm also worried about this trend. Next we'll need a skin-format-manager that can simultaneously select different skins in all managed applications. Yuck. Now is the time to avert such a crisis, isn't it?

    --

    The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    1. Re:+5 Insightful by uradu · · Score: 2

      Oh, oh, and it should also have an MP3 player, because they can always do it better anyway. And a file manager. And a plug-in architecture, so I can expand it into an entire OS if I so choose.

    2. Re:+5 Insightful by tweedle99 · · Score: 1

      Actually it is not such a bad idea:))

  50. apt-get with Red Hat by Captain+Zion · · Score: 2
    Ok, here's the straight link for apt packages for Red Hat and a success report:

    I just updated ~10 workstations and ~25 production servers from RHL 6.0 and 6.1 to RHL 6.2. It went fine, no troubles [kernels were already upgraded earlier]. Workstations had ~600 packages (1 GB) worth of RPM's, the servers ~300 (400 MB). :-)
  51. Re:Licensing - This is not free software! by Bruce+Perens · · Score: 2
    If they are currently linking to any GPL component, their beta license would not be legit because it would be in conflict with the GPL. But I've not examined their software.

    Given that they say they are going to GPL it, if they are not currently linking to a GPL component, they aren't doing anything wrong.

    Not that I am sure the business model makes much sense. There are too many people willing to give away what they are seeking to sell.

    Thanks

    Bruce

  52. If you want source, but also pkgs, use src.rpms by richie123 · · Score: 2

    Why do so few people use src.rpm?

    I love src.rpm packages for simple reasons, they make instalation and removal a cinch, but at the same time they have all the advantages of source.

    I can recompile with opt flags, change install paths, apply custom patchs, and build myself a nice reusable rpm file for later use.

    For all the people who complain about package systems "robbing me of control" try using src.rpm packages more often, there easy to use, flexable, and give you a nice clean souce tarballs that you can tweak to your hearts content.

  53. RPM front-end to apt-get? by _typo · · Score: 1
    Wasn't that an apt-get front-end to RPM?

    Anyway it's great. If i can apt-get from RedHat and Mandrake I'll start using them for desktops.

    Debian is n1 for servers though.

    --

    Pedro Côrte-Real.

  54. Oh, you mean like rpm -U --oldpackage? by mrsam · · Score: 2
    Well, you do have to have the older version of the package lying around, but that's pretty much what this is.

    Well, technically RPM will automatically deinstall any obsoleted packages on an upgrade, and so you'll also need to grab those as well, but this doesn't happen to often. Besides, you can always do:

    rpm -q -a | sort >before

    rpm -UvhF *.rpm

    rpm -q -a | sort >after

    It shouldn't be too hard to put together a wrapper for RPM that does that, and then reinstall all the older packages if you want to back out.

    ---

    1. Re:Oh, you mean like rpm -U --oldpackage? by Bob+Uhl · · Score: 2
      The problem is that the old package simply has it s default config files, not all the nifty ones you added yourself. Downgrading with RPM can be a bit of a drag at times.

      I just compile from source--that way all the problems are my fault:-)

  55. HTML::Mason by java.bean · · Score: 1

    And they're HTML::Mason newbies too! ;-) See that /mason in the URL? That's how you initially set up Mason until you figure it out and get everything working. I guess it doesn't do any harm leaving it in there, but it looks pretty goofy. (HTML::Mason is a really cool HTML templating package for Perl.)

    --jb
  56. Actually... by Drone-X · · Score: 2

    Next we'll need a skin-format-manager that can simultaneously select different skins in all managed applications. Yuck.

    Helix Code is working on such a program that they call IIIRC a meta theming engine. It currently has support for Gtk, Sawfish and XMMMS but it should be very modular.

  57. Graph by SmokeSerpent · · Score: 1
    I love the area graph that shows how signifigantly the product decreases the required skill level and number of tasks that need to be performed by support staff. Clearly, it will reduce support costs by at least half!

    Of course, it's an entirely unlabeled fiction, but that shouldn't disuade any pointy-hairs.

    --
    All kings is mostly rapscallions. -Mark Twain, The Adventures of Huckleberry Finn
  58. Good for you! You get a cookie! by Enahs · · Score: 1

    >This leads me to believe this will not always be free.

    Yup, in both senses. If that's a problem for you, don't use the software. It's an extremely simple concept. If you don't agree with the license, and you can live without the software, don't use the software.

    One thing that's ignored when discussing freedom is the freedom of an individual developer/organization to choose the license for their own software. I think it's high time we start respecting people for their choices (when they don't violate our rights, which this software doesn't seem to do) rather than bashing them over the head for not releasing software under the GPL.

    --
    Stating on Slashdot that I like cheese since 1997.
  59. Re:What about yup? by Enahs · · Score: 1

    I think it's an excellent idea. I hadn't realized, when I last worked with it, that it wasn't RPM4-friendly yet. :-} It looks great, and doesn't live in the shadow of Debian, which is double good. "Oh look, you had to go to Debian to fix your distro!" No, Connectiva simply fulfilled one of the promises of apt-get -- that it'd be packaging system format agnostic.

    I'd be more interested in yup simply because it's custom-built for RPM and isn't going to get constant flack from Debian zealots.

    --
    Stating on Slashdot that I like cheese since 1997.
  60. automation is good by soellman · · Score: 1
    for a in 1 2 3 4 5 6 7 8 ; do ssh user@host-$a rpm -Uvh http://server/software.rpm ; done

    if you feel the need to compile, compile. but package after that, and you'll thank yourself if you manage more than one machine..

    If you have a problem that requires 'tweaking,' your problem is most likely a configuration problem, not a packaging problem. If you have a packaging problem, make your own packages from source RPMs.

    Of course, if you're like me and have redhat running on a few different architectures, I only get source RPMs and make binary RPMs from there.

    and if you want to use RPM on Solaris, check out snapdragon, very cool. Also to be extended to Digital Unix and Darwin if I ever get the time!
    -o

  61. For x = 1 To null by Graymalkin · · Score: 2

    SuSE for a long time has had the ability to do updates off the web. You run YaST and tell it your installation medium is an FTP server and then tell it you want to update your existing setup. You can go through and install new apps or just update stuff you already have. It's worked pretty well for me and I've had the same system since version 6.1. Things I would like to see added to this are XML package descriptors vis a vis HelixCode, and support for HTTP updates in addition to FTP. YaST2 does all the stuff YaST does but with a friedlier X interface. I also want GNOME and KDE pluggins for YaST2 that will run in their respective trays and keep me up to date on package updates are up on servers.

    --
    I'm a loner Dottie, a Rebel.
  62. I think I'm in love with Linux by cafelatte · · Score: 1

    Software for Linux just keeps on getting better and better. Everytime new software for Linux comes out, it's always got cool and usable features that manage to kick MS's butt. As time goes by, more microshills will be putting their tails up their ass.

  63. FreeBSD anyone? by reh187 · · Score: 1

    is to get a clue and look at the success of the BSD's ports collection... Nothing like a good "make install" and a "make world" combined with CVSup to keep up to date... FreeBSD has done so well on making installs simple yet understandable and controllable. Its easy to kee up with dependancies (as this is controlled all by the Makefile)

    LIB_DEPENDS= tk82.1:${PORTSDIR}/x11-toolkits/tk82


    As you can see, the "LIB_DEPENDS" handles all the dependancies...

    OH AND FREEBSD's Port Collection will always be free... NO LICENCES!!!! :)

    CVSup updates your Makefiles so you have the latest versions... Schedule this with CRONTAB and a good perl script and you are good to go...

    BSD has had it right all along... IMHO

    --
    Sarcasm is the recourse of a weak mind...
    --
  64. Aduva, Conectiva, apt, RPM? by cesarcardoso · · Score: 1

    1) It's written Conectiva (with one n!)
    2) Yeah, I know that RPM 4 has quite important differences relative to RPM 3, but... is programming to RPM 4 so difficult? Or nobody
    (Aduva or Conectiva) wants to tackle it?
    3) It's yet to be seen a success of RPM 4 and Conectiva's apt.
    4) up2date can suck, but for the job it was designed for (maintain people's system updated) works well.
    5) Let's face it, people! apt is great and stuff, but it's used as a kind of up2date/rpmup *BECAUSE PEOPLE WANT ONLY AN UPDATER!*.

    --
    Cesar Cardoso can be found at cesar at zyakannazio dot eti dot br (or at least I believe so)
  65. How Debian' APT does it. by mschmitt · · Score: 1

    1) Calculates dependencies, asks you if you really want to download these 30 MBs of packages. (The required packages along with your requested package.)

    2) Downloads all packages in one go.

    3) Installs the packages.

    4) Packages are left in /var/cache/apt/archives. Keep in Mind that this may fill small /var Filesystem pretty fast.

    Once you've spent a few months with Debian you won't touch any other distro again.

  66. Privacy policy. by eshefer · · Score: 2

    - wonder if they have a privacy policy... They have one, find it here: http://aduva.com/mason/new/privacy.html
    --------------------------------

  67. up2date has just been changed by teg · · Score: 2

    The up2date service has been changed, and no longer uses that directory - it's now a part of Red Hat Network. I like the new program better - I never liked the old one, so I didn't use it much. The new version works nicely, and I use it on my private machines.

  68. Re:I wish they'd all just can rpm and use Debian.. by thanatosis · · Score: 1

    i'd have to agree for the most part. i'm having
    to do a lot of work with rpm packages and the
    rpm source code. i pretty much think it's crap,
    and isn't designed well at all. allowing rpm
    packagers to VERSION tag their packages with any
    arbitrary string, and then trying to logically
    parse it to handle dependency resolution is just
    fucking stupid IMO.
    how does one compare cdalpha3.7p to 0.3.7 ?
    that's just one example,
    there really isn't ANY way to consistently
    perform version comparisons when everyone is
    allowed to make up their own rules.

    I run into these problems all the times, plus
    "circular dependencies" and other such nonsense.

    now a lot of people might argue that those are
    "packager errors", but a lot of stupid packaging
    mistakes could easily be avoided from the outset
    with a more well thought out design.

    i haven't really looked into debian that much,
    but i'm hoping it's a better system.

    --thanny

    --
    Incantations Media Group
  69. up2date can do this by teg · · Score: 2

    Just run "up2date -u", and it will update your system from the command line.

    It can be configured with up2date-config, so if you just want to download the packages or mark certain packages to be skipped you can easily do that as well.

  70. Re:up2date by bensej · · Score: 1

    The system requirements page clearly states that aduva is for Redhat 6.x and will not work on Redhat 7.0

  71. Re:Redhat caught sleeping, still... by tweedle99 · · Score: 1

    1. It is good to keep the open-source open and make Linux top operating system with the help of companies like Eazel, Helixcode and Aduva. Competition is good for Linux and for Users. 2. Aduva does NOT keep any information regarding peoples downloading.