You can do it.
But, you need to implement a kernel QEMU patch to emulate non-x86 architectures.
If you can't find info about it, I'll dig up the stuff I've done.
I first ran into this awhile back when an openSUSE ARM project setting
up a chroot on an x86 system.
Tony
On Mon, Se
s
probably cross platform so probably would work on any other RPM based
distro) you should be able to build from source and add it manually
to your available kernel modules.
Tony
On Mon, Sep 1, 2014 at 11:28 AM, Tony Su wrote:
> You can do it.
> But, you need to implement a kernel QEMU
On 23/01/14 20:58, Geert Uytterhoeven wrote:
> On Thu, Jan 23, 2014 at 8:45 AM, Tony Prisk wrote:
>>>-static inline int clocksource_register_hz(struct clocksource *cs, u32
>>> hz)
>>> +static inline void clocksource_register_hz(struct clocksource *cs, u32
>&g
oid clocksource_register_hz(struct clocksource *cs, u32 hz)
> {
> return __clocksource_register_scale(cs, 1, hz);
> }
This doesn't make sense - you are still returning a value on a function
declared void, and the return is no
penvz I've used them for UML, LXC.
HTH
Tony
On Aug 7, 2013 11:10 AM, "Han" wrote:
>
>
> On Tue, Aug 6, 2013 at 7:51 PM, Michael Richardson wrote:
>
>>
>> Han wrote:
>> > I am trying to build and run some of my C programs in UML. One way
>&
Don't know what you might mean by derive, getting info on the Guest,
Host or DHCP server.
If on the Guest or Host, will any of the following answer your question?
ip addr
ifconfig
Tony
On Fri, Apr 26, 2013 at 9:26 AM, Toralf Förster wrote:
> After I started an UML instance (configure
sufficiently.
- Debian uses Upstart which does things its own way, so SysV and systemd
components won't likely work.
Would be so much easier if the fs included a complete set of basic
functionality specific to that fs.
IMO,
TSU
On Feb 4, 2013 7:05 PM, "Lakshmipathi.G" wrote:
&g
.
In the end, I found a workaround... I simply killed the UML process
identified by the invoked kernel using top on the Host. This is likely OK
because all the UML fs so far have mounted only read only.
Tony
On Feb 5, 2013 6:32 AM, "Tony Su" wrote:
>
> Of course!
>
> Thx,
>
Of course!
Thx,
Tony
On Feb 4, 2013 7:05 PM, "Lakshmipathi.G" wrote:
> Hi Tony -
> Did something like 'init 0' works ?
>
> Sometime back,I faced few problems after shutdown with 'init 0' file
> system became read-only !
> more info here :
>
thers like PING be retrieved from the distro's repo?
Tony
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu
temd improvement before I can even get
a single UML instance launched, but I would suggest that wherever chroot is
recommended that the systemd configuration supporting file system
namespaces be used instead
Http://0pointer.de/blog/proj
Hello,
Actually, 4 questions...
1. I noticed the standard procedure for preparing and launching
including applying chroot 755 to the backing file. Is this really
necessary? I should think that any file system that is installed into
a file should already be jailed or otherwise restricted from acce
> I think I'd go ahead and ACK this unless Tony has some comments. I'm not
> happy about the two pr_emerg calls based on the conditional.
As written the patch has the nice property of not making any changes to the
console output (except to eliminate the possibility of interleaved
>From gdb, it has the following:
Program received signal SIGSEGV, Segmentation fault.
0x0828abd5 in _dl_non_dynamic_init () at dl-support.c:282
282 dl-support.c: No such file or directory.
in dl-support.c
LIne 282 is the line that compare PT_GNU_STACK:
for (uint_fast16_t i = 0; i
I will try networking again in
the latest 2.6.21-rc4 patch.
Tony
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo
continues with no ethernet)
Tony
On Mon, Mar 12, 2007 at 07:09:45PM -0700, Tony wrote:
> ZLIB Compression causes a segv which is only appearent when being
> debugged. It happens arount lib/zlib_inflate/inflate.c:78 in
> zlib_inflate. Sounds like a uml kernel-code handler error.
some odd reason (maybe /proc/mm?) the SEGV wasn't fatal for the whole
kernel. Can you picture a non-fatal segv? I think it MAYBE is a host bug/skas
bug/gcc bug.
Tony
We won't tell. Get more on
17 matches
Mail list logo
