Archlinux Vs Ubuntu Core?


Answer :

There are many differences between Ubuntu and Arch Linux.

With Ubuntu core, you get a ready-made distribution (based on Debian) aimed towards embedded devices.

Arch Linux on the other hand "is what you make it". After installing Arch Linux you are left with a minimal GNU/Linux system (not based on any other distribution). It is then up to you to configure the system as you want it.

To summarize; Ubuntu core is indeed tailored towards embedded systems, whereas with Arch Linux you will have to do the tailoring yourself.

Arch Linux link: https://wiki.archlinux.org/index.php/Arch_Linux
Ubuntu Core link: http://www.ubuntu.com/internet-of-things


Since this is an embedded project. I suggest you use either buildroot or yocto. Having used both, I further suggest you use buildroot. Its easier to get started with. However, if you have the time to come up to speed, pick yocto. Either is fine and although I am big fan or Arch and Debian, either of these two build systems are really the way to go.


I would say that both could be a good fit. But if you are going to do embedded development the answer might be tied to the platform you choose.

Example on a Raspberry Pi 2 you could use both. But Archlinux would be lighter weight in terms of disk space used, that's the disadvantage of snap packets on Ubuntu core.

Then you should try to see which software you would need and how they are readily available on both platforms. Finally given the power of many embedded systems, you could consider how viable it is to develop and possibly test from your desktop/laptop and then deploy on the target platform. How easy it is to do cross compilation from your main OS, etc. Snap packages might be "fattier" but are easier to deploy: they contain everything they require.

In the end there is no wrong choice. You need to assess your needs and then look at the best fit.


Comments

Post a Comment

Popular posts from this blog

Chemistry - Bond Angles In NH3 And NCl3

Answer : Solution 1: As Tan Yong Boon stated, it is Bent’s Rule with which we can explain the lower bond angle of \ce N F 3 \ce{NF3} \ce NF 3 when compared to \ce N H 3 \ce{NH3} \ce N H 3 . The rule as stated by Henry Bent: Atomic s character concentrates in orbitals directed towards electropositive substituents. Fluorine is more electronegative that hydrogen, and the \ce N − F \ce{N−F} \ce N − F bond would have greater p character than the \ce N − H \ce{N−H} \ce N − H bond. And more s character leads to large bond angles. Thus, the bond angle is greater in \ce N H 3 \ce{NH3} \ce N H 3 than in \ce N F 3 \ce{NF3} \ce NF 3 . Now, consider \ce N C l 3 \ce{NCl3} \ce NCl 3 . Clearly, \ce C l \ce{Cl} \ce Cl atom islarger in size than the central atom, nitrogen. Hence the higher bond angle here is due to the steric crowding caused by \ce C l \ce{Cl} \ce Cl atoms.(More pronounced than the electrongativity of \ce C l \ce{Cl} \ce Cl atom). They repel eachother and hence b
Read more

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more