ubuntu-phone team mailing list archive

[François Leblanc <fleblanc50@xxxxxxxxx>]

Thank you, it become a little more clear for me,  I'm in the situation of a
porter since I've a quite old nexus model (Nexus S) unsupported for now...


But I'm wondering, when I have a look on touch script this seems use
SWP.img ubuntu have file SWP.swap  so I get in trouble find that

my image wasn't adapt to use currently script kernel with system.img

So I've decided to use old flipped port (make an ubuntu directory). Since
userdata on crespo seem to small I make an ubuntu.img on

sdcard and modify touch script to my need.

Now I'm afraid that all I do don't work with system.img and I've two
choice, I can try to make it running on my nexus S but not sure

to successfully port it, or I can wait and hope like is a Nexus to have an
official port on it moreover nexus S userdata is only up to 900 Mo

(less than 1GB) this maybe it will never be officially ported....

don't know what is the best bet ...



Where does come from the gap betwen official system.img and cd image ?


Regards



2013/11/4 Dmitrijs Ledkovs <xnox@xxxxxxxxxx>

> On 4 November 2013 13:40, François Leblanc <fleblanc50@xxxxxxxxx> wrote:
> > I apalogize I don't understand very well,
> > ,
> >
> > by system-image do you mean the use of system.img ? If so where can we
> found
> > this?
> >
>
> From phablet-flash -h:
>     cdimage-touch
>                   Provisions the device with a CDimage build of Ubuntu
> Touch.
>     cdimage-legacy
>                   Provisions the device with legacy unflipped images.
>     ubuntu-system
>                   Provisions the device with an Ubuntu Image Based Upgrade
>                   image.
>     community     Provisions the device with a community supported build.
>
>
> At the moment - "ubuntu-system" are read-only, upgradable with binary
> deltas. It's default image type for official nexus targets, which is
> generated on canonical infrastructure and signed by trusted keys which
> are verified on each upgrade. At the moment it's not possible to
> replicate, nor host community ports on that infrastructure. A
> stand-alone flipped image (cdimage-touch) is produced more-or-less as
> a by-product whilst generating "ubuntu-system". Depending on how
> well-behaved CyanogenMod porting is, creating a new community port
> will always be preferably based on "cdimage-touch", unless not
> possible or buggy in which case it would be based on "cdimage-legacy".
>
> Once everything is ported and works, and the device is official indeed
> "end-users" only need ubuntu-system to flash their device for the
> first time, later they can upgrade using OTA updates UI.
>
> For bootstrapping a new device, e.g. Nexus 5, Nexus 7 2013, any
> community ports. One will need to start off with cdimage-legay
> (optionally) and/or cdimage-touch.
>
> Thus removing support / fallbacks to cdimage-touch / cdimage-legacy
> will effectively prevent us from starting new ports for new devices.
> Unused by default, but very much needed for:
>  1) day-to-day for unofficial ports
>  2) for starting new official or unofficial port =))))
>
> I hope above reasoning clears things up.
>
> If you are using phablet-flash with nexus device as a "user" rather
> than "porter to new devices", flash it once and use over the air
> updates and/or system-image-update CLI to wipe device clean.
> phablet-flash is only needed on nexus device for the initial first
> provisioning of unlcoked device that only has android installed on it.
>
> Regards,
>
> Dmitrijs.
>
>
> > Last time I have a look on trusty-preinstalled-touch-armhf.zip scripts
> unzip
> > under directory ubuntu,
> >
> > and not in a system.img file...
> >
> > If so how, to inject needed files for device porting (70-device.rules,
> > device.conf etc etc..)?
> >
> > If system.img design is completly different does it make a sence to port
> on
> > old design? Perhaps we have
> >
> > porting problems that not appear in this new design, or perhaps we will
> make
> > functionnal a device that
> >
> > become not in system-image...
> >
> >
> > Perhaps I'm completly wrong.. Sorry.
> >
> >
> > So my main trouble is if system-image is the way where can I find it to
> > adapt to my device?
> >
> > Regards.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 2013/11/4 Oliver Grawert <ogra@xxxxxxxxxx>
> >>
> >> hi,
> >> Am Montag, den 04.11.2013, 09:57 -0200 schrieb Roberto Colistete Jr.:
> >> > Em 02-11-2013 18:09, Chris Wayne escreveu:
> >>
> >> >
> >> >     So I ask the Ubuntu Touch community : aren't cdimage-touch images
> >> > not maintained anymore ? 2 months after the cited email ? Please
> >> > clarify.
> >> they are an interim product on the way to system-images, we only test
> >> the final product but keep that interim image around for image
> >> developers (porters).
> >>
> >> due to the completely different image design the cdimage image might
> >> have bugs that do not show up on system-image images so it is hard to
> >> fully support them ...
> >>
> >> if you do a port it is still the best image to use though and we will
> >> keep it around until we have a proper way for porters to create self
> >> signed system images and provide a system-image server for their builds.
> >>
> >> ciao
> >>         oli
> >>
> >> --
> >> Mailing list: https://launchpad.net/~ubuntu-phone
> >> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~ubuntu-phone
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> >
> > --
> > Mailing list: https://launchpad.net/~ubuntu-phone
> > Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~ubuntu-phone
> > More help   : https://help.launchpad.net/ListHelp
> >
>