>"apt-get upgrade” doesn’t upgrade the linux-headers to the latest
>fixed version
You need “apt-get upgrade --with-new-pkgs” at the very least to keep
a stable system up-to-date. I use “apt-get --purge dist-upgrade” myself
while keeping an eye on what packages apt wants to remove with that.
On Sat, 9 Jan 2021, Andrei POPESCU wrote:
> In practice several important packages are updated quite regularly:
[…]
Note that packages being updated is not always a good thing.
Having the stability of a tested set to rely on is also
appreciated. It’s also more important to have the security
and
On Fri, 24 Oct 2014, Thomas Goirand wrote:
OpenBSD’s libc.so major number is 50 or something like that right now,
because they – correctly – increment it on every incompatible change.
The correct thing to do is to not do incompatible change.
No, in the interest of software hygiene it is
Gregory Smith dixit:
They say you're a hard nose, skeptical, untrusting, old unix admin and
programmer from the old days and you do not take one ounce of
My old days were on DOS¹. I am a relative newcomer to the Unix world,
starting about 1999. But I grew up with the “old values”, including
On Tue, 21 Oct 2014, Michael Ole Olsen wrote:
suddenly I couldnt just place a script in rc2.d folder anymore, needed to
symlink
needed to add an lsb header too it seems
Indeed.
It took me quite some effort to learn about LSB headers, exit codes,
SYSV init scripts, and all that, in order to
Konstantin Khomoutov dixit:
Sometimes we have to run software which is neither Open Source nor Free
on our systems which are (luckily) Open Source and Free.
Things like f-prot are shipped statically linked, when in their
binary form for OpenBSD. And binary compatibility only goes so
far either
On Mon, 13 Oct 2014, Miles Fidelman wrote:
Those who are most impacted are sys admins of servers, and upstream developers
I’m both, and I joined Debian to try to make an impact…
- the two communities most impacted, but that seem to have no say in the
matter.
… but even then, am drowned by
Hi,
just got this vomited onto the console and into dmesg:
[ 998.354300] perf interrupt took too long (2516 2500), lowering
kernel.perf_event_max_sample_rate to 5
What sort of problem is this, and why is it so important that it
occurs basically on every boot, and what can I do to “fix”
Roger Leigh dixit:
However, if you have any lingering scripts without any LSB headers,
you'll need to fix them up or remove them to allow dynamic boot
ordering to be enabled. This is obviously not too desirable, since
sudo apt-get --purge install file-rc insserv-
bye
//mirabilos
--
9 matches
Mail list logo
