Am 13.05.2013 22:59, schrieb LANGLOIS Olivier PIS -EXT:
> I hear you. I, however, disagree when you qualify the old C trick pattern as
> incorrect.
It is incorrect according to C standards. There is no room for
"disagreement". If you write non-conforming code, you cannot expect it
to work right.
Sorry if this is OT and a dumb question, but are you sure you want
On Mon, May 13, 2013 at 8:20 PM, LANGLOIS Olivier PIS -EXT
wrote:
[...]
> struct B
> {
> int numelem;
> /*
> * Old C trick to define a dynamically sizable array just by
> allocating
> * sizeof(B)
Hi
On Mon, May 13, 2013 at 9:51 AM, Don deJuan wrote:
> On 05/12/2013 03:21 PM, Anatol Pomozov wrote:
>> Hi
>>
>>
>> On Sat, May 11, 2013 at 1:25 PM, Don deJuan wrote:
>>
>>> On 05/11/2013 11:26 AM, Anatol Pomozov wrote:
Hi everyone
Per discussion in 'pacman-dev' maillist [1] I im
On Mon, May 13, 2013 at 4:59 PM, LANGLOIS Olivier PIS -EXT
wrote:
>>
>> The only time the switch makes a difference is when the program is already
>> incorrect. I really doubt Arch is going to enable a flag slowing down all
>> programs to make invalid programs behave
>> *differently* (not necessar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 02:32 AM, Thomas Bächler wrote:
>
> In any case, booting a default installation without init= is
> supported and recommended, and we will make sure it keeps working.
>
Good. That alleviates a lot of my concern.
- --
David Benfell / be
>
> The only time the switch makes a difference is when the program is already
> incorrect. I really doubt Arch is going to enable a flag slowing down all
> programs to make invalid programs behave
> *differently* (not necessary as they were intended to behave, just
> *differently*).
>
> GCC is cor
Hello!
An advice for VMware Workstation users: upgrading to gtkmm 2.24.3-1 on
x86_64 makes VMware Workstation 8.0.6 crash on start or after a few seconds.
I don't know about other versions. It happens with kernel 3.8.11 and 3.9.2.
Downgrading to gtkmm 2.24.2-2 solves it (after an hour of trial an
On Mon, May 13, 2013 at 2:20 PM, LANGLOIS Olivier PIS -EXT
wrote:
> I have just been hit by something:
>
> lano1106@hpmini ~/dev/gcc-test $ g++ --version
> g++ (GCC) 4.8.0 20130502 (prerelease)
> Copyright (C) 2013 Free Software Foundation, Inc.
> This is free software; see the source for copying
I have just been hit by something:
lano1106@hpmini ~/dev/gcc-test $ g++ --version
g++ (GCC) 4.8.0 20130502 (prerelease)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR
On Wed, May 8, 2013 at 5:52 PM, Guus Snijders wrote:
> So at least one way would be place a script that calls
> "/etc/rc.d/libvirtd-guests stop" (or equivalent, it's not hard to replace)
> in /etc/systemd/system-shutdown/ . My main question is if this would be a
> "correct" way or that i could bet
On 05/12/2013 03:21 PM, Anatol Pomozov wrote:
> Hi
>
>
> On Sat, May 11, 2013 at 1:25 PM, Don deJuan wrote:
>
>> On 05/11/2013 11:26 AM, Anatol Pomozov wrote:
>>> Hi everyone
>>>
>>> Per discussion in 'pacman-dev' maillist [1] I implemented a tool that
>> tries
>>> to find Arch out-of-date package
On Mon, 13 May 2013 09:30:49 +0200 Joaquin Villanova
wrote:
[...]
>@Whiskers maybe custom /etc/X11/xorg.conf.d/ profiles could help you
>with mouse/keyboard issues, i have to do it once in a chromium OS
>laptop and it solved the issues just fine. I felt more comfortable with
>lxde/openbox
On Mon, 13 May 2013 10:41:57 +0100 Mauro Santos
wrote:
>On 13-05-2013 08:30, Joaquin Villanova wrote:
>
>> I've got a mobility radeon (rv620) chip and I've had a ton of problems
>> with xfce. I was not using any login manager and xfce was always
>> crashing the X session and getting me to tty, it
On Mon, 13 May 2013 10:19:36 +0200 Thomas Bächler
wrote:
>Am 13.05.2013 10:18, schrieb Iru Cai:
>> Well, some people seldom read pacman's output. e.g. I use a cron job to
>> use pacman to update the system, and I don't read the log very often.
>
>That's your own fault then.
>
>>> Why do you think
Am 13.05.2013 11:41, schrieb Mauro Santos:
>
> That has been a problem for a long time and people recurrently ask how
> to solve it.
>
> Uncheck "Save session for future logins" at the logout menu, then delete
> everything inside ~/.config/xfce4-session and the problem should go away.
So it seem
On 13-05-2013 08:30, Joaquin Villanova wrote:
> I've got a mobility radeon (rv620) chip and I've had a ton of problems
> with xfce. I was not using any login manager and xfce was always
> crashing the X session and getting me to tty, it was horrible (far from
> stable IMHO).
>
That has been a pr
Am 13.05.2013 11:23, schrieb David Benfell:
> On 05/13/2013 01:19 AM, Thomas Bächler wrote:
>
>> The wiki has told you to use init=/usr/lib/systemd/systemd for
>> quite some time.
>
> When I was configuring the bootloaders (grub in two cases, gummiboot
> in another), I was following the installat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 01:19 AM, Thomas Bächler wrote:
>
> The wiki has told you to use init=/usr/lib/systemd/systemd for
> quite some time.
>
When I was configuring the bootloaders (grub in two cases, gummiboot
in another), I was following the installation i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 01:03 AM, Karol Blazewicz wrote:
>
> Not reading pacman's output may lead to problems. Why do you think
> it's a bad way?
>
It's precisely because I *did* read pacman's output that I was
alarmed. Like I say, I think it's okay. But I'd l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2013 12:26 AM, Hussam Al-Tayeb wrote:
> On Sunday 12 May 2013 22:32:03 David Benfell wrote:
>> Hi all,
>>
>> I was alarmed, I think unnecessarily, when I saw the message that
>> a symlink for systemd was removed on an upgrade.
>>
>> As near
Preliminary question and regarding to this question multiposted: Does
anybody still use a RME HDSPe AIO ;)?
Hi,
since the issues I get for my RME HDSPe AIO didn't became less, but more
within the last two years, I cleaned a primary partition to install XP,
just to test, if there are issues caused
Am 13.05.2013 08:15, schrieb Ralf Mardorf:
>
> It's "normal" that lot of options are broken and reporting them to
> upstream as a bug, only does lead to flame.
>
Do you have any examples?
--
xmpp b...@schafweide.org
bjo.nord-west.org | nord-west.org | freifunk-ol.de
On 05/13/13 08:15, Ralf Mardorf wrote:
On Mon, 13 May 2013 00:53:17 +0200, Whiskers
wrote:
The blank screen I first reported in January with Linux-3.7.3-1-i686
seems
to have been cured by the latest update to Linux-3.9.2-1-i686 (and/or
other updates that have happened at the same time). (Usin
On Sunday 12 May 2013 22:32:03 David Benfell wrote:
> Hi all,
>
> I was alarmed, I think unnecessarily, when I saw the message that a
> symlink for systemd was removed on an upgrade.
>
> As near as I can tell, the boot sequence still relies on init, which
> links to the right place.
>
> Is there
Am 13.05.2013 10:18, schrieb Iru Cai:
> Well, some people seldom read pacman's output. e.g. I use a cron job to use
> pacman to update the system, and I don't read the log very often.
That's your own fault then.
>> Why do you think it's a bad way?
>>
> Maybe some people haven't installed systemd-
2013/5/13 Karol Blazewicz
> On Mon, May 13, 2013 at 7:32 AM, David Benfell
> wrote:
> > Hi all,
> >
> > I was alarmed, I think unnecessarily, when I saw the message that a
> > symlink for systemd was removed on an upgrade.
> >
> > As near as I can tell, the boot sequence still relies on init, wh
On Mon, May 13, 2013 at 7:32 AM, David Benfell
wrote:
> Hi all,
>
> I was alarmed, I think unnecessarily, when I saw the message that a
> symlink for systemd was removed on an upgrade.
>
> As near as I can tell, the boot sequence still relies on init, which
> links to the right place.
>
> Is there
27 matches
Mail list logo
