>Is there a way that I can use BBEdit as the editor even for my ubuntu
>server files just like I use it on my local machine?
The combination of [MacFuse][1] and [MacFusion][2] does the job for me.
I mount all my remote file systems via SSH and edit files on said
file systems with BBEdit, as if the files were local.
My only caveat: I prefer not to leave .DS_Store files scattered
through a remote system and, by default, the Finder writes .DS_Store
files to any mounted file system. To turn that off for
network-mounted volumes run the following command in Terminal.app:
$ defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool YES
Regards,
Brian Forte.
[1]: <http://code.google.com/p/macfuse/>
[2]: <http://macfusionapp.org/>
--
words, edits, type, layout, code
<mailto:bfo...@betweenborders.com>
<http://betweenborders.com/>
I'm doing it regularly.
ftp works and is supported by Bare Bones. You need to enable an ftp
server on ubuntu.
Actually, though, I prefer scp with the ssh protocol. I have set up
an ssh certificate with a public key that makes the connection with
no passwords required. I use a bbedit worksheet on the Mac where I
keep prepared scp command lines for each direction with a bbedit tool
command between them.
Execute the top two and I quickly get a working copy on the Mac. Save
from bbedit and execute the third and it's all back in ubuntu - or
BSD on any server that lets me have a user account.
I'm getting fairly close to being able to connect a bbedit worksheet
on a Mac so that it uses a shell on the ubuntu machine. I can do it
with ubuntu's gedit but not, yet, with bbedit.
And yes. I'm on ubuntu 8 but it all started with 7.
--
--> Life begins at ovulation. Ladies should endeavor to get every
young life fertilized. <--
OK, I, for one. would like a lot more details on exactly how this
works. I'd love to be able to mount my remote FreeBSD machine over
SSH and have it look like a local volume. I looked up MacFUSE, but it
looked like something other than what you described.
"MacFUSE implements a mechanism that makes it possible to implement a
fully functional file system in a user-space program on Mac OS X."
What?
And I assume you are having to add 'PermitRootLogin nopwd' to /etc/
sshd_config on the target machines?
--
Dinosaurs are attacking! Throw a barrel!
On 4/02/09 at 1:02 PM -0700, Lewis@Gmail wrote:
>"MacFUSE implements a mechanism that makes it possible to
>implement a fully functional file system in a user-space
>program on Mac OS X."
>
>What?
You want to add the 'ssh' file system. That will allow the
remote server to appear as a local volume (file system).
>And I assume you are having to add 'PermitRootLogin nopwd' to
>/etc/ sshd_config on the target machines?
NO, Don't do that!
You want to set up PubkeyAuthentication. There should be plenty
of howtos available via Google.
Charlie
--
Charlie Garrison <garr...@zeta.org.au>
PO Box 141, Windsor, NSW 2756, Australia
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
http://www.ietf.org/rfc/rfc1855.txt
As I understand it, PermitRootLogin nopwd is suppose to allow root
access ONLY with a key exchange.
<http://www.ssh.com/support/documentation/online/ssh/adminguide/32/Configuring_Root_Logins.html
>
> You can limit the authentication methods by using the following
> setting:
>
> PermitRootLogin nopwd
>
> This allows root logins only when an authentication method other
> than password is used.
however, on my FreeBSD install it requires
PermitRootLogin without-password
instead.
--
How do you feel? I'm lonely
What do you think? Cant take it all
Whatcha gonna do? Gonna live my life
On 4/02/09 at 7:43 PM -0700, Lewis@Gmail <gkr...@gmail.com> wrote:
>As I understand it, PermitRootLogin nopwd is suppose to allow
>root access ONLY with a key exchange.
I was probably confusing it with a different option then. Main
point I was making is to be very careful about allowing root
access via ssh of any sort.
I turn off password auth for all users anyway on servers I
manage; so I don't have to give special consideration to root
user. Hmm, after checking it seems as though most of my servers
don't allow root login so not an issue.
Of course the ssh FUSE works best when not restricted to a
single non-privileged user. So it's the standard security vs
convenience argument.
It's interesting running this (yes, I finally managed to figure it all
out). On the one hand, it is really neat being able to use bbedit to
adit all my server config files; on the other hand it is weird when I
am missing a command line tool I'm used to having in a SSH session.
But yeah, I think I can get used to this.
Thanks for the info.
--
If we get through this alive I'll meet you next week same place
same time