On Sun, 21 Jun 2020 at 15:46, Adrian Bunk wrote:
>
> With "atomic where they have to be" I meant the normal fsync+rename
> that ensures that you can never end up with a half-written file
> after a power-cut.
>
What about half-installed packages? Does dpkg guarantee atomicity on that
level, and
On Sun, Jun 21, 2020 at 02:09:44PM +0200, Stefano Babic wrote:
> Hi Adrian,
Hi Stefano,
>...
> If it can work in many case, it won't in many other cases. Hash issues with
> packages ? System does not boot and a grub-rescue shell is started ? Not a
> very big problem (in many cases) on server /
The problem which I have is that this one below doesn't work (*):
KERNEL_MODULE_AUTOLOAD_velismate += "A"
KERNEL_MODULE_AUTOLOAD += "B"
The two kernel modules are autoloaded during linux startup only if I have
in bb recipe this one:
KERNEL_MODULE_AUTOLOAD += "A"
KERNEL_MODULE_AUTOLOAD += "B"
or
Hi Adrian,
On 21.06.20 09:11, Adrian Bunk wrote:
On Fri, Jun 19, 2020 at 03:35:33PM +0100, csimmonds wrote:
I would like to add that this is a design decision. Package updates, be
they based on rpm, deb, or ipk, are not atomic. Which means that if you
power off during an update the system will
On Fri, Jun 19, 2020 at 03:35:33PM +0100, csimmonds wrote:
> I would like to add that this is a design decision. Package updates, be
> they based on rpm, deb, or ipk, are not atomic. Which means that if you
> power off during an update the system will usually not boot afterwards.
This is not
