Sponsored Content
Operating Systems Solaris Solaris I386 ifconfig devices ?? Post 302140840 by sysgate on Tuesday 16th of October 2007 10:16:31 AM
Old 10-16-2007
Code:
dmesg | grep -i "link up"

most likely you will see :
Quote:
Aug 20 10:46:25 host-name bge: [ID 801593 kern.notice] NOTICE: bge0: link up 1000Mbps Full-Duplex
where bge0 is the name of the interface.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris 8 on a i386

Hi, I am trying to installing solaris on a intel PC, but I am unable to do it. So my question is where can I find some good documents (I tried sun.com did not find any thing). If I want to dual boot between Linux and Solaris, would I install solaris first if so why? Thanks alot ... (5 Replies)
Discussion started by: chamkila
5 Replies

2. Solaris

devices in solaris 10

i want to use the devfsadm command and understand its function (3 Replies)
Discussion started by: bondoq
3 Replies

3. UNIX for Dummies Questions & Answers

Solaris print devices

I've been looking in my /dev directory for my available devices to set up a printer and was expecting to see some lp or lpr devices using Solaris 8, but I do not see them so I'm a little confused? Any help would be greatly appreciated. (2 Replies)
Discussion started by: jroglass
2 Replies

4. Solaris

Solaris 10 question on ifconfig

On prior versions to solaris 10 when I want to add/change the IP address of an interface I will use this command. ifconfig eri0 down ifconfig eri0 192.xxx.xxx.xxx netmask 255.xxx.xxx.xxx up then change /etc/hosts so that /etc/hostname.eri0 picks up on the correct IP. I strange thing... (2 Replies)
Discussion started by: sparcguy
2 Replies

5. Solaris

solaris way if interpreting devices?

Hi all, I wanted to know the solaris way of interpreting devices? I mean i understand all those c0t0....stuff but when i start mounting devices , most of the times i get either a I/O error or it says that the directory does not exist. eg: I have a external usb hub to which i have connected... (1 Reply)
Discussion started by: wrapster
1 Replies

6. Solaris

good tripwire policy for Solaris sparc and i386

I haven't found a good resource for this. Does anyone have a good resource for this? I've compiled the code, and all I have is an old twpol.txt from solaris 8.. :-( (0 Replies)
Discussion started by: biea
0 Replies

7. Solaris

solaris I/O devices info

Hi, can anyone help in finding the hardware related details of I/O devices of remote solaris machine .Thanks in advance. (7 Replies)
Discussion started by: pratheepv
7 Replies

8. Solaris

Solaris zone devices

Hello all, I'm having issue with trying to add device resource to my zone from the global zone. I did the following zoncfg -x larryase add device set match="/dev/tty*" end I get device already set, but in me zone I don't see the device. Is there a "reboot -- r" command for zones? or... (0 Replies)
Discussion started by: larryase
0 Replies

9. Solaris

Not showing n/w interface name in Solaris with ifconfig -a

hi frineds in sunfire 6800 server for one domain when ever i am giving ifconfig -a interface names like hme0,hme1.......are not showing.Actually in the server hme0,hme1,qfe are showing .when i was tried with the cat /etc/path_to_intstshowing tphysical interfcace names . after giving the... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies

10. Solaris

Ethereal Solaris i386

Hello guys, I am trying to install ethereal in Solaris10 based on i386 system. But i can find only packet for sparc. Any idea? Thanks a lot! (2 Replies)
Discussion started by: @dagio
2 Replies
deallocate(1)                                                                                                                        deallocate(1)

NAME
deallocate - device deallocation SYNOPSIS
deallocate [-s] device deallocate [-s] [-F] device deallocate [-s] -I The deallocate utility deallocates a device allocated to the evoking user. device can be a device defined in device_allocate(4) or one of the device special files associated with the device. It resets the ownership and the permission on all device special files associated with device, disabling the user's access to that device. This option can be used by an authorized user to remove access to the device by another user. The required authorization is solaris.device.allocate. When deallocation or forced deallocation is performed, the appropriate device cleaning program is executed, based on the contents of device_allocate(4). These cleaning programs are normally stored in /etc/security/lib. The following options are supported: device Deallocate the device associated with the device special file specified by device. -s Silent. Suppresses any diagnostic output. -F device Forces deallocation of the device associated with the file specified by device. Only a user with the solaris.device.revoke authorization is permitted to use this option. -I Forces deallocation of all allocatable devices. Only a user with the solaris.device.revoke authorization is permitted to use this option. This option should only be used at system initialization. The following exit values are returned: non--zero An error occurred. /etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /etc/security/lib/* See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ allocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. 28 Mar 2005 deallocate(1)
All times are GMT -4. The time now is 06:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy