search for: mirbsd

...mit the content addition here, then? > > Please do. Okay, MediaWiki syntax docs follow. Note I have tested those only a bit, and not within the vesamenu context, but if mboot.c32 resets to text mode, all will be fine. ------------------------------------------------------------------ === MirBSD === The MirBSD [https://www.mirbsd.org/mani386/boot.8 second-stage bootloader] acts as faux MultiBoot ?OS kernel?. It can either load the boot.cfg file and the kernel from disc, or have them passed as faux MultiBoot ?OS modules?. In SYSLINUX scenarios, the bootloader is commonly renamed as ?ldbsd...

> On Fri, 5 Dec 2014, Gene Cumm wrote: > > > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), > > The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. > It can then use disc access (not PXE), or you can pass it the "real" > kernel, but also e.g. configuration files, as Multiboot modules, > which are made available as a pseudo-filesystem inside that loader. > > >...

...gt; > Please do. > > Okay, MediaWiki syntax docs follow. Note I have tested those > only a bit, and not within the vesamenu context, but if mboot.c32 > resets to text mode, all will be fine. > > ------------------------------------------------------------------ > > === MirBSD === > > The MirBSD [https://www.mirbsd.org/mani386/boot.8 second-stage > bootloader] acts as faux MultiBoot "OS kernel". It can either > load the boot.cfg file and the kernel from disc, or have them > passed as faux MultiBoot "OS modules". > > In SYSLINUX...

Hello, how would I go porting llvm-gcc-4.2 to an “unknown” platform, i.e. MirBSD? For regular gcc, I’d have to add stuff to gcc/gcc/config/ and patch quite some configure scripts, but seeing that llvm-gcc uses LLVM for target specific stuff, how much of this still applies? cpp defines and startup files at the least, probably, for the com- piler driver… Which dependencies does...

...ork any more on a system that had pxelinux.0 was updated. ?Since version 5.00, support for 16-bit COMBOOT modules has been dropped, and c32 modules switched from the COM32 object format to ELF.? Ugh. Well, updating the *.c32 files was enough to make the Linux discless thingy work again. BUT! The MirBSD bootloader actually took advantage of COMBOOT to provide access to SYSLINUX storage and other things. It was integrating nicely. Why did you take this away? I?m not amused. bye, //mirabilos -- Yes, I hate users and I want them to suffer. -- Marco d'Itri on gmane.linux.debian.devel.general

On Fri, 5 Dec 2014, Gene Cumm wrote: > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. It can then use disc access (not PXE), or you can pass it the ?real? kernel, but also e.g. configuration files, as Multiboot modules, which are made available as a pseudo-filesystem inside that loader. > If so: http://www.syslinux.org/wik...

This uses time, ASLR and pid for randomisation. (Closes: #516774) Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- usr/include/stdlib.h | 2 + usr/klibc/Kbuild | 2 +- usr/klibc/mkstemp.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 96 insertions(+), 1 deletions(-) create mode 100644 usr/klibc/mkstemp.c diff --git a/usr/include/stdlib.h b/usr/include/stdl...

On Thu, 6 Nov 2014, Geert Stappers wrote: > > The MirBSD bootloader actually took advantage of COMBOOT to > > provide access to SYSLINUX storage and other things. It was > > integrating nicely. > > Please tell more about that COMBOOT use case. Okay. The BSD kernels are normally loaded by their own BSD-specific bootloaders (although so...

Hi, after changing mksh to no longer use mkstemp, I decided to try and build mksh-static with klcc on most platforms, in Debian. Here are the results by Debian architecture: alpha (4) fails amd64 works armel works armhf (3) fails i386 works ia64 works m68k (1) workaround mips works mipsel works powerpc (2) fails ppc64 works (!) s390 works s390x works sparc works Architectures not listed either

...+tg.1) unstable; urgency=low + + * debian/patches/add-{arc4random,mkstemp}: add a minimalistic + implementation of the arc4random() API on top of jrand48(3) + to have a self-seeding PRNG; add simple mkstemp(3) implemen- + tation using it. (Closes: #516774) + + -- Thorsten Glaser <tg at mirbsd.de> Fri, 28 Jan 2011 12:59:06 +0000 + klibc (1.5.21-1) unstable; urgency=low * New upstream release (i386 signal(), make 3.82, cleanups) diff -Nru klibc-1.5.21/debian/patches/add-arc4random klibc-1.5.21/debian/patches/add-arc4random --- klibc-1.5.21/debian/patches/add-arc4random 1970-01-0...

...es Binary file ./debian-installer/jessie/amd64/linux matches Binary file ./debian-installer/jessie/i386/linux matches Binary file ./debian-installer/wheezy/amd64/linux matches Binary file ./debian-installer/wheezy/i386/linux matches It does not switch back to text mode when chaining to https://www.mirbsd.org/MirOS/current/i386/boot renamed to "pxebsd.0" (used to be "ldbsd.com" before you dropped COMBOOT support). bye, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228 54881-235 HRB 5168 (AG Bonn) ?...

Anton Korobeynikov dixit: >> Any suggestions? >Please do read http://clang.llvm.org/get_started.html about correct >way of building clang. Oh, I did. I took LLVM and Clang from the very same SVN revision even, placed clang in llvm/tools/ and built. This has worked on GNU/Linux for me once, but clang-current seems to rely on things not yet in llvm. Like I said, I’m using r58565 for

Dixi quod… >Like I said, I’m using r58565 for both llvm and clang (now). Must have been broken, as r58935 for both works. I’ve even fixed some system headers for clang now, and mksh – http://mirbsd.de/mksh – builds fine and passes the regression tests (with the Xcode version, about 83% of it failed, back then). Now up to llvm-gcc *sigh*… //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuate...

Hi sh4 porters, I?ve just fixed a regression of klibc to build from source on sh4 using the sumotsu.debian.net porterbox (thanks for making one available) and found a problem with your archi- tecture: all binaries built with klibc (shared and static) get a SIGILL (illegal instruction). I suspect that different CFLAGS are needed. Please, someone, have a look at it; a release of klibc 2.0 upstream

Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- klcc/klcc.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/klcc/klcc.in b/klcc/klcc.in index 43d0984..e03bf3c 100644 --- a/klcc/klcc.in +++ b/klcc/klcc.in @@ -136,7 +136,7 @@ while ( defined($a = shift(@ARGV)) ) { } else { die "$0: unknown option:...

Commit-ID: 62d84fb8793fdf21c5267688de231cc1a111e070 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=62d84fb8793fdf21c5267688de231cc1a111e070 Author: Thorsten Glaser <tg at mirbsd.org> AuthorDate: Sat, 29 Sep 2012 20:18:48 +0000 Committer: maximilian attems <max at stro.at> CommitDate: Mon, 1 Oct 2012 14:55:24 +0200 [klibc] arm: unbreak armhf shared binaries (those with thumb) The linker command was wrong. Signed-off-by: Thorsten Glaser <tg at mirbsd.org>...

Steve Capper dixit: >> Do we need the fpregs saved even though klibc doesn't do fp? >For gcc targetting Aarch64, We can only guarantee that d8-d15 are >left alone when -mgeneral-regs-only is supplied for building klibc >and any software linked against klibc. I would much prefer to We can enforce this in klcc, just like -mregparm=3 is used by the i386 target. bye, //mirabilos

...ts are but a small part of it. You need to add a new target to llvm. Please read llvm documentation and llvmdev archieve for more information. Evan On Nov 2, 2008, at 7:38 AM, Thorsten Glaser wrote: > Hello, > > how would I go porting llvm-gcc-4.2 to an “unknown” platform, i.e. > MirBSD? For regular gcc, I’d have to add stuff to gcc/gcc/config/ > and patch quite some configure scripts, but seeing that llvm-gcc > uses LLVM for target specific stuff, how much of this still applies? > cpp defines and startup files at the least, probably, for the com- > piler driver… >...

...ginal documentation is very useful. Links to manpages > and/or to CVSweb are both fine. Some users might prefer the man page > (which might or might not be up-to-date and/or enough), and the CVSweb > content might be valuable for others. OK, sure. The sources are mostly in https://www.mirbsd.org/cvs.cgi/src/sys/arch/i386/stand/ (boot/ is the entry point here), plus some stuff in https://www.mirbsd.org/cvs.cgi/src/sys/lib/libsa/ > Regarding EXTLINUX, why would it be trickier than for SYSLINUX? Do you Figuring out the block numbers the loader occupies. Our first stage loader (bootx...

Commit-ID: 49419d2df2018fff5ae6250cf55b16fa65bdc490 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=49419d2df2018fff5ae6250cf55b16fa65bdc490 Author: Thorsten Glaser <tg at mirbsd.org> AuthorDate: Sun, 27 May 2012 17:16:48 +0000 Committer: maximilian attems <max at stro.at> CommitDate: Tue, 29 May 2012 19:07:09 +0200 [klibc] alpha: fix signal handler setup on DEC Alpha We need a five-argument rt_sigaction syscall form with a hidden argument but that can be NULL a...