Sponsored Content
Full Discussion: SPARC and device drivers
Operating Systems Solaris SPARC and device drivers Post 302487384 by orange47 on Wednesday 12th of January 2011 09:34:44 AM
Old 01-12-2011
@jlliagre
OK, thank you, I'll try that.

Just a thought.. Would it be possible to simply remove it manually with rm ?
(I'm worried a bit that devfsadm might delete some other dev that is essential)
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

View device drivers?

I might sound stupid for asking, but could someone please tell me how to view all the device drivers? I'm just starting to use UNIX after using Windows for years. Thanks. -sysop0130 (1 Reply)
Discussion started by: sysop0130
1 Replies

2. Programming

Linux Device Drivers

Here is a cool book. And the price is right! Linux Device Drivers, 2nd Edition (0 Replies)
Discussion started by: Perderabo
0 Replies

3. Windows & DOS: Issues & Discussions

Are Your Device Drivers Wacked Or Hacked?

Suggestion. Besides running scans it is also a good thing to run "sigverif". This will create a list of ALL drivers on your system, signed and unsigned. The output is located in your C:Windowssigverif.txt file. It surprised me most people do not do this. Many trojans mask themselves as... (0 Replies)
Discussion started by: ZOverLord
0 Replies

4. UNIX for Dummies Questions & Answers

drivers unix 5.01 is compatible with drivers epson fx-2190

Please, I'm From Argentina, And I Need To Know If The Drivers Of Program Unix, Version 5.01 Is Compatible Whit Drivers Of The Printer Epson Fx-2190 Thanks, And I Hope Yuor Answer. (0 Replies)
Discussion started by: juan alberghina
0 Replies

5. Solaris

writing device drivers,for a beginner!!!

Hi all, Please excuse me if this is not the right forum to ask my question. I would like to know more about writing device drivers for Unix,particularly Solaris 10. excuse me if am being vague, but I have absolutely no idea about how i can start. I did try to search for a beginners guide to... (1 Reply)
Discussion started by: wrapster
1 Replies

6. Programming

linux device drivers

hi, this is manju .... i want linux device drivers source codes. pls help me (2 Replies)
Discussion started by: miraclemanju
2 Replies

7. UNIX for Advanced & Expert Users

Learn Linux File System and Device Drivers

I am to start working on two project on Linux Device Drivers and other on File System. So I got the book "Understanding Linux Kernel" by Daniel and Marco. But I am confused as how to proce Will anybody pls let me know how to go to about studying the chapter in this book? I mean the order in... (1 Reply)
Discussion started by: shefalibv
1 Replies

8. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

9. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

10. UNIX for Beginners Questions & Answers

Configuring NIC device in Solaris 9 SPARC OS [QEMU]

I have Xubuntu 18.04 installed on my PC. I have created a 10G .img image file created by QEMU-IMG. I have installed inside of it Solaris 9 SPARC edition . If I try and mount the image file as a loop device (using sudo losetup /dev/loop0 /path-to-img-file) I can only mount it as read only. ... (1 Reply)
Discussion started by: alphatron150
1 Replies
devfsadm(1M)						  System Administration Commands					      devfsadm(1M)

NAME
devfsadm, devfsadmd - administration command for /dev SYNOPSIS
/usr/sbin/devfsadm [-C] [-c device_class] [-i driver_name] [ -n] [-r root_dir] [-s] [-t table_file] [-v] /usr/lib/devfsadm/devfsadmd DESCRIPTION
devfsadm(1M) maintains the /dev namespace. It replaces the previous suite of devfs administration tools including drvconfig(1M), disks(1M), tapes(1M), ports(1M), audlinks(1M), and devlinks(1M). The default operation is to attempt to load every driver in the system and attach to all possible device instances. Next, devfsadm creates logical links to device nodes in /dev and /devices and loads the device policy. devfsadmd(1M) is the daemon version of devfsadm(1M). The daemon is started during system startup and is responsible for handling both reconfiguration boot processing and updating /dev and /devices in response to dynamic reconfiguration event notifications from the kernel. For compatibility purposes, drvconfig(1M), disks(1M), tapes(1M), ports(1M), audlinks(1M), and devlinks(1M) are implemented as links to devfsadm. In addition to managing /dev, devfsadm also maintains the path_to_inst(4) database. OPTIONS
The following options are supported: -C Cleanup mode. Prompt devfsadm to cleanup dangling /dev links that are not normally removed. If the -c option is also used, devfsadm only cleans up for the listed devices' classes. -c device_class Restrict operations to devices of class device_class. Solaris defines the following values for device_class: disk, tape, port, audio, and pseudo. This option might be specified more than once to specify multiple device classes. -i driver_name Configure only the devices for the named driver, driver_name. -n Do not attempt to load drivers or add new nodes to the kernel device tree. -s Suppress any changes to /dev. This is useful with the -v option for debugging. -t table_file Read an alternate devlink.tab file. devfsadm normally reads /etc/devlink.tab. -r root_dir Presume that the /dev directory trees are found under root_dir, not directly under root (/). No other use or assumptions are made about root_dir. -v Print changes to /dev in verbose mode. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. FILES
/devices device nodes directory /dev logical symbolic links to /devices /usr/lib/devfsadm/devfsadmd devfsadm daemon /dev/.devfsadm_dev.lock update lock file /dev/.devfsadm_daemon.lock daemon lock file /etc/security/device_policy device policy file /etc/security/extra_privs additional device privileges ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), add_drv(1M), modinfo(1M), modload(1M), modunload(1M), rem_drv(1M), svcadm(1M), tapes(1M), path_to_inst(4), attributes(5), privi- leges(5), smf(5), devfs(7FS) NOTES
This document does not constitute an API. The /devices directory might not exist or might have different contents or interpretations in a future release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API. devfsadm no longer manages the /devices name space. See devfs(7FS). The device configuration service is managed by the service management facility, smf(5), under the service identifier: svc:/system/device/local:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 6 Aug 2004 devfsadm(1M)
All times are GMT -4. The time now is 01:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy