Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
megamaced said:Why would somebody want to hack a website that belongs to an open source, Linux distribition?
It's just pointless...
smb://192.168.1.xxx/share
Not neccessarily a hack, maybe they're just having database problems, maybe the connection to the database isn't set properly, maybe the config isn't right, who knows.megamaced said:Not getting any better for the poor guys over at Vector. They got the website back late last night, but I tried to access it this morning and now all it says is:
'Unable to select database'
Two hacks in 2 days? :eek:
Someone must really have it in for them!
I'm still trying to figure out why you're using Windows file & print sharing to share files with another *nix. You should be using NFS for this purpose, as it's faster with less overhead.megamaced said:It's quite annoying because I am trying to get help on their forums! Samba doesn't seem to be working properly. I am sharing a folder on my Ubuntu machine with Samba, but when I try to access it on Vector it just says 'unknown location'!
That depends, are you trying to browse the SMB share with Konqueror? If so, try smb://xxx.xxx.xxx.xxx/ --OR-- smb://$NETBIOSNAME/megamaced said:Just to be sure, what is the correct syntax for a samba address? Is itCode:smb://192.168.1.xxx/share
Anti-Trend said:I'm still trying to figure out why you're using Windows file & print sharing to share files with another *nix. You should be using NFS for this purpose, as it's faster with less overhead.
NFS is mounted like any other data volume in your /etc/fstab. Here's some documentation to help you get started, in both basic and extensive flavors. :)megamaced said:What is the correct syntax for an NFS share?
/home/common 192.168.25.0/255.255.255.0(rw,async,all_squash,anonuid=1000,anongid=1000)
/home/incoming 192.168.25.0/255.255.255.0(rw,async,all_squash,anonuid=1000,anongid=1000)
/home/antitrend 192.168.25.101(rw,async,all_squash,anonuid=500,anongid=500)
/home/somebody_else 192.168.25.100(rw,async,all_squash,anonuid=501,anongid=501)
192.168.25.5:/home/common /mnt/server/common nfs rsize=8192,wsize=8192,nosuid,soft 0 0
192.168.25.5:/home/incoming /mnt/server/incoming nfs rsize=8192,wsize=8192,nosuid,soft 0 0
192.168.25.5:/home/antitrend /home/antitrend/remote nfs rsize=8192,wsize=8192,nosuid,soft,user 0 0
AT said:Code:anonuid=1000,anongid=1000
Good job. :)megamaced said:It's all up and running now :)
The quota daemon can enforce user's disc space quotas on your system. This is so on shared resources, one user can't fill up the entire partition and leave none for everyone else. You really don't need this in a single-user environment.megamaced said:... there is one service that I couldn't start called 'rpc.rquotad'. I don't know whether this is supposed to come with the nfs-utils package or not, but I can't find it in /sbin or /usr/sbin. What does it do and do I actually need it? As I said before, I am able to share files as it is.
Yes, my user mapping on my local machines are different from that on my server, so I use that to force the correct UID. "all_squash" disregards the UID on the client machine, forcing them to connect anonymously, and the "anonuid" and "anongid" entries specify what I want the anonymous user and group ID's to be. Make sense? As for the "async" entry, that makes it perform faster.megamaced said:I assume this means that only the user who's ID is 1000 can use this service?
megamaced said:Why would somebody want to hack a website that belongs to an open source, Linux distribition?
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL
On a 100MiB network, I've found 8192 works very well for both.megamaced said:Just two more things I need to know :)
The 'rsize' and 'wsize' options increase the buffer and improve network performance? What do you think a good size would be for a standard 100Mb/s network?
I'm not paranoid about my security because I setup my network with security in mind. In so far as the hosts.deny goes, it looks good. That being said, you need just about every one of those services to be reachable by your NFS clients. On any machines which are sharing files via NFS, you should have an entry in the hosts.allow for each of your machines which will connect as clients.megamaced said:Also, what security measures have you taken to protect your network?
Hehe, don't get the wrong end of the stick - I am not testing the water, so to speak ;) I would like to know so I can take similiar steps.
I've set up a firewall on all machines, and I've edited the 'hosts.allow' to accept only the IP addresses of my machines. I have also edited the 'hosts.deny' file to include:
Code:portmap:ALL lockd:ALL mountd:ALL rquotad:ALL statd:ALL
Why would somebody want to hack a website that belongs to an open source, Linux distribition?
It's just pointless...