Add warning when using the script

[dragetd]

This script spews bootloader, kernel and kernel-module files over the system into directories that should be managed by apt, without a chance to cleanly remove those again. There is a kernel package 'raspberrypi-bootloader' which comes with the bootloader-files and the foundation kernel.

Alternatively one can use 'raspberrypi-bootloader-nokernel' to only get the required Broadcom-files and use a different kernel. Like a manually compiled one or the one packaged by raspbian 'linux-image-rpi-*'

This results in a more clean setup that does not conflict with the apt packages and prevents inexperienced users from accidentally installing files they do not want to install without a chance to cleanly remove them.

I think it would be good to have such a warning when using this tool.

[dragetd]

Also see https://github.com/raspberrypi/documentation/commit/a5c386cb3691fd9cfea0f99f303db023ff59dff1 (as mentioned by @diederikdehaas on IRC). Strangely this does not reflect https://www.raspberrypi.org/documentation/linux/kernel/updating.md

[dragetd]

I updated the RPi-documentation. It would be still nice to have the warning in rpi-update. Or a version that makes sure not to conflict with the package-manger and able to cleanly uninstall the files.

[Ruffio]

Is this going to be merged?

[Ruffio]

@popcornmix Is this going to be merged?

[dragetd]

The update to the docs has been merged a while ago. There is now even work on an open-source implementation of the boot-loader files.

I am not around too often in the IRC but when I am, I have seen people using rpi-update while they only wanted some drivers that would come with the regular kernel package. This is the type of confusion I was trying to avoid.

Again, as much as I appreciate the work he put into this utility which I am very thankful for, IMHO in its current from it is obsolete. If it was able to uninstall kernels and prevent collisions with the repository packages, it would be okay.

But the way it is right now, I'd rather prefer it to be archived and replaced by a README.md that simply links to the official RPi documentation.

[dragetd]

I do not believe that we will see an update here and that rpi-update will be maintained anymore. And since there is more harm done than it helps, I am considering suggesting to update the rpi-documentation to actively warn about rpi-update.

[Ruffio]

@popcornmix Is this going to be merged?

[popcornmix]

Yes, it just needs some time spent testing.

[dragetd]

Sorry, I did not expect to see any activity here. Please do not take my suggestions personal. From the outside, this project looked sort of abandoned. :-)

[Ruffio]

No/minor activity doesn't mean that it is no longer maintained. I for one is glad the way that rpi-update works so that updates to the kernel is easily updated on my RPis.

[dragetd]

Ture. But you need to know what you are doing. You need to be aware of cruft left in the system, you should uninstall the repository kernel to avoid conflicts and keep your kernel up to date to not miss security updates.

It is very useful for this situation, but the regular RPi users sort of expects it to play along with the system. Maybe 'master' contains in comparison to the released version some checks for installed kernel packages which I overlooked. :-)

[Ruffio]

I consider myself an inexperienced user and that is why I'm so glad for using rpiupdate, as I only have to execute one command in order to update the firmware. I wouldn't know how else to do it...

[Ruffio]

@popcornmix merge?

[dragetd]

Outdated and no interested in re-evaluating from my side. Close.