Hi,
On Sun, 13 Jan 2013 01:36:21 -0500
kpn...@pobox.com wrote:
On Sun, Jan 13, 2013 at 08:09:00AM +0700, Erich Dollansky wrote:
For what is glabel then still good?
It is still useful for partition schemes that don't have labels (eg,
MBR) AND the filesystem used doesn't support labels
On Sun, 13 Jan 2013, kpn...@pobox.com wrote:
On Sun, Jan 13, 2013 at 08:09:00AM +0700, Erich Dollansky wrote:
For what is glabel then still good?
It is still useful for partition schemes that don't have labels (eg, MBR)
AND the filesystem used doesn't support labels itself AND the end of the
On Sun, 13 Jan 2013, Warren Block wrote:
On Sun, 13 Jan 2013, kpn...@pobox.com wrote:
On Sun, Jan 13, 2013 at 08:09:00AM +0700, Erich Dollansky wrote:
For what is glabel then still good?
It is still useful for partition schemes that don't have labels (eg, MBR)
AND the filesystem used
Hi,
in general, I try to create the partitions with gpart, add a label with
glabel and put a filesystem. I think that I am doing something very
simple the wrong way but I cannot see the error.
I try to do it in the following way:
# gpart destroy -F da0
# gpart create -s GPT da0
# gpart add -t
FWIW I could not partition using the FreeBSD 9.0 amd64 install DVD. I
partitioned with the PcBSD 8.2 DVD and then tried to install from 9.0, but it
anyway caused partitioning issues.
After that I partitioned using FreeBSD 8.3, installed 8.3 and then updated to
9.1.
Regards,
Ralf
On Sat, 12 Jan 2013, Erich Dollansky wrote:
in general, I try to create the partitions with gpart, add a label with
glabel and put a filesystem. I think that I am doing something very
simple the wrong way but I cannot see the error.
I try to do it in the following way:
# gpart destroy -F da0
Hi,
On Sat, 12 Jan 2013 09:56:39 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:
On Sat, 12 Jan 2013, Erich Dollansky wrote:
in general, I try to create the partitions with gpart, add a label
with glabel and put a filesystem. I think that I am doing something
very simple the wrong
After instrumenting 'bruteblock' (and accidentally causing auth.log
to explode), I discovered that the ssh.conf file that ships with it won't
work on FreeBSD 6.1 (or at least my copy of it).
The shipped regexp looks for illegal users. But 'sshd' on FreeBSD
6.1 records login
On Mon, Nov 13, 2006 at 09:16:35PM +0100, Erik Norgaard wrote:
Honestly, I wouldn't worry about it: review your config and make some
simple choices to reduce the noise, see this article:
http://www.securityfocus.com/infocus/1876
But I rather thought that was the point of
On Mon, Nov 13, 2006 at 10:10:58AM +0100, Frank Staals wrote:
I had the same 'problem'. As said it's not realy a problem since FreeBSD
will hold just fine if you don't have any rather stupid user + pass
combinations.
While FreeBSD and OpenSSH are very good, I'm not prepared to rely
Leo L. Schwab wrote:
On Mon, Nov 13, 2006 at 09:16:35PM +0100, Erik Norgaard wrote:
Honestly, I wouldn't worry about it: review your config and make some
simple choices to reduce the noise, see this article:
http://www.securityfocus.com/infocus/1876
But I rather thought that was
Erik Norgaard wrote:
Leo L. Schwab wrote:
On Mon, Nov 13, 2006 at 09:16:35PM +0100, Erik Norgaard wrote:
Honestly, I wouldn't worry about it: review your config and make some
simple choices to reduce the noise, see this article:
http://www.securityfocus.com/infocus/1876
But I rather
Peter N. M. Hansteen wrote:
Erik Norgaard [EMAIL PROTECTED] writes:
Honestly, I wouldn't worry about it: review your config and make some
simple choices to reduce the noise, see this article:
One other noise reduction method which is really easy to implement is
to use pf and write arule set
Leo L. Schwab wrote:
I recently installed FreeBSD 6.1 on my gateway. It replaced an
installation of FreeBSD 4.6.8 (fresh install, not an upgrade) on which I had
disabled the SSH server. Since all the bugs in SSH are fixed now ( :-) ), I
thought I'd leave the server on, and am somewhat
On Monday November 13, 2006 at 04:10:58 (AM) Frank Staals wrote:
I had the same 'problem'. As said it's not realy a problem since FreeBSD
will hold just fine if you don't have any rather stupid user + pass
combinations. ( test test or something like that ) Allthough I thought
it was
Leo L. Schwab writes:
A little Googling revealed a couple of potentially useful
tools: 'sshit' and 'bruteblock', both of which notice repeated
login attempts from a given IP address and blackhole it in the
firewall.
There's also denyhosts. I found the configuration
PROTECTED] On Behalf Of Leo L. Schwab
Sent: Monday, November 13, 2006 9:05 AM
To: freebsd-questions@freebsd.org
Subject: Blocking SSH Brute-Force Attacks: What Am I Doing Wrong?
I recently installed FreeBSD 6.1 on my gateway. It replaced an
installation of FreeBSD 4.6.8 (fresh install
On 11/13/06, Gerard Seibert [EMAIL PROTECTED] wrote:
On Monday November 13, 2006 at 04:10:58 (AM) Frank Staals wrote:
I had the same 'problem'. As said it's not realy a problem since FreeBSD
will hold just fine if you don't have any rather stupid user + pass
combinations. ( test test or
Quoting Andy Greenwood [EMAIL PROTECTED]:
On 11/13/06, Gerard Seibert [EMAIL PROTECTED] wrote:
On Monday November 13, 2006 at 04:10:58 (AM) Frank Staals wrote:
I had the same 'problem'. As said it's not realy a problem since FreeBSD
will hold just fine if you don't have any rather stupid
Gerard Seibert wrote:
On Monday November 13, 2006 at 04:10:58 (AM) Frank Staals wrote:
I had the same 'problem'. As said it's not realy a problem since FreeBSD
will hold just fine if you don't have any rather stupid user + pass
combinations. ( test test or something like that ) Allthough
On Monday 13 November 2006 10:11, Frank Staals wrote:
The point is it isn't security through obscurity: as allready pointed
out, FreeBSD sshd can withstand those brute force attacks without much
of a problem so there is no security problem, the only thing is those
brute force attacks are
Leo L. Schwab wrote:
I recently installed FreeBSD 6.1 on my gateway. It replaced an
installation of FreeBSD 4.6.8 (fresh install, not an upgrade) on which I had
disabled the SSH server. Since all the bugs in SSH are fixed now ( :-) ), I
thought I'd leave the server on, and am somewhat
On Mon, Nov 13, 2006 at 12:19:27PM +0600, Bachilo Dmitry wrote:
? ? ?? ??? 13 ?? 2006 12:05 Leo L. Schwab ???(a):
I recently installed FreeBSD 6.1 on my gateway. It replaced an
installation of FreeBSD 4.6.8 (fresh install, not an upgrade) on which I
had disabled
Erik Norgaard [EMAIL PROTECTED] writes:
Honestly, I wouldn't worry about it: review your config and make some
simple choices to reduce the noise, see this article:
One other noise reduction method which is really easy to implement is
to use pf and write arule set which to uses the overload
I recently installed FreeBSD 6.1 on my gateway. It replaced an
installation of FreeBSD 4.6.8 (fresh install, not an upgrade) on which I had
disabled the SSH server. Since all the bugs in SSH are fixed now ( :-) ), I
thought I'd leave the server on, and am somewhat dismayed to discover
В сообщении от Понедельник 13 ноября 2006 12:05 Leo L. Schwab написал(a):
I recently installed FreeBSD 6.1 on my gateway. It replaced an
installation of FreeBSD 4.6.8 (fresh install, not an upgrade) on which I
had disabled the SSH server. Since all the bugs in SSH are fixed now ( :-)
On 29 Jan 2006, at 22:56, Ensel Sharon wrote:
edquota -u -e /mnt/fs1:810:900:81:90 test200
Looks fine. Things to check:
Do any other quotas work?
Is the filesystem mounted with the appropriate quota options?
Do you have QUOTA support in your kernel?
Does /mnt/fs1/quota.user
(edquota man page has no examples)
# edquota -u -e /mnt/fs1:810:900:81:90 test200
#
# quota test200
Disk quotas for user test200 (uid 1002): none
#
#
So I run the edquota command non-iunteractively, and it produces no
errors, and it seems to follow the format specified in the
On Fri, Dec 23, 2005 at 10:07:21PM -0700, Warren Block wrote:
On Fri, 23 Dec 2005, Gary Kline wrote:
Do I need to have the device for USB 2.0 perhaps??
Only in the unlikely event that it's a USB 2 scanner. But I thought you
were kldloading the uscanner module, and here you have it built
Gary Kline wrote:
So far, I've upgraded my second FBSD platform to 5.4. With
# USB support
device uhci# UHCI PCI-USB interface
device ohci# OHCI PCI-USB interface
#device ehci# EHCI PCI-USB interface (USB 2.0)
device usb
On Fri, Dec 23, 2005 at 09:57:04AM +0100, Erik Norgaard wrote:
Gary Kline wrote:
So far, I've upgraded my second FBSD platform to 5.4. With
# USB support
device uhci# UHCI PCI-USB interface
device ohci# OHCI PCI-USB interface
#device
On Thu, 2005-12-22 at 19:12 -0800, Gary Kline wrote:
So far, I've upgraded my second FBSD platform to 5.4. With
# USB support
device uhci# UHCI PCI-USB interface
device ohci# OHCI PCI-USB interface
#device ehci# EHCI
On Fri, 23 Dec 2005, Gary Kline wrote:
Do I need to have the device for USB 2.0 perhaps??
Only in the unlikely event that it's a USB 2 scanner. But I thought you
were kldloading the uscanner module, and here you have it built in the
kernel. Don't do both--although the system shouldn't
So far, I've upgraded my second FBSD platform to 5.4. With
# USB support
device uhci# UHCI PCI-USB interface
device ohci# OHCI PCI-USB interface
#device ehci# EHCI PCI-USB interface (USB 2.0)
device usb #
Nathan Kinkade said...
Here is quick rundown on how you could achieve your goal:
1) Mount the new disk at at /mnt with something like:
# mount /dev/ad1s1a /mnt
2) Copy everything from your original /var partition to the new one:
# cd /var tar cf - ./ | (cd /mnt tar xvpf -)
3)
On Wed, Mar 02, 2005 at 01:42:40AM -0800, Gerald Lightsey wrote:
Nathan Kinkade said...
Here is quick rundown on how you could achieve your goal:
1) Mount the new disk at at /mnt with something like:
# mount /dev/ad1s1a /mnt
2) Copy everything from your original /var partition to
of new
databases within MySQL while drive 1 is mounted on /var shows that the
databases have been created on the original /var on disk 0 as directories
after disk 1 is unmounted.
What am I doing wrong or what don't I understand about a drive being mounted
on /var where data is being written underneath
to a temporary mount point. Also by
experimentation/confirmation I find that simply creating a couple of new
databases within MySQL while drive 1 is mounted on /var shows that the
databases have been created on the original /var on disk 0 as directories
after disk 1 is unmounted.
What am I
within MySQL while drive 1 is mounted on /var shows that the
databases have been created on the original /var on disk 0 as directories
after disk 1 is unmounted.
What am I doing wrong or what don't I understand about a drive being mounted
on /var where data is being written underneath
39 matches
Mail list logo
