online build bot?

[Mahir Sayar]

i remember that there was something online a few years back

that would build a package from source and send an email link back to the user

id very much like to run nano (dont ask why) on my dev/chomeos system

is there anyway i could upload the nano source code and get it built for chromeos? 

[Steve Pirk]

An enthusiastic developer has prebuilt binaries for many add programs, including nano. He has tar balls for both x86_64 and i686 versions of Chrome OS. The files are on a public Google Drive share. I will post the link once I get back to my Cr-48. I don't seem to be able to grok how to copy the folder link on the tablet :-)

--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[Mahir Sayar]

i am eagerly waiting your reply :D:D

[Mike Frysinger]

i don't think Google ever hosted such a service. we have a remote
trybot system, but it's for @chromium.org developers only currently.

btw, using nano isn't a dirty secret ;). some of us prefer it over vim/emacs.

what device did you want to use it on ? x86/amd64/arm ?
-mike

[Mahir Sayar]

hehe @nano comment.

for arm...

and i think it was sourceforge or someone like that, i know it wasnt google..

so you google devs have special perks we dont get...

no fair

[Mike Frysinger]

On Tue, Jan 1, 2013 at 7:57 PM, Mahir Sayar wrote:
> for arm...

happy b-day:
http://wh0rd.org/nano-2.2.5.tbz2

> so you google devs have special perks we dont get...

well, i think we already knew that ;)
-mike

[Mahir Sayar]

mike - thanks !! really.. though i feel stupid to ask - i did

 

sudo tar -xvjpf nano-2.2.5.tbz2  -C /

and got alot of perm errors,

how do i put this onto the system to use?!

[Mike Frysinger]

CrOS has rootfs verification enabled by default which means you can't
mount it read-write let alone modify it.

if you were to disable that, your system would be less secure, but you
could then modify /. although it'd get ugly when the system tried to
update.

all other mount points are mounted noexec, so you can't unpack a file
and execute it :).

you could mount a tmpfs somewhere (like ~/mnt/) and extract & execute
the file from there.
-mike

[Steve Pirk]

Mahir,

The best way to get you the link is to share a link to the Chromebook Central post Taylor did when he announced his project.

https://groups.google.com/d/topic/chromebook-central/UGD2ISPogAY/discussion

There are about 100 posts, but it is worth checking out some of the questions and package requests. I do not believe any of these will work on ARM though.

-- steve

[Alec Warner]

Can't you just use the loader to execute it, or did that get fixed?

-A

On Tue, Jan 1, 2013 at 5:38 PM, Mike Frysinger <vap...@chromium.org> wrote:

[Mike Frysinger]

that probably would work, but i'm not sure that's less complicated for
most people :)

i don't think the mainline kernel has added support like grsec to
disable creating of executable mappings from mount points that were
mounted with noexec
-mike

[Mahir Sayar]

i feel lost...

what loader?

still cant figure out how to do it - 

:| i have it - but i cant use it..

[Mike Frysinger]

he's talking about using the runtime loader (aka the ldso aka the
dynamic linker)
http://en.wikipedia.org/wiki/Dynamic_linker

so if you unpack the nano.tbz2 into your ~/ and then run:
/lib/ld-linux-armhf.so.3 ./bin/nano
-mike

[Mahir Sayar]

bin/nano: error while loading shared libraries: bin/nano: failed to map segment from shared object: Operation not permitted

i got this error

[Mike Frysinger]

i guess we have support in our kernel to deny executable maps to mount
points mounted noexec

so your only choice is what i said before -- mount a tmpfs somewhere,
unpack it there, and then run it from there

you could automate it by writing a small shell script like:
$ cat ~/nano.sh
cd ~/
[ -e mnt ] || mkdir mnt
[ "$(stat -f -c %T mnt)" != "tmpfs" ] || mount -t tmpfs tmpfs mnt
[ -e mnt/bin/nano ] || tar xf nano-2.2.5.tbz2 -C mnt
exec mnt/bin/nano "$@"

then run it like so:
$ sh ~/nano.sh <somefile>

note: i haven't actually tested the above. just typed it by hand, so
it might have bugs. g'luck.
-mike

[Richard Barnette]

On Jan 3, 2013, at 1:39 PM, Mike Frysinger <vap...@chromium.org> wrote:

> i guess we have support in our kernel to deny executable maps to mount
> points mounted noexec
>

Yeah, all file systems except root are mounted w/ -o noexec, and the
kernel is expected to enforce that. However, for a unit in dev mode,
we also create a mount point for /usr/local, and mount it with -o exec.

In practical terms, this means if you put your executable stuff in
/usr/local, then you shouldn't need to do anything special.

-- jrb

[Mike Frysinger]

On Thu, Jan 10, 2013 at 4:54 PM, Richard Barnette
<jrbar...@chromium.org> wrote:
> On Jan 3, 2013, at 1:39 PM, Mike Frysinger <vap...@chromium.org> wrote:
>> i guess we have support in our kernel to deny executable maps to mount
>> points mounted noexec
>
> Yeah, all file systems except root are mounted w/ -o noexec, and the
> kernel is expected to enforce that.

well, there's a difference between not being able to do `./foo` and
not being able to do mmap("foo", PROT_EXEC). classically, the noexec
flag only mattered to the former. not sure when the latter became
mainstream (or if it is something we're carrying ourselves).

> However, for a unit in dev mode,
> we also create a mount point for /usr/local, and mount it with -o exec.

ah, good stuff. that should work.

> In practical terms, this means if you put your executable stuff in
> /usr/local, then you shouldn't need to do anything special.

yeah, and you can even put it into /usr/local/bin so `nano` "just works"
-mike

[Mahir Sayar]

fantastic!!! this works.. superrrrrr.. 

mark - ... what else do you have compiled in that wonderful treasure chest of yours#/ :D :D