new
packages if they are masked by the ~x86 keyword.
Actually it does.
Updated packages can be a deep dependency, so try emerge --update --deep -a
world
- Whenever I install a new kernel I have to reinstall all those packages
which generate a kernel module, e.g. nvidia-drivers, openafs
On Wednesday 17 October 2007, Helmut Jarausch wrote:
- Whenever I install a new kernel I have to reinstall all those
packages which generate a kernel module, e.g. nvidia-drivers,
openafs-kernel or virtualbox-modules.
When emerge has installed the kernel module in
/lib/modules/new-kernel
.
- Whenever I install a new kernel I have to reinstall all those packages
which generate a kernel module, e.g. nvidia-drivers, openafs-kernel
or virtualbox-modules.
When emerge has installed the kernel module in
/lib/modules/new-kernel/...
it removes the corresponding module in
/lib
d from the system (e.g.
encrypted or deleted).
The benefit of this approach compared to kernel without modules is:
1) out of the tree kernel modules can be used (e.g. I use openafs)
2) kernel can be made smaller and faster by removing rarely needed
functionality into modules (e.g. support for vario
Howdy,
I ran across an old, (use to be) deprecated set of cluster instructions
for a Beowulf cluster. Nothing fancy but dirt simple to set up, with
NFS. But the really cool thing now is NFS can be replace with OrangeFS
(eix -R orangefs) or OpenAFS as both are now supported in portage
tilization) managing these clusters
or outsourced clusters (clouds in vendor speak). I Use the same cluster
setup, to test a myriad of different problem-solution sets on the
identical hardware, but only change the software, including file
systems: both DFS (cephfs/orangefs/openAFS/Beefs) and the loc
6 matches
Mail list logo
