Re: [OpenIndiana-discuss] Looking for capable notebook for OI and other OSes, small size and with real network.
If you find a good option I would like to know. The last good laptop I have personally used that worked great with open Indiana was my Lenovo T61p from 2008. I still have it and it works well though it is a bit dated and big. -- Sent from my Jelly Bean Galaxy Nexus "Hans J. Albertsson" wrote: >I've been looking at possible choices for a small note-book for OI and >some sort of Windows in dual boot, possibly even an ultrabook thingie. > >However, I keep running into disappointments: > >The biggest one is the apparent scarcity of proper high-capacity GB >wired ethernet. > >Also, if I'd like to run such a thing under some Illumos based OS, I'd >have to think very carefully. > >I sort of liked the Dell XPS 13 Linux Developer's Edition; small, full >HD screen, nice kbd, very thin and fairly large SSD disk. > >But, running it under OI151a7??? I think that might be a bit unlikely to >succeed! > >So, what advice can people give me on this subject? > >The Dell XPS 13 is the right price range, around €1000. >The size is very nice, the screen is VERY good.. > >So, there's a nice exterior target type, but what if I absolutely >require to run OI and have a proper network connector, and PXE capacity? >And MUST run OI, with working wired network and graphics accel. > > > >___ >OpenIndiana-discuss mailing list >OpenIndiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] opensolaris.org shutting down next month
And it can go away at any time. If they change robots.txt to block spiders they will remove content. That happened to an old site I had in the 90s that they archived. I let domain go and new owners did that and archive blocked or purged my sites pages. -- Sent from my Jelly Bean Galaxy Nexus Hugh McIntyre wrote: >Is this going to be any different from www.archive.org, which already >exists and has a full archive of the Internet, including opensolaris.org? > >See http://web.archive.org/web/*/opensolaris.org. > >Of course this does not guarantee to include active content that rely on >server-side scripting, but then you won't get this with wget either. > >Hugh. > > >On 2/14/13 4:16 PM, Lázaro wrote: >> somebody could make a >> >> wget -m http://www.opensolaris.org/ (or wherever the archive is) >> >> pack all the content and send it to me (s, don't tell it to nobody) >> Then, here, in the Caribean's Pirate land I could put it in a friend's >> public web server :D >> >> all the knowledge (in a poor and cheap format) would be saved >> >> >> Greetings >> >> Jack Sparrows > > >___ >OpenIndiana-discuss mailing list >OpenIndiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ssh root login
Don't forget by default root is not a regular user account. Or at least it didn't used to be. You may need to issue the command to make root a full account before you can ssh to the root account. Also, depending on what you're doing, you might consider ssh to a regular user and then escalate via sudo or pfexex instead of ssh to the root user directly. Greg -- Sent from my Jelly Bean Galaxy Nexus Bob Friesenhahn wrote: >On Sun, 13 Jan 2013, Serge Fonville wrote: > >> It took me 2 minutes to set it up, succesfully >> >> The steps I took: >> >>> create key using ssh-keygen >>> edit sshd_config and set PermitRootLogin to yes >>> restarted sshd >>> added the public key to authorized_keys >>> specified the private key in the connection >> >> I tried with and without and empty root password >> >> What did you do different? > >As far as I know, that is what I did. > >Various other people have experienced similar Solaris related issues. >These postings suggest editing /etc/pam.conf. Neither edit worked for >me: > >http://snltd.co.uk/snippets/index.php?c=v&sn=ssh_as_root.php&PHPSESSID=25648260eca8ea5afc1e120278b2b1f6 > >http://www.semicomplete.com/blog/geekery/solaris-10-sshd-publickey-solution.html > >If it makes any difference, I am using OpenIndiana oi_151a7 on the >server host. Ssh on the server host identifies itself as > >Sun_SSH_1.5, SSH protocols 1.5/2.0, OpenSSL 0x0090818f > >And the ssh client (Solaris 10) is > >Sun_SSH_1.1.5, SSH protocols 1.5/2.0, OpenSSL 0x0090704f > >I am only using files+DNS for configuration. No LDAP, NIS, or >anything fancy like that. > >Bob >-- >Bob Friesenhahn >bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ >GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ > >___ >OpenIndiana-discuss mailing list >OpenIndiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Tribblix update
Don't know what the current state is but window maker had wdm that used to work pretty well. Disclaimer, used to maintain it briefly on Linux 10 or so years ago. Greg -- Sent from my Jelly Bean Galaxy Nexus Alan Coopersmith wrote: >On 12/16/12 11:48 AM, Richard L. Hamilton wrote: >> >> On Dec 16, 2012, at 1:37 PM, Peter Tribble wrote: >> [...] >>> I'm keeping a keen eye on other lightweight desktops. E17 builds >>> with very little effort, and the full E17 release is just around the >>> corner. It would be nice to have LXDE and awesome available as >>> well. I'm still looking for a viable graphical login manager. >> >> Since Open Group released CDE source, there's always dtlogin. :-) >> >> Unfortunately, last I heard it only built on Linux and FreeBSD - the source >> released does NOT correspond to what any particular vendor supplied, let >> alone provide much clue how they built their variants. > >dtlogin was definitely one of the CDE areas that Sun customized/forked a lot >from the TOG upstream. > >If you've pulled the entire X consolidation, then you have xdm for whatever >that's worth. I've also heard a lot of people talking about lightdm as a >good path off of gdm. > >-- > -Alan Coopersmith- alan.coopersm...@oracle.com >Oracle Solaris Engineering - http://blogs.oracle.com/alanc > >___ >OpenIndiana-discuss mailing list >OpenIndiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Gnome and the future
WindowMaker sounds good. Used it for a while a few years ago. Been thinking about looking at it again. :) -- Sent from my Jelly Bean Galaxy Nexus Christopher Chan wrote: > > >On Thursday, November 01, 2012 03:01 AM, Ben Taylor wrote: >> On Wed, Oct 31, 2012 at 11:25 AM, openbabel wrote: >>> I am of a commercial view. I am interested in the most popular desktop and >>> most developed environment which is accepted by the current or potential >>> user base.It would not be the correct choice >>> going with a project which either peters out or is not accepted by >>> commercial users as this would waste development time and resource too? >>> >>> As an Enterprise system the commercial view should prevail? >> My suggestion, as someone who spent an inordinate amount of time porting KDE >> 4.x >> to Solaris 10, go with something simple and easy. >> >> Once there's a working DE, folks can then choose to work/port other >> more complex DE's. >> >> > >What has the least dependencies? XFCE? KDE 3.5? Or forget DE and just >get a window manager like WindowMaker? > >___ >OpenIndiana-discuss mailing list >OpenIndiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS; what the manuals don't say ...
Probably should use find -type f to limit to files and also cp -a to maintain
permissions and ownership. Not sure if the will maintain ACLs.
For the truly paranoid, dont delete the original file so early, rename it, move
the temp file back as the original filename, then compare md5 or sha checksums
to make sure they are the same, only deleting the original file if the two sums
match.
--
Sent from my Jelly Bean Galaxy Nexus
Roy Sigurd Karlsbakk wrote:
>> Wouldn't walking the filesystem, making a copy, deleting the original
>> and renaming the copy balance things?
>>
>> e.g.
>>
>> #!/bin/sh
>>
>> LIST=`find /foo -type d`
>>
>> for I in ${LIST}
>> do
>>
>> cp ${I} ${I}.tmp
>> rm ${I}
>> mv ${I}.tmp ${I}
>>
>> done
>
>or perhaps
>
># === rewrite.sh ===
>#!/bin/bash
>
>$fn=$1
>$newfn=$fn.tmp
>
>cp $fn $newfn
>rm -f $fn
>mv $newfn $fn
># === rewrite.sh ===
>
>find /foo -type f -exec /path/to/rewrite.h {} \;
>
>Vennlige hilsener / Best regards
>
>roy
>--
>Roy Sigurd Karlsbakk
>(+47) 98013356
>r...@karlsbakk.net
>http://blogg.karlsbakk.net/
>GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
>--
>I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er
>et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av
>idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og
>relevante synonymer på norsk.
>
>___
>OpenIndiana-discuss mailing list
>OpenIndiana-discuss@openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Namespace management and symlinks in /usr
I took a different approach to do something very similar. I used an env file where all the executable locations were defined and also built a few aliases. I then used uname to detect the os and source the appropriate file. Wrapped that in a single file something so my scripts started with ". ~/bin/loadenvexes.sh" and I was good to go. Worked well across sol/osol/oi, Mac, and several flavors of Linux. -- Sent from my Jelly Bean Galaxy Nexus Reginald Beardsley wrote: > > >--- On Wed, 10/17/12, Udo Grabowski (IMK) wrote: > >> From: Udo Grabowski (IMK) >> Subject: Re: [OpenIndiana-discuss] Namespace management and symlinks in /usr >> To: "Discussion list for OpenIndiana" >> Date: Wednesday, October 17, 2012, 10:11 AM >> On 17/10/2012 16:50, Reginald >> Beardsley wrote: >> > In chasing the Firefox/Java issue, I happened to look >> at the symlinks in /usr. I'm rather disturbed by what >> I find. >> > >> > There are 15715 in my installation of oi_151a. >> > ... >> > Yes, it is painful to force people to fix their >> scripts, but in the end, indulging bad behavior just makes >> the problem worse. >> > Having written scripts that ran cleanly across Ultrix, >> SunOS, AIX, HPUX, Irix and more I know it's not hard to do >> things w/o >> > resorting to polluting the system namespace w/ >> bandaids. >> > >> >> This is for people running heterogenous systems, like old >> Osol >> combined with new OI, or for people upgrading from Osol to >> OI >> for not having trouble with scripts after upgrade, and >> problems >> with configure setups for software (on solaris you usually >> have >> to patch configure scripts, and it's a pain to redo this on >> every upgrade). So having these symlinks is a good thing, >> and >> when these old systems gradually die away, people will >> adapt >> their scripts, but at least up to the next stable release >> of >> OI these links should be kept. As there's usually not much >> left in >> these legacy directories, they will quickly become a simple >> symlink to the default places. > >To paraphrase your response: >" >"These links are good because they keep people from having to fix badly >written scripts. > >When there are more symlinks people will fix their scripts." > >It's been my observation that rather than fix the badly written scripts, they >just write more badly written scripts and the problem gets worse rather than >better. > >The following *really* isn't a lot of work the first time, and it's easy to >fix when it does break. When I was writing scripts that needed to run across >6 distinct flavors of Unix, I had a boilerplate file I placed at the start of >the scripts to handle all this stuff. Typically took about 10-15 minutes to >update all the path information for a new platform and that was for a version >control and build system I wrote. > >if [ -e /usr/sfw/bin/fubar ] > then > FUBAR=/usr/sfw/bin/fubar > >elif [ -e /usr/bin/fubar ] > then > FUBAR=/usr/bin/fubar > >else > echo "Can't find fubar" > exit > >fi > > >As for ./configure, setting PATH properly will take care of most of those. >The ones it won't fix generally can't be fixed. > >Reg > >___ >OpenIndiana-discuss mailing list >OpenIndiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
