On Thu, 21.04.11 09:55, fykc...@gmail.com (fykc...@gmail.com) wrote:
> The third version of patch "Fix broken syscall(__NR_fanotify_mark...
> on o32 mips".
>
> Changes since v2:
> 1. Condition of whether split 64bit argument is now gated by ''defined
> _MIPS_SIM && _MIPS_SIM == _MIPS_SIM_ABI32".
Heya,
http://www.freedesktop.org/software/systemd/systemd-25.tar.bz2
Bigger changes:
- This now includes hostnamed as already announced on this mailing list
- You may now use "auto" and "comment=systemd.automount" on the same
fstab entry so that a mount point is set up as automount, and
aut
The third version of patch "Fix broken syscall(__NR_fanotify_mark...
on o32 mips".
Changes since v2:
1. Condition of whether split 64bit argument is now gated by ''defined
_MIPS_SIM && _MIPS_SIM == _MIPS_SIM_ABI32".
Thank David for pointing it out.
--
Regards,
- cee1
0001-Fix-broken-syscall
2011/4/21 David Daney :
> On 04/20/2011 06:02 PM, fykc...@gmail.com wrote:
>>
>> 2011/4/21 David Daney:
Any comment whether this will break non-MIPS 32bit archs, like x86?
>>>
>>> It would break the MIPS n32 ABI userspace.
>>>
>>> On MIPS n32 we are still __LP64__, but 64-bit values are p
On 04/20/2011 06:18 PM, fykc...@gmail.com wrote:
2011/4/21 Eric Paris:
I am pretty arch stupid, and I have no idea at all if it is related, but
I'm looking at kernel commit 5e844b31c2ace282ab8bea630b63e0212d9532d4
which wires up the fanotify syscalls for mips. I see that it used a u64
for a3 an
2011/4/21 Eric Paris :
> I am pretty arch stupid, and I have no idea at all if it is related, but
> I'm looking at kernel commit 5e844b31c2ace282ab8bea630b63e0212d9532d4
> which wires up the fanotify syscalls for mips. I see that it used a u64
> for a3 and a4 when these are only going to be 32 val
t list
depends on the endianness. Figuring out the correct order is left
as an exercise for the reader.
That's basically the same patch as this one, right?
http://lists.freedesktop.org/archives/systemd-devel/attachments/20110420/be2d393b/attachment.obj
It looks like it might do the
w, mask_high, dfd,
>>> pathname);
>>>
>>> }
>>>
>>> The order of mask_low, mask_high in the syscall argument list
>>> depends on the endianness. Figuring out the correct order is left
>>> as an exercise for the reader.
>>
>>
On 04/20/2011 06:02 PM, fykc...@gmail.com wrote:
2011/4/21 David Daney:
Any comment whether this will break non-MIPS 32bit archs, like x86?
It would break the MIPS n32 ABI userspace.
On MIPS n32 we are still __LP64__, but 64-bit values are passed in a single
register.
It isn't a problem. n32
2011/4/21 David Daney :
>> Any comment whether this will break non-MIPS 32bit archs, like x86?
>
> It would break the MIPS n32 ABI userspace.
>
> On MIPS n32 we are still __LP64__, but 64-bit values are passed in a single
> register.
It isn't a problem. n32 syscall supports 64bit registers, and 64-
On Wed, 20.04.11 15:20, David Daney (dda...@caviumnetworks.com) wrote:
> >Hmm, OK. Do you happen to know which predefined userspace macro we
> >should check against for the o32 ABI?
> >
> >There seems to be __mips__, but that probably covers both ABIs?
>
> How about (untested):
>
> #if defined(_
ly the same patch as this one, right?
http://lists.freedesktop.org/archives/systemd-devel/attachments/20110420/be2d393b/attachment.obj
It looks like it might do the same thing. Someone should try it on
an o32 MIPS userland running on a mips64 kernel.
I think the behavior of the union thing i
On Mon, Apr 18, 2011 at 07:38:54PM +0200, Lennart Poettering
wrote:
> At this point we have collected a few components of systemd that are of
> little or no use on embedded systems. To mind come here hostnamed, the
> binfmt handling, the console handling or even readahead.
I'm attaching a patch
igh, dfd,
> >>>>pathname);
> >>>>
> >>>>}
> >>>>
> >>>>The order of mask_low, mask_high in the syscall argument list
> >>>>depends on the endianness. Figuring out the correct order is left
> >>>>as
On Wed, 20 Apr 2011 18:41:33 +0200 Lennart Poettering
wrote:
> On Wed, 20.04.11 17:01, Christian Hesse (l...@eworm.de) wrote:
>
> > Ok, got one step further I think.
> > The scripts in my initrd call
> >
> > $ /sbin/vgchange --sysinit -a y
> >
> > I think this breaks udev in any way? After call
der of mask_low, mask_high in the syscall argument list
depends on the endianness. Figuring out the correct order is left
as an exercise for the reader.
That's basically the same patch as this one, right?
http://lists.freedesktop.org/archives/systemd-devel/attachments/20110420/be2d393b/att
I'm going to set a high bar for you here:
On Thu, Jan 13, 2011 at 12:29 PM, Daniel Poelzleithner
wrote:
>
> I'm currently implementing a dynamic linux kernel optimizer called
> ulatencyd [1]. In my opinion the desktop experience (which applies to
> servers as well) can be much improved by dynamic
scall(4337, fanotify_fd, flags, mask_low, mask_high, dfd,
> >>pathname);
> >>
> >>}
> >>
> >>The order of mask_low, mask_high in the syscall argument list
> >>depends on the endianness. Figuring out the correct order is left
> >>as an exer
as an exercise for the reader.
That's basically the same patch as this one, right?
http://lists.freedesktop.org/archives/systemd-devel/attachments/20110420/be2d393b/attachment.obj
It looks like it might do the same thing. Someone should try it on an
o32 MIPS userland running on a mips64
er is left
> as an exercise for the reader.
That's basically the same patch as this one, right?
http://lists.freedesktop.org/archives/systemd-devel/attachments/20110420/be2d393b/attachment.obj
It has been suggested that this patch would also work fine on other
32bit CPUs, is tha
On 04/20/2011 09:14 AM, Eric Paris wrote:
On Wed, 2011-04-20 at 12:16 +0200, Aurelien Jarno wrote:
On Wed, Apr 20, 2011 at 03:22:08AM +0200, Lennart Poettering wrote:
On Wed, 20.04.11 09:15, fykc...@gmail.com (fykc...@gmail.com) wrote:
2011/4/20 Lennart Poettering
On Thu, 14.04.11 17:34, f
On Wed, 20.04.11 17:01, Christian Hesse (l...@eworm.de) wrote:
> Ok, got one step further I think.
> The scripts in my initrd call
>
> $ /sbin/vgchange --sysinit -a y
>
> I think this breaks udev in any way? After calling
>
> $ vgchange -a n && vgchange -a y
>
> everything seems to work fine.
On Wed, 2011-04-20 at 12:16 +0200, Aurelien Jarno wrote:
> On Wed, Apr 20, 2011 at 03:22:08AM +0200, Lennart Poettering wrote:
> > On Wed, 20.04.11 09:15, fykc...@gmail.com (fykc...@gmail.com) wrote:
> >
> > >
> > > 2011/4/20 Lennart Poettering
> > > >
> > > > On Thu, 14.04.11 17:34, fykc...@gma
Will do, thanks for the input and help.
-Chris
On 04/19/2011 04:07 PM, Lennart Poettering wrote:
On Tue, 19.04.11 13:57, Chris Ferron (chris.e.fer...@linux.intel.com) wrote:
Heya,
Please send patches to the systemd-devel mailing list, as
systemd-commits is only for notifications of actual ups
On Wed, 20.04.11 16:55, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
>
> On Wed, Apr 20, 2011 at 04:01:05PM +0200, Lennart Poettering wrote:
> > On Wed, 20.04.11 11:24, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> >
> > > > If this is for SSH keys and stuff you might even want to spl
On Wed, 20 Apr 2011 16:35:51 +0200
Christian Hesse wrote:
> On Wed, 20 Apr 2011 16:04:55 +0200
> Lennart Poettering wrote:
>
> > On Wed, 20.04.11 12:12, Christian Hesse (l...@eworm.de) wrote:
> >
> > >
> > > On Tue, 19 Apr 2011 17:02:51 +0200 Albert Strasheim
> > > wrote:
> > > > Hello again
On Wed, Apr 20, 2011 at 04:01:05PM +0200, Lennart Poettering wrote:
> On Wed, 20.04.11 11:24, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
>
> > > If this is for SSH keys and stuff you might even want to split this up
> > > into several units and just look for the sshd key files
> > > directl
On Wed, 20 Apr 2011 16:04:55 +0200
Lennart Poettering wrote:
> On Wed, 20.04.11 12:12, Christian Hesse (l...@eworm.de) wrote:
>
> >
> > On Tue, 19 Apr 2011 17:02:51 +0200 Albert Strasheim
> > wrote:
> > > Hello again
> > >
> > > I had the same problem again today trying to start a service.
>
On Wed, 20.04.11 12:12, Christian Hesse (l...@eworm.de) wrote:
>
> On Tue, 19 Apr 2011 17:02:51 +0200 Albert Strasheim wrote:
> > Hello again
> >
> > I had the same problem again today trying to start a service.
>
> Hello everybody,
>
> I have the same problem on a number of Arch Linux System
On Wed, 20.04.11 11:24, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > If this is for SSH keys and stuff you might even want to split this up
> > into several units and just look for the sshd key files
> > directly. i.e. stick in your ssh-keygen.service something like this:
> >
> > Conditi
On Wed, 20.04.11 10:49, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > The logger service needs the kmsg-syslogd service around? Did you remove
> > that from your build?
>
> I found the problem:
> systemd-logger.service has "After=syslog.socket" but no "Require". I with a
> multi-user or g
On Wed, 20.04.11 07:16, Rainer Gerhards (rgerha...@hq.adiscon.com) wrote:
> > > > I believe it's an rsyslog (imuxsock module) newer feature to limit
> > flow
> > > > from extra-verbose apps by default, which you can tune or
> > completely
> > > > bypass, as described in the docs:
> > > >
> > >
> >
On Wed, 20.04.11 10:47, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
> I'm use cloudfuse module to access remote storage.
>
> If i mount -a after system booted in multi-user.target all work's fine
> But automount in boot process not work:
>
> [5.629611] <27>systemd[1]: Failed to initiali
On Wed, 20.04.11 10:01, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
> Hello.
>
> After upgrade to systemd-24 my sshd.socket after some time die.
>
> netstat -nal | grep 22 says nothing.
>
> systemctl status sshd.socket says:
> Active: failed
> Accepted: 2652 Connected:1
Can you check syslog
On Wed, Apr 20, 2011 at 03:22:08AM +0200, Lennart Poettering wrote:
> On Wed, 20.04.11 09:15, fykc...@gmail.com (fykc...@gmail.com) wrote:
>
> >
> > 2011/4/20 Lennart Poettering
> > >
> > > On Thu, 14.04.11 17:34, fykc...@gmail.com (fykc...@gmail.com) wrote:
> > >
> > > > diff --git a/src/missin
On Tue, 19 Apr 2011 17:02:51 +0200 Albert Strasheim wrote:
> Hello again
>
> I had the same problem again today trying to start a service.
Hello everybody,
I have the same problem on a number of Arch Linux Systems. The boot process
stalls untill dev-{vg-{home,swap},bt-boot}.device times out aft
Hi all,
The second version of patch "Fix broken syscall(__NR_fanotify_mark...
on 32bit mips".
Changes since v1:
1. Use __LP64__ to detect whether in a 64bit environment.
2. Some code clean up.
Fix-broken-__NR_fanotify_mark.-on-32bit-v2.patch
Description: Binary data
On Wed, Apr 20, 2011 at 02:43:36AM +0200, Lennart Poettering wrote:
> On Fri, 18.03.11 13:40, Gustavo Sverzut Barbieri (barbi...@profusion.mobi)
> wrote:
>
> >
> > On Fri, Mar 18, 2011 at 10:52 AM, Andrey Borzenkov
> > wrote:
> > > On Fri, Mar 18, 2011 at 12:35 PM, fykc...@gmail.com
> > > wr
On Wed, Apr 20, 2011 at 01:21:06AM +0200, Lennart Poettering wrote:
> On Sun, 17.04.11 10:33, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > I'm trying to migrate some stuff to systemd, but I have some problems
> > getting it right.
> > The scenario:
> > I'm cross-building root file systems.
On Wed, Apr 20, 2011 at 01:22:32AM +0200, Lennart Poettering wrote:
> On Tue, 19.04.11 13:52, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> > On Tue, Apr 19, 2011 at 12:15:01PM +0200, Mirco Tischler wrote:
> > Ok, now I'm starting with "systemd.unit=setup.service". There are some
> > issues h
40 matches
Mail list logo
