When did Solaris become Windows?
in [Solaris]
|
From: Colin B. on 19 Nov 2009 00:51 OK, rant mode on. Tonight I went to yank a drive out of my system, and replace it with a quieter one. The only thing on the old drive was swap space, which is part of my regular boot environment. 1) swap -d /dev/dsk/c0t1d0s1 2) (yank drive, put in new one) 3) go to partition the new drive. "You can't label the drive, because I think that c0t1d0s1 is supposed to be in use" 4) Edit /etc/vfstab, temporarily commenting out the swap line 5) partition the drive 6) Undo step #4 7) swap -a /dev/dsk/c0t1d0s1. "According to vfstab, this device is normally swap, so I won't let you add it as swap." Are you KIDDING ME????? If I wanted my hand held to the point of being unable to do things, I'd have chosen an OS that pops up friendly windows all the time. QUIT GETTING IN MY WAY!!! Yes, it's something I can work around, but it's #$&( STUPID! This is so utterly anti-Unix, anti-professional, and anti-sensible that it makes my teeth hurt. Whoever dumbed down Solaris to the lowest common denominator should be fired, beaten, and publically shamed. Grumpily, Colin
From: Thomas Tornblom on 19 Nov 2009 03:08 "Colin B." <cbigam(a)somewhereelse.shaw.ca> writes: > OK, rant mode on. > > Tonight I went to yank a drive out of my system, and replace it with a > quieter one. The only thing on the old drive was swap space, which is > part of my regular boot environment. > > 1) swap -d /dev/dsk/c0t1d0s1 > 2) (yank drive, put in new one) > 3) go to partition the new drive. "You can't label the drive, because I > think that c0t1d0s1 is supposed to be in use" > 4) Edit /etc/vfstab, temporarily commenting out the swap line > 5) partition the drive > 6) Undo step #4 > 7) swap -a /dev/dsk/c0t1d0s1. "According to vfstab, this device is normally > swap, so I won't let you add it as swap." Are you KIDDING ME????? > > If I wanted my hand held to the point of being unable to do things, I'd > have chosen an OS that pops up friendly windows all the time. QUIT GETTING > IN MY WAY!!! Yes, it's something I can work around, but it's #$&( STUPID! > > This is so utterly anti-Unix, anti-professional, and anti-sensible that > it makes my teeth hurt. Whoever dumbed down Solaris to the lowest common > denominator should be fired, beaten, and publically shamed. > > Grumpily, > Colin > I'm working in the services division, and you'd be suprised at the mistakes customers used to do, which these checks stops. Items 3, 4 and 6 above can be worked around by starting format as: env NOINUSE_CHECK=1 format This inhibits all the "in use" checks in format. Personally I would have prefered a "-f" option to the command line, but that was not my call. I'm fairly certain that item 7 would also have been worked around by: env NOINUSE_CHECK=1 swap Of course we still see mistakes where they set NOINUSE_CHECK=1 in their .*shrc file, but much less often. Thomas
From: Richard B. Gilbert on 19 Nov 2009 09:11 Colin B. wrote: > OK, rant mode on. > > Tonight I went to yank a drive out of my system, and replace it with a > quieter one. The only thing on the old drive was swap space, which is > part of my regular boot environment. > > 1) swap -d /dev/dsk/c0t1d0s1 > 2) (yank drive, put in new one) > 3) go to partition the new drive. "You can't label the drive, because I > think that c0t1d0s1 is supposed to be in use" > 4) Edit /etc/vfstab, temporarily commenting out the swap line > 5) partition the drive > 6) Undo step #4 > 7) swap -a /dev/dsk/c0t1d0s1. "According to vfstab, this device is normally > swap, so I won't let you add it as swap." Are you KIDDING ME????? > > If I wanted my hand held to the point of being unable to do things, I'd > have chosen an OS that pops up friendly windows all the time. QUIT GETTING > IN MY WAY!!! Yes, it's something I can work around, but it's #$&( STUPID! > > This is so utterly anti-Unix, anti-professional, and anti-sensible that > it makes my teeth hurt. Whoever dumbed down Solaris to the lowest common > denominator should be fired, beaten, and publically shamed. > > Grumpily, > Colin > Maybe you should climb into your time machine and go back twenty or thirty years. Been there, done that. I'll take today!!!!!!
From: Colin B. on 19 Nov 2009 13:34 Richard B. Gilbert <rgilbert88(a)comcast.net> wrote: > Colin B. wrote: >> OK, rant mode on. >> >> Tonight I went to yank a drive out of my system, and replace it with a >> quieter one. The only thing on the old drive was swap space, which is >> part of my regular boot environment. >> >> 1) swap -d /dev/dsk/c0t1d0s1 >> 2) (yank drive, put in new one) >> 3) go to partition the new drive. "You can't label the drive, because I >> think that c0t1d0s1 is supposed to be in use" >> 4) Edit /etc/vfstab, temporarily commenting out the swap line >> 5) partition the drive >> 6) Undo step #4 >> 7) swap -a /dev/dsk/c0t1d0s1. "According to vfstab, this device is normally >> swap, so I won't let you add it as swap." Are you KIDDING ME????? >> >> If I wanted my hand held to the point of being unable to do things, I'd >> have chosen an OS that pops up friendly windows all the time. QUIT GETTING >> IN MY WAY!!! Yes, it's something I can work around, but it's #$&( STUPID! >> >> This is so utterly anti-Unix, anti-professional, and anti-sensible that >> it makes my teeth hurt. Whoever dumbed down Solaris to the lowest common >> denominator should be fired, beaten, and publically shamed. >> >> Grumpily, >> Colin >> > > Maybe you should climb into your time machine and go back twenty or > thirty years. Been there, done that. I'll take today!!!!!! Really Richard? I'm not suggesting we get rid of 20 years of progress, but a computer that prevents admins from doing admin work bugs me. It's not even hand-holding, it's hand-tying. If I'm root, then let me be root. I can always find a way to destroy a computer as root, why prevent me from some of them but not others? Basically, the computer is now deciding what is dangerous and what is not; and the truth is that EVERYTHING YOU DO as root is potentially dangerous. Thankfully, Thomas has given me a workaround. No more nanny-computer, at least for this problem. Colin
From: Colin B. on 19 Nov 2009 13:39 Thomas Tornblom <thomas(a)hax.se> wrote: > "Colin B." <cbigam(a)somewhereelse.shaw.ca> writes: > >> OK, rant mode on. >> >> Tonight I went to yank a drive out of my system, and replace it with a >> quieter one. The only thing on the old drive was swap space, which is >> part of my regular boot environment. >> >> 1) swap -d /dev/dsk/c0t1d0s1 >> 2) (yank drive, put in new one) >> 3) go to partition the new drive. "You can't label the drive, because I >> think that c0t1d0s1 is supposed to be in use" >> 4) Edit /etc/vfstab, temporarily commenting out the swap line >> 5) partition the drive >> 6) Undo step #4 >> 7) swap -a /dev/dsk/c0t1d0s1. "According to vfstab, this device is normally >> swap, so I won't let you add it as swap." Are you KIDDING ME????? >> >> If I wanted my hand held to the point of being unable to do things, I'd >> have chosen an OS that pops up friendly windows all the time. QUIT GETTING >> IN MY WAY!!! Yes, it's something I can work around, but it's #$&( STUPID! >> >> This is so utterly anti-Unix, anti-professional, and anti-sensible that >> it makes my teeth hurt. Whoever dumbed down Solaris to the lowest common >> denominator should be fired, beaten, and publically shamed. >> >> Grumpily, >> Colin >> > > I'm working in the services division, and you'd be suprised at the > mistakes customers used to do, which these checks stops. > > Items 3, 4 and 6 above can be worked around by starting format as: > > env NOINUSE_CHECK=1 format > > This inhibits all the "in use" checks in format. Personally I would > have prefered a "-f" option to the command line, but that was not my > call. > > I'm fairly certain that item 7 would also have been worked around by: > > env NOINUSE_CHECK=1 swap > > Of course we still see mistakes where they set NOINUSE_CHECK=1 in > their .*shrc file, but much less often. Thanks Thomas! You have just made me a much happier guy. As an added benefit, I see that format is no longer slow as a dog to come up, with the checking out of the way. Cheers! Colin
|
Pages: 1 Prev: Keyboard issue in console. Next: panic[cpu1]/thread=140a000: vfs_mountroot: cannot mount root |