Closed LionNatsu closed 3 years ago
This is a tough question as we would need to know first, what is the component updated that resulted in this issue?
After which, a warning/notice shall be added.
I guess it was kernel? I will test this in the next update of kernel package.
@LionNatsu did you do autoremove after upgrade?
Well our Kernel update is not invasive as far as I'm concerned...
Oh wait are you talking about the sunxi line of releases?
2017年2月10日 10:48,"Icenowy Zheng" notifications@github.com写道:
@LionNatsu https://github.com/LionNatsu did you do autoremove after upgrade?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/AOSC-Dev/aosc-os-abbs/issues/580#issuecomment-278996290, or mute the thread https://github.com/notifications/unsubscribe-auth/AExjt4BEK48YmLIRNnHCe-RJPipcCchWks5rbJS5gaJpZM4L9Vqr .
@Icenowy Yes, I did. --autoremove
exactly.
@LionNatsu it's no wonder — as autoremove included, our kernel upgrade will act like Arch's, so please reboot
But still it shouldn't do with anything in /dev should it?
@MingcongBai tun/tap is a kernel module
But I wouldn't have though merely removing a kernel would result in any changes in /dev?
@MingcongBai seems that the device file is only a stub — it loads a module when using
Right... Let me just suppose that then. Let's wait till @LionNatsu gets his next kernel update and see if it happens. If so, I will close with wontfix
.
I think I need a notice for this Bizarre Natural Phenomenon.
@Icenowy You're right. It is a stub.
I think I need a notice for this Bizarre Natural Phenomenon.
As in notifying users that if they remove the old kernels whilst running that particular kernel (confusion), they are likely to run into issues such as... this?
See, we need an Errata page right about now...
@LionNatsu Input needed, if not, please close this issue...
Are there any ways to remove that stub?
@LionNatsu I think it doesn't need to be removed
@LionNatsu Shall we address it as a little kernel bug…?
@LionNatsu Shall we address it as a little kernel bug…?
@Icenowy Needing your verdict here.
Stale issue with no further information providence. Closing.
That is,
/dev/net/tun
does not exist.BTW, If there is no solution to restart this module immediately, would you add any warning or caution to somewhere for this?