#8847 closed bug (invalid)
net_server won't run as it should
Reported by: | modeenf | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Servers/net_server | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
You can't have a link in /boot/system/add-ons/kernel/network/protocols/ pointing to a second partition ;)
I was hoping to have links to all Bluetooth stuff, but l2cap in protocols won't work, probably as the partition are loaded after and some how the net_server won't run as it should. Restarting net_server made it work as it should.
net_server won't show any network devices but they are loaded id you look in /dev/net
Perhaps a broken link in /boot/system/add-ons/kernel/network/protocols/ should be ignored not breake the system ;)
Change History (3)
comment:1 by , 12 years ago
Version: | R1/alpha3 → R1/Development |
---|
comment:2 by , 12 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 by , 12 years ago
I only made the l2cap protocol symlink all other protocol's where as they chould. So removing l2cap protocol symlink made the network work agin.
Now if net_server where to handle that symlink without to tell me of the problem, I would probably never find the problem with Bluetooth that would exist if not l2cap was loaded.
Keep it this for now.. :)
If your protocols are on that (not yet mounted) partition, there is nothing that can be done about it. You cannot get a working network out of it, as core components are missing.
The only way out would be to check if the link becomes valid after a volume has been mounted, but frankly, I don't see the point, especially with package management around the corner which makes /system/ read-only as it should.
Instead of moving all protocols to another partition, you could just add a symlink to the Bluetooth stuff.