Here's the situation. The software that I've mentioned contains several
scripts to build itself. Those scripts are XPG4 compliant and they
have '#!/bin/sh' as their first line. The scripts use some features
that Solaris's /bin/sh does not grok.
You could make the first line of the
[EMAIL PROTECTED] wrote:
You could make the first line of the scripts:
#!/usr/bin/env sh
That is what I thought. Shouldn't this become the law then? ;-) I
mean, writing '#!/bin/sh' is obviously wrong if you intend your scripts
to be run on a standards compliant OS.
Although
Artem Kachitchkine [EMAIL PROTECTED] wrote:
And hopefully, it will work better than HAL and DBUS on Linux where the
system is responsible for cdrecord problems.
See e.g. this thread:
Stephen Lau [EMAIL PROTECTED] wrote:
Josip: Compliant with what standard?
To everybody else: please resist the urge. I know you so desperately
want to reply, but in the interest of the US-based Sun engineers who
don't want to come back from summer break with a mailbox-full of threads
and
Josip Gracin [EMAIL PROTECTED] wrote:
Stephen Lau wrote:
Josip: Compliant with what standard?
Here's the situation. The software that I've mentioned contains several
scripts to build itself. Those scripts are XPG4 compliant and they
have '#!/bin/sh' as their first line. The scripts
[EMAIL PROTECTED] wrote:
You could make the first line of the scripts:
#!/usr/bin/env sh
and set $PATH to find the proper shell.
This is not POSIX either and is opens a security hole in case
that PATH is problematic.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353
Hello!
I have several standard-compliant shell scripts. These scripts use
'#!/bin/sh'. However, since /bin/sh on Solaris is not
standard-compliant, these scripts fail.
What is the proper way to write standard scripts in Solaris and make
sure that those scripts can be run on other
Is there any news on these two features on X86? Are
they being worked on or we still have to wait a bit longer?
this is indeed something I would like to know also. according to Laptop HCL, my
nc6000 should be fine, but while browsing opensolaris.org, theres quite little
information about the
Joerg Schilling wrote:
Josip Gracin [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
You could make the first line of the scripts:
#!/usr/bin/env sh
That is what I thought. Shouldn't this become the law then? ;-) I
No, because it opens security issues.
Can we conclude then that
On 7/2/06, Josip Gracin [EMAIL PROTECTED] wrote:
Joerg Schilling wrote:
Josip Gracin [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
You could make the first line of the scripts:
#!/usr/bin/env sh
That is what I thought. Shouldn't this become the law then? ;-) I
No, because it
Joerg Schilling wrote:
Josip Gracin [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
You could make the first line of the scripts:
#!/usr/bin/env sh
That is what I thought. Shouldn't this become the
law then? ;-) I
No, because it opens security issues.
Can we conclude
I. Szczesniak wrote:
Yes, but Sun doesn't really care about interoperability. There may be
a change in the future through the ksh93 integration project, but it
is doubtful whether Sun will ever update /bin/ksh to ksh93.
I don't work at Sun (any more), but it seems more accurate to say that
Here's the June issue of the OpenSolaris Community Newsletter:
http://www.opensolaris.org/os/project/content/newsletter/june06/
Another fine month, I'd say. :) Only a day late (due to me, of course).
I'll see you guys next at the end of July from Japan.
Jim
Just wanna check, is it possible to get the next IP address provided by DHCP
server.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Sun, 2 Jul 2006, tyw wrote:
Just wanna check, is it possible to get the next IP address
provided by DHCP server.
Yes. See the 'auto-dhcp' (or 'dhcp' shortcut) option of ifconfig:
ifconfig interface auto-dhcp
regards,
--
shell-init: error retrieving current directory: getcwd: cannot
15 matches
Mail list logo