All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Joel Soete <joel.soete@freebel.net>,
	bame@fc.hp.com, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Palo: cmdline and commanline has different limits?
Date: Mon, 5 Aug 2002 10:59:19 -0400	[thread overview]
Message-ID: <20020805145919.GB31773@systemhalted> (raw)
In-Reply-To: <20020804223618.GG19482@systemhalted>

> > I do not know yet if pad1 can be removed so that cmdline could reach 204 
> > [240-8-7*(sizeof int = 4?)] char lenght, also I prefer to let you choise.
> > 
> > Joel
> 
> I don't see why not? Would 200 characters be enough for your application?
> 
> I do think that "> 255" should be changed in palo.c
> 
> To push it out further would require teaching palo about 
> both formats (and understanding why the comment mentions 
> that all the data must fit in 256 byes).
> 
> c.

Joel,

I just talked to Bame and we both agree that those bytes would
best be left for future expansion.

I've made the change in palo.c such that it checks for "> 127"
I'll be cheking that in today, and a new deb of palo should be out
next week. If you would like to help in the testing process then 
checkout palo from cvs and you can build the package yourself.

The documentation for palo was updated to reflect a limit
in the -c argument.

Do you have a particular use for more than 127 bytes of command line
information? Passing a _lot_ of data via the command line is not 
accepted as good practice :}

c.

  reply	other threads:[~2002-08-05 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 19:05 [parisc-linux] Palo: cmdline and commanline has different limits? Joel Soete
2002-08-04 22:36 ` Carlos O'Donell
2002-08-05 14:59   ` Carlos O'Donell [this message]
2002-08-07  6:30     ` jsoe0708

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020805145919.GB31773@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=bame@fc.hp.com \
    --cc=joel.soete@freebel.net \
    --cc=parisc-linux@parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.