#1983 closed bug (invalid)
npipefs: could not resolve symbol 'new_lock'
| Reported by: | thorn | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | File Systems | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
Haiku hrev24635 from serial log
KDiskDeviceManager::_AddDiskSystem() done: No error "/boot/home/config/add-ons/kernel/file_systems/npipefs": could not resolve symbol 'new_lock' Could not load kernel add-on "/boot/home/config/add-ons/kernel/file_systems/npipefs": Symbol not found load_module_image(/boot/home/config/add-ons/kernel/file_systems/npipefs) failed: Symbol not found
Change History (3)
comment:1 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 by , 17 years ago
Replying to thorn:
i see, it's come from 'official' subversion package.
Yep, but that's the official BeOS package.
Note:
See TracTickets
for help on using tickets.
The lock API in the BeOS kernel is private. BeOS file systems cannot be used in Haiku. The npipefs provides no additional value over the Haiku pipefs implementation, anyway.