Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make debian broken on master and dunfell #134

Closed
humanoid2050 opened this issue Sep 5, 2021 · 4 comments
Closed

make debian broken on master and dunfell #134

humanoid2050 opened this issue Sep 5, 2021 · 4 comments

Comments

@humanoid2050
Copy link
Contributor

The build scripts do not actually copy the updated image to the toFlash directory.

@htot
Copy link
Member

htot commented Sep 6, 2021

True. Because I didn't want to pollute the toFlash directory while generating the btrfs subvolume. But probably as long as we support also ext4 it makes sense to behave as the original.

BTW: Have you tried the btrfs image? It allows you to dual boot Yocto/Debian.

@htot
Copy link
Member

htot commented Sep 7, 2021

@htot htot closed this as completed Sep 7, 2021
@humanoid2050
Copy link
Contributor Author

I see that you enabled the cp in your branch. I did the same in mine.

I did try the brtfs image.I didn't know that it was easy to dualboot yocto and debian though. That's a neat capability.

Even though I like some of the btrfs capabilities, they don't really buy me much. I prefer having a bit more control over where my data physically ends up. I also know ext4 and it's comfortable. I also don't really need OTA updates for my use case.

If anything, I'd actually like to set up my Edison to be completely based on the SD card, and just flash images to a card the way I do with the other 15 or so embedded computers in my collection.

Has any thought been given to being able to support btrfs/ext4, emmc/uSD, separate boot/home, yocto/debian and various combinations of those options in a robust way? I know it represents a lot of work, but I think it might be something that could be implemented once and then used for a long time if done right. I wonder if cmake could be leveraged (with its build options and custom commands) to generate the make file dynamically, then generate an appropriately configured set of images and flash scripts.

@htot
Copy link
Member

htot commented Sep 8, 2021

If anything, I'd actually like to set up my Edison to be completely based on the SD card, and just flash images to a card the way I do with the other 15 or so embedded computers in my collection.

You can already do that now, as U-Boot can read the SD card to load the kernel.

Has any thought been given to being able to support btrfs/ext4, emmc/uSD, separate boot/home, yocto/debian and various combinations of those options in a robust way?

Yes, this is already the case. But maybe not all combinations have been tested rigidly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants