Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5240 - fuse install message is wrong

Attached to Project: Arch Linux
Opened by Dale Blount (dale) - Friday, 18 August 2006, 12:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Simo Leone (neotuli)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

installing fuse... done.
==> You must load the fuse kernel module to use FUSE.
-> Run 'modprobe fuse' to load the module now.
-> Add fuse to $MODULES in /etc/rc.conf to load on every boot.
==> You will need a /dev/fuse device node to use FUSE.
-> If you use udev, run 'udevstart' to re-populate /dev.

"udevstart" doesn't exist any longer.
my /dev/fuse was also created automatically, so the point may be moot.

This task depends upon

Closed by  Simo Leone (neotuli)
Sunday, 24 September 2006, 18:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  I checked it into cvs but I don't think it's worth rebuilding fuse over, so it'll get cycled in on the next update.

As for sshfs... it works here.
Comment by Dale Blount (dale) - Friday, 18 August 2006, 13:36 GMT
also, i can't seem to get sshfs working, let me know if you want a separate bug for that.
Comment by Simo Leone (neotuli) - Friday, 18 August 2006, 14:27 GMT
(would you believe I forgot fuse is my package?)

I'll take a look.
Comment by Roman Kyrylych (Romashka) - Monday, 21 August 2006, 07:31 GMT
> also, i can't seem to get sshfs working, let me know if you want a separate bug for that.
I had no problems with fuse and sshfs. I didn't use them 2 months but IIRC they weren't updated anyway.
What problems do you have with sshfs?
Comment by Dale Blount (dale) - Monday, 21 August 2006, 12:07 GMT
usage: sshfs [user@]host:[dir] mountpoint [options]

[dale@dale ~]$ ssh root@server /home/dale/sshfs-mnt/server/
root@server's password:
bash: /home/dale/sshfs-mnt/server/: No such file or directory

even though it exists. relative paths don't work either.
Comment by Roman Kyrylych (Romashka) - Monday, 21 August 2006, 12:44 GMT
Why do you use ssh???

mount sshfs#root@alpha:/var/cache/pacman/pkg/ /var/cache/pacman/pkg
Comment by Dale Blount (dale) - Monday, 21 August 2006, 12:49 GMT
[root@dale dale]# mount sshfs#root@server:/path/on/server sshfs-mnt/server/
mount: can't get address for sshfs#root@server
Comment by Roman Kyrylych (Romashka) - Monday, 21 August 2006, 13:25 GMT
mount -t fuse ...
or
sshfs root@alpha:/var/cache/pacman/pkg/ /var/cache/pacman/pkg
Comment by Dale Blount (dale) - Monday, 21 August 2006, 13:59 GMT
the "mount -t fuse" one works, but the sshfs command one doesn't seem to (see 4 posts up).
Comment by Roman Kyrylych (Romashka) - Monday, 21 August 2006, 19:24 GMT
Ooops... I read there ssh and didn't understand that it was a typo. :-)
BTW why sshfs depends on pkgconfig? Shouldn't pkgconfig be in makedepends?
We flooded this bug report with slightly offtopic comments already. :-)

Loading...