On Tue, Jan 10, 2012 at 10:19:36PM -0800, ron minnich wrote:
This is kind of a fun one: stuff that DID NOT work. I like the basic idea
I generally learn more from what I do wrong than from what I do right---
sometimes because when it works, it is not absolutely for the reasons
I had explicitely
(When I plug it into my plan9 machine, I don't see any entry like
/dev/sdUXX, I see 3 entries under /dev/usb/, ep4.0, ep4.1 and ep4.2,
which appear/disappear as I plug/unplug the device. Running usb/disk
claims sth. like 'there is no disk unhandled').
It appears you have no partition table
On 11 January 2012 11:06, Richard Miller 9f...@hamnavoe.com wrote:
It appears you have no partition table and an ext2 fs occupying
the whole device. This should be OK.
Yes, I think the ext2 is really occupying the whole device. This is in
accord with what linux has said.
Try 'mount -a
On Tue, 2012-01-10 at 22:19 -0800, ron minnich wrote:
This is kind of a fun one: stuff that DID NOT work. I like the basic
idea ...
“failures” may actually provide clues to even more significant
results than the original experimenter had intended. The research is
useful, even though the
Hello,
As readers may remember from a previous thread, I have historically
been, well, less than enamored with some aspects of the coding style
used in Plan 9/plan9port. Now that I'm getting into development, I'd
like to know what coding conventions the Plan 9 community endorses. I
have read
style(6) deals with some of your questions.
Are these practices official/unofficial Plan 9 coding conventions? Are
they used for performance purposes? Are they just poor style? Or has
this kind of style been used for so long that it's BECOME Plan 9's style
of choice? Also, is it considered polite or acceptable coding practice
to
In any project, the polite thing to do is to make your code
look like the surrounding code. You have identified many
ways in which your code does not look like the surrounding
code. That's always the first step.
Russ
(1) For example, P9 code tends to use variable names like i and j,
where I would typically use self-documenting variable names like row
and col. Variable names like row and col are much easier to
search for (i.e., with a right-click), too. Names like i and j
(which occur in many
Style is style; it is not defensible on its own.
If I were contributing to smiley's projects, I would
make the code look the way the rest of his code
does. It's not that one way is necessarily better,
but one way is definitely least distracting in a given
context.
Russ
On Wed, Jan 11, 2012 at 7:20 PM, John Floren j...@jfloren.net wrote:
(1) For example, P9 code tends to use variable names like i and j,
where I would typically use self-documenting variable names like row
and col. Variable names like row and col are much easier to
search for (i.e., with a
Back when I had my FreeBSD server, I used to run a tmux session and
irssi to keep myself connected to IRC at all times. This let me
access it from any computer with an SSH client.
Now I only run a Plan 9 server, but I missed the simplicity and
convenience of having just one nickname on IRC at
by way of an example:
int pszBesmirchHungeriansNotation;
-Skip
On Wed, Jan 11, 2012 at 3:57 PM, John Stalker stal...@maths.tcd.ie wrote:
One thing to remember about descriptive identifiers is that the
compiler doesn't check whether the descriptions are accurate or
not. Often they were when
On Wed Jan 11 20:34:39 EST 2012, skip.tavakkol...@gmail.com wrote:
by way of an example:
int pszBesmirchHungeriansNotation;
who let the camel's nose in the tent?
- erik
On Wed, Jan 11, 2012 at 3:03 PM, John Floren j...@jfloren.net wrote:
Back when I had my FreeBSD server, I used to run a tmux session and
irssi to keep myself connected to IRC at all times. This let me
access it from any computer with an SSH client.
Now I only run a Plan 9 server, but I
That error is very common where ls -di is called in the configure
script (strange that it did not complain on your other system).
a nice fix is fgb's config script
http://plan9.bell-labs.com/sources/contrib/fgb/rc/config
another common problem is grep, where the easiest is to write
GREP=grep
at
Turns out it's been fixed after a pull--thanks to whoever submitted that patch!
John
On Wed, Jan 11, 2012 at 10:40 PM, Jens Staal staal1...@gmail.com wrote:
That error is very common where ls -di is called in the configure
script (strange that it did not complain on your other system).
a
17 matches
Mail list logo
