2009/8/27, Marko Knöbl openmoko.ma...@gmail.com:
2009/8/27, Risto H. Kurppa ri...@kurppa.fi:
Hi!
Sorry for an ugly post.
Now that I also decided to go for SHR I was requested [1] to check if
the SHR user manual is factually correct.
So here are some comments:
SHR (Stable Hybrid Release)
Risto H. Kurppa ri...@kurppa.fi writes:
How about preferring nano over vi? I think nano - telling people what
to press, might be more friendlier.
Nano is fucked-up shit imho. I'd be sad to see it mentioned in the SHR
manual, no matter what the reasoning is.
--
Be free, use free
On Fri, Aug 28, 2009 at 11:32:09AM +0400, Paul Fertser wrote:
Risto H. Kurppa ri...@kurppa.fi writes:
How about preferring nano over vi? I think nano - telling people what
to press, might be more friendlier.
Nano is fucked-up shit imho. I'd be sad to see it mentioned in the SHR
manual, no
see http://wiki.openmoko.org/wiki/SHR_User_Manual#Audio:_Volume
On Fri, Aug 28, 2009 at 10:40 AM, Markus Törnqvistm...@nysv.org wrote:
On Fri, Aug 28, 2009 at 11:32:09AM +0400, Paul Fertser wrote:
Risto H. Kurppa ri...@kurppa.fi writes:
How about preferring nano over vi? I think nano - telling
On Friday 28 August 2009 08:40:19 Markus T�rnqvist wrote:
On Fri, Aug 28, 2009 at 11:32:09AM +0400, Paul Fertser wrote:
Risto H. Kurppa ri...@kurppa.fi writes:
How about preferring nano over vi? I think nano - telling people what
to press, might be more friendlier.
Nano is fucked-up shit
Maybe the manual should explain how to use vi: how to save, exit etc..
I have no idea how to use it. Maybe a link to vi howto?
the question is how in depth should the manual go. even describing how
to adjust volume level (which as has been said million times is unique
to each device so there is
2009/8/28 Risto H. Kurppa ri...@kurppa.fi:
I have no problems accepting that some prefer more vi than nano but I
have hard time accepting it being suggested in a manual where you
can't be sure people know how to use it as it isn't as
self-explanatory as nano, no matter how much Ctrl you have
On Fri, Aug 28, 2009 at 11:49 AM, Petr Vanekvan...@penguin.cz wrote:
Maybe the manual should explain how to use vi: how to save, exit etc..
I have no idea how to use it. Maybe a link to vi howto?
the question is how in depth should the manual go. even describing how
to adjust volume level
On Fri, 2009-08-28 at 11:00 +0300, Risto H. Kurppa wrote:
see http://wiki.openmoko.org/wiki/SHR_User_Manual#Audio:_Volume
...
Wait a sec - did I understand correctly that you want to tell people
to use vi in the user manual?
So I take you expect that people going through the manual are
The FLTK distribution has an excellent editor that is largely based on
nedit code which I use on my FR. Forward your X display to another host
and fire it up. Does not have all the features of nedit, but works just
fine when compiled out of the box.
...
Wait a sec - did I understand
2009/8/28, Petr Vanek van...@penguin.cz:
I also question too many links in the manual as i would like to package
it as html for people to view it on the phone...
The Wiki Editing Guidelines[1] are already telling people to Use as
few links as possible. However these guidelines are hard to
On Friday 28 August 2009, William Kenworthy wrote:
On Fri, 2009-08-28 at 11:00 +0300, Risto H. Kurppa wrote:
see http://wiki.openmoko.org/wiki/SHR_User_Manual#Audio:_Volume
...
Wait a sec - did I understand correctly that you want to tell people
to use vi in the user manual?
So I
I would agree with Risto here - vi is great for experienced users,
but for the inexperienced or pure user - it can be a nightmare
experience that provides detractors with plenty of ammunition that
linux is hard to use, for geeks only and not for serious use ...
and what about leafpad - it's
On Fri, Aug 28, 2009 at 9:34 PM, Petr Vanekvan...@penguin.cz wrote:
I would agree with Risto here - vi is great for experienced users,
but for the inexperienced or pure user - it can be a nightmare
experience that provides detractors with plenty of ammunition that
linux is hard to use, for
Hi!
Sorry for an ugly post.
Now that I also decided to go for SHR I was requested [1] to check if
the SHR user manual is factually correct.
So here are some comments:
SHR (Stable Hybrid Release) is here to provide you with Root
FileSystem images that you can easily install onto your Freerunner
2009/8/27 Risto H. Kurppa ri...@kurppa.fi:
Hi!
Sorry for an ugly post.
snip
Ugly? Is a great review :) thanks a lot Risto :)
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
ps, the alsa state I used is the 'official' a7 with some little
changes, DON'T use it but try the original:
http://wiki.openmoko.org/wiki/Alsa_state_a7
(each unit is unique - each unit needs some editing of statefile, a7
is a great statefile to start with!)
r
--
| risto h. kurppa
| risto at
your observations are good :) . perhaps you spent more time describing
things rather then would take editing the wiki?
i just returned from holidays yesterday, so will try to check the page
and catch with the latest development that made many things obsolete.
the page has a life on it's own now,
On Thu, Aug 27, 2009 at 4:02 PM, Petr Vanekvan...@penguin.cz wrote:
your observations are good :) . perhaps you spent more time describing
things rather then would take editing the wiki?
No, I don't think so. And I knew someone would say this :)
i just returned from holidays yesterday, so
2009/8/27, Risto H. Kurppa ri...@kurppa.fi:
Hi!
Sorry for an ugly post.
Now that I also decided to go for SHR I was requested [1] to check if
the SHR user manual is factually correct.
So here are some comments:
SHR (Stable Hybrid Release) is here to provide you with Root
FileSystem
After reading this excellent statement from Risto I realized that we
should expand the guidelines for writing manuals on the Wiki [1]
The issues I want to address with these additional rules are:
1) If there is a problem with a distribution several editors are
adjusting the instructions on the
i am not sure if you guys really know what you are talking about:
navit and sms-sentry have been in shr since long time ago. navit
always needed several tricks to get it working (issues reported) .
I'm aware of that. However I think the guide on using Navit and
sms-sentry should not be in the
22 matches
Mail list logo
