man 2 write - clarification

[Daniel Baluta]

Hello,

The following phrase taken from man 2 write manual page is confusing:
POSIX  requires that a read(2) which can be proved to occur after a
write() has returned returns the new data.

I think you should you some comas to make a clear statement.
POSIX  requires that a read(2), which can be proved to occur after a
write() has returned, returns the new data.

thanks,
Daniel.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Call for Testing: Nouveau

[Christopher James Halse Rogers]

Hi all,

The drive towards stabilising Nouveau for a rocking Lucid LTS release
has resulted in large changes to the packaging stack.  Nouveau's kernel
module is now in the main kernel package, which fixes most of the
problems people have previously reported.  If you have previously tested
nouveau and found your VTs didn't work, or that plymouth splash didn't
work, or that you just got no display at all please test again with the
2.6.32-16 kernel.  If you've updated in the last day, you should already
have this kernel installed.  You can check which kernel you are running
by running “uname -r” from a terminal - it should print something like
“2.6.32-16-generic”.  The important bit is 2.6.32-16.

This work means that nouveau now has a lack of good bugs reported
against it.  I'm hoping that the fine testers of Ubuntu can rectify
this!  If you've got an nvidia graphics card, please try disabling the
restricted drivers and testing nouveau for a day.  Just using your
computer with the nouveau drivers and reporting any problems you
encounter will be useful, but if you want to test more systematically,
there's a list[1] of things to check on the wiki.

Filing a good bug is as simple as running “ubuntu-bug xorg” and
describing the problem you see, and how you can trigger it, in the
report.  The apport hooks will magically attach all the relevant logs
for you.

If you run into a bug and want to invest some extra effort to help get
it fixed, after reporting the bug you can test with a newer version of
Nouveau.  These packages are available in the xorg-edgers/nouveau PPA.  
Further instructions are on the wiki[2].

Your feedback is greatly appreciated.  Let's go find some bugs!

[1]: https://wiki.ubuntu.com/X/Testing/NouveauEvaluation
[2]:
https://wiki.ubuntu.com/X/Testing/NouveauEvaluation#upstreamtesting 


signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: String break in ubuntone-client without freeze exception

[Benjamin Humphrey]

I would like to second that. Please make sure that you try to stick
the to the freezes.

Over here in the Manual project we have to capture over 2000
screenshots before Lucid is released, the earlier we start, the better
chance we have of reaching our goal and producing a quality product.
But we can't start yet because the default theme has yet to be
finalized, along with a heap of other stuff.

It would make life a lot easier for everyone if the UI freeze was
taken seriously :)

Thanks,
Benjamin

On Fri, Mar 12, 2010 at 7:42 PM, Timo Jyrinki  wrote:
> Hi Rodney,
>
> You recently uploaded a new version of ubuntuone-client source
> package. Please note that Ubuntu has been in UserInterfaceFreeze since
> March 4th, requiring freeze exception including a bug report and a
> note to relevant mailing lists. See more information at
> https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze%20Exceptions
> . I see that there has been an ongoing feature freeze exception, which
> probably should have been user interface freeze exception at the same
> time.
>
> cc:ing ubuntu-devel-discuss just to remind everyone of how to handle
> the user interface freeze exceptions. Let's just try to keep the
> processes in mind, since they are there for a reason. The translators
> and documentation people are mainly interested in getting a proper
> notification on time to make sure documentation changes and new
> translations for both UI and the docs are done as completely as
> possible.
>
> The new UI strings are available at
> https://translations.launchpad.net/ubuntu/lucid/+source/ubuntuone-client
>
> -Timo
>
> --
> ubuntu-doc mailing list
> ubuntu-...@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc
>



-- 
Benjamin Humphrey

Ubuntu Manual Team Lead
Dunedin, New Zealand

http://www.ubuntu-manual.org
www.interesting.co.nz

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: String break in ubuntone-client without freeze exception

[andregondim]

Hi Timo,

Just to fix your link:

https://translations.edge.launchpad.net/ubuntu/lucid/+source/ubuntuone-client/+pots/ubuntuone-client/

Cheers,-
André Gondim
E-mail: andregon...@ubuntu.com
Blog: http://andregondim.eti.br
OpenPGP keys: C9721403
-


On Fri, Mar 12, 2010 at 03:42, Timo Jyrinki  
wrote:
Hi Rodney,

You recently uploaded a new version of ubuntuone-client source
package. Please note that Ubuntu has been in UserInterfaceFreeze since
March 4th, requiring freeze exception including a bug report and a
note to relevant mailing lists. See more information at
https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze%20Exceptions
. I see that there has been an ongoing feature freeze exception, which
probably should have been user interface freeze exception at the same
time.

cc:ing ubuntu-devel-discuss just to remind everyone of how to handle
the user interface freeze exceptions. Let's just try to keep the
processes in mind, since they are there for a reason. The translators
and documentation people are mainly interested in getting a proper
notification on time to make sure documentation changes and new
translations for both UI and the docs are done as completely as
possible.

The new UI strings are available at
https://translations.launchpad.net/ubuntu/lucid/+source/ubuntuone-client

-Timo

--
ubuntu-translators mailing list
ubuntu-translat...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

util-linux-ng v2.17.1 (new support for 4K-sector disks is useless in DOS-compatible mode. The fdisk command prints warning(s) when startup in DOS mode.)

[pp]

New feature by Karel Zak in util-linux-ng v2.17.1 :
fdisk:
   - supports new command line option "-c" to disable DOS-compatible mode from
 command line.

 The DOS-compatible mode is DEPRECATED and will be disabled by default
 in the next major release. Currently, the DOS mode is enabled by default
 for backward compatibility only. 

 The cylinders as display units are DEPRECATED. It's recommended to use
 "-u" command line option or "u" fdisk command and use sectors as display
 units.

   Note that the new support for 4K-sector disks is useless in DOS-compatible
   mode. The fdisk command prints warning(s) when startup in DOS mode.

more : http://thread.gmane.org/gmane.linux.file-systems/38367
more : http://lwn.net/Articles/322777/

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

default screen-saver : why not energy efficient ?

[Jérôme Bouat]

Hello,


Because:

- the cost of the energy will increase in the coming years (what ever 
the primary source is)

- a laptop needs to spare its battery

I think that Ubuntu should set the blank screen as default screensaver 
for all its flavour (Ubuntu, Kubuntu, Xubuntu, Ubuntu netbook edition, ...).


Could we possibly apply this default configuration before the next LTS 
release ? Since there will be a lot of users, it would save a lot of energy.

Each step can make the world better.


Regards.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: String break in ubuntone-client without freeze exception

[Andr� Gondim]

Hi Timo,

Just to fix your link:

https://translations.edge.launchpad.net/ubuntu/lucid/+source/ubuntuone-client/+pots/ubuntuone-client/

Cheers,-
André Gondim
E-mail: andregon...@ubuntu.com
Blog: http://andregondim.eti.br
OpenPGP keys: C9721403
-


On Fri, Mar 12, 2010 at 03:42, Timo Jyrinki  
wrote:
Hi Rodney,

You recently uploaded a new version of ubuntuone-client source
package. Please note that Ubuntu has been in UserInterfaceFreeze since
March 4th, requiring freeze exception including a bug report and a
note to relevant mailing lists. See more information at
https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze%20Exceptions
. I see that there has been an ongoing feature freeze exception, which
probably should have been user interface freeze exception at the same
time.

cc:ing ubuntu-devel-discuss just to remind everyone of how to handle
the user interface freeze exceptions. Let's just try to keep the
processes in mind, since they are there for a reason. The translators
and documentation people are mainly interested in getting a proper
notification on time to make sure documentation changes and new
translations for both UI and the docs are done as completely as
possible.

The new UI strings are available at
https://translations.launchpad.net/ubuntu/lucid/+source/ubuntuone-client

-Timo

--
ubuntu-translators mailing list
ubuntu-translat...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug: python2.5-minimal

[mail2george]

Hi All

I am using this list for my bug report because using "ubuntu-bug" did not work. 
I could not establish a connection to the bug database (continuous errors).

My bug report is as follows:

Richte python2.5-minimal ein (2.5.4-1ubuntu6.1) ...
Linking and byte-compiling packages for runtime python2.5...
/usr/lib/python2.5/site-packages/Onboard/KeyboardSVG.py:104: Warning: 'with' 
will become a reserved keyword in Python 2.6
Compiling /usr/lib/python2.5/site-packages/Onboard/KeyboardSVG.py ...
  File "/usr/lib/python2.5/site-packages/Onboard/KeyboardSVG.py", line 104
with open(pane_svg_filename) as svg_file:
^
SyntaxError: invalid syntax

I gathered the following information using apport-cli -f -p python2.5-minimal:

ProblemType: Bug
Architecture: i386
Date: Mon Mar 15 16:24:07 2010
Dependencies:
 coreutils 7.4-2ubuntu1
 debconf 1.5.27ubuntu2
 debconf-i18n 1.5.27ubuntu2
 dpkg 1.15.4ubuntu2.1
 findutils 4.4.2-1
 gcc-4.4-base 4.4.1-4ubuntu9
 libacl1 2.2.47-2
 libattr1 1:2.4.43-3
 libc-bin 2.10.1-0ubuntu16
 libc6 2.10.1-0ubuntu16--
mail2geo...@gmx-topmail.de
 libgcc1 1:4.4.1-4ubuntu9
 liblocale-gettext-perl 1.05-4build1
 libselinux1 2.0.85-2ubuntu2
 libstdc++6 4.4.1-4ubuntu9
 libtext-charwidth-perl 0.04-5build1
 libtext-iconv-perl 1.7-1build1
 libtext-wrapi18n-perl 0.06-7
 lzma 4.43-14ubuntu1
 perl-base 5.10.0-24ubuntu4
 tzdata 2010e-0ubuntu0.9.10
 zlib1g 1:1.2.3.3.dfsg-13ubuntu3
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: python2.5-minimal 2.5.4-1ubuntu6.1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SourcePackage: python2.5
Uname: Linux 2.6.31-20-generic i686
XsessionErrors:
 (gnome-settings-daemon:1506): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (gnome-settings-daemon:1506): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
 (nautilus:1610): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1621): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:1691): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:1691): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:1691): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:1767): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:1767): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:3066): GLib-WARNING **: g_set_prgname() called multiple times


I have done something wrong using ths list for my bug report, please let me 
know. I can only do better if I know that something is wrong.

Best regards

Georg

-- 




-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: String break in ubuntone-client without freeze exception

[Rodney Dawes]

Hi Timo,

The link you provided doesn't work (I get a nominally blank page),
and the one Andr provided just shows the different languages for
which there are translations, and doesn't really explain which
strings you feel broke this freeze. Can you list them please, so
we can determine which ones exactly you think broke the freeze?

I'll leave you in the capable hands of Elliot if there are any
ones that do violate the freeze.

Thanks, and sorry for any confusion.



On Fri, 2010-03-12 at 08:42 +0200, Timo Jyrinki wrote:
> Hi Rodney,
> 
> You recently uploaded a new version of ubuntuone-client source
> package. Please note that Ubuntu has been in UserInterfaceFreeze since
> March 4th, requiring freeze exception including a bug report and a
> note to relevant mailing lists. See more information at
> https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze%20Exceptions
> . I see that there has been an ongoing feature freeze exception, which
> probably should have been user interface freeze exception at the same
> time.
> 
> cc:ing ubuntu-devel-discuss just to remind everyone of how to handle
> the user interface freeze exceptions. Let's just try to keep the
> processes in mind, since they are there for a reason. The translators
> and documentation people are mainly interested in getting a proper
> notification on time to make sure documentation changes and new
> translations for both UI and the docs are done as completely as
> possible.
> 
> The new UI strings are available at
> https://translations.launchpad.net/ubuntu/lucid/+source/ubuntuone-client
> 
> -Timo
> 



signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug: python2.5-minimal

[Dmitrijs Ledkovs]

On 15 March 2010 15:48,   wrote:
> Hi All
>
> I am using this list for my bug report because using "ubuntu-bug" did not 
> work. I could not establish a connection to the bug database (continuous 
> errors).
>

You can try https://bugs.edge.launchpad.net/ubuntu/+filebug in your
browser to file bugs in the future

> My bug report is as follows:
>
> Richte python2.5-minimal ein (2.5.4-1ubuntu6.1) ...
> Linking and byte-compiling packages for runtime python2.5...
> /usr/lib/python2.5/site-packages/Onboard/KeyboardSVG.py:104: Warning: 'with' 
> will become a reserved keyword in Python 2.6
> Compiling /usr/lib/python2.5/site-packages/Onboard/KeyboardSVG.py ...
>  File "/usr/lib/python2.5/site-packages/Onboard/KeyboardSVG.py", line 104
>    with open(pane_svg_filename) as svg_file:
>            ^
> SyntaxError: invalid syntax
>

After quick search I've found this
https://bugs.edge.launchpad.net/ubuntu/+source/onboard/+bug/460389
This is a known bug in onboard package and fixed in lucid.

If you can try lucid's package. if not comment on that bug saying that
you want this in karmic-backports.

With regards

Dima.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: man 2 write - clarification

[Lucian Adrian Grijincu]

On Wed, Mar 10, 2010 at 12:48 PM, Daniel Baluta  wrote:
> The following phrase taken from man 2 write manual page is confusing:
> POSIX  requires that a read(2) which can be proved to occur after a
> write() has returned returns the new data.
>
> I think you should you some comas to make a clear statement.
> POSIX  requires that a read(2), which can be proved to occur after a
> write() has returned, returns the new data.

I think this should be reported upstream directly.
Write a patch for it and send it on the mailing list CC-ing the
maintainer. Check the contributing rules.

http://www.kernel.org/doc/man-pages/contributing.html
http://www.kernel.org/doc/man-pages/patches.html
http://news.gmane.org/gmane.linux.man


-- 
 .
..: Lucian

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: man 2 write - clarification

[Soren Hansen]

On Wed, Mar 10, 2010 at 12:48:24PM +0200, Daniel Baluta wrote:
> The following phrase taken from man 2 write manual page is confusing:
> POSIX  requires that a read(2) which can be proved to occur after a
> write() has returned returns the new data.
>
> I think you should you some comas to make a clear statement.
> POSIX  requires that a read(2), which can be proved to occur after a
> write() has returned, returns the new data.  thanks, Daniel.

You may find it clearer to read that way, but I believe it would
incorrect. A comma before a which clause suggests that it does not
/define/ the element to which it refers, but merely /describes/ it. In
this case the which clause adds essential, defining information about
the read(2) call, so I believe adding the comma would be wrong.

I should note that I'm not a native English speaker, nor have I studied
English grammar for well over 10 years. The Intarweb[1] does seem to
support my argument, though.

[1]: A search for "comma before which" yields a lot of promosing
 references. http://wire.rutgers.edu/p_grammar_comma2.html for one
 looks credible to me.

-- 
Soren Hansen
Ubuntu Developer & wanna-be grammar nazi
http://www.ubuntu.com/


signature.asc
Description: Digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug: python2.5-minimal

[Soren Hansen]

On Mon, Mar 15, 2010 at 04:48:55PM +0100, mail2geo...@gmx-topmail.de wrote:
> I have done something wrong using ths list for my bug report, please
> let me know. I can only do better if I know that something is wrong.

This list is not for bug reports. There should be a way for you to file
the bug directly on Launchpad.

I can't quite pinpoint where the problem is. onboard says it works with
the "current" python version, which in Karmic is 2.6, but for some
reason python-central is attempting to byte-compile onboard for python
2.5. Are you running some sort of hybrid Jaunty/Karmic system or have
you perhaps changed /usr/bin/python to point to python2.5? 

-- 
Soren Hansen
Ubuntu Developer
http://www.ubuntu.com/


signature.asc
Description: Digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Subject: default screen-saver : why not energy efficient ?

[Brett]

>the cost of the energy will increase in the coming years (what ever
the primary source is)
>I think that Ubuntu should set the blank screen as default screensaver
for all its flavour (Ubuntu, Kubuntu, Xubuntu, Ubuntu netbook edition, ...).

This is a good idea, however it will not save nearly as much energy as keeping 
the OS small and efficient, thus avoiding the need for users to buy new 
computers every few years :-)



  

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Subject: default screen-saver : why not energy efficient ?

[Jérôme Bouat]

Hello,


 > This is a good idea,
 > however it will not save nearly as much energy
 > as keeping the OS small and efficient

Each detail has a side effect and may make the system better.

For example, if a bicycle competitor knows that lycra shoe cover will 
save 1/1000 of his power. He will wear those shoe covers because it will 
maybe save up to 1/10 of his power when it is added to many other tiny 
tweaks.


Regards.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: man 2 write - clarification

[schultz . patrick]

Hyphens or parens would be more appropriate.

 POSIX requires that a read(2) -- proved to occur after a write() has returned 
-- returns the new data. 

But I don't see why its necessary to have the information in the same sentence 
anyways. 

Patrick
Sent from my Verizon Wireless BlackBerry

-Original Message-
From: Soren Hansen 
Date: Thu, 18 Mar 2010 12:31:53 
To: Daniel Baluta
Cc: ; 
Subject: Re: man 2 write - clarification

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug: python2.5-minimal

[Brian Murray]

On Thu, Mar 18, 2010 at 10:34:28AM +, Dmitrijs Ledkovs wrote:
> On 15 March 2010 15:48,   wrote:
> > Hi All
> >
> > I am using this list for my bug report because using "ubuntu-bug"
> > did not work. I could not establish a connection to the bug database
> > (continuous errors).
> >
> 
> You can try https://bugs.edge.launchpad.net/ubuntu/+filebug in your
> browser to file bugs in the future

However, they'll be much more complete if you use ubuntu-bug and that
should always be your first mechanism for reporting bugs about Ubuntu.
 
--
Brian Murray
Ubuntu Bugmaster
Days running lucid: 37


signature.asc
Description: Digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

building ubuntu apps

[Rene Veerman]

Hi,

i'm getting a bit tired with nautilus' 90's-style quirks.

so i'd like to know what a good ubuntu dev environment looks like.

min req: a tree class that's as much as win7's win-explorer tree as
possible, and which can easily be extended.
i gotta be able to put a background on that tree-class, via extension
if need be.

i have some years of OOP exp in delphi (visual pascal on windows) and
l.a.m.p., aswell as a strong inclination towards easy-to-read code.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: man 2 write - clarification

[Daniel Baluta]

On Thu, Mar 18, 2010 at 1:31 PM, Soren Hansen  wrote:
> On Wed, Mar 10, 2010 at 12:48:24PM +0200, Daniel Baluta wrote:
>> The following phrase taken from man 2 write manual page is confusing:
>> POSIX  requires that a read(2) which can be proved to occur after a
>> write() has returned returns the new data.
>>
>> I think you should you some comas to make a clear statement.
>> POSIX  requires that a read(2), which can be proved to occur after a
>> write() has returned, returns the new data.  thanks, Daniel.
>
> You may find it clearer to read that way, but I believe it would
> incorrect. A comma before a which clause suggests that it does not
> /define/ the element to which it refers, but merely /describes/ it. In
> this case the which clause adds essential, defining information about
> the read(2) call, so I believe adding the comma would be wrong.
>
> I should note that I'm not a native English speaker, nor have I studied
> English grammar for well over 10 years. The Intarweb[1] does seem to
> support my argument, though.
>
> [1]: A search for "comma before which" yields a lot of promosing
>     references. http://wire.rutgers.edu/p_grammar_comma2.html for one
>     looks credible to me.

Comma was just a suggestion. I'm not a native english speaker but I don't
find the actual description very clear.

Any suggestions from native speakers are welcomed.

thanks,
Daniel.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: man 2 write - clarification

[John Moser]

On Wed, Mar 10, 2010 at 6:48 AM, Daniel Baluta  wrote:
> Hello,
>
> The following phrase taken from man 2 write manual page is confusing:
> POSIX  requires that a read(2) which can be proved to occur after a
> write() has returned returns the new data.
>

This parses properly.  "a read(2) which can be proved to occur after a
write() has returned" is a noun clause.

> I think you should you some comas to make a clear statement.
> POSIX  requires that a read(2), which can be proved to occur after a
> write() has returned, returns the new data.

"a read(2)" is a noun clause.

"which can be proved to occur after a write() has returned" is
adverbial when separated by commas.

Thus, in your suggested form, we would delete the stuff between commas
because it's auxiliary; but this is incorrect, because it's a
constraint.

Perhaps the following:

"POSIX requires a read(2) provably occuring after the return of a
write() to return the new data."

This is why more complex things are written in a very dry and
structured manner...

  Given the assumptions:

  1.  That a write() has been performed;
  2.  That the write() performed in [1] has returned;
  3.  That a read() is performed;
  4.  That the read() performed in [3] had been performed at some time
later than [2];
  5.  That [4] is provable in the context of the program executing the read()

  The read() performed in [3] must return the new data acquired by the
write() performed in [1].

Notice my wording in (5).  If a program has not verified that a
write() performed in another thread has returned correctly (by thread
synchronization), then it may execute the read() before or after that
write() has actually been performed (i.e. the program doesn't know any
better).  The OS of course would have an easier time making better
assumptions, since it only has to check the real state of read/write
requests internally.  But whatever.

This "communications" thing is complex.  Words are hard to get down in
a clear manner.
>
> thanks,
> Daniel.
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Touch Screen Issues

[Brandon Kuczenski]

Hello all,

I want to inquire about the state of touchscreen development in Ubuntu. 
  I recently built a touch-screen-only system running Karmic and I'm 
generally happy with it (the OS is pretty heavy weight, lots of caching 
to disk, etc, but that is the way of things in this Aero-Aqua-world) but 
the touch screen support is lacking.  I'm using xorg-input-evtouch.

1- No click and drag!! This is an absolute killer.  Many UI features 
don't work at all without click and drag.  What's worse, I *know* the 
capability is there because when I move a window using right-click-> 
move, or resize using right-click->resize, click and drag works (albeit 
awkwardly).

2- I have to start Xorg twice in order for the touchscreen calibration 
to load.  I don't know why this is, but I suspect that the config 
settings (which are currently loaded in /etc/init.d) should be loaded 
from somewhere within the Xsession (doesn't X handle the touchscreen?). 
  This problem is very bad because, when the touch screen doesn't work 
the first time, it is impossible to exit gnome.  I have to restart gdm 
via ssh.  I have to do this every time the computer boots.  If I didn't 
have sshd running, I would not be able to use the system at all without 
a physical mouse.

3- I'm using onboard for my onscreen keyboard.  It takes 5 seconds to 
start.  Surely I could do with a bit more RAM in the machine (1GB not 
enough?) but is there some way for me to force it to stay in memory?

3a- it would be really nice, since it's so much trouble to move the 
onboard window (no click and drag), if onboard would show the text 
that's been typed so far in some kind of display space, since often 
onboard itself appears in front of the cursor location.

3b- onboard doesn't have a man page.

Mostly I'm sending this post as a trial to see if I should file bugs for 
any of these.

Thanks for your input.  Thanks for making ubuntu.

-Brandon

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Moblin session just Not Working in Lucid?...

[Dylan McCall]

Sorry, this is an odd place to post a bug discussion, but I really don't
know where else this can go and I think it's a particularly critical
bug.

I have regular Lucid desktop edition installed (and up to date) on a
very normal netbook.

Three weeks ago, I noticed Moblin is packaged in a really slick fashion
for Lucid: there's moblin-session and a whole lot of moblin-panel-*
packages. I installed moblin-session, which also pulled in all of those.
Logged in to the Moblin session with a completely fresh account and was
greeted, unfortunately, by a completely empty space. Those panel applets
are started (and are running) but don't populate the panel, thus the
session is unusable; the only thing that's there is the Zones feature.

Filed a bug report (with logs and the aftermath of some poking) against
the moblin-session package, since that's what felt sensible to me
(although it could be completely the wrong thing!):
https://bugs.edge.launchpad.net/ubuntu/+source/moblin-session/+bug/535360

Unfortunately, no activity thus far. Can anyone reproduce this? Anybody
here know Moblin? Maybe we can get to the bottom of it... I'm happy to
use whatever interrogation techniques are necessary on the netbook.


Many thanks,

Dylan McCall


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss