> On May 7, 2020, at 11:34 AM, Martin Husemann wrote:
>
> It should do everything correctly, nothing special needed for 9.0 or newer.
Confirmed.
I was also able to roll my own with LVM.
Having a writable /dev on arm64 really helps :D
Riccardo Mottola writes:
> I would check if the .so.x file has a corresponding symlink, if it has,
> it is latest version, else it is old.
That's not true. There is a symlink e.g. from .so.1 to .so.1.1.
Maybe you mean "the libfoo.so symlink does not point to it".
In general deleting these has
On Thu, May 07, 2020 at 10:58:03AM -0400, Eric S. Hvozda wrote:
> Do you still need to handcraft the partitioning as suggested in
> https://wiki.netbsd.org/users/spz/moderndisk/ or does sysinst do the
> correct things as of v9.0?
It should do everything correctly, nothing special needed for 9.0 or
On Thu, May 07, 2020 at 06:04:25PM +0200, Riccardo Mottola wrote:
> this is quit clear and makes sense to me. I wondered if there existed a
> ready script for 2) to share...
>
> I would check if the .so.x file has a corresponding symlink, if it has,
> it is latest version, else it is old.
That is
>> On May 7, 2020, at 4:26 AM, Martin Husemann wrote:
>>
>> On Wed, May 06, 2020 at 05:55:08PM -0400, Eric S. Hvozda wrote:
>> It is know what installing boot blocks on the devices to supporting a
>> raid set with GPT is useless (i.e. does not work due to lack of
>> support)
>
> Missing conte
In article <20200506223952.hyjgwirjwfddd...@pumpkin.pr0.tips>,
Timo Buhrmester wrote:
>> What happens to the "old libraries" ? I think they are left in so
>> binaries continue to run.
>> Just the new ones are symlinked to current.
>
>Some get removed with postinstall obsolete, some don't. I've n
Hi Martin,
Martin Husemann wrote:
> There are multiple cases and they are treated differently:
>
> 1) there were neither major nor minor version changes between the releases
> -> the library is overwritten with the new version during the update
> 2) the major version was bumped
> ->
Martin Husemann wrote:
> 2) the major version was bumped
> -> new version is installed, old version stays around as 3rd party
>software in your installation could still refer to it.
>There are scripts for finding all references and actually
>obsolete
Martin Husemann writes:
> On Thu, May 07, 2020 at 12:39:53AM +0200, Timo Buhrmester wrote:
>> > What happens to the "old libraries" ? I think they are left in so
>> > binaries continue to run.
>> > Just the new ones are symlinked to current.
>>
>> Some get removed with postinstall obsolete, some
I am trying to re-implement a large PERL prog I wrote about 10yrs ago.
It has custom vars that you can set in a *rc file.
IS THERE a way to track these vars down, and set them in the config file?
On Thu, May 07, 2020 at 12:39:53AM +0200, Timo Buhrmester wrote:
> > What happens to the "old libraries" ? I think they are left in so
> > binaries continue to run.
> > Just the new ones are symlinked to current.
>
> Some get removed with postinstall obsolete, some don't.
There are multiple cases
On Wed, May 06, 2020 at 05:55:08PM -0400, Eric S. Hvozda wrote:
> It is know what installing boot blocks on the devices to supporting a
> raid set with GPT is useless (i.e. does not work due to lack of
> support)
Missing context here. What machine are you trying to boot and what NetBSD
version?
O
Hi All,
Did anybody try on NetBSD 9.0 and amd64 SkypeForLinux ? Does it run with
linux compatibility with access to audio & video?
just wondering, since it is quite usable on a semi-decent laptop running
Devuan, but I know therewere pulseaudio problems etc etc in the past.
Riccardo
13 matches
Mail list logo
