Jump to content

adamw

Members
  • Posts

    2327
  • Joined

  • Last visited

Posts posted by adamw

  1. tyme: the Errata is almost entirely written by...me. :P

     

    It's kind of a mixture, to be honest. I was fairly slack with doing the 2008 and 2008 Spring Errata; they could have a few more entries each if I really worked on it. But this was mostly because they were both pretty stable releases that I got lazy about the Errata.

     

    2009 I'm being more active on the Errata, but this is partly because it isn't quite such a high-quality release.

     

    The KDE 4 bit could also be billed as 'Things Adam Noticed Within 2 Minutes Of Starting KDE 4 In The Release ISO'. Wish I'd bothered to test it in Beta 2 or something. Serves me right for being a GNOME user.

  2. It won't upgrade KDE 3, though. The KDE 3 packages are not on the disc. It will keep the 2008 Spring KDE 3 packages, which probably will not work too well in a 2009 environment.

     

    You can add the content of the disc as a repository, yes, and then *also* add online repositories; then do the urpmi upgrade as advised on the Release Notes. It will use the DVD for all the packages it can, and then grab the rest from the internet repositories.

     

    I don't honestly quite remember the syntax for adding a disc as a repo, but it's quite simple and I think is in the manpage. If you can't figure it out, post back and I'll look it up.

  3. I've been looking into this a bit; it is indeed to do with fortification. If built with -Wp,-D_FORTIFY_SOURCE=0 it works, but with 1 or 2 it fails. I'm reluctant to upload it 'fixed' this way, however, because it indicates a fairly major bug in the code which should really be fixed first. I have contacted the upstream developer to try and get him to fix it.

  4. I'm the kompozer maintainer. I know about the crash, but unfortunately I haven't a clue what the hell the problem is or how to fix it, as I'm not a hacker. Patch is welcome...

     

    The odd thing is is started happening after I just did a straight rebuild of the package for 2009.0. It's the exact same code and build as used on 2008.1, but somehow, rebuilding in the 2009 environment made it break. Odd.

     

    If you grab the 2008.1 package from a 2008.1 repo (this kind of thing is of course usually expressly discouraged), it will likely work.

  5. Just to confirm, I would definitely not suggest using KDE 4 in 256MB of RAM. It uses 250MB just sitting at a desktop. GNOME, Xfce and LXDE are all good alternatives (task-gnome , task-xfce , task-lxde).

     

    pinging the router doesn't always work, depending on how it's set up. What happens when you try to ping a remote site?

     

    also, try switching back to DHCP, but use 'dhcpcd' instead of 'dhclient' (you can set this in ifcfg-wlan0 , or in drakconnect).

  6. You don't need kernel-source unless you actually want to build a kernel. For anything else, such as building a driver that needs to build against the kernel, kernel-devel is what you need.

     

    The -latest packages do exactly what they say in their descriptions. The kernel packages themselves are not, technically, upgrades of each other. If you don't have kernel-desktop-latest , a new kernel-desktop package won't be automatically installed when it becomes available, because it's a 'new package', not an upgrade to the latest kernel-desktop package. The -latest package is simply a metapackage that makes kernel packages 'upgrade' automatically, like every other package in the distro. I can go into more details if you want. :)

     

    kernel-source matches all kernel flavors. This is because it's the full source tree used to generate each of the different flavors. So there isn't a kernel-source-desktop , kernel-source-server , kernel-source-desktop586 ... there's just kernel-source.

×
×
  • Create New...