SUMMARY: Running devlinks
2007-12-24 19:20:00
them explained that you can rerun devlinks, the process is:
drvconfig
devlinks
With a new device, you should proceed this with add_drv command. Several
people mentioned the tapes command, but the (newer) add_drv command calls
tapes, disks, and ports as appropriate for you. Several people also put in
appropriate cautions about making changes like this on production systems.
However the post that helped me with my problem, was from David Evans:
> From: David Evans [mailto:David.J.Evans at oracle.com]
> Sent: Thursday, February 01, 2001 5:02 PM
> To: BAUMLER Julie L
> Subject: Re: Running devlinks
>
>
>
> Your probably missing the the special file under /devices. Depending
> on how the driver was written you may be able to load it by hand
> using modload, then the devices command may work and then devlink
> should work. But since your dealing with the kernel be careful. If the
> code isn't clean your machine will stop.
>
> The devices command may fail if the driver and system aren't talking
> properly. This happens a lot with third party drivers.
>
> And any of these commands can bring down the machine if the driver
> has any problems. It may not bring the machine down but you should be
> prepared for worst case.
>
> David
> All of the statements and opinions expressed here are my own,
> and do not necessarily represent those of Oracle Corporation.
The special file was missing from devices and we seem to have some other
problems with the driver. We're looking at some other ways to get what we
want done, so I haven't investigated further.
Thanks to Sandy Gordon, David Evans, Vinnie German, Thomas Wardman,
Frederick Hall, and Clifford Thurber.
> -----Original Message-----
> From: BAUMLER Julie L
> Sent: Thursday, February 01, 2001 4:17 PM
> To: 'codeprof at codeprof.com'
> Subject: Running devlinks
>
>
> Hello -
>
> We added a new device driver (sst from the amanda source) to
> our system,
> edited /etc/devlink.tab and did a reconfiguration reboot.
> Due to a typo in
> our /etc/devlink.tab; devlinks skipped that entry and the new
> /dev entry was
> not created. We found and fixed the typo; but cannot
> schedule the downtime
> to reboot again so that devlinks will run. From the devlinks
> man page, it
> appears that since drvconfig was just run, we should be able
> to run devlinks
> by hand - however, neither devlinks or devlinks -t
> /etc/devlink.tab causes
> the /dev entry to be created. devlinks does not issue an
> error message. We
> know the driver is there because rerunning add_drv results in
> a message that
> the driver is already installed. This system is running
> Solaris 7 on an
> E450.
>
> Thanks,
> Julie
>
> -------------------------------------
> Julie L Baumler
> Sr System Administrator Multnomah Co ISD
> 503-988-3749 X26909
> julie.x.baumler at co.multnomah.or.us
> _______________________________________________
> codeprof mailing list
> codeprof at codeprof.com
> http://www.codeprof.com/execute/ask/?codeinfoid=1631
>
Comments
Got something to say?
You must be logged in to post a comment.
