* Kyle McDonald <[EMAIL PROTECTED]> [2008-02-08 19:56]:
> I see no [EMAIL PROTECTED] mailiing list.
>
> (I also didn't see a nameservice-discuss, or ldap-discuss list either)
>
> Is there a goo list whee one can find experts or developers for the
> differen nameservices in solaris?
[EMAIL PRO
I reinstalled using CXDE 1/08 and decided to try using the built-in CIFS server
instead of Samba.
I have a very simple setup (simply trying to share some ZFS filesystems to my
Mac). No domains, no Active Directory, etc. I think I have everything setup
according to the documentation and can se
> Installation (on an AMD64x2, ATI video chipset) seems
> to be flawless.
>
> OOo 2.3.1 now runs on Preview 2 out of the box (see
> attached screenshot).
>
> The missing (Chinese) fonts problem seems to have
> been at least ameliorated (see another screenshot).
>
Additional truetype fonts can b
On Fri, 08 Feb 2008 14:53:19 -0500
Kyle McDonald <[EMAIL PROTECTED]> wrote:
> I see no [EMAIL PROTECTED] mailiing list.
>
> (I also didn't see a nameservice-discuss, or ldap-discuss list either)
>
>
> Is there a goo list whee one can find experts or developers for the
> differen nameservices i
I see no [EMAIL PROTECTED] mailiing list.
(I also didn't see a nameservice-discuss, or ldap-discuss list either)
Is there a goo list whee one can find experts or developers for the
differen nameservices in solaris?
-Kyle
___
opensolaris-discuss mai
> It may well be that there are some features of inst that could teach
> us how to do better. If that's the case, call them out so we can
> learn from them.
One of the main features is the namespaces. For example, sgi came out with
eoe.sw.ssh.(man|sw|libs)
If I want the latest SSH, I make my ow
> It usually works, but is clumsy and not terribly user-friendly. Worse,
> it can get its knickers in such a complete twist that it can go neither
> forward nor back. I'm glad I don't have to deal with it any more.
inst(1M) is almost like a woman: you gotta love a woman right,
and if the woman's
This is pretty startling. I just assumed that something like this would work,
since most people have growing data needs and adding new pools to a stripe
would be a waste of money, space, power, time, etc. I'm glad I read this -
I'll go ahead and buy more hard drives now, though I would rather
Here is the output of the program with usb_debug_level set to 5 -
$./a.out
libusb debug level is 5
usb_set_debug(): Setting debugging level to 5 (on)
usb_claim_interface(): hdl=0x8062e98: interface = 0
configuration_value=1, ind
I am currently working on a project to build bluetooth usb driver for
opensolaris using libusb.
I can read the details of the ( configuration , interface and endpoint numbers)
of the usb bluetooth dongle.
I have written a code to send a HCI command to device and read the event packet
arriving
> A few weeks ago I decided to use Solaris as the basis of my home NAS. After
> learning about the benefits of ZFS I just couldn't let myself use anything
> else.
Hello MacBoy2000 : ( I saw that in your email )
I have a fairly excellent build of Samba 3.0.28 if you want to do some
testing :
Joerg Schilling schrieb:
> Roman Morokutti <[EMAIL PROTECTED]> wrote:
>
>
>>> Warning:
>>> ==> Never use cpio to do this kind of work! <
>>>
>>> cpio has a bug with hard link handling that will
>>> cause real problems
>>> if you use the outdated mkisofs that currently comes
>>> w
Someone pointed out that storage -> discuss is a better place for this. Discuss
there instead:
http://www.opensolaris.org/jive/thread.jspa?threadID=51522
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discus
Alan Hargreaves wrote:
> The functionality to change shell is in passwd, but there is a
> completely wrong check in there.
>
> See CR 6638715 Checks in passwd should be authorisation based, not uid based
And of course the ancient RFE 1226020 *other* RFE: add chfn & chsh commands to
Solaris 2
(
Adding CC
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Feb 8, 2008 6:01 AM, Joerg Schilling
<[EMAIL PROTECTED]> wrote:
> "Shawn Walker" <[EMAIL PROTECTED]> wrote:
>
> > Really, any changes to the existing shell, whether its outright
> > replacement or otherwise need a lot of testing.
> >
> > I myself even created a patch to add support for "export B
A few weeks ago I decided to use Solaris as the basis of my home NAS. After
learning about the benefits of ZFS I just couldn't let myself use anything else.
Setting up the RAIDZ storage (4x500GB in my case) is the easy part. The hard
part is making all that storage available to the Windows and M
On Feb 8, 2008 4:04 AM, Joerg Schilling
<[EMAIL PROTECTED]> wrote:
> Chris Linton-Ford <[EMAIL PROTECTED]> wrote:
> > I'm afraid I'm no POSIX expert, so I'm not clear on whether the
> > Bourne/Korn test below implies POSIX compatibility *only* if Korn-style
> > is returned; but if using a POSIXy sh
>As the terrm "multi-command pipeline" is not defined, it is questionable what
>this text should mean
It's a pipeline with more than one command as directly follows from the
pipeline definition.
A pipeline is a sequence of one or more commands separated by
the control opera
[EMAIL PROTECTED] wrote:
>
>
> >
> >You cannot look at too few claims from POSIX.
> >
> >the definitions for read say that read affects the shell execution
> >environment
> >unless it is run on a sub shell.
> >
> >As in "cat from-file | read value" the read command is not run in a sub shell
> >en
>
>You cannot look at too few claims from POSIX.
>
>the definitions for read say that read affects the shell execution environment
>unless it is run on a sub shell.
>
>As in "cat from-file | read value" the read command is not run in a sub shell
>environment, it needs to affect the environment.
>[EMAIL PROTECTED] wrote:
>
>>
>>
>> >Cheers - I just wanted to check that Bourne-style => non-POSIX (rather
>> >than Korn-style <=> POSIX)
>>
>> That is actually unclear to me; certainly I would like to have chapter and
>> verse quoted of the relevant POSIX standard.
>>
>> I certainly believe th
[EMAIL PROTECTED] wrote:
>
> >[EMAIL PROTECTED] wrote:
> >
> >>
> >>
> >> >Cheers - I just wanted to check that Bourne-style => non-POSIX (rather
> >> >than Korn-style <=> POSIX)
> >>
> >> That is actually unclear to me; certainly I would like to have chapter and
> >> verse quoted of the relevant
Hello,
Problem is no more actual. Now all works fine.
Thanks.
Regards,
Girts
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
stty erase ^h
>
> Not followed the whole discussion but above does not work?
It does - that's just made my Friday - cheers. Now for tab completion
and editable command history.. :)
Chris
___
opensolaris-discuss mailing list
opensolaris-discuss@opens
[EMAIL PROTECTED] wrote:
>
>
> >Cheers - I just wanted to check that Bourne-style => non-POSIX (rather
> >than Korn-style <=> POSIX)
>
> That is actually unclear to me; certainly I would like to have chapter and
> verse quoted of the relevant POSIX standard.
>
> I certainly believe that this shou
"Shawn Walker" <[EMAIL PROTECTED]> wrote:
> Really, any changes to the existing shell, whether its outright
> replacement or otherwise need a lot of testing.
>
> I myself even created a patch to add support for "export BLAH=FOO"
> syntax to the current /bin/sh:
> http://icculus.org/~eviltypeguy/sh
On Fri, 08 Feb 2008 11:00:57 +
Chris Linton-Ford <[EMAIL PROTECTED]> wrote:
> > This test _only_ checks for one small and single aspect of POSIX vs. Bourne
> > compatibility. If you find a program like pdksh that intends to be POSIX
> > compatible to return "Bourne" with this test, it only pro
Chris Linton-Ford <[EMAIL PROTECTED]> wrote:
> > The best way to deal with this bug is to use "rxvt" or "gnome terminal"
> > instead
> > of "xterm". Both programs map the key position code from the BS key to DEL
> > before sending the event to the speudo tty.
>
> None of my servers run X - it'
>Cheers - I just wanted to check that Bourne-style => non-POSIX (rather
>than Korn-style <=> POSIX)
That is actually unclear to me; certainly I would like to have chapter and
verse quoted of the relevant POSIX standard.
I certainly believe that this should work:
read value < from-file
> This test _only_ checks for one small and single aspect of POSIX vs. Bourne
> compatibility. If you find a program like pdksh that intends to be POSIX
> compatible to return "Bourne" with this test, it only proves that this
> shell needs a major rewrite to become POSIX compliant.
But the consens
Roman Morokutti <[EMAIL PROTECTED]> wrote:
> So, you would also recommend to update cpio then, or using
> isomaster? What does I have to do in general to activate a
> program which has been freshly built and installed when to
> want to exchange mkisofs, for example?
I would not trust programs li
Chris Linton-Ford <[EMAIL PROTECTED]> wrote:
> > > It's actually pdksh, wh/was +/- based off of ksh88, w/Korn's blessings,
> > > from back in day when ATT was less amenable to open source licenses.
> >
> > On Solaris /bin/ksh is ksh88+
> >
>
> If pdksh is compatible with the existing /sbin/sh, w
> > It's actually pdksh, wh/was +/- based off of ksh88, w/Korn's blessings,
> > from back in day when ATT was less amenable to open source licenses.
>
> On Solaris /bin/ksh is ksh88+
>
If pdksh is compatible with the existing /sbin/sh, why not use that as
its replacement? I've been using OpenBSD
Roman Morokutti <[EMAIL PROTECTED]> wrote:
> > Warning:
> > ==> Never use cpio to do this kind of work! <
> >
> > cpio has a bug with hard link handling that will
> > cause real problems
> > if you use the outdated mkisofs that currently comes
> > with Solaris.
>
> Would you say t
> Warning:
> ==> Never use cpio to do this kind of work! <
>
> cpio has a bug with hard link handling that will
> cause real problems
> if you use the outdated mkisofs that currently comes
> with Solaris.
Would you say that with a more recent version
of mkisofs those problems are
On 2/6/08, a b <[EMAIL PROTECTED]> wrote:
>
> And I'm telling you: inst(1M) is simply phenomenal.
It usually works, but is clumsy and not terribly user-friendly. Worse,
it can get its knickers in such a complete twist that it can go neither
forward nor back. I'm glad I don't have to deal with it a
37 matches
Mail list logo
