Ticket #128 (closed enhancement: fixed)

Opened 7 months ago

Last modified 4 months ago

Review BuildingtheMamonarootfs

Reported by: keesj Owned by:
Priority: normal Milestone: 0.2
Component: Documentation Version: 0.2
Keywords: Cc:

Description (last modified by rsalveti) (diff)

I updated the MamonaSetup? to match the way I create the mamona rootfs It would be good to review it.

BuildingtheMamonarootfs

Change History

  Changed 7 months ago by rsalveti

Some comments:

You can also use sudo debootstrap --include=task-mamona,task-mamona-e to install the tasks you want.

  • Copying your repository inside the root-fs:

Didn't get the point of copying everything inside the root-fs, you could just export at your http server and use it inside your chroot environment, as it has a valid ethernet connection.

Thanks for working on the documentation :-)

follow-up: ↓ 3   Changed 7 months ago by keesj

Didn't get the point of copying everything inside the root-fs

For me it is what worked best because I did not need to setup network(it still does not work out ot the box for me) or copy the data over to my web-server. It is easier right?

in reply to: ↑ 2   Changed 7 months ago by rsalveti

Replying to keesj:

Didn't get the point of copying everything inside the root-fs

For me it is what worked best because I did not need to setup network(it still does not work out ot the box for me) or copy the data over to my web-server. It is easier right?

Sure :-)

Ok, we could just put the 2 options there :-)

follow-up: ↓ 6   Changed 5 months ago by vivijim

I've updated the meta packages part that was out of date.

I believe that "Mamona Development Setup" should stop on "bitbake meta-mamona", and everything below should be on "Setting up the deb Repository"(wiki:DeRepository?) and "Creating your own rootfs.jffs2 image"(wiki:CreateOwnRootfs?)

Another thing is that it should be clear that some of these manual steps are optionals because gen_repository.sh does already generate the rootfs and the image automatically.

  Changed 5 months ago by rsalveti

Yeah, I also think we should create another wiki page for the repository and for the rootfs, because we can then link it at some other place, SDK for example.

For the gen_repository I think we could give both solutions, as sometimes it's easier just to use debootstrap and mkfs by hand.

in reply to: ↑ 4 ; follow-up: ↓ 7   Changed 5 months ago by keesj

Replying to vivijim:

I've updated the meta packages part that was out of date. I believe that "Mamona Development Setup" should stop on "bitbake meta-mamona", and everything below should be on "Setting up the deb Repository"(wiki:DeRepository?) and "Creating your own rootfs.jffs2 image"(wiki:CreateOwnRootfs?)

I agree that the rootfs and deb repo content could better be placed somewhere else. I Do get confused with all the links and the lack of structure on the website and splitting up will not help

in reply to: ↑ 6   Changed 5 months ago by rsalveti

Replying to keesj:

I agree that the rootfs and deb repo content could better be placed somewhere else. I Do get confused with all the links and the lack of structure on the website and splitting up will not help

Yep, the website structure is not as we expected, it's very easy to get confused.

For 0.2 release we're planing something like a "doc day", where we're going to organize the wiki and create more documentation regarding Mamona's usage and about release 0.2.

We'll keep you posted so you can help if you want.

  Changed 5 months ago by rsalveti

  • description modified (diff)

I moved some stuff around the wiki, see how it's looking now.

Basically I focused on separating the logical stuff at the "correct" places. Now everything related with creating the rootfs image and/or flashing you device will be inside Running Mamona (if you're going to flash it you're going to use mamona :-).

  Changed 4 months ago by rsalveti

  • status changed from new to closed
  • resolution set to fixed

Since we already made the review and it's now looking much better than before, closing this ticket.

Note: See TracTickets for help on using tickets.