HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: how to associate one physical device to one bl...
Operating System - Linux
1827862
Members
1797
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2003 09:16 PM
04-16-2003 09:16 PM
yes, I know such as:
mknod -m 660 /dev/ram b 1 1
can make up one block file, but, how it can associate to the designated device, or call locate the driver program? for example, if i want to create /dev/fla what link to one flash-memory, how mknod can know it should use the flash card driver for /dev/fla?
apprecate for your helps in advance.
Best Regards,
Frederick
mknod -m 660 /dev/ram b 1 1
can make up one block file, but, how it can associate to the designated device, or call locate the driver program? for example, if i want to create /dev/fla what link to one flash-memory, how mknod can know it should use the flash card driver for /dev/fla?
apprecate for your helps in advance.
Best Regards,
Frederick
frederick van targero
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2003 09:52 PM
04-16-2003 09:52 PM
Solution
Hi Frederick.
The actual device filename doesn't matter so much, but it depends on the applicaitons. If you can tell your application which device file to use, it's not a problem to name it the way you want.
The driver doesn't care about the filename, it only needs to know the major and minor number of the device (those are the numbers that you specify at the end of the mknod command).
So you can create a device /tmp/foo and use it to happily mount your flash device, as long as the major and minor numbers correctly correspond to it (i.e. it should be the same as sda1 in most cases).
Hope this helps,
Goran
The actual device filename doesn't matter so much, but it depends on the applicaitons. If you can tell your application which device file to use, it's not a problem to name it the way you want.
The driver doesn't care about the filename, it only needs to know the major and minor number of the device (those are the numbers that you specify at the end of the mknod command).
So you can create a device /tmp/foo and use it to happily mount your flash device, as long as the major and minor numbers correctly correspond to it (i.e. it should be the same as sda1 in most cases).
Hope this helps,
Goran
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP