On 03/26/10 02:37, Olivier Nicole wrote:
Hi,
I just finished installing FreeBSD on a machine whose CMOS time is not
set to UTC.
The System time is reported correctly (using 'date') but, suprisingly
(?), 'ls -la' reports that, among others, the files belonging to the
skeleton in the user home
Hello People !
I just finished installing FreeBSD on a machine whose CMOS time is not
set to UTC.
The System time is reported correctly (using 'date') but, suprisingly
(?), 'ls -la' reports that, among others, the files belonging to the
skeleton in the user home have been modified... in
Hi,
I just finished installing FreeBSD on a machine whose CMOS time is not
set to UTC.
The System time is reported correctly (using 'date') but, suprisingly
(?), 'ls -la' reports that, among others, the files belonging to the
skeleton in the user home have been modified... in the future
Ooops...
I forgot the most important part of my question... IPv6
how does this all work under IPv6? is the IPv6 domain name allocation as
fully fledged as teh IPv4 services? I.e. are there and what are the
restrictions on who can set up a name broker service for IPv6? what are the
likely
paul van den bergen wrote:
Ooops...
I forgot the most important part of my question... IPv6
how does this all work under IPv6? is the IPv6 domain name allocation as
fully fledged as teh IPv4 services? I.e. are there and what are the
restrictions on who can set up a name broker service
as usual, there has been a bit of a misunderstanding... being a loosely typed
language, Engliosh is difficult to communicate in :-0
Names, addresses and DNS are obviously different things.
I understand where IPv6 addresses come from (sort of).
I understand (sort of) how IPv6 works for DNS
On Mon, 24 Nov 2003 12:43:11 +1100
paul van den bergen [EMAIL PROTECTED] granted us these pearls of wisdom:
as usual, there has been a bit of a misunderstanding... being a loosely typed
language, Engliosh is difficult to communicate in :-0
Names, addresses and DNS are obviously different
if I operate a network, boxen1.example.org, boxen2.example.org, etc., as an
IPv4 address space and a second coincident network, boxen1.example6.org,
boxen2.example6.org, etc., as an IPv6 based address space, where does the
authority to allocate the IPv6-network based names reside?
AFAIK,
You are responsible for keeping track of the names
under *.example.org, *.example6.org, *.example46.org.
There is no such thing as an IPv6[-only] domain name.
If you asked about PTR records, this would be more
interesting... [Hint: ip6.arpa.] ;-)
The reference is:
RFC 3596: DNS
On Sun, Feb 02, 2003 at 05:39:09PM +1030, [EMAIL PROTECTED] wrote:
The command I used to copy was:
dump 0af - / | restore xf -
Is it dump or restore that have been causing the problem?
Shouldn't that be: dump 0af - / | restore rf - ?
Jeff
To Unsubscribe: send mail to [EMAIL PROTECTED]
Quoting Bill Moran [EMAIL PROTECTED]:
I've been quietly following this thread since it started and ...
I can't reproduce this behaviour. I've created and deleted I don't
know how many test directories and symlinks and I can't get it to
do what you're claiming it did.
As root, try copying
On 2003-02-01 20:53, [EMAIL PROTECTED] wrote:
Quoting Bill Moran [EMAIL PROTECTED]:
I've been quietly following this thread since it started and ...
I can't reproduce this behaviour. I've created and deleted I
don't know how many test directories and symlinks and I can't get
it to do
mind as I
was taking my time ensuring I would not do exactly what I did :-(
cd /
mount /dev/da1s1a /mnt
mount /dev/da1s1g /mnt/var
mount /dev/da1s1e /mnt/usr
...
cd /mnt
look around a bit...
cd /mnt
cwd (server shows /mnt)
rm -rf *
Ooops!
I have since been to the terminal, both drives are shiny
Are we aiming at the wrong target, here?
I used the fixit CD to examine ad0s3, where my missing files reside.
What I found was that (eg) /bin, /etc, /dev were full of files/directories, but
/var and /usr were empty. I didn't ask dump/restore to delete anything, and did
not ask rm to remove the
On 2003-01-31 13:56, [EMAIL PROTECTED] wrote:
Quoting Lowell Gilbert [EMAIL PROTECTED]:
[EMAIL PROTECTED] writes:
Can you explain what you think is a problem?
Well - it's happened to two uf us in the past month! In both cases
the operator was copying files from one drive to another and
Giorgos Keramidas wrote:
Unfortunately, rm -rf home removed home from the source /usr
directory as well! :-( I presume that this was due to /home being
a symlink to /usr/home, and somehow that link remained, so that -r
referred to everything below the symlink as well as to the directory
I was
Quoting Grant Peel [EMAIL PROTECTED]:
Hi all,
Two hard drives.
da0s1
da1s1
da0 is primary boot and OS drive.
da1 is a mirror drive.
da1's filesystems are mounted on /mnt.
Silly me runs a rm -rf * while in /mnt .
Next thing I know EVERYTHING is gone.
What did I miss here?
[EMAIL PROTECTED] writes:
rm will, unless specifically denied (I THINK you can do that), also follow symlinks.
In my case I was copying files from one HD to another, put one in the wrong
place, and deleted it using rm -rf , only to find that it deleted the original
as well! :-(
Eh?
PS I
Quoting Lowell Gilbert [EMAIL PROTECTED]:
[EMAIL PROTECTED] writes:
Can you explain what you think is a problem?
Well - it's happened to two uf us in the past month!
In both cases the operator was copying files from one drive to another and
wished to delete files from the second drive on
On Fri, Jan 31, 2003 at 01:56:54PM +1030, [EMAIL PROTECTED] typed:
Quoting Lowell Gilbert [EMAIL PROTECTED]:
[EMAIL PROTECTED] writes:
Can you explain what you think is a problem?
Well - it's happened to two uf us in the past month!
In both cases the operator was copying files from one
20 matches
Mail list logo
