filesystem
use.
My situation: install a fileserver (samba) for 3 clients and put it as
gateway/server on internet (ssh, and samba to internal lan).
I installed FreeBSD with raid 1 following this howto:
http://www.ateamsystems.com/blog/Installing-FreeBSD-9-gmirror-GPT-partitions-raid-1
Hi all and sorry for this (newbie) question.
I study FreeBSD (I come from linux) and I'm not sure which filesystem use.
My situation: install a fileserver (samba) for 3 clients and put it as
gateway/server on internet (ssh, and samba to internal lan).
I installed FreeBSD with raid 1 following
On Tue, May 21, 2013 at 06:43:25PM +0200, Pol Hallen wrote:
Hi all and sorry for this (newbie) question.
I study FreeBSD (I come from linux) and I'm not sure which filesystem use.
My situation: install a fileserver (samba) for 3 clients and put it as
gateway/server on internet (ssh
On Tue, Dec 4, 2012 at 4:50 PM, Rick Miller vmil...@hostileadmin.com wrote:
Hi all,
I remember one time seeing a site that explained why soft-updates was
not enabled for the root filesystem. I tried looking for it earlier,
but failed to locate it. Is there someone who knows where
Hi all,
I remember one time seeing a site that explained why soft-updates was
not enabled for the root filesystem. I tried looking for it earlier,
but failed to locate it. Is there someone who knows where it is?
--
Rick
--
Sent from my mobile device
Take care
Rick Miller
On 12/04/12 22:50, Rick Miller wrote:
Hi all,
I remember one time seeing a site that explained why soft-updates was
not enabled for the root filesystem. I tried looking for it earlier,
but failed to locate it. Is there someone who knows where it is?
--
Rick
Hi Rick
Maybe in the FAQ? http
On Tue, 4 Dec 2012 16:50:42 -0500
Rick Miller vmil...@hostileadmin.com wrote:
Hi all,
I remember one time seeing a site that explained why soft-updates was
not enabled for the root filesystem. I tried looking for it earlier,
but failed to locate it. Is there someone who knows where
Hello,
are the remarks given for the -m option in tunefs(8) and newfs(8) still the same for very large
filesystems, or the free-space margin might be safely reduced in these cases?
For instance, when I have a 12TB filesystem then the default 8% margin gets close to the value of
1TB, which
From owner-freebsd-questi...@freebsd.org Fri Nov 23 09:31:00 2012
Date: Fri, 23 Nov 2012 16:27:23 +0100
From: Ireneusz Pluta ipl...@wp.pl
To: freebsd-questions@freebsd.org
Subject: newfs -m for large filesystem
Hello,
are the remarks given for the -m option in tunefs(8) and newfs(8
, when the filesystem is labelled and mounted, it is
slightly over 1TB in size. Am I correct in assuming that it's only
1TB because the disk geometry is greater than what is supported by
sysinstall and/or bsdlabel?
--
Take care
Rick Miller
___
freebsd
that uses the entire
disk. However, when the filesystem is labelled and mounted, it is
slightly over 1TB in size. Am I correct in assuming that it's only
1TB because the disk geometry is greater than what is supported by
sysinstall and/or bsdlabel?
It's an MBR limitation, I think. Use GPT, which
On 11/16/12 21:38, Warren Block wrote:
On Fri, 16 Nov 2012, Gary Aitken wrote:
On 11/16/12 12:10, Warren Block wrote:
Additional SSD suggestions: when creating partitions, leave out the swap
partition. If you have lots of memory, leave out the /tmp partition. Add
that extra space to the
On 11/15/12 15:56, Warren Block wrote:
On Thu, 15 Nov 2012, Gary Aitken wrote:
Trying to rebuild ports, I'm consistently getting the following:
ahcich1 Timeout on slot 13 port 0
^ slot varies
g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6
On Fri, 16 Nov 2012, Gary Aitken wrote:
~$ gpart show ada0
= 34 250069613 ada0 GPT (119G)
34128 1 freebsd-boot (64k)
162 41943040 2 freebsd-ufs (20G) /
419432021048576 3 freebsd-swap (512M)swap
429917788388608 4
~$ gpart show ada0
= 34 250069613 ada0 GPT (119G)
34128 1 freebsd-boot (64k)
162 41943040 2 freebsd-ufs (20G) /
419432021048576 3 freebsd-swap (512M)swap
429917788388608 4 freebsd-ufs (4.0G) /var
51380386
in /etc/rc.conf:
swapfile=/usr/swap
Use tmpfs for /tmp in /etc/fstab:
tmpfs /tmptmpfs rw,mode=01777 0 0
It's possible to limit the size, but not necessary. This /tmp will be
cleared on reboot.
Now: why?
Using a swapfile through the filesystem gives three advantages
: why?
Using a swapfile through the filesystem gives three advantages:
1. Disk space is not tied up in an unused swap partition.
2. Swap can be resized without repartitioning.
3. Swap goes through the filesystem, using TRIM, helping the SSD
maintain performance.
/tmp as tmpfs is auto
On Fri, 16 Nov 2012, Gary Aitken wrote:
On 11/16/12 12:10, Warren Block wrote:
Additional SSD suggestions: when creating partitions, leave out the swap
partition. If you have lots of memory, leave out the /tmp partition. Add
that extra space to the /usr partition.
Format the UFS filesystems
On 11/14/12 23:38, Robert Bonomi wrote:
it appears that FreeBSD, at least 8.0 and later:
a) no longer uses 'raw' devices for anything
b) no longer uses 'block' devices for anything
c) randomly assigns device 'major' numbers
d) doesn't use device 'minor' numbers for anything.
Trying to rebuild ports, I'm consistently getting the following:
ahcich1 Timeout on slot 13 port 0
^ slot varies
g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6
/usr got error 6 while accessing filesyustem cpuid=0
panic:
On Thu, Nov 15, 2012 at 1:18 PM, Gary Aitken free...@dreamchaser.orgwrote:
Error 6 is ENXIO, device not configured; not sure exactly what that means.
This machine has:
16G mem
0.5G swap
2G /tmp
4G /var
Is any of that likely to be related to the problem?
Given an addr in
On Thu, 15 Nov 2012 13:30:43 -0600
Adam Vande More amvandem...@gmail.com wrote:
Sounds like you have bad hardware. Drive, cable, controller etc.
Probably wouldn't hurt to do a fsck either.
*After* identifying and fixing the hardware problem, otherwise you
may make things worse.
--
On Thu, 15 Nov 2012, Gary Aitken wrote:
Trying to rebuild ports, I'm consistently getting the following:
ahcich1 Timeout on slot 13 port 0
^ slot varies
g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6
That seems familiar, maybe others have
On Tue, 16 Oct 2012 13:13:41 -0700
Devin Teske devin.te...@fisglobal.com wrote:
When two files have the same inode, they are hard links to each other.
Unlike a soft link (or symbolic link as they are more appropriately
called), which stores a destination-path of the target, a hard link
On Oct 17, 2012, at 1:30 AM, Steve O'Hara-Smith wrote:
On Tue, 16 Oct 2012 13:13:41 -0700
Devin Teske devin.te...@fisglobal.com wrote:
When two files have the same inode, they are hard links to each other.
Unlike a soft link (or symbolic link as they are more appropriately
called), which
Hi everybody!
Thanks for answering my questions and helping me out with this problem.
It's been fixed now and I managed to locate the problem with the find /
-type d | awk 'length 900' command.
What caused it was something that looked like a directory loop or at least
a very deep list of sub
understand. ;-) The advantage of my approach is
avoiding a kernel panic when writing to the tmpfs when you haven't
pre-allocated all the filesystem space at creation time. If that
happens to matter to you...
___
freebsd-questions@freebsd.org
and swap md devices don't actually need swap. I don't seen any
advantage in your way of creating an md device for /tmp.
Then you don't understand. ;-) The advantage of my approach is
avoiding a kernel panic when writing to the tmpfs when you haven't
pre-allocated all the filesystem space
. ;-) The advantage of my approach is
avoiding a kernel panic when writing to the tmpfs
md device
when you haven't
pre-allocated all the filesystem space at creation time. If that
happens to matter to you...
It's the other way around, malloc md devices can cause kernel
panics. swap md device
in this thread didn't give me a
better clue about what's happening.
Anyone have any other ideas what I can try to find out why locate fails?
I'm starting to wonder if you have a corrupt filesystem. Do you have
a large number of files or something? My locate database is about three
megs
Andy Wodfer wodfer at gmail.com
Thu Aug 23 09:04:08 UTC 2012
Can't seem to figure out the problem with MAXPATHLEN.
locate: integer out of +-MAXPATHLEN (1024): 1029
Your database may be corrupted. I would suggest you delete it and
recreate.
jb
___
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic link ln -s to say /usr/tmp instead (where I have
several hundred GBs free)?
PS! This
Hi,
On Wed, 22 Aug 2012 12:59:13 +0200
Andy Wodfer wod...@gmail.com wrote:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply
remove it and create a symbolic link
On Wed, 22 Aug 2012 12:59:13 +0200
Andy Wodfer wrote:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply
remove it and create a symbolic link ln -s to say /usr/tmp
RW writes:
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
There's also a periodic script to remove older files from /tmp which
may help.
My gut reaction is: what's taking up so much room?
My /tmp contains
El día Wednesday, August 22, 2012 a las 12:59:13PM +0200, Andy Wodfer escribió:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic
thanks for the tip on omitting parts of the filesystem. Perhaps I need
to do that.
/Andreas
On Wed, Aug 22, 2012 at 1:56 PM, Michael Ross g...@ross.cx wrote:
On Wed, 22 Aug 2012 12:59:13 +0200, Andy Wodfer wod...@gmail.com wrote:
Hi,
I have about 500MB in my /tmp and it seems to be too small
, but now I faced a different
problem which I've never seen before:
locate: integer out of +-MAXPATHLEN (1024): 1029
There are some directories that contains A LOT of small files I think.
Need to investigate.
Also thanks for the tip on omitting parts of the filesystem. Perhaps I
need to do
Le 22/08/2012 12:59, Andy Wodfer a écrit :
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic link ln -s to say /usr/tmp instead (where
-s to say /usr/tmp instead (where I have
several hundred GBs free)?
PS! This is on a live server and I would like to keep downtime and
problems
to a minimum. :-)
Cheers,
Andy
If it's just locate.updatedb filling it up temporarily,
perhaps you can solve this by ommitting part of your filesystem
From owner-freebsd-questi...@freebsd.org Wed Aug 22 05:59:52 2012
Date: Wed, 22 Aug 2012 12:59:13 +0200
From: Andy Wodfer wod...@gmail.com
To: freebsd-questions freebsd-questions@freebsd.org
Subject: /tmp filesystem full
Hi,
I have about 500MB in my /tmp and it seems to be too small when
On Wed, 22 Aug 2012 14:12:25 +0200, Andy Wodfer wrote:
How can I find which directories break the MAXPATHLEN variable?
It's easy to do this with find and awk:
% find / -type d | awk 'length LIMIT'
where LIMIT is the numerical value you want to be exceeded (in
your case, MAXPATHLEN).
: /tmp filesystem full
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply
remove it and create a symbolic link ln -s to say /usr/tmp instead
(where I have
instead (where I have
several hundred GBs free)?
PS! This is on a live server and I would like to keep downtime and
problems to a minimum. :-)
One way is to work around your problem is to add
'TMPDIR=/path/to/bigger/filesystem' in /etc/crontab
and/or 'export TMPDIR=/path/...' in /etc
From owner-freebsd-questi...@freebsd.org Wed Aug 22 08:27:59 2012
Date: Wed, 22 Aug 2012 14:25:51 +0100
From: Steve O'Hara-Smith st...@sohara.org
To: freebsd-questions@freebsd.org
Subject: Re: /tmp filesystem full
On Wed, 22 Aug 2012 08:14:35 -0500 (CDT)
Robert Bonomi bon...@mail.r
If you use zfs, that is easy... zfs set quota=NNG pool/tmp
if not
try to mount tmp in memory...
in /etc/rc.conf
tmpmfs=YES
tmpsize=400m
reboot
this would create a /tmp in memory (swap)
size=400 Megabytes
Sergio
___
This will happen automatically if you go to multiuser without a
writeable /tmp. See /etc/rc.d/tmp
I have a problem with the semantics of the rc scripts for this and
var, though - if you are going to use a memory-backed filesystem, you
should reserve all the space at the outset. Bad things can
for this and
var, though - if you are going to use a memory-backed filesystem, you
should reserve all the space at the outset.
It defaults to 20MB. There's no such thing as an unlimited md-backed
device
Bad things can occur as
you approach the memory limit (like a kernel panic) otherwise.
Provided
On Wed, 22 Aug 2012 23:21:12 +0100
RW wrote:
On Wed, 22 Aug 2012 14:14:17 -0700
Michael Sierchio wrote:
This will happen automatically if you go to multiuser without a
writeable /tmp. See /etc/rc.d/tmp
It doesn't, the default is an old-fashioned md device, not tmpfs.
Sorry I misread
On Wed, Aug 22, 2012 at 3:29 PM, RW rwmailli...@googlemail.com wrote:
Sorry I misread the previous post which *was* referring to an md device,
but the rest is right.
Not really. ;-) The one compelling reason to use an md filesystem for
/tmp or /var is when you have no swap, and/or your root
filesystem for
/tmp or /var is when you have no swap, and/or your root fs is read
only (or read mostly), as with embedded computers, Soekris boxes
booting from CF, USB stick, or even mSATA (I wouldn't swap on a
partition on an MLC mSATA device).
In that case, you most certainly want to reserve
On Wed, Aug 22, 2012 at 5:43 PM, Polytropon free...@edvax.de wrote:
For the mentioned appliances, that would not be a problem.
However there's a distinction between /tmp and /var/tmp
that can be summarized like this: The content of /tmp may
disappear after a reboot (see clear_tmp_enable=YES
filesystem for
/tmp or /var is when you have no swap, and/or your root fs is
read-only
tmpfs and swap md devices don't actually need swap. I don't seen any
advantage in your way of creating an md device for /tmp.
___
freebsd-questions@freebsd.org
writing to the tmpfs when you haven't
pre-allocated all the filesystem space at creation time. If that
happens to matter to you...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
Robert Bonomi bon...@mail.r-bonomi.com wrote:
MSDOS/PCDOS had no _documented_ functions to directly access the
disks, bypassing the file system, but the functions _did_ exist.
I'm sure you can provide the DOS 'function number' for those calls,
and cites to published data confirming.
They
I could have provided specifics 25 years ago :) when I was involved
with this stuff on a daily basis. I have no idea whether it was
same as me. still it is off topic.
___
freebsd-questions@freebsd.org mailing list
Regarding the security of various methods of deleting data, I just saw in
Office Depot's online ad for the coming week, which is the reason I couldn't
post this any earlier:
Need to discard an old PC but worried about protecting your identity?
Let us securely erase your personal files and
Date: Sun, 22 Jul 2012 05:52:17 -0400
From: Thomas Mueller muelle...@insightbb.com
Subject: Re: fsck on FAT32 filesystem?
Regarding the security of various methods of deleting data, I just saw in
Office Depot's online ad for the coming week, which is the reason I
couldn't post this any
Personally, I've always used a product from http://www.jetico.com/.
On Sunday, July 22, 2012 at 17:06:04 UTC, g...@ross.cx confabulated:
On Sun, 22 Jul 2012 17:08:56 +0200, Bruce Cran br...@cran.org.uk wrote:
On 22/07/2012 16:01, Wojciech Puchar wrote:
'dd if=/dev/zero of=/dev/sda bs=1M'
On 22/07/2012 17:14, Polytropon wrote:
Furthermore, in your example using Cygnwin's dd _on_ the disk
Cygnwin is currently running from, and the Windows it runs
on too, doesn't seem like a very good idea. I assume it will
result in a bluescreen soon and a _partially_ erased disk.
Sorry, I
on FAT32 filesystem?
'dd if=/dev/zero of=/dev/sda bs=1M' works under Cygwin - or you can
just write a load of zeros to \\.\PhysicalDrive0 .
who prevents you to bood live CD or pendrive with FreeBSD (or
openbsd,netbsd,linux,solaris,whatever usable)?
Merely the real-world FACT that *most* Windows
From: Polytropon free...@edvax.de
Date: Sun, 22 Jul 2012 18:14:02 +0200
Subject: Re: fsck on FAT32 filesystem?
By the way, I remember I had a DD.EXE program on my old DOS
system. I'm not sure if such a tool could operate on devices
(instead of filesystem-based representations as drive
From owner-freebsd-questi...@freebsd.org Sun Jul 22 07:22:29 2012
Date: Sun, 22 Jul 2012 14:19:43 +0200 (CEST)
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Thomas Mueller muelle...@insightbb.com
Cc: freebsd-questions@freebsd.org
Subject: Re: fsck on FAT32 filesystem?
Let us
From owner-freebsd-questi...@freebsd.org Sun Jul 22 09:19:24 2012
Date: Sun, 22 Jul 2012 15:16:01 +0100
From: Bruce Cran br...@cran.org.uk
To: Robert Bonomi bon...@mail.r-bonomi.com
Cc: freebsd-questions@freebsd.org
Subject: Re: fsck on FAT32 filesystem?
On 22/07/2012 11:38, Robert
...@mail.r-bonomi.com
Subject: Re: fsck on FAT32 filesystem?
On 22/07/2012 17:14, Polytropon wrote:
Furthermore, in your example using Cygnwin's dd _on_ the disk
Cygnwin is currently running from, and the Windows it runs
on too, doesn't seem like a very good idea. I assume it will
result
From: Michael Ross g...@ross.cx
Date: Sun, 22 Jul 2012 19:06:04 +0200
On Sun, 22 Jul 2012 17:08:56 +0200, Bruce Cran br...@cran.org.uk wrote:
Microsoft's format.exe can zero a volume, at least in the newer (2008)
versions:
/p:passes : Zeros every sector on the volume for the number of
On Sun, 22 Jul 2012 16:01:41 -0500 (CDT)
Robert Bonomi articulated:
I haven't had occasion to dissect a copy of format in years, I don't
know if it still defaults to one write attemptto every sector on the
disk.
I read on the MS TechNet several years ago that it attempted three
writes per
system. I'm not sure if such a tool could operate on devices
(instead of filesystem-based representations as drive letters),
but it actually _was_ a DOS-based copy convert utility
for the PC. :-)
MSDOS/PCDOS had -no- O/S functions to directly access actual disk
devices. The ONLY fuctionality
On Sun, 22 Jul 2012 23:01:41 +0200, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
I haven't had occasion to dissect a copy of format in years, I don't know
if it still defaults to one write attemptto every sector on the disk.
By default in Windows Vista, the format command writes zeros
On Sun, 22 Jul 2012 15:31:51 -0500 (CDT)
Robert Bonomi articulated:
Yes, in theory, they _could_ learn everything they need to know to do
it themselves, but the list of things that a 'know nothing' Windows
user has to dig out, understand, and _use_, is incredibly long and
daunting.
I know
Robert Bonomi bon...@mail.r-bonomi.com wrote:
MSDOS/PCDOS had -no- O/S functions to directly access actual disk
devices. The ONLY fuctionality provided to the user, by the O/S
was filesystem based access. To get 'raw' device access, one had
to bypass the O/S entirely, and use direct BIOS
From per...@pluto.rain.com Sun Jul 22 22:15:48 2012
Date: Mon, 23 Jul 2012 03:10:40 -0700
From: per...@pluto.rain.com
To: bon...@mail.r-bonomi.com
Cc: freebsd-questions@freebsd.org
Subject: Re: fsck on FAT32 filesystem?
Robert Bonomi bon...@mail.r-bonomi.com wrote:
MSDOS/PCDOS had
From owner-freebsd-questi...@freebsd.org Thu Jul 19 03:21:28 2012
Date: Thu, 19 Jul 2012 10:18:43 +0200 (CEST)
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Robert Bonomi bon...@mail.r-bonomi.com
Cc: freebsd-questions@freebsd.org
Subject: Re: fsck on FAT32 filesystem?
entitled
Date: Fri, 20 Jul 2012 20:18:48 +0200 (CEST)
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
Subject: Re: fsck on FAT32 filesystem?
Indeed.
But getting GELI certified and approved by the relevant
institutions and agencies isn't that easy either. Yet without
no idea what are you
On Sat, 21 Jul 2012 05:12:14 -0500 (CDT)
Robert Bonomi articulated:
Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
entitled to have opinions, *BUT* the Gospel According to
Wojciech is -not- 'the answer' for everybody, in every
situation. *IF* you ever learn that,
Seems like you
It seems like all you know how to do is engage in ignorant, uninformed,
personal attacks/insults.
if you would read more carefully then you will see clearly that i am
personally attacked most often.
___
freebsd-questions@freebsd.org mailing list
Seriously though, I wish people would stop feeding this TROLL. There is
absolutely no upside to it. As has been stated so eloquently many times
before, Never argue with a fool - they will drag you down to their
level, then beat you with experience.
so why you are continuing that thread?
People
On Thu, Jul 19, 2012 at 4:53 AM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
All I'm going to say is:
1) There's a _reason_ the gov't requires hard drives with anthing higher
than 'somewhat' classified data on them to be =physically= destroyed
before leving the secure area.
regulations have been tightened further recently as to mandate
sector-level encryption of the hard disks as well, just to be on the
sure(rer) side. At least in certain particularly sensitive areas.
which may be a proof that governments know backdoors alloving recovery
from encrypted drives
On Fri, Jul 20, 2012 at 6:07 PM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
regulations have been tightened further recently as to mandate
sector-level encryption of the hard disks as well, just to be on the
sure(rer) side. At least in certain particularly sensitive areas.
which
Indeed.
But getting GELI certified and approved by the relevant
institutions and agencies isn't that easy either. Yet without
no idea what are you talking about. For your own use you don't need
anyones certification. You need safe solution. geli just do this.
As for any government agencies
developed countries.
Not really sure what you wanted to imply,
as SMB looks like americanism to me.
as well as SOHO.
As not the first time, some people here when lacking arguments say i work
for larger company. We have more servers in one place.
Esp. second is nopt something to be proud
1) There's a _reason_ the gov't requires hard drives with anthing higher
than 'somewhat' classified data on them to be =physically= destroyed
before leving the secure area.
no. for modern hard drives it was already proved that
dd if=/dev/zero of=/dev/disk bs=1m
is enough to make data
entitled to have opinions, *BUT* the Gospel According to Wojciech is -not-
'the answer' for everybody, in every situation. *IF* you ever learn that,
Seems like you have 45 years of experience in words. nothing more.
Aggression is normal today from such people, that have good position in
some
Jerry jerry at seibercom.net writes:
...
I couldn't have said it better myself. Wojciech lives in his own little
world, which is fine as long as he doesn't try to visit mine. He sounds
like he works at a small Polish SMB, more commonly referred to as a
SOHO in more developed countries. I
Otherwise, you may run the danger of building a wall around yourself.
everyone should judge by his/her own brain which opinions are right.
Actually in every moment i try to encourage EVERYONE to turn on his/her
brain that we all have but rarely use.
To be ever able to use ones brain
On Thu, 19 Jul 2012 10:15:17 +0200 (CEST)
Wojciech Puchar articulated:
1) There's a _reason_ the gov't requires hard drives with anthing
higher than 'somewhat' classified data on them to be =physically=
destroyed before leving the secure area.
no. for modern hard drives it was already
for very old drives it may not
Would you be so kind as to point out the proof of that statement?
sorry but i didn't save that article on hard drive. So no proof if you
don't believe me i've actually read it.
The main point is that you have
- track
- intra-track gap
- finite precision of
This topic went totally off, but anyway there are interesting bits,
do you say that e.g. Gutmann method is totally unneeded?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/fsck-on-FAT32-filesystem-tp5727015p5728126.html
Sent from the freebsd-questions mailing list archive
On Thu, 19 Jul 2012 12:49:50 +0200 (CEST)
Wojciech Puchar articulated:
Otherwise, you may run the danger of building a wall around
yourself.
everyone should judge by his/her own brain which opinions are right.
Actually in every moment i try to encourage EVERYONE to turn on
his/her
://en.wikipedia.org/wiki/File:MFM_AFM_JANUSZ_REBIS_INFOCENTRE_PL_HDD_MAGNETIC_MEMORY_EVOLUTION.png
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/fsck-on-FAT32-filesystem-tp5727015p5728126.html
Sent from the freebsd-questions mailing list archive at Nabble.com
can add FreeBSD knowledge to their CV.
That statement goes beyond stupid. At some point, everyone is a
You proved well enough about what stupid means.
esp your mail carmel...@hotmail.com
that's truly a mail address that System Admin should be proud of ;)
At least you don't worry about
Wojciech Puchar wojtek at wojtek.tensor.gdynia.pl writes:
...
This should clear up some confusion. Will it ?
Disk Wiping One Pass Is Enough
http://www.anti-forensics.com/disk-wiping-one-pass-is-enough
...
---
http://www.anti-forensics.com/disk-wiping-one-pass-is-enough-part-2-this-time-wi
and just as good as random
scrubs.
That's still makes a robust procedure, even If
overkill and dated (which isn't exactly bad
thing).
Thanks for replies.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/fsck-on-FAT32-filesystem-tp5727015p5728161.html
Sent from the freebsd
On 19/07/2012 09:15, Wojciech Puchar wrote:
no. for modern hard drives it was already proved that
dd if=/dev/zero of=/dev/disk bs=1m
is enough to make data unreadable.
for very old drives it may not
How about data stored in remapped sectors, or any flash cache?
The Secure Erase command
On Thu, 19 Jul 2012, Carmel wrote:
On Thu, 19 Jul 2012 10:15:17 +0200 (CEST)
Wojciech Puchar articulated:
1) There's a _reason_ the gov't requires hard drives with anthing
higher than 'somewhat' classified data on them to be =physically=
destroyed before leving the secure area.
no. for
How about data stored in remapped sectors, or any flash cache?
how about being able to restore random 0.1% of former user data.
Not really useful.
Flash cache is quite recent idea, nobody serious would like to scrap such
a drive instead of reuse.
agencies recover overwritten data? at
http://www.nber.org/sys-admin/overwritten-data-gutmann.html
at first - it should be asked can agencies recover your data without
being overwritten first.
just use geli(8)
then second problem is even less problem.
Finally use geli (or similar method)
On Thu, 19 Jul 2012 16:26:57 +0200 (CEST), Wojciech Puchar wrote:
agencies recover overwritten data? at
http://www.nber.org/sys-admin/overwritten-data-gutmann.html
at first - it should be asked can agencies recover your data without
being overwritten first.
Sure, because it's stored
From owner-freebsd-questi...@freebsd.org Tue Jul 17 12:06:29 2012
Date: Tue, 17 Jul 2012 19:02:19 +0200 (CEST)
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Robert Bonomi bon...@mail.r-bonomi.com
Cc: freebsd-questions@freebsd.org
Subject: Re: fsck on FAT32 filesystem
1 - 100 of 1296 matches
Mail list logo
