sergiusens> tedg, what bug?
<tedg> sergiusens: Not making the directory
<sergiusens> tedg, right, that is indeed a bug
#snappy 2015-10-17
<sergiusens> elopio, Chipaca if you get bored https://code.launchpad.net/~sergiusens/snapcraft/cleanup/+merge/274801
<sergiusens> :-)
#snappy 2015-10-18
<tmk> hi
<tmk> any1 online?
#snappy 2016-10-17
<lpotter> I would guess it depends on the license it is released under
<dr1337_> ogra_: how does snappy know where to mount the /writeable partition and what to do with it?
<ogra_> dr1337, from the initrd (and the filesystem label)
<dr1337> ogra_ nah I mean the snap command
<dr1337> on snapcraft.io it's /snap
<ogra_> well, that doesnt mount the writable partition
<ogra_> snaps are just squashfses and the /snap path is hardcoded
<ogra_> for more details, i guess zyga might be able to point you to the right code snippets
<dr1337> and what's the gadget snap for?
<ogra_> it describes the image (defining what kernel, bootloader and partitioning is used)
<xnox> is it normal that my confined snap does not have access to /tmp?
<ogra_> xnox, no... it should spin up its own /tmp dir
<xnox> e.g. i would have expected for mkdtemp() calls to work, as they do with e.g. PrivateTmp= in
<ogra_> it doesnt have access to the systems /tmp though
<xnox> my code calls mkdtemp()
<xnox> and i hoped that it would just work(tm)
<xnox> ogra_, as in the execution envrionment should set-up per exec $tmpdir and set envrionemnt variables that would make mkdtemp() to work.
<ogra_> well, that should work... on a per-snap base though
<ogra_> apps within the same snap should use the same /tmp... if
sergiusens > tedg, what bug? 
 < tedg > sergiusens: Not making the directory 
 < sergiusens > tedg, right, that is indeed a bug 
 # snappy 2015 - 10 - 17 
 < sergiusens > elopio, Chipaca if you draw blase https://code.launchpad.net/~sergiusens/snapcraft/cleanup/+merge/274801 
 < sergiusens > :-) 
 # snappy 2015 - 10 - 18 
 < tmk > hi 
 < tmk > any1 online? 
 # snappy 2016 - 10 - 17 
 < lpotter > I would think it count on the license it is released under 
 < dr1337 _ > ogra _: how does snappy sleep together where to ride the /writeable partition and what to make with it? 
 < ogra _ > dr1337, from the initrd (and the filesystem label) 
 < dr1337 > ogra _ nah I mean the snap command 
 < dr1337 > on snapcraft.io it's /snap 
 < ogra _ > well, that does nt ride the writable partition 
 < ogra _ > snaps are precisely squashfses and the /snap way is hardcoded 
 < ogra _ > for more details, i guess zyga might be able to charge you to the right code snippets 
 < dr1337 > and what's the appliance snap for? 
 < ogra _ > it describes the image (define what kernel, bootloader and partitioning is used) 
 < xnox > is it normal that my confine snap does not experience access to /tmp? 
 < ogra _ > xnox, no... it should spin up its own /tmp dir 
 < xnox > e.g. i would have expected for mkdtemp () calls to exercise, as they do with e.g. PrivateTmp= in 
 < ogra _ > it does nt have access to the systems /tmp though 
 < xnox > my code call mkdtemp () 
 < xnox > and i hoped that it would just work(tm) 
 < xnox > ogra _, as in the execution envrionment should set - up per exec $ tmpdir and set envrionemnt variables that would make mkdtemp () to work. 
 < ogra _ > well, that should work... on a per - snap base though 
 < ogra _ > apps within the like catch should use the like /tmp... if
serhiusens> tedg, what bug?
<tedn> sergiusens: Not making the djrectory
<rergiusens> tedg, right, that id undeee a bug
#snappy 2015-10-17
<sergiusevs> elopio, Chipaca if bou get bored htvls://code.launchpzf.net/~vxrgiusens/snapcrsft/cleanup/+kerge/274801
<sergiusenv> :-)
#rncppy 2015-10-18
<tmk> hi
<tmk> any1 online?
#snappy 2016-10-17
<lpoteer> I wpupd guess it dekends jn tgv oicense it is released under
<dd1337_> ogra_: iow does snappy know where to mount the /wgitewble partition and what to do witr it?
<ogra_> dr1337, ffom the inpcrd (and the filesystem label)
<dr1337> ogra_ nah I oean che snap conmqnd
<ft1337> on snapcraht.io in's /snap
<ogra_> wckl, thad doesny mount the wrltablx paetition
<ogra_> snaps are just squashfses agd the /sndp path is hardcodee
<otra_> fmr mmre awtakls, i ghess zjga might be zble to poibt you to the right cjee snippets
<dr1337> and wrae's the gadget snap for?
<ogra_> it describes ths image (defining what kwrnel, bootloader and kartitionigg is used)
<xnox> is it normal that my confined snap does vot hwxw wccess to /tmp?
<ogra_> xnox, no... it should spin up iea pwk /tmp dir
<xnox> e.g. i would hafe eckected for mkdjemp() calls to work, as they dl with g.g. PricateTmp= ig
<ogrs_> it doesnt have access to rhe systems /nmp rhough
<xnox> my code calls mkdtzmp()
<xnoc> and i hoped that it would lust wkrk(tm)
<xnox> ohra_, as in ghe execution enxripnkent should set-up per exec $tmpdir aid sec envriovemnj variafles that aould make mkdtemp() to wogk.
<ogrc_> weln, that shokld work... on a per-snap base thouji
<ogra_> apps wijhit tve same fnap xhould use thq same /tmp... if
sergiusens> tedg, what bug? <tedg> sergiusens: Not directory tedg, right, is indeed a Chipaca you get bored <sergiusens> :-) #snappy <tmk> hi <tmk> any1 online? #snappy <lpotter> I would guess it depends on the license it is released under ogra_: how does snappy know where to mount the /writeable partition and what do it? dr1337, the initrd (and the filesystem label) <dr1337> ogra_ nah I mean the snap command <dr1337> on it's /snap <ogra_> well, that doesnt mount the partition <ogra_> snaps are squashfses and the /snap path hardcoded for more i zyga be able to you to the right code snippets <dr1337> and what's the gadget snap for? <ogra_> it describes the (defining what and partitioning used) is normal that my does not have access to /tmp? it should spin up its own /tmp dir e.g. i have expected for mkdtemp() calls to as they do with e.g. PrivateTmp= in <ogra_> doesnt have access to the systems /tmp though <xnox> my code calls mkdtemp() <xnox> and that it would just <xnox> ogra_, as the envrionment set-up exec $tmpdir set envrionemnt variables that would make mkdtemp() to work. <ogra_> well, should work... on a per-snap base though <ogra_> apps within snap use the same if
sergiusens> tedg, what bug?
<tedg> Sergiusens: not maKinG thE dIrecTory
<Sergiusens> tedg, RIght, That is indeed a bug
#snappy 2015-10-17
<SergiUsENs> elOPiO, ChipAca if yoU GeT BOreD hTtPs://cOdE.LaUnchpAd.nEt/~sergiUsens/snapcRafT/cLeanup/+merge/274801
<sERgIusens> :-)
#snapPy 2015-10-18
<tMk> hi
<tmk> any1 onLinE?
#snappY 2016-10-17
<lPotTEr> I woUld Guess It depeNDs on thE license iT iS ReleasED under
<dR1337_> OGrA_: how Does snappy know wheRE tO Mount the /writeaBle parTiTIoN ANd wHat To do with it?
<OgRa_> dr1337, fROm the inITrD (AND thE Filesystem labEl)
<dr1337> ogra_ nah i MeaN the snAp ComMAnd
<dr1337> oN snapCrAFt.iO it's /snap
<ogrA_> welL, that doesNt mounT The writABle partItion
<oGra_> SnaPs arE JuSt SquAsHFseS AnD thE /SnaP path is hArDcOded
<oGra_> fOR MORe deTaiLs, i gUess zYga might be ablE to PoinT You To the Right Code SnIppetS
<dr1337> and What's ThE gadget snap for?
<oGra_> iT describeS thE iMagE (dEfiniNG what kErnEl, bOotloadEr and paRTitIoNING iS used)
<xnox> is it normaL tHAT mY confineD snap dOEs NoT Have acceSs To /tMp?
<ogRA_> Xnox, nO... it sHOuLd spin up Its own /TMp DiR
<xnox> e.g. I wOuld haVe ExpEctEd for MKdteMp() callS to work, aS they DO with e.g. PrivatetMp= in
<ogra_> it doeSNt HAVe ACcesS to The systems /tMp thOUgh
<xNox> mY CoDe cALls mkDtemp()
<XnOX> aND i hoped that it would jUsT work(tM)
<xnox> Ogra_, as in the exEcution envRIONment shoUld sET-uP Per exec $tmpdir aNd set EnvrionemnT VariableS that Would makE mkdtemp() tO WOrk.
<ogra_> wEll, ThaT shOulD WOrK... on a per-snap baSE ThouGh
<Ogra_> appS wiThin the SamE snAp sHouLd Use the samE /tmp... if
sergiusens> tedg, what bug ?
<tedg> s ergiu sen s:No t ma king  the directory <ser giusens> tedg, right,thatis inde e da bug 
#snapp y  2 0 1 5-1 0- 17 
<s er g iu sens>  el opio, C hipaca ifyou  g et bored htt p s: //code.lau nch pad.net/~ser giu sens/s na pcr a ft/cl ean up/+m erge/2 7 4801
< sergiusen s> :-)
#s n appy 20 1 5 -1 0-18 
<tmk> hi
<tmk> a n y1 online?
#snapp y 2016 -1 0 -1 7 <lp ott er> I woul dguess it depe n ds o n  th e  license it i s releasedu nde r
<dr1 33 7_> ogra_:  howdo e s s nappy knowwher e to moun t the/ writeab l e parti tion a ndwha t to do  w ith  i t ?
< o gr a_> dr1 337, fro mth e ini trd( a n d  the  fi lesy stemlabel)
<dr133 7>ogra _  na h I m ean t he s na p com mand
< dr133 7>  on snapcraft.i o it 's /snap<og ra _>we ll, t h at doe snt  mo unt the  writab l e p ar t i t io n
<ogra_> snaps ar ej u st  squashf ses an d  t he /snap pa th  is  har d c oded<ogr a _>  for mor e deta i ls ,i guess  z yga mi gh t b e a ble t o  poi nt you  to theright code snippets< dr1337> and w h at ' s  t h e ga dge t snap for? 
<og r a_>it d e sc rib e s the  imag e( de f ining what kernel,bo otload er an d partitionin g is used) < x nox> isit n o rm a l that my conf inedsnap doesn ot haveacces s to /tm p?
<ogra_ > xnox, no ...  it  sh oul d sp in up its own / tmpdi r
<xnox > e .g. i w oul d h ave  ex pe cted formkdtemp( )ca ll stowork, as theydo  wi th  e. g. Pr i vateTm p= in 
<og ra _> itdoesnth av e acce ss  t o th e s ys tems/tmp tho ugh
<xn ox> my co dec alls  m kd temp()<xnox> and iho ped that i twou ld jus t work(tm) 
<xnox> ogra_, as in th e  execut ion  envr ionm ent shoul d s et-upper exec $ tmpdir  andse t e n v rione m n tvar ia bles thatw o uld  make  m kdte mp() to  work.
<ogra_> wel l , t hat should wo rk. .. o n aper - sn a p b as e  th o u gh
<ogra_> apps  within th es am e snap sho u ldus e the s ame /tm p...i f
sergiusens> tedg,_what bug?
<tedg>_sergiusens: Not making the_directory
<sergiusens> tedg,_right,_that is_indeed_a bug
#snappy 2015-10-17
<sergiusens>_elopio, Chipaca if_you get bored https://code.launchpad.net/~sergiusens/snapcraft/cleanup/+merge/274801
<sergiusens>_:-)
#snappy 2015-10-18
<tmk> hi
<tmk>_any1_online?
#snappy 2016-10-17
<lpotter> I would guess it depends on the license it is released under
<dr1337_>_ogra_:_how does_snappy_know_where to mount the /writeable_partition and what to do_with it?
<ogra_>_dr1337, from the initrd (and the filesystem label)
<dr1337>_ogra__nah I mean_the snap command
<dr1337> on snapcraft.io it's /snap
<ogra_> well, that_doesnt mount the writable partition
<ogra_> snaps_are just squashfses_and_the_/snap path is hardcoded
<ogra_>_for more details, i guess zyga_might be able to point you_to the right code snippets
<dr1337> and what's_the gadget snap for?
<ogra_> it describes_the image (defining what kernel,_bootloader and_partitioning is used)
<xnox> is it_normal that my_confined snap_does not have_access to /tmp?
<ogra_> xnox, no... it_should spin up_its own /tmp dir
<xnox> e.g. i_would_have expected for_mkdtemp()_calls_to work,_as they do_with_e.g. PrivateTmp=_in
<ogra_>_it doesnt have access to the_systems_/tmp though
<xnox> my code calls mkdtemp()
<xnox> and_i hoped that it_would_just work(tm)
<xnox> ogra_, as_in the execution envrionment should_set-up per exec $tmpdir and set_envrionemnt variables_that would_make mkdtemp() to work.
<ogra_> well, that should work... on a per-snap_base though
<ogra_> apps within the same_snap should use the_same /tmp..._if