> > Apostolos, I think you perfectly know the solaris reboot command exists as
> a (simple) "shutdown 6" or if you want to go fast: "shutdown 6
> now" what is so hard about this command?
> I'm sorry. Typo. Of course I ment init 6
>
Yes of course, but that was not the point I was trying to make
Op 28-3-2011 14:02, Apostolos Syropoulos schreef:
$ copy -x4 -z7 -q66 original_file new_file
to copy a file?
Apostolos, I think you perfectly know the solaris reboot command exists
as a (simple) "shutdown 6" or if you want to go fast: "shutdown 6 now"
what is so hard about this command?
___
Op 28-3-2011 14:42, Dick Hoogendijk schreef:
Op 28-3-2011 14:02, Apostolos Syropoulos schreef:
$ copy -x4 -z7 -q66 original_file new_file
to copy a file?
Apostolos, I think you perfectly know the solaris reboot command
exists as a (simple) "shutdown 6" or if you want to go fast: "shutdown
6
> Apostolos, Hi,
> Sorry but it is interesting to me and I need to ask:
> Is it only me or I keep seeing your every message as new topic?
> Could it be it is you? and do you think it could be avoided for you somehow?
>
I really do not understand what this is supposed to mean.
I am using YAHOO!
On 03/28/11 11:35 PM, GUY WOOLLEY wrote:
> discussions have now moved into some new thread,
> but I guess there will be interference between the two lines.
> Sorry for the inconvenience.
Think Apostolos should be check he's mail client
(ditch yahoo or something), since he was starting new thr
On 03/28/11 06:53, Apostolos Syropoulos wrote:
> Really? Do you know how many times my system became useless
> just because I had used reboot?
you're not providing an *actionable* complaint here with specifics about
how the system became "useless".
It should not be necessary to use "init 6" for
y question. "shutdown"
discussions have now moved into some new thread, but I guess there will be
interference between the two lines. Sorry for the inconvenience.
Guy
--- On Mon, 28/3/11, Nikola M. wrote:
From: Nikola M.
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discus
On 03/27/11 11:39 AM, Apostolos Syropoulos wrote:
>> findroot (pool_rpool,X,Y)
Apostolos, Hi,
Sorry but it is interesting to me and I need to ask:
Is it only me or I keep seeing your every message as new topic?
Could it be it is you? and do you think it could be avoided for you somehow?
(I person
On Mon, Mar 28, 2011 at 19:23, Apostolos Syropoulos
wrote:
>>
>> I fail to see the benefit of changing well-known behaviour in an
>> incompatible way. Change for the sake of change may be chique for
>> fashion items, but not necessarily a good thing in a server-grade OS.
>>
>
> Hey but that's exac
On 28/03/2011 5:51 PM, Michael Schuster wrote:
On Mon, Mar 28, 2011 at 17:39, Apostolos Syropoulos
wrote:
SunOS has a long history of providing many flavors of commands. No one will
object to adding a few. However, changing the behavior of commands that have
been around for 20+ years really d
>
> I fail to see the benefit of changing well-known behaviour in an
> incompatible way. Change for the sake of change may be chique for
> fashion items, but not necessarily a good thing in a server-grade OS.
>
Hey but that's exactly another problem: this is not a server OS only.
The graphics a
laris:~$ pfexec touch /a/rpool/boot/grub/bootsign/pool_rpool
touch: cannot touch `/a/rpool/boot/grub/bootsign/pool_rpool': No such file or
directory
What am I doing wrong ?
Guy
--- On Sun, 27/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss
On Mon, Mar 28, 2011 at 17:39, Apostolos Syropoulos
wrote:
>> SunOS has a long history of providing many flavors of commands. No one will
>> object to adding a few. However, changing the behavior of commands that have
>> been around for 20+ years really doesn't make any sense. Many of these are
> SunOS has a long history of providing many flavors of commands. No one will
> object to adding a few. However, changing the behavior of commands that have
> been around for 20+ years really doesn't make any sense. Many of these are
But that is exactly the problem with these commands: they
roid Incredible.
- Reply message -
From: "Reginald Beardsley"
Date: Mon, Mar 28, 2011 7:38 am
Subject: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
FWIW
There is no justification for breaking the expectations of long time SunOS
users b
FWIW
There is no justification for breaking the expectations of long time SunOS
users because some other system does things differently. The all too common
practice of gratuitously breaking things because some twit thinks it should be
different is why I don't like Gnu/Linux.
At one time, my w
Gary Generous wrote:
The problem is always legacy stuff. If you change the behaviors then
expect that things that people wrote for Solaris to fail. For example,
napp-it, webmin, etc.
The only acceptable solution for me is to put all the Linux compatible
stuff somewhere and let the sysadmin de
On 28.03.2011, at 16:53, Apostolos Syropoulos wrote:
>>> This command does not do the expected thing and that is the problem.
>>
>> The reboot command most certainly does do exactly what I expect it to
>> do, and what it has been successfully doing for years. It may not do
>> what *you* expecte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/03/2011 14:53, Apostolos Syropoulos wrote:
>>> This command does not do the expected thing and that is the problem.
>>
>> The reboot command most certainly does do exactly what I expect it to
>> do, and what it has been successfully doing for yea
> > This command does not do the expected thing and that is the problem.
>
> The reboot command most certainly does do exactly what I expect it to
> do, and what it has been successfully doing for years. It may not do
> what *you* expected it to do, but you know different now?
>
Really? Do you
Nikola M. writes:
> Do you support any change from the way that it is done now by default?
> How about proposed by Guido:
> > If you really care we could create some shutdown/halt/reboot
> > wrappers in /usr/gnu/bin which just call /usr/bin/shutdown with
> > the appropriate options, should be simpl
On 3/28/11 9:34 AM, Volker A. Brandt wrote:
The problem is always legacy stuff. If you change the behaviors then
expect that things that people wrote for Solaris to fail. For example,
napp-it, webmin, etc.
You are quite correct.
The only acceptable solution for me is to put all the
On 03/28/11 03:27 PM, Volker A. Brandt wrote:
> There are two "families" of commands:
> - init and shutdown (shutdown is a script that calls init)
> - halt, poweroff, and reboot (they are hardlinks to one binary)
>
> Please look at:
>
> init(1M)
> shutdown(1M)
> halt(1M) (the same man p
> The problem is always legacy stuff. If you change the behaviors then
> expect that things that people wrote for Solaris to fail. For example,
> napp-it, webmin, etc.
You are quite correct.
> The only acceptable solution for me is to put all the Linux compatible
> stuff somewhere and let t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/03/2011 13:58, Apostolos Syropoulos wrote:
>> The shutdown command certainly is not broken. If indeed the Linux
>> newbie must be catered to, then we can change the defaults, and tell
>> them to "just use shutdown".
>
> This command does not do
Nikola M. writes:
> On 03/28/11 01:31 PM, Toomas Soome wrote:
> in opensolaris based distributions you *can* now use reboot as well,
> which was updated to be safe, but its *not* safe for solaris 10 or older
> ones. if its still too hard to understand, you can always just use
> shutdown from gnome
On 03/28/11 01:12 PM, Volker A. Brandt wrote:
> Hello Nikola!
Hi! Thank you for your response.
>> I figured that out by being stubborn and looking at man pages, and that
>> is what 99 percent of eventual newcomers will not do.
> While you may be right here, I fail to see the problem. The command
>
> > The shutdown command certainly is not broken. If indeed the Linux
> > newbie must be catered to, then we can change the defaults, and tell
> > them to "just use shutdown".
>
> This command does not do the expected thing and that is the problem.
Sorry, I disagree. The shutdown command has be
On 3/28/11 8:58 AM, Apostolos Syropoulos wrote:
The shutdown command certainly is not broken. If indeed the Linux
newbie must be catered to, then we can change the defaults, and tell
them to "just use shutdown".
This command does not do the expected thing and that is the problem.
The GNU
On 03/28/11 01:31 PM, Toomas Soome wrote:
in opensolaris based distributions you *can* now use reboot as well,
which was updated to be safe, but its *not* safe for solaris 10 or older
ones. if its still too hard to understand, you can always just use
shutdown from gnome system menu
>
> and st
> The shutdown command certainly is not broken. If indeed the Linux
> newbie must be catered to, then we can change the defaults, and tell
> them to "just use shutdown".
This command does not do the expected thing and that is the problem.
The GNU grep and the Solaris grep have different command l
>
> That strikes me as a trifle contrived - copying a file is a regular
> occurrence,
> and rebooting a non-desktop machine isn't. (Unless you're doing
> something badly wrong)
>
This is what one would call a fallacy! I am not comparing the two actions.
What I say is that it must be easy to
> Of course it is not a
> solution to remember seven switches to perform a simply task.
You can accept the defaults, then you need none -- or maybe one.
> What if
> someone would tell you that in Solaris one needs to enter
>
> $ copy -x4 -z7 -q66 original_file new_file
>
> to copy a file?
Yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Mar 2011, at 13:02, Apostolos Syropoulos wrote:
>
> By following this train of thought one could say that if one wants a decent
> desktop he should use MacOS, or if one wants some other facility he should
> use Linux, etc. To me this is simp
>
> and still, if you wanna have linux commands, just use linux.
>
By following this train of thought one could say that if one wants a decent
desktop he should use MacOS, or if one wants some other facility he should
use Linux, etc. To me this is simply unacceptable! If the reboot command
is
* Alasdair Lumsden [2011-03-26 21:20]:
> Excuse the top-posting, I'm on my Blackberry...
>
> I've always found the default solaris reboot and shutdown commands a 'pain in
> the ass'.
>
> I doubt there are many systems out there that would be broken by an
> adjustment to the default reboot and
On 28.03.2011, at 13:58, Nikola M. wrote:
> On 03/27/11 07:56 PM, Richard L. Hamilton wrote:
>
>>> I agree. It is surprising that the Indiana project attempted to make
>>> Solaris more Linux-like and then left some obviously different commands
>>> around.
>>> Perhaps adding /usr/gnu/bin/reboot
Hello Nikola!
> Well, I agree that remembering
> shutdown -g 0 -y -i 5 for shutdown machine is not that hard.
>
> BUT that is the question I was asked from newcomers a year ago
> (Obviously you know where newcomers are coming from.. from Linux and
> very few quite new ones) and I did not told the
On 03/26/11 09:20 PM, Alasdair Lumsden wrote:
> What do others think?
>
> Alasdair.
+ for it. Like new command or new switch or something else.
Together with making old users happy with their known default behavior
where it is.
But newcomers I suppose are more/most important.
__
On 03/27/11 07:56 PM, Richard L. Hamilton wrote:
>> I agree. It is surprising that the Indiana project attempted to make Solaris
>> more Linux-like and then left some obviously different commands around.
>> Perhaps adding /usr/gnu/bin/reboot etc would be a compatible way to fix this?
>> Chris
>
Hello,
This is my second post to this mailing list, - so Hello to All,
and - additionally - some thoughts :
> I doubt there are many systems out there that would be broken by an
adjustment to the default reboot and shutdown behaviour
I agree, but
>to bring them more in line with BSD and Linu
On 28.03.2011, at 11:39, Tom Kranz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On 26 Mar 2011, at 20:20, Alasdair Lumsden wrote:
>
>> Excuse the top-posting, I'm on my Blackberry...
>>
>> I've always found the default solaris reboot and shutdown commands a 'pain
>> in the a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26 Mar 2011, at 20:20, Alasdair Lumsden wrote:
> Excuse the top-posting, I'm on my Blackberry...
>
> I've always found the default solaris reboot and shutdown commands a 'pain in
> the ass'.
>
> I doubt there are many systems out there that wou
On Mar 27, 2011, at 8:47 AM, Chris Ridd wrote:
>
> On 26 Mar 2011, at 20:20, Alasdair Lumsden wrote:
>
>> Excuse the top-posting, I'm on my Blackberry...
>>
>> I've always found the default solaris reboot and shutdown commands a 'pain
>> in the ass'.
>>
>> I doubt there are many systems out
> Just for interest (and to prove publicly I know not what I'm doing) did all
> the business with zpool import, zfs mount, installgrub.etc actually
> change
As I said: avoid zfs mount for BEs.
> anything ? Or is the answer to the original question of how to deal with a
> lost
> BE due to
On 03/27/11 05:47 AM, Chris Ridd wrote:
> I agree. It is surprising that the Indiana project attempted to make Solaris
> more Linux-like and then left some obviously different commands around.
It was never going to be completed overnight, and work on updating the
commands to resolve differences w
On 26 Mar 2011, at 20:20, Alasdair Lumsden wrote:
> Excuse the top-posting, I'm on my Blackberry...
>
> I've always found the default solaris reboot and shutdown commands a 'pain in
> the ass'.
>
> I doubt there are many systems out there that would be broken by an
> adjustment to the default
e relevant disk?
I now need to make things permanent.
Thanks to all who helped
Guy
--- On Sun, 27/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
Date: Sunday, 27 March, 2011, 10:39
from my original menu.lst and
try to boot I get
findroot (pool_rpool,1,a)
File not found
That seems to be the nub of it.
What next ?
Guy
--- On Sun, 27/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussio
> findroot (pool_rpool,X,Y)
> file not found
On two systems I have just checked:
$ ls -l
σύνολο 1
-r--r--r-- 1 root root 0 2010-05-19 17:49 pool_rpool
$ more pool_rpool
$ pwd
/rpool/boot/grub/bootsign
Now when you boot with the live thing just
make sure the file exists. Otherwise, created with
it be
somewhere else as well ?
Cheers
Guy
--- On Sun, 27/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
Date: Sunday, 27 March, 2011, 9:48
> jack@opensolaris:~$ pfexec zpo
> jack@opensolaris:~$ pfexec zpool import -f rpool
> jack@opensolaris:~$ pfexec mkdir /a
> jack@opensolaris:~$ pfexec beadm mount 0i_148-2 /a
> jack@opensolaris:~$ pfexec /a/usr/sbin/installgrub /a/boot/stage1
> /a/boot/stage2
> /dev/rdsk/c5d0s0
OK the last command is not correct. My apologies.
read stage1 file /a/boot/stage1
Error opening /a/boot/stage1
jack@opensolaris:~$
G
--- On Sat, 26/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
Date: Saturday, 26 March, 2
> jack@opensolaris:~$ pfexec zpool import -f -R /a rpool
I would just use:
#zpoll import -f rpool
the -R /a sets the altroot property which I think is not what you want.
> jack@opensolaris:~$ pfexec beadm mount 0i_148-2 /a
Provided you did a
# mkdir /a
A.S.
--
Aposto
Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
Date: Saturday, 26 March, 2011, 19:28
> Thanks - I've tried what you suggest but as noted above "reboot"
> just leads to the black
Ok - I stand corrected; in my particular case I see no difference in result
between init 6 and reboot (black screen with GRUB_ etc).
G
--- On Sat, 26/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion lis
> I doubt there are many systems out there that would be broken by an
> adjustment
> to the default reboot and shutdown behaviour to bring them more in line with
> BSD
> and Linux.
>
> What do others think?
A couple of years ago my system (SXCE) became non-functional because I used
a reboot
em more in line with
BSD and Linux.
What do others think?
Alasdair.
--
Alasdair Lumsden
alasdai...@gmail.com
-Original Message-
From: Apostolos Syropoulos
Date: Sat, 26 Mar 2011 13:10:35
To: Discussion list for OpenIndiana
Reply-To: Discussion list for OpenIndiana
Subject: Re: [Ope
> OK - actually I don't see that in the man pages which I've read; be that
> as it may, what do you suggest ?
>From man reboot:
The reboot utility does not execute the scripts in
/etc/rcnum.d or execute shutdown actions in inittab(4). To
ensure a complete shu
OK - actually I don't see that in the man pages which I've read; be that as it
may, what do you suggest ?
--- On Sat, 26/3/11, Chris Ridd wrote:
From: Chris Ridd
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
Date: Saturday, 2
On 26 Mar 2011, at 17:59, GUY WOOLLEY wrote:
> Thanks - I've tried what you suggest but as noted above "reboot" just leads
> to the black screen with GRUB_.
You know that the reboot command isn't the safe way to reboot a Solaris system?
The man page will say something like it doesn't shut down
> Thanks - I've tried what you suggest but as noted above "reboot"
> just leads to the black screen with GRUB_.
>
> In the scenario of my previous post, if I do
> pfexec bootadm update-archive -R /a/b
>
> I get
>
> bootadm: missing /boot/grub on root: /a/b
>
> and I don't know how to fix that.
Guy
--- On Sat, 26/3/11, Apostolos Syropoulos wrote:
From: Apostolos Syropoulos
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list for OpenIndiana"
Date: Saturday, 26 March, 2011, 17:37
> jack@opensolaris:~$ pfexec zfs mount rpool/ROOT/0i_148-2
> jack
> jack@opensolaris:~$ pfexec zfs mount rpool/ROOT/0i_148-2
> jack@opensolaris:~$ cd /a/b
Hello,
If Oi_148-2 is a boot environment (BE), I just wonder why you don't
use /usr/sbib/beadm to mount this BE? I have also tried to mount
using zfs mount and in the end the file system became useless.
A.S
am missing something here (probably quite a lot) but I don't see
what to try next. If anything looks wrong in the above, or any suggestions as
how to boot 0i_148-2 please tell me!
Guy
--- On Wed, 23/3/11, GUY WOOLLEY wrote:
From: GUY WOOLLEY
Subject: Re: [OpenIndiana-discuss] OI
On 23/03/2011, at 20:28, GUY WOOLLEY wrote:
> Thanks Matt - you've put your finger on the problem. I have no /a/boot/grub !
>
> I'd noticed that the live USB image has /boot/grub with the entries you
> identify. I wasn't sure what to make of that.
>
> I don't really get your line
>
> "excha
what was the active boot environment,
not just the root of the pool."
what was the active boot environment ? How do I discover that ?
Cheers
Guy
--- On Wed, 23/3/11, Matt Connolly wrote:
From: Matt Connolly
Subject: Re: [OpenIndiana-discuss] OI boot problem
To: "Discussion list fo
On my system, I see:
matt@vault:/opensolaris/boot/grub$ ls /rpool/boot/grub/
bootsign capability menu.lst splash.xpm.gz
and
matt@vault:/opensolaris/boot/grub$ ls /boot/grub/
bine2fs_stage1_5 install_menu menu.lst
pxegrubstage1
Since last October I've had OI 147/148 running on a new home PC. A while ago I
attempted to mirror it. All seemed good though I didn't fully check that the
mirror booted (silly me etc. - this is a home PC). Then the worst happened and
the new drive where OI was installed failed. So I'm left with
69 matches
Mail list logo
