Help

[miki3421]

Hi, I'm getting stucked once time I'm in root console. Every change that I'm doing is not permanent at the reboot. It's seems the authentication is not working. I tried also to change the root password but it's not working. Someone can help me? Thanks.

I'm using a Raspberry Pi4 connected via serial0

[bmork]

miki3421 notifications@github.com writes:

Every change that I'm doing is not permanent at the reboot.

Correct. There is no writeable file system, so you cannot permanently change any file.

The only way to make permanent changes are either 1) change an nvram variable, or 2) replace a file system with your own copy

The first option is easy and pretty safe. But obviously limited to the settings D-Link have chosen to implement. Still pretty usefull, as it must include anything you can configure with the app.

But many changes require at least modifying a script running at boot. Which is why I propose building a new file system for the "userdata" partition. You can build on top of the existing My DLink application, or you can do it like I did by replacing everything in that file system.

The D-Link firmware will call the "opt.local" script in the "userdata" partition at boot. So you can hook anything you want permanent in there, without making any other changes to the system if you dont want to.

[miki3421]

Thanks Bjork, I will try, sorry but I’m not a super Linux expert, I need some guidance.

On Sun, 10 May 2020 at 10:02, Bjørn Mork notifications@github.com wrote:

miki3421 notifications@github.com writes:

Every change that I'm doing is not permanent at the reboot.

Correct. There is no writeable file system, so you cannot permanently change any file.

The only way to make permanent changes are either 1) change an nvram variable, or 2) replace a file system with your own copy

The first option is easy and pretty safe. But obviously limited to the settings D-Link have chosen to implement. Still pretty usefull, as it must include anything you can configure with the app.

But many changes require at least modifying a script running at boot. Which is why I propose building a new file system for the "userdata" partition. You can build on top of the existing My DLink application, or you can do it like I did by replacing everything in that file system.

The D-Link firmware will call the "opt.local" script in the "userdata" partition at boot. So you can hook anything you want permanent in there, without making any other changes to the system if you dont want to.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bmork/defogger/issues/17#issuecomment-626289541, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKFA25QDLNPWRCWTW575OMTRQZNRJANCNFSM4M5EERTA .

[miki3421]

miki3421 notifications@github.com writes: Every change that I'm doing is not permanent at the reboot. Correct. There is no writeable file system, so you cannot permanently change any file. The only way to make permanent changes are either 1) change an nvram variable, or 2) replace a file system with your own copy The first option is easy and pretty safe. But obviously limited to the settings D-Link have chosen to implement. Still pretty usefull, as it must include anything you can configure with the app. But many changes require at least modifying a script running at boot. Which is why I propose building a new file system for the "userdata" partition. You can build on top of the existing My DLink application, or you can do it like I did by replacing everything in that file system. The D-Link firmware will call the "opt.local" script in the "userdata" partition at boot. So you can hook anything you want permanent in there, without making any other changes to the system if you dont want to.

Sorry but I don't have any idea how to do it what are you writing. If you are so kind to contact me in private. I tried to read multiple times your instruction but I think I have same lack of knowledge.

My email is miki3421@gmail.com Thanks

[rahools]

sorry for posting off-topic here, @miki3421 how did you connect and use serial console with help of rpi4? any guide you know of? sorry, total noob here.