Correct Use of Boot Command

I was wondering what is the correct way to use the boot command.
If an image is installed on every switch in the stack, should each switch load it's own image or just the Masters image? Or, does it really matter if they are really the same image. But, if a switch in the stack dies for whatever reason then if there were 8 switches in the stack, number 8 would become 7 and it would have a incorrect boot statement as there wouldn't be a switch 8 anymore. Since flash: will always exist in the stack wouldn't it be better to use flash: in the boot statement?
For instance:
Switch 8
BOOT path-list : flash8:/c3750e-universalk9-mz.150-2.SE/c3750e-universalk9-mz.150-2.SE.bin
or
Switch 8
BOOT path-list : flash:/c3750e-universalk9-mz.150-2.SE/c3750e-universalk9-mz.150-2.SE.bin
Thank you - Pat

Thanks for the response Jody
Just so I understand -
you are saying that each switch should be configured to boot from flash: rather than flash:# in the switch stack?
So, no matter what the number switch a switch is in the stack, it's individual boot statement should be flash:Image
Hope that is clear - Pat

Similar Messages

MacMini won't accept boot commands - HELP!

My MacMini recently had a fresh Leopard installation. Yesterday it wouldn't open any applications (click icon on dock and it would load the application and immediately quit) so I rebooted the machine. Now it boots, displays the apple symbol, blue screen and then Leopard standard background, the mouse cursor toggles between mouse pointer and colourful circle. Here it stops!
I have attempted to use the boot commands such as Command-T to access it via firewire but it ignores all commands (I cannot even boot from a bootable installation DVD). I have tested the keyboard and it isn't that.
Please HELP!

I had a similar experience where a brand new Mac Mini (Model Identifier: Macmini2,1) would intermittently fail to recognize the pre-boot command keys. Apple support decided it needed a new system board, which it got, but that did not fix the problem.
In this case an Apple aluminum/white keyboard worked as expected at the Apple store.
I was using a PC keyboard and mouse through a cheap PS/2 to USB adapter and the folks at the Apple store were quick to suggest that was the problem, but connecting my keyboard and adapter to another Mini of the same model at the Apple store worked perfectly.
In the end, the 'official' recommendation was to buy a 'USB 2.0 compatible keyboard'.
Well, a plain Logitech ($20 at Fry's) also failed! I decided to return the Mini and buy one that worked!
While carefully documenting the problem, it began working as expected!
It turned out that, in my case, the pre-boot commands only worked if the keyboard was connected to the outside USB port. That's the port nearest the right side of the mini when viewed from the back, under the audio out port.
This configuration has been working now for over a year with the original keyboard and adapter.
Try connecting the keyboard to the right-most USB port.
Regards,
-Glen

[SOLVED] Arch won't mount my hard drives correctly, problems at boot.

Sometimes (only sometimes) Arch Linux will have an error during bootup because my Linux drive gets mounted as sdb instead of sda. My NTFS Sata storage drives gets mounted in its place as sda.
When this happens, Arch Linux will stop booting at the "checking filesystems" step:
:: Checking Filesystems [BUSY]
/dev/sda3:
The superblock could not be read or does not describe a corect ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAIL]
**************** FILESYSTEM CHECK FAILED ****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
Give root password for maintenance
(or type Control-D to continue):
And from there i have to remount my drives manually or restart the computer. Everytime I start the computer, I simply have to hope that my Linux drive will mount as sda. It's totally hit and miss.
Now, I know that my superblock is not corrupt. fsck is failing because it is looking for my linux filesystem on sda. It is encountering my NTFS Sata drive on sda instead of the expected Linux ext filesystem.
So how do I know that this is happening?
Well, after giving the root password, it shows the root prompt
[root@(none) ~]#
and i proceed to use the lshw command to see what's up with the drives:
[root@(none) ~]# lshw -short | grep /dev/
/0/6/0.0.0 /dev/sdb disk 120GB WDC WD1200JB-00E
/0/6/0.0.0/1 /dev/sdb1 volume 101MiB Linux filesystem partition
/0/6/0.0.0/2 /dev/sdb2 volume 258MiB Linux swap volume
/0/6/0.0.0/3 /dev/sdb3 volume 7506MiB EXT4 volume
/0/6/0.0.0/4 /dev/sdb4 volume 104GiB EXT4 volume
/0/6/0.1.0 /dev/sdc disk 81GB Maxtor 6Y080P0
/0/6/0.1.0/1 /dev/sdc1 volume 76GiB Windows NTFS volume
/0/8/0.0.0 /dev/sda disk 640GB Hitachi HDT72106
/0/8/0.0.0/1 /dev/sda1 volume 596GiB Windows NTFS volume
So, clearly, this shows that my Linux drive has gotten mounted as sdb and my NTFS Sata drive has gottem mounted as sda. It's totally random: sometimes they mount vice versa and the system boots just fine.
When Arch does happen to mount itself properly as sda and the system starts successfully, then the lshw command shows this:
[root@(none) ~]# lshw -short | grep /dev/
/0/6/0.0.0 /dev/sda disk 120GB WDC WD1200JB-00E
/0/6/0.0.0/1 /dev/sda1 volume 101MiB Linux filesystem partition
/0/6/0.0.0/2 /dev/sda2 volume 258MiB Linux swap volume
/0/6/0.0.0/3 /dev/sda3 volume 7506MiB EXT4 volume
/0/6/0.0.0/4 /dev/sda4 volume 104GiB EXT4 volume
/0/6/0.1.0 /dev/sdb disk 81GB Maxtor 6Y080P0
/0/6/0.1.0/1 /dev/sdb1 volume 76GiB Windows NTFS volume
/0/8/0.0.0 /dev/sdc disk 640GB Hitachi HDT72106
/0/8/0.0.0/1 /dev/sdc1 volume 596GiB Windows NTFS volume
The above correctly mounted format shows the drives in the same order as my Hard Disk boot priority in BIOS as well as in the same order as during the initial drive detection directly following the memory test (don't know if it has anything to do with it though).
So my question is this. How do I ensure that Arch Linux mounts itself as sda ALL of the time, and not randomly?
Or should I remove my sda entries in etc/fstab and let Arch determine where my Linux filesystems are? If so, how?
It's interesting to note that GRUB is set to boot Arch Linux from hd0, which should be sda.
It's also intriguing to note that if I take out my Sata drive, I never encounter this problem.
Last edited by trusktr (2010-06-15 07:49:31)

Thanks kgas, here's what i found out so far:
Alright so after rebooting, this is what i determined:
When Linux mounts the drives incorrectly (take note of the parts in bold, the short numbers are NTFS filesystems, long numbers the Linux filesystems):
[trusktr@rocketship ~]$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Jun 14 21:08 01CA836D8BE82040 -> ../../[b]sdc1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 0ddf0e41-e7e6-4af5-b0e9-bc79a91b12eb -> ../../[b]sdb1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 92b88528-dd0f-4c1b-bcce-54084ef2aceb -> ../../[b]sdb4[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 C838CF5838CF4462 -> ../../[b]sda1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 cdb33de5-0100-4c5f-a9b1-5c1a444e6eac -> ../../[b]sdb3[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 d0a5d49d-169d-43ce-af0f-216dc4a9f604 -> ../../[b]sdb2[/b]
So an NTFS filesystem is mounted in sda instead of the Linux filesystem
When Linux mounts everything properly:
[trusktr@rocketship ~]$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Jun 14 21:08 01CA836D8BE82040 -> ../../[b]sdb1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 0ddf0e41-e7e6-4af5-b0e9-bc79a91b12eb -> ../../[b]sda1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 92b88528-dd0f-4c1b-bcce-54084ef2aceb -> ../../[b]sda4[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 C838CF5838CF4462 -> ../../[b]sdc1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 cdb33de5-0100-4c5f-a9b1-5c1a444e6eac -> ../../[b]sda3[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 d0a5d49d-169d-43ce-af0f-216dc4a9f604 -> ../../[b]sda2[/b]
This doesn't tell us much except that I indeed do have uuid's for all the drives.
So, i guess as kgas said, i probably need to use the uuid in fstab so that Linux always knows which hard drive is the linux drive! In that case, only the uuid for the Linux drive will be necessary. For the other drives it wouldn't matter so much i guess since they don't contain the operating system.
Alright, i'll be back to determine if this fixes it!
Last edited by trusktr (2010-06-15 06:41:25)

Won't Boot to Apple Hardware Test or accept Boot Commands

Hi All,
I would appreciate some help with this issue, I am trying to boot up to the Apple Hardware Test on my Install Disk 1 that shipped with my MacBook Pro 2.4GHz Model #A1226 ordered new with 4 gigs of memory (around Aug. 2007). I am currently running 10.5.6 and the install disk of course contains the Tiger OS. I have nothing plugging into my computer, other than the Power Adapter. I have the proper install disk inserted in the computer and am holding down the "d" key on my built in keyboard throughout startup, but it will not go to the AHT. It simply boots to the normal login screen for Leopard. In fact the only boot commands that I see any visible or audible confirmation that it has taken effect is the option key, taking me to selecting a Startup Manager and holding down the Power Button gives me a tone from the internal speaker after a few seconds.
Below are what I have tried with seemingly no effect:
"d"
"c"
"t"
Option-Command-"p"-"r" (no beeps)
Command-"v"
Command-"s"
Shift (not sure I should see or hear any confirmation, I don't have any login items set right now so I can't tell if it has any effect)
I have not tried an of the networked drive boot commands as I don't have any networked drives
The only way I have been able to boot from either the optical drive or another disk is either holding down the option key during boot up or selecting the drive from the startup manager in system preferences.
I can't seem to access the AHT an in any way. The reason I am trying to access it is because I have had a few weird intermittent problems that I can't put my finger on and would like to be able to rule hardware out.
I also just replaced my HD with a WD 320 gig drive after my original drive failed due to a physical error. I just restored my data, and all seems to be running well after a permissions repair and a disk repair while booted up on my install disk.
The intermittent problems I was talking about are very vague and rare so I is difficult to describe them other that just a hunch that something is still a bit off. One is the display, every once in a while, showing what looks like a massive bar code or UPC code on my screen. This is not like the bands with soft edges that seem to be a well documented issue with the early MBP but transparent lines of alternating width and brightness with hard edges. Again it looks just like a UPC code transposed on my screen. The other items are random freezing of the OS or the mouse and the fact that my keyboard does not respond to any but a few boot commands. Again all the things are either rare and intermittent or do not come up in daily use of my machine. But when taken together, seem to add up to the conclusion there is still some issue present (at least in my mind).
To recap my specific questions relate to not being able to run the Apple Hardware Test and many of the boot commands having no effect. If you can shed light on the other items mentioned, great!
Thank you!

At a guess, I would think this error code has to do with the video artifacts you are experiencing. You might try reseating all the cables to the display. If the position of the screen makes a difference, there may be damage to a cable, particularly where it goes through the hinge.
Apple is the keeper of the error codes. If you have access to an Apple Store, you could probably ask about this.
Don't know about the other intermittent problems. Does an external keyboard work? If so, there's likely a problem with the internal, maybe even again, a cable or connection.
You could also try creating a new use account and see if the keyboard and mouse problems persist. If not, there could be some sort of software corruption in your usual account. Ditto with the freezing.
Good luck!

Do I need to use a boot image? 6509 / Sup2T Quad / VSS

I'm curious about boot loader images and if or why I should use one.
I've got a 6509 VSS setup running right now with no bootloader variable and no boot image.
SHEC-VSS#sh boot
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby BOOT variable =
Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
SWITCH-VSS#sh ver
Cisco IOS Software, s2t54 Software (s2t54-ADVIPSERVICESK9-M), Version 15.1(2)SY2, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Wed 26-Feb-14 16:03 by prod_rel_team
ROM: System Bootstrap, Version 12.2(50r)SYS3, RELEASE SOFTWARE (fc1)
SHEC-VSS uptime is 16 weeks, 3 days, 21 hours, 10 minutes
Uptime for this control processor is 16 weeks, 3 days, 21 hours, 10 minutes
System returned to ROM by power on
System restarted at 13:56:56 CDT Fri May 16 2014
System image file is "bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin"
Last reload reason: power-on
I'm about to set up a nearly identical VSS pair for another facility.
I just downloaded the latest SY3 version of IOS for the new pair, and there is a boot image available:
s2t54-boot-mz.SPA.151-2.SY3.bin
I just don't know why I would want or need that. Can anyone explain? I'm not a newbie by any means, but I just don't know why I'd need it. Right now, in the bootdisk: volume, I just have my IOS image: s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin That was all that was in there before, but now that I'm building this new pair, I copied s2t54-advipservicesk9-mz.SPA.151-2.SY3.bin onto the same volume.
I understand that if I set a boot variable I can tell it to boot from one image or the other, but what does the BOOTLDR variable do for me. If I were to set the BOOTLDR variable to bootdisk:/s2t54-boot-mz.SPA.151-2.SY3.bin then what does that do for me? Right now, if I reboot, (until I added that 2nd image) it will just boot the only image in that directory with no issue.
What am I missing? Do I need to upgrade or use this boot image for anything?
Thanks for any tips you can provide!
Tim

Tim,
In simple terms, the bootldr file is the helper file to load the IOS.
The BOOTLDR environment variable specifies the Flash file system and filename that contains the boot loader image required to load system software.
The variable defines the primary Cisco IOS image that will load the final image from another source.
we need to set the BOOTLDR environment variable to specify the Flash device and filename of the boot loader image.
For Old version of IOS, there is a requirement of boot loader image to boot up the IOS image.
But for the latest version of IOS, no need for boot loader image.
Below are few things happen when the device boots:-
1. The router initially boots into ROMMON (this is your bootstrap code, which you can see in the show version command).
2. Then the router loads into the bootloader code (this is the bootloadr code, which you see in show version). This bootloader code is just an intermediate step between the ROMMON mode and the IOS mode.
3. The router then boots into the IOS mode from the bootloadr mode.
So if you do not mention the bootloadr specifically by giving the "boot bootloadr" command, the router will assume the bootloadr to be in bootflash of the device and try to boot it from there. If you mention the "boot bootloadr flash:...." command, then the router will look for the bootloadr in the flash (instead of the bootflash). Thats the only difference.
However, in both cases, if you have a valid IOS to boot into, then the router will come up without a problem, irrespective of the fact whether bootloadr image is in bootflash or flash.
HTH
REgards
Inayath
*Plz dont forget to rate if this info is helpfull.

Abobe 9: Printing a PDF file using a DOS command

I have Adobe 9.4.0 on a server and would like to print PDF files using a DOS command. The DOS command we are using is:
start Acrord32.exe /T/S/h/O "C:\BO_Archival_Code_Deployment\Print\TINF018_C.pdf" "Lexmark T644 PS3 - 10.192.36.126"
With this, we are able to print only page 1 of the PDF file. The other pages remain unprinted. This means there is no issue related to printer configuration, firewalls, etc.
Other observations:
1) When we print the file manually after opening it in Adobe 9.4.0, all pages are printed.
2) We found that the above command provides different results with Adobe 8.2.6 i.e. with the DOS command, all pages are printed while using Adobe 8.
We are trying to automate some tasks for which we require the PDF files to be printed automatically through a DOS command. We are being advised to use Adobe 9 as technical support for Adobe 8 is likely to be withdrawn soon.
Please can you help.

Sorry. This is a forum for Adobe Connect issues not PDF issues. Please locate the correct forum so your question can be addressed properly there.

Using unix 'diff' command to publish iweb to non .mac server

It is a common problem that you can't upload incremental changes to a website a web server that is not a .mac. Recently I found that the unix (shell) 'diff -qr' works nicely for this.
However I can't seem to get this to work in automator. That is where I need some help.
What I did :
I have an iweb website in my directory
Documents/website
I made a second directory where I store my uploaded version of the website:
Documents/websiteonserver
Using a shell script I want to compare the differences between these two directories using the diff command in a shell script. When I run 'diff -qr websiteonserver website' in a terminal window, it gives a nice overview of which files are changed and which ones are new. When workin with iWeb this saves me a lot of time uploading my homepage to a non .mac server. I can only upload the changed files, which is usually only a few. Diff does not look at timestamps (which are useless in the iweb case) but it actually looks into a file and with the -q option it stops when it finds a difference. With the -r added (-qr) it also looks through all subdirectories and compares files with the same name.
I like to automate this process so that my wife can update our family homepage with just one mouseclick (or as few as possible)
Unfortunately the diff command in automator gives an error, and there's no info on why it does this.
The commands I gave:
cd Documents
diff -qr websiteonserver website
(using PWD i verified that the path is correct like this). The only stumbling block for automator seems to be the diff command. Anybody any suggestions on this?
The next challenge is to take the diff output and use that to upload only changed/new files to a ftp server.
Any help / ideas are welcome
Greetings,
Adriaan

Dear Cyclosaurus,
I used a single command as us specified. It really helped to add the path to the directories I wanted to compare. So now at least I got it two work partly:
It seems to work only if I compare two files. Comparing directories still does not work. Maybe diff generates some kind of error code when doing this??? It does not do that in the shell.
If I compare all files in directories + subdirectories , the workflow does not work. It seems as if it only accepts a single output line or so from the diff function. If there is more output (or maybe some newline character) the workflow halts. Very peculiar.
mmm.... I will try to make a shell script which I can run in automator. In the script file I will then generate a txt file. Then the automator can run the script and then it can open the resulting file in a text editor. See if that works.
mmm nope. I made a script like this:
#!/bin/bash
diff -qr ~/Documents/websiteon_theserver/ ~/Documents/website/ > ~/Documents/logfile.txt
I modified the atributes to executable and I could run it from the command line. The logfile.txt was created and has the correct info. I could not run it from automator...
I did copy the last line from the script into automator. And also there it does create the logfile, but the automator still says there was an error and stops.
maybe I should try Applescript, were it not that I am totally clueless on that language...

Mtrr: type mismatch for d8000000 / Grub boot command line

Hi,
Dmesg is showing:
mtrr: type mismatch for d8000000,2000000 old: uncachable new: write-combining
(DL380 G5 - generic KVM/LCD Monitor)
I googled for the problem found
Disable MTRR for vesafb. iirc, there's a boot command line option to do it.video=vesafb:nomtrr
Does anyone know this problem, how to fix it, how to put this into Grub to avoid the error on next boot?
Best regards

Is that for the video card you are using? In that case you can just edit "/etc/grub.conf" and add that clause to the line beginning with "kernel" and reboot.

Using 'defaults delete' command with com.apple.dock

I have been using the "defaults" command in my scripts to add an icon to a user's dock after a new application has been installed. But now, I'm having trouble trying to figure out how to remove an icon from the dock using the command line. For adding an icon, I use:
defaults write com.apple.dock persistent-apps -array-add '<dict><key>tile-data</key><dict><key>file-data</key><dict>
<key>_CFURLString</key><string>/Applications/NewApp/Program.app
</string><key>_CFURLStringType</key><integer>0</integer>
</dict></dict></dict>'
(take out all the carriage returns and spaces. I had to put them in here for the line to show properly on the post)
This works great for adding an icon. But, I cannot seem to write something similar using "defaults delete"
Any help is appreciated.
Thanks,
-Steve
PowerMac G5 Mac OS X (10.4.7)

Hi Steve,
   If it froze then the code isn't robust against problems. In this case the problem is the web. The command has four spaces in a row in two of the matches. However, the browser smashes that down into a single space. I never understood that aspect of HTML but I know about it and should have considered it. I will replace the spaces with capital Xs. If you replace the Xs with regular spaces, the command should work:
defaults write com.apple.dock persistent-apps "$( defaults read com.apple.dock persistent-apps | awk 'BEGIN{ ARRAY = "("; ELEM = "" } /^XXXX{/{ while ( $0 !~ /^XXXX}/ ) { if ( ELEM == "" ){ ELEM = $0 } else { ELEM = ELEM "\n" $0 } if ( $0 ~ "_CFURLString\"" && $0 !~ /zzzz/ ){ FOUND = "true" } getline } ELEM = ELEM "\n" $0; if ( FOUND == "true" ){ ARRAY = ARRAY "\n" ELEM }; FOUND = "false"; ELEM = "" } END{ sub( /,[^\n]*$/, "", ARRAY); print ARRAY; print }' )"
In some sense that is poor coding but in the default syntax of the "defaults" command, the only way to determine depth is by how far something is indented. It would have been far more robust to actually count the number of opening parentheses and keep track of the depth but that would have been more complex to code. If I have time, I'll look into changing that.
   I assume that the reason the command hung is that it went into an infinite loop. I've also added a carat, '^', in front of the first group of four spaces that will keep that from happening. When typed correctly the command works without it but now it will fail without going into an infinite loop.
Gary
~~~~
   United Nations, New York, December 25. The peace and joy of the Christmas season was marred by a proclamation of a general strike of all the military forces of the world. Panic reigns in the hearts of all the patriots of every persuasion. Meanwhile, fears of universal disaster sank to an all-time low over the world.
      -- Isaac Asimov

Problem with boot commands on G3 iMac

My iMac G3 will not accept any boot commands like "C" or "CMD, ALT, P, R" etc... etc... when using the original Apple PRO keyboard.
The Pro keyboard is fine and all the keys work in OS X. For the sake of it i tried another keyboard from my Power Mac and the boot commands worked perfectly.
What could the problem be so?

Macintosh: How to Troubleshoot the Apple Pro Keyboard and Mouse
Apple Pro Keyboard: System Requirements

Lion Preview.app crashes every time i use a key command

Whenever I use a key command in Preview.app it crashes.
I'm fine selecting any command from the actual menus, but as soon as I use the key commands for the same functions the app crashes.
(And we're talking also basic stuff like command N or O or even Period to exit an Open dialog.)
So … anyone have any ideas?
I've tried trashing all Preview preferences in my library folder, and I've repaired permissions, and I've tried a safe boot … but the problem remains.
The problem is local, and everything works just fine for other user accounts on the same machine. But I'd rather solve the issue than migrating all my data to a new account.

Ha! Fixed it!
Kept reading all "Preview+plist" threads and found this one: https://discussions.apple.com/message/17195650#17195650
And sure enough, trashing ~/Library/Containers/com.apple.Preview/ reset the preferences for Preview.app and now all key commands work without crashing.
But if erasing that folder, and more importantly the plist in it, did reset the preferences, that would suggest the preferences were being saved there. So I now changed the prefs and quit the app, and then trashed the containers folder again, and restarted the app. But strangely the prefs remained. So I thought, well if the prefs were being stored there, maybe erasing that plist made Preview reinstate the regular plist in the regular Preferences folder? But no go, as there's still no regular Preview plist in the regular Preferences folder.
So now, there's no regular plist, and erasing the Containers folder no longer resets the prefs, but changes to prefs are still being saved somewhere … so where the **** are they being saved now? It's like they just keep burrowing down further into the ground with every attempt to erase them. What the **** is going on? ;-)
Anyways, the initial problem is solved, so … maybe I should just let the mystery remain? ;-)

Reducing apps size using the "strip" command

Hello,
I'm trying to create a Terminal script to reduce all my apps size, using the "strip" command.
Therefore, I have to look up into all the .app packages of my hard drive to find all the exec files, and then apply the strip command to them.
The thing is I am a complete newbie, and all I come up with is : (without the ")
"find . -name "exec" -exec strip '{}' \;"
But it doesn't seem to work at all...
I think this is due to the name reference.
-> How do I find Unix executable files (even inside the .app packages) using the "find" command?
-> And how do I correctly apply the "strip" command to them?
thanks for your help!

wykazox wrote:
"find . -name "exec" -exec strip '{}' \;"
I think that you need to check the -perm option of find.
Mihalis.

Sunfire 480R + boot command does not boot from disk

Hi All,
I'm trying to work out why when I type ok>boot
the server keeps booting off the network. It's almost as it does not find any disks and then since diag-device is set to net it tries that instead. The same happens even if I do an init 6 or reboot from solaris??
the output from eeprom looks like:
# eeprom
test-args: data not available.
diag-passes=1
local-mac-address?=false
silent-mode?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttya-mode=9600,8,n,1,-
output-device=ttya
input-device=ttya
auto-boot-on-error?=false
load-base=16384
auto-boot?=true
boot-command=boot disk
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f124c1,0:a rootmirro
r disk net
use-nvramrc?=true
nvramrc=devalias rootmirror /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f232
61,0:a
security-mode=none
security-password: data not available.
security-#badlogins=0
fcode-debug?=false
diag-out-console=false
post-trigger=error-reset power-on-reset
diag-script=normal
diag-level=min
diag-switch?=false
obdiag-trigger=error-reset power-on-reset
error-reset-recovery=boot

Hello,
Sun Fire 480R ?
Maybe Fire v480 ?
This is device path for the two internal disks (per InfoDoc 21216):
Disk 1 /pci@9,600000/SUNW,qlc@2/fp@0,0
Disk 2 /pci@9,600000/SUNW,qlc@2/fp@1,0
These are your current settings in the OBP
boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f124c1,0:a rootmirror disk net
nvramrc=devalias rootmirror /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f23261,0:a
Both point the the same first slot (location in the fc-al backplane), but use different WWNs.
Use show-disks to display the available disks and re-assign the boot-device accordingly.
Michael
P.S.: I just noticed that you never provided feedback in previous posts.

My macbook won't start up i have used the option command p r while holding down power button but not done.. please help guys

my macbook won't start up i have used the option command p r while holding down power button but not done.. please help guys

It not polite to repost asking fro more help three minutes after initial post.
Recovery mode is Command & R keys after depressing and releasing the Power button for a normal startup.
OS X: About OS X Recovery - Apple Support
That only works for Lion and later.
What exactly happens when your try to boot to Recovery?
Try starting in Safe Mode resetting the SMC and NVRAM/PRAM
OS X: What is Safe Boot, Safe Mode?
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
What model MacBook Pro and what OSX version was on the Mac?
Have you tried booting from an OSX install DVD?
When you try to start doe the Power light light?
This is the Mac Pro desktop forum. I requested your post be moved to the MacBook Pro laptop forum.

Help with broken? macbook. Boot commands dont work.

I have an old macbook that is from late 2008 and is kinda old. First time it did 3 beeps (ram error) So i exchanged the ram and now it starts. But i get stuck at greyscreen, and sometimes at a flashing folder with a Question mark.
I did try to go through the community here but i cant use any of the commands people are recommending..
Command + Alt + R dont work
Alt during boot dont work.
Command + alt wont work... No commands do anything except leaving a blank screen and a cursor.
If i dont hold any keys during boot i eventually get the flashing questionmark folder.
Any suggestions?
Can i reinstall it from a USB and how do i do it if i cant use the bootup commands? :S
(The keyboard seems to work so that cant be the issue)
Thanks.

i dont know what the existing OS is.
Cannot help with troubleshooting since you do not know which OS is installed on your comp. If you purchased your MBP from a private party, ask them. Better yet, did the previous owner provide you w/the DVDs that originally came w/the MBP? If not, you purchased a glorified door stop.
If none of the suggestions in the KB Article work out, take the MBP to your local AS or an AASP.
There is nothing more for me to suggest until you determine which OS you are working with and you have possession of the system DVDs that originally came w/the MBP.

Correct Use of Boot Command

Similar Messages

Maybe you are looking for