# Migrating from mender-converted Debian to Yocto

**URL:** https://hub.mender.io/t/migrating-from-mender-converted-debian-to-yocto/506
**Category:** General Discussions
**Tags:** debian
**Created:** [April 28, 2019, 2:10am UTC](https://hub.mender.io/t/migrating-from-mender-converted-debian-to-yocto/506 "2019-04-28T02:10:53Z")
**Posts on this page:** 1
**Page:** 2

<div class="post-metadata">

### Author: ![HerrMuellerluedensch](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/herrmuellerluedensch/32/513_2.png) [@HerrMuellerluedensch](https://hub.mender.io/u/HerrMuellerluedensch)
#### Post date: [August 20, 2020, 3:22pm UTC](https://hub.mender.io/t/migrating-from-mender-converted-debian-to-yocto/506/24 "2020-08-20T15:22:51Z")

</div>

Hello everyone,  
I just wanted to check-in and provide a little update on this thread. I remotely deployed several releases built genuinely with yocto to devices (raspberry pi zero) which were provisioned with `mender-convert`ed images. I had to apply a few hacks, such as manually providing `/etc/fw_env.config` on each release which `u-boot-fw-util` usually soft-links into persistent storage.  
The devices are mostly running stable (except for some where I prematurely deployed updates with a memory leak 🤦‍♂️). I’m clearly _NOT_ recommending here to anyone to follow that which is also discouraged by the mender team. I just wanted to share my experience in case others are in a similar position where deployed devices are too far away to be re-provisioned and where loss of devices is actually not super critical. So be aware! I actually learned quite a bit about things that can go wrong with this approach so, for me it was worth taking that road just for the learning experience 😉 Plus having more device still an the network for testing on “semi-proper” yocto images.

[Previous page](https://hub.mender.io/t/migrating-from-mender-converted-debian-to-yocto/506.md?page=1)