The duplication of /filz is because I accidentally tripple-clicked. That doesn't normally happen. My bad.

Anyway, those partitions also have labels in /dev, with names like ad0s1. I attempted to mount the WinXP partition by mounting /dev/ad0s1 to a prepared mount point, but it failed. In fact, the only place I can mount these partitions is in the /media directory, according to the whim of fuse.

Simply put, I would rather mount these partitions the old-fashioned way, with either a mount command or the fstab. I do not want to be restricted to fuse. Furthermore, fuse only appears to work in conjunction with Dolphin, and I generally prefer to use a lighter-weight file cruncher like xfe or Midnight Commander. Dolphin is effective and nice looking, but personally I prefer a simpler display.

Can anyone give me any pointers on how to, essentially, bypass or override fuse?

As I've said elsewhere, and if it matters, my computer is running PC-BSD 8.2, which is essentially FreeBSD 8.2 with some added bells and whistles. And I'm beginning to find some of those bells and whistles annoying...

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

I just installed virtualbox-4.0.6-amd64.pbi and I'm now running Vista, Windows-7 (32) and (64). Is your mounting method about doing the same thing but in a more manual way?

Nothing is perfect, but PcBSD is darn close compared to the rest. I don't like Explorer (KDE). I simply PBI a GNOME install and PcBSD do the rest. No tutor tells you about the 5000 GNOME dependency and to install xWINDOWS anymore. It makes me feel it's All-In-One until I get stuipt enough to try again behind those words .. And I did twice back when it was really hard

It would be nice to find information on how to turn something off, but not many are saying or even know. Anyway, I think these are the best place to start ... From another BSD install, I did it so I can log-in as root to get some things dones in PcBSD. Go to around line (200).

ee /usr/local/kde4/share/config/kdm/kdmrc

/etc/rc.conf

... than work with the boot loader.conf I guest. KDE is pretty but real men use GNONE!

To Nilsgecko and Sharris:
PC-BSD is far from perfect, but my collective experience with it has been good. When I first installed it, my experience with BSD was minimal, but PC-BSD allowed me to get a BSD system up and running quickly, and it took most of the guesswork out of instillation. With a system that has a lot of mixed components (like mine), that can be a very big deal. Once the system was running, I was then able to examine the FreeBSD system at my own pace, and customize it as I choose. One of FreeBSD's biggest selling points is the ability to extensively customize it. In PC-BSD, you can still do that, but I suspect it takes a little longer because you have to bypass the added value stuff before you can access the guts of the system. But once you're there, FreeBSD's array of options are easily available. Furthermore, should you ever need to use some of the fancy-schmancy tools that come with PC-BSD, like the PBI framework, they are still available when you need them. It's a real win/win.

My own system started out as a shake-the-box PC-BSD 8.2 system, complete with KDE 4.2.1. (Yuch!) Now, it's running all kinds of software from the ports tree, and I generally use one of the "classic" x-window managers, Window Maker. This fuse business is just the latest alteration I've attempted. If someone from the PC-BSD team were to look at my system, they may not recognize it as running their product.

If the aim of PC-BSD is to get more people to try and use FreeBSD, then I think it's working. It worked on me.

I found a script template, and ran with it. This is new to me, so I only half know what I'm doing. For all I know, I may still be going about this the wrong way.

One thing I have done is enable fusefs in rc.conf. I saw a notice of this in the startup scroll, but I still can't mount the internal partitions. Still, I like to think I'm a step closer. I suspect that since fusefs wasn't enabled in rc.conf, it was somehow tied to the Dolphin file manager. If that's the case, then I'll have to make sure that fuse is running separately from Dolphin at all times. Does Dolphin have configuration scripts of it's own? If so, then I'll be paying them a visit. Baby steps...

I tried this, and unfortunately, it doesn't work. The result I get is:

Code:

ntfs-3g /dev/ad0s1 /mnt
fuse: failed to open fuse device: No such file or directory

Do You have fusefs_enable=YES in /etc/rc.conf file?

Code:

% grep fuse /etc/rc.conf
fusefs_enable=YES

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick

__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick

Just noticed your using PC-BSD, although "essentially" it is FreeBSD, I believe they do modify somethings. I'm not sure where you got the /dev/fuse devices as I have not seen these and being that it worked in one directory and not another leads me to believe it to be something modified by PC-BSD.

But, I have none of that and I'm using just freebsd and fuse for some years now and it works fine.

__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick