Hot answers tagged

4

The apt-get upgrade command you have used will only upgrade packages that need no new packages as dependencies. You can use apt-get dist-upgrade to include new packages in the set of candidates. Be aware though that using dist-upgrade will also delete packages that have been obsoleted by other, possibly newer, packages.


3

The … situation :) … here is that pacman doesn't clean its package cache. This is by design. Quoting the Arch Wiki: pacman stores its downloaded packages in /var/cache/pacman/pkg/ and does not remove the old or uninstalled versions automatically, therefore it is necessary to deliberately clean up that folder periodically to prevent such folder to ...


3

After you have mounted them somewhere (/media/usb) do a chroot /media/usb /bin/bash to chroot into the USB system. Do whatever you need to do and exit afterwards. Replace /bin/bash if you prefer another shell or bash isn't available.


2

As jasonwryan notes this is not generally a wise approach, but simply pacman -S <pkg name> will install the latest version and anything that it depends on, though I'm not sure what your meaning: Without uninstalling it Are you attempting to keep multiple versions of the same package? if so, then no I do not think archlinux will support this ...


2

Maybe it will take more than 90 min to build the kernel . To speed up the compilation process we need to use -j option for example if you have 2 core you can type: fakeroot make-kpkg..... -j 2 or make -j 2 you can speed up the compilation process X2 ( 45 min) , (8 core less than 10min) Also you can use the CONCURRENCY_LEVEL variable for example if ...


2

It takes roughly a day for me to build 5 or so different architectures, as complete release builds (aka, tarballs and ISO images.) I'm building on a relatively low memory (512M), i386 virtual machine, using a script that also checks out the sources, and does a bunch of setup around build.sh. If you have more than one processor/core, you can speed things up ...


2

According to debian-administration some packages are being "kept back" beacause: There we can see four packages haven't been upgraded, even though newer packages are available. This is because two new packages were introduced, and these upgrades depend upon it. To fix this you must run : apt-get dist-upgrade


1

It is important to note immediately that it is not just the video that has been disrupted. The modules/drivers were not permitted to load because of version-matching restraints. I would like to provide the direct cause of the problem, although I do not know the ultimate cause of the problem. I did indeed have kernel + module mismatch that led to the error ...


1

cron typically runs things in a fairly minimal environment (man 5 crontab to see what exactly), which probably doesn't have enough in its path for this. If you want to see what is in the path, you can always run printenv > /tmp/cron_env from (presumably at a time in the near future) to see. Generally you can just define an updated PATH in your crontab ...


1

First, let me warn you that upgrading any OS in place has the potential to fail and then cause problems resulting from that failure. Having said that, Fedora 24 is still not yet released, so the latest official release of Fedora is Fedora 23. Instructions for that upgrade can be found at the Fedora Project Wiki. There are multiple methods for performing ...


1

I would suggest that any decent not-so-modern x86_64 true server should be able do a full build in a couple of hours or maybe less, including xsrc. My NetBSD-current build server is a Xen domU with 8GB RAM and 8 VCPUs running on a Dell PE2950 8-core (Xeon E5440 @2.83GHz) with 32GB RAM and with a decently fast set of SAS disks on the integrated PERC 6/i ...


1

The main point here is that pacman keep populating your /var/cache. Which means that if you don't do the cleaning yourself, it will indefinitely grow! Apart from that, you can imagine that some software will take more space, some may take less. If you do your housekeeping well, it shouldn't increase that much. With Arch, you are in charge and can really ...


1

To me it sound like your upgrade restarts a service of some kind which drops your connection. Alternatively you just loose connection, and the mid upgrade state screws with the system, resulting in the need for a reboot. Typically I would think that a network manager/interface has been upgraded, and "service networking restart" has happened. The issue here ...


1

SSH actually is pretty stable normally. Maybe you have a faulty setting in your SSHD config (can't tell that without seeing it), or your network has some problems. As a workaround, you could try using Mosh "instead" of SSH, it does a much better job at reconnecting, even if your IP changes or your network connection fails completely for some time. When ...


1

I recommend you to always use screen when you ssh in to your remote host. $ ssh -t username@hostname screen -D -RR If you would lose connection to your ssh session it's no problem because you can just run the same command again and you'll return back to your screen session with nothing terminated. The problem with you ssh session not being kept alive ...


1

Let us start a list: Debian/Ubuntu/...: apt-get update && apt-get upgrade -y Suse/OpenSuse/... zypper update Gentoo: emerge -u world Red Hat/Fedora: dnf upgrade Arch Linux/...: pacman -Syu CentOS: yum update This is a Community Wiki post, please add more!



Only top voted, non community-wiki answers of a minimum length are eligible