gmane.linux.sabotage.general

golang

Daniel Cegiełka — 2013-04-16T20:00:23

Hi,
Is there a chance to add go-lang (Google) to sabotage?

Daniel

Re: gdb-7.5.1 (patch)

Daniel Cegiełka — 2013-04-16T19:58:02

2013/4/9 John Spencer <maillist-sabotage< at >barfooze.de>:


hi, it's only missing a header.
Daniel

Re: Sabotage gone native...

John Spencer — 2013-04-09T13:59:39

sorry for the late reply... we've talked about the issues you 
encountered on irc, i'm sending this for documentation purposes.

On 02/27/2013 06:09 PM, Hugh Lavery wrote:

glad to hear!

btw i've looked at what you suggested ( /proc/bus/input/devices )
but those ids seem to differ from what works.
if anyone knows a way to process this file correctly to get the proper 
mouse and kbd evdev ids please let me know.


yes, this is all fixed in git.
https://github.com/rofl0r/sabotage/issues/69


there seem to be some kernel bugs related to vfork on 32bit platforms 
that affect butch.
once the error happens, there's no way to get butch working again in the 
current session.
the only known solution is to reboot the host, and then resume the 
stage0 build using utils/resume-stage0.sh.
there's another bug in debian testing (they've made some headers only 
available in an arch-specific subdir) that prevents the stage0 gcc from 
building correctly. i have to look into that.
however, debian stable works.
known-good plat

Re: gdb-7.5.1 (patch)

John Spencer — 2013-04-09T13:44:29

does that patch work on all supported platforms ?

gdb-7.5.1 (patch)

Daniel Cegiełka — 2013-03-26T22:31:06

best regards,
Daniel

Sabotage gone native...

Hugh Lavery — 2013-02-27T17:09:41

Thank you for your work on the sabotage image files.  Wanted to let
you know that I have the latest version up on both an x86_64 box and
on an armv7 (Allwinner A10 Hackberry) device.  Sabotage works well,
even in X once the mouse and keyboard events are sorted out (bit of an
adventure, there).  There are some bugs to sort out on the arm device
(tmux dies on "assertion ctx failed in evmap_io_active", as does
transmission in gui; no such issues on x86_64).

What do you use to build the rofl0r/sabotage scripts?  I have tried to
build these on the latest x86_64 releases (+/- a week or two of today)
of Arch, Ubuntu (Q.Q) and Crux3.0 but only get (at best) as far as the
kernel-headers in Stage 0 before  the build dies.  Since I have your
image/rootfs to work with this is just a matter of interest....

Re: [musl] [ANN] sabotage 0.9.7 milestone (x86[_64]) release

Jens Staal — 2012-11-08T17:20:24

tisdagen den 6 november 2012 17.34.38 skrev  John Spencer:

I am happy to report that the x86_64 image boots nicely natively and that dwm 
seems to work well as well (I put "exec dwm" in ~/.xinitrc). Now I just need 
feh (or similar) and conky to make it fully functional :)

I could however not test it completely yet since I need to figure out which 
events under /dev/input that are responsive for keyboard and mouse on my 
native boot in order to really test it (keyboard completely unresponsive under 
X).

I have not been able to test dwm under Virtualbox (where mouse and keyboard 
work under LXDE) since I have not figured out how to get the network working 
(for the native install, I ran butch with the root file system mounted as a 
chroot).

Another odd thing I noticed is that using mksh as login shell makes me loose 
job control sometimes. Slightly odd. Could be a non-root permission issue with 
/dev/tty-stuff too.

Re: Bootstrapping

Ivan Kanakarakis — 2012-02-20T15:03:11

An update. Using rofl0r's fork I've made a couple of
changes to the scripts, and will be pushing to github.
many broken links for packages again.
Also as seen in the comments of utils/utils, busybox
wget is _really_ buggy.

rofl0r is using `butch`to build stages. butch is called
by `./build-stage 0` and should be called directly (as
`butch.bin install stage1`) from into the chroot, from
what I can tell.
I've also updated the COOKBOOK for this.

I couldn't build stage1 again. gcc4 fails with a nasty
error. I lost the log, dah, but it's basically this:

    error: Link tests are not allowed after GCC_NO_EXECUTABLES

here's some related references:
http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html
http://comments.gmane.org/gmane.comp.gcc.help/35381
http://comments.gmane.org/gmane.comp.gcc.help/36631

I'll look more into that later.

I'm also concerned about building stage0 as non-root, as
all the directories and files are owned by my user, and on
chroot, the owner:group is 1000 (uid of my user).
I think that caus

Re: Bootstrapping

Moritz Wilhelmy — 2012-02-19T19:57:05

This is in fact a recent musl issue, which was discussed in length in
this thread.
http://openwall.com/lists/musl/2012/02/16/1

HTH,

Moritz

Re: Bootstrapping

Ivan Kanakarakis — 2012-02-19T16:40:37

yeah, that's correct. I've noticed too that it hadn't been updated
but I thought I'd gve it a try ;)



definately, musl is great, and I'd love to see some projects around it too



I'll sure do, stage1 failed again, so I'll try rofl0r's repo and see
how that goes. I see he's put quite some work in there.
thanks ;)

Re: Bootstrapping

Ian Denhardt — 2012-02-19T15:52:22

...

I'm guessing you used Chris's repo? I'm not surprised it doesn't build;
hasn't been updated in 7 months and pulls musl from git, So parts are
still moving. I'd be stunned if it hadn't succumbed to bitrot.

I'd love to see the project revived; For one thing it booted incredibly
quickly, and with C++ support in musl on the horizon, it might not be
too long before something based around it might really be viable for my
use.

I haven't looked at it carefully, but there's a more recent fork at:

http://github.com/rofl0r/sabotage

You might look at that before you get started fixing things; might save
some time.

Bootstrapping

Ivan Kanakarakis — 2012-02-19T15:08:51

hi there,

I've seen this project some time now, and I got some free
time so I thought, I'd try it. I went with the bootstrap option.

both stage0 and stage1 failed. Some adjustments are
needed to get everything compiled.

for stage0:
binutils failed because a header had a mismatching definition.
string.h by musl had the following

    char *basename(char *);

while binutils-2.21.1/libiberty/strsignal.c wanted

    char *basename(const char *);


before I get to stage1, the cookbook said after the chroot
one should cd to /tmp/src/sabotage, while the correct path
was /src/sabotage.


for stage1:
busybox wget segfaulted
zlib and git links were broken
zlib just needs a the new version
I can't see git archives on kernel.org anymore

I downloaded those by hand and placed them on /src to
get things going


I am now building stage1 but I already had problems once
another header mismatch for gcc on the definition of psignal

libiberty/strsignal.c was

    psignal (int signo, char *message)

while that char needed to

errors while make'ing the kernel

uki — 2011-12-20T23:19:11

Hi,

I've installed x86_64/sabotage-2011-07-28, using lilo as my bootloader.
System works fine, except:
I've tried to `make $anything` the 3.0 kernel, which errs mostly,
because it does not seem to see limits.h, MAX_PATH define.
Here are the logs:
make all http://codepad.org/CaX12hyz
make menuconfig http://codepad.org/ObdP08qI

Should I be exporting some extra variables to make it work?
kernel mkfile did not have any patches. Any tips?

Cheers,
Łukasz Gruner

Re: perl & python in base set

Džen — 2011-05-03T12:05:52

Makes sense now that you mentioned the kernel. And yes, moving python to
"extra" or a similar set could be a good idea in future.

Too bad about perl, but I wonder whether there is a possibility to
compile the kernel without perl.

Regards

On 02/05/11 10:43am, Christian Neukirchen wrote:

Re: perl & python in base set

Christian Neukirchen — 2011-05-02T08:43:51


The kernel needs perl to build.
libxcb needs python to build.

I think perl belongs to base, if there ever is a "extra" set, perhaps
python will move there.

perl & python in base set

Džen — 2011-05-01T17:40:47

Hi,

I noticed that perl and python are included in the base set. What I'm
curious about: which tools depend on perl or python in base? Wouldn't it
be more accurate to move these into a different/new set?

Regards

[ANN] sabotage 2011-04-30, a musl+busybox based distribution

Christian Neukirchen — 2011-04-30T22:29:56

Hi,

this is the third public release of sabotage, a distribution based on
musl and busybox.  Provided software is:

9base-6 autoconf-2.68 automake-1.11 binutils-2.21 bison-2.4.3
busybox-1.18.4 curl-7.21.4 diffutils-3.0 e2fsprogs-1.41.14 expat-2.0.1
file-5.05 flex-2.5.35 gawk-3.1.8 gcc-core-4.5.3 git-1.7.4 gmp-5.0.1
grep-2.7 less-436 libarchive-2.8.4 linux-2.6.38.2 lynx2.8.7 m4-1.4.16
make-3.82 mpc-0.9 mpfr-3.0.1 musl-2011-04-18 ncurses-5.9 openssh-5.8p1
openssl-1.0.0d patch-2.6.1 perl-5.12.3 pkg-config-0.25 psmisc-22.13
python-2.7.1 sed-4.2.1 syslinux-4.04 vim-7.3 xz-5.0.2 zlib-1.2.5

There also is an experimental xorg set with:

bigreqsproto-1.1.1 compositeproto-0.4.2 damageproto-1.2.1
fixesproto-5.0 fontconfig-2.8.0 fontsproto-2.1.1 freetype-2.4.4
inputproto-2.0.1 kbproto-1.0.5 libICE-1.0.7 libSM-1.2.0 libX11-1.4.3
libXau-1.0.6 libXaw-1.0.9 libXdmcp-1.1.0 libXext-1.2.0 libXfixes-5.0
libXfont-1.4.3 libXft-2.2.0 libXi-1.4.2 libXmu-1.1.0 libXpm-3.5.9
libXrender-0.9.6 libXt-1.1.1 libfontenc-1.1.0 libpthread-s

[ANN] sabotage 2011-04-18, a musl+busybox based distribution

Christian Neukirchen — 2011-04-18T17:32:23

Hi,

this is the second public release of sabotage, a distribution based on
musl and busybox.  Provided software is:

9base-6 autoconf-2.68 automake-1.11 binutils-2.21 bison-2.4.3
busybox-1.18.4 curl-7.21.4 diffutils-3.0 e2fsprogs-1.41.14 expat-2.0.1
file-5.05 flex-2.5.35 gawk-3.1.8 gcc-core-4.5.2 git-1.7.4 gmp-5.0.1
grep-2.7 less-436 libarchive-2.8.4 linux-2.6.38.2 lynx2.8.7 m4-1.4.16
make-3.82 mpc-0.9 mpfr-3.0.1 musl-2011-04-18 ncurses-5.9 openssh-5.8p1
openssl-1.0.0d patch-2.6.1 perl-5.12.3 pkg-config-0.25 psmisc-22.13
python-2.7.1 sed-4.2.1 syslinux-4.03 vim-7.3 xz-5.0.2 zlib-1.2.5

There also is an experimental xorg set with:

bigreqsproto-1.1.1 compositeproto-0.4.2 damageproto-1.2.1
fixesproto-5.0 fontconfig-2.8.0 fontsproto-2.1.1 freetype-2.4.4
inputproto-2.0.1 kbproto-1.0.5 libICE-1.0.7 libSM-1.2.0 libX11-1.4.3
libXau-1.0.6 libXaw-1.0.9 libXdmcp-1.1.0 libXext-1.2.0 libXfixes-5.0
libXfont-1.4.3 libXft-2.2.0 libXi-1.4.2 libXmu-1.1.0 libXpm-3.5.9
libXrender-0.9.6 libXt-1.1.1 libfontenc-1.1.0 libpthread-

Fwd: sabotage feedback

Kai Hendry — 2011-05-07T12:47:36

Took >10 mins for lists.openwall.com to respond. jeez!

---------- Forwarded message ----------
From: Kai Hendry <hendry< at >iki.fi>
Date: 7 May 2011 00:25
Subject: sabotage feedback
To: chneukirchen< at >gmail.com

I did email sabotage-subscribe< at >lists.openwall.com though I've yet to
receive a response.

I tried your distro tonight on an old Lenovo S10e I had laying around.
It took me a while to past the "Missing Operating System" to realise
from http://syslinux.zytor.com/wiki/index.php/Common_Problems that I
had not marked sda1 as bootable, doh.

i'm not sure how fb0 is supposed to work.
http://www.flickr.com/photos/hendry/5694735910/in/photostream
can i setup vesa or intel Xorg or something?

I'm impressed by your distro, keep it up.