I have a 6.0-RELEASE-p1 box with a GENERIC kerbnel that I'm having some
trouble with.
I recently reconstituted the machine from being a 5.4 box. I didn't
upgrade, I reinstalled.
When I was trying to install tripwire, kept getting this message:
./bin/i386-unknown-freebsd_r/siggen missing. Build
: error: previous definition of 'td' was
here
*** Error code 1
Do you think is still supported?
Quoting from mount_umapfs(8):
| BUGS
| THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
| AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN
| RISK
Hi all
do you think is possible to compile cleanly and to use
the umapfs file system?
I tried but I got this error:
cc -c -O -pipe -mcpu=ev67 -mieee -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -std
to be able to change configuration options, such as adding
something from the packages collection on the CDs, or adding more of the
distributions at a later point remotely, using /stand/sysinstall. I
figured
I could copy both cds 1 and 2 into a directory on the machine, and choose
file system from
Cc: 'freebsd-questions@freebsd.org'
Subject: Re: Installing from File System
Dean Weimer [EMAIL PROTECTED] writes:
I have setup FreeBSD 5.4, with a minimal installation from the CDRom,
I would like to be able to change configuration options, such as
adding something from the packages
Company
_
From: Thomas Linton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 01, 2005 4:13 AM
To: Dean Weimer
Cc: freebsd-questions@freebsd.org
Subject: Re: Installing from File System
I do have the same problem and don't really understand the syntax of the
INDEX file.
I guess
Hi all,
There's fire in the house... I recently inserted a USB memory stick and my
5.4 Stable machine rebooted suddenly. I now get the following on boot :
Starting file system checks :
/dev/ad0s3a: UNKNOWN FILE TYPE I=2900154
/dev/ad0s3a: UNEXPECTED SOFT UPDATE INCONSISTENCY: RUN fsck MANUALLY
On 10/31/05, Edward Lichtner [EMAIL PROTECTED] wrote:
Hi all,
There's fire in the house... I recently inserted a USB memory stick and my
5.4 Stable machine rebooted suddenly. I now get the following on boot :
Starting file system checks :
/dev/ad0s3a: UNKNOWN FILE TYPE I=2900154
/dev/ad0s3a
At 02:06 AM 10/31/2005, Edward Lichtner wrote:
Hi all,
There's fire in the house... I recently inserted a USB memory stick and my
5.4 Stable machine rebooted suddenly. I now get the following on boot :
Starting file system checks :
/dev/ad0s3a: UNKNOWN FILE TYPE I=2900154
/dev/ad0s3a
On 10/31/05, Edward Lichtner [EMAIL PROTECTED] wrote:
Hi all,
There's fire in the house... I recently inserted a USB memory stick and my
5.4 Stable machine rebooted suddenly. I now get the following on boot :
Starting file system checks :
/dev/ad0s3a: UNKNOWN FILE TYPE I=2900154
/dev
, using /stand/sysinstall. I figured
I could copy both cds 1 and 2 into a directory on the machine, and choose
file system from the installation media page. All works good up to a point.
then I receive a message stating that this is Disc 0 and the packages is on
Disc 1. How do I make
could copy both cds 1 and 2 into a directory on the machine, and choose
file system from the installation media page. All works good up to a point.
then I receive a message stating that this is Disc 0 and the packages is on
Disc 1. How do I make the install section realize that all of the files
Hi all,
cvsup failed on me ( filled up a 3.0 G /usr dir).
I am in the proces of moving /usr to a sub dir under /home/ which has 30 G.
Hopefully, I can rerun cvsup with success.
I will create a soft link from /usr - /home/usr.
At some point, I will want to move /usr back to its proper place.
On Saturday 17 September 2005 13:44, Grant Peel wrote:
Hi all,
cvsup failed on me ( filled up a 3.0 G /usr dir).
I am in the proces of moving /usr to a sub dir under /home/ which has 30 G.
Hopefully, I can rerun cvsup with success.
I will create a soft link from /usr - /home/usr.
At some
Robert Fitzpatrick wrote:
I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file system.
Hi Robert,
I'd get
On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote:
I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file
Robert Fitzpatrick wrote:
I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file system.
When it happened
I made a mistake to my /boot/loader.conf file and now the system hangs
after pressing F1 and before the boot options menu. How can I access the
file to edit it? I have the install CD, but can't seem to figure out how
to get to the file system.
--
Robert
On Sat, 2005-09-03 at 13:31 -0500, Kevin Kinsey wrote:
What resources do you have?
Don't have another FreeBSD machine at this location. I have my SuSE 9.2
linux workstation and Windows 2003 server machine.
2] Fixit CD or Fixit floppy. Available via FTP
from ftp.freebsd.org.
I tried the
http://uranus.it.swin.edu.au/~jn/linux/
and specifically:
http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm
these are all windows programs that take away the frustration
of installing linux. however freebsd and any os follows the same concept
when it comes
to boot disks (.img) - so give
Bruce Evans [EMAIL PROTECTED] writes:
Mostly (b). Sizes are 64 bits in the standard, but FreeBSD has always
silently discarded the highest 32 bits and corrupted the next highest
bit to a sign bit, so the file size limit is at most 2GB or 4GB
(depending on whether the sign bit gets corrupted
The attached patch should make the isonum functions in iso.h much
clearer. It also gets rid of the optimizated versions; I trust the
compiler to take care of that.
The inode number situation can be improved by dividing the byte offset
of the directory entry by a suitable number guaranteed not to
ISO9660 does not use 64-bit values. Those 8-byte values you see in
the headers are 32-bit values stored first in little-endian format and
second in big-endian format.
So, in my original question, the blame lies solely with
3) ISO-9660 standard
? No single file on a ISO9660
Mikhail Teterin [EMAIL PROTECTED] writes:
No single file on a ISO9660 filesystem may exceed 4Gb?
The ISO 9660 file system was designed for a storage medium which had a
fixed capacity of 600 MB.
Is there some newer, superceeding backwards-compatible standard -- all the new
DVD devices are now
Hello!
I have a cd9660 image with several files on it. One of the files is very large
(above 4Gb). When I mount the image, the size of this file is shown as
realsize % 4Gb -- 758876749 bytes instead of 5053844045.
What should I blame:
1) The software, that created the image (modified
On Fri, 19 Aug 2005, Mikhail Teterin wrote:
I have a cd9660 image with several files on it. One of the files is very large
(above 4Gb). When I mount the image, the size of this file is shown as
realsize % 4Gb -- 758876749 bytes instead of 5053844045.
What should I blame:
1) The
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2 do this other stuff
thanks in advance
=
Either write things worth reading, Or do
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2 do this other stuff
Parse /etc/fstab?
I'm sure there are lots of other ways too...
___
Jorge Mario G. Mazo wrote:
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2 do this other stuff
not sure if this is what your looking for, but there are likely a million ways,
one being
in
--- jdyke [EMAIL PROTECTED] escribió:
Jorge Mario G. Mazo wrote:
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2 do this other stuff
not sure if this is what your looking
In the last episode (Aug 17), jdyke said:
Jorge Mario G. Mazo wrote:
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2 do this other stuff
not sure if this is what your looking for, but
In the last episode (Aug 17), Jorge Mario G. Mazo said:
--- jdyke [EMAIL PROTECTED] escribió:
Jorge Mario G. Mazo wrote:
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2
On Wed, 17 Aug 2005, Jorge Mario G. Mazo wrote:
hi there
I've been looking for a way to check the fs type
I need to do something like this
if NTFS do this
if msdis do that
if ufs2 do that
if ext2 do this other stuff
thanks in advance
I'd check out the fdisk code. For example:
$ fdisk
Marcin [EMAIL PROTECTED] writes:
Hello, where can i find information or examples of how to write a file system
for FreeBSD, apart from /usr/src/sys/* and /usr/share/man/*?
The Architecure Handbook. (/usr/share/doc/en/arch-handbook)
The old McKusick book (/usr/share/doc/en/design-44bsd
Thanks! The arch-book is something i was looking for. Somehow i missed that
when seeking doc/
m.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL
Hello, where can i find information or examples of how to write a file system
for FreeBSD, apart from /usr/src/sys/* and /usr/share/man/*?
What is vnode_if.h for? Why is it generated for every fs module if it is the
same every time? I tried to google for the answer but found nothing. Only
Don't know the answers, but the fs mailing list would probally be a
better one to ask on.
On Wed, 27 Jul 2005 20:38:22 +0200
Marcin [EMAIL PROTECTED] wrote:
Hello, where can i find information or examples of how to write a
file system for FreeBSD, apart from /usr/src/sys/*
and /usr/share
Just curious if there is an option that can be set (I've checked the man
page, and didn't find one) that would prevent a file system from being
mounted twise on the same mount point?
For instance, I have /du defined in my /etc/fstab, and want to prevent:
mount /du
mount /du
from working
On Fri, Jul 22, 2005 at 04:59:56PM -0300, Marc G. Fournier wrote:
Just curious if there is an option that can be set (I've checked the man
page, and didn't find one) that would prevent a file system from being
mounted twise on the same mount point?
For instance, I have /du defined in my
Hi, i have a problem with an erro of me : i have formated unfortunely my
ufs partition of my server data, how is possible to unformat ufs file
system, i've try easy recovry with raw mode but many files lost , please
anybody can help me or my data as lost
On 6/14/05, snoopy [EMAIL PROTECTED] wrote:
Hi, i have a problem with an erro of me : i have formated unfortunely my
ufs partition of my server data, how is possible to unformat ufs file
system, i've try easy recovry with raw mode but many files lost , please
anybody can help me or my data
Hi, i have a problem with an erro of me : i have formated unfortunely my
ufs partition of my server data, how is possible to unformat ufs file
system, i've try easy recovry with raw mode but many files lost , please
anybody can help me or my data as lost?
What do you mean by format? Did
Is there an option that I can add to fstab (or some way of doing it?)
that, when a server reboots, it will 'ignore' that file system, but I can
still do a 'mount /fs' after the fact?
I have remote servers that I'd like to manually fsck one of the file
systems after it comes up, but I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc G. Fournier wrote:
|
| Is there an option that I can add to fstab (or some way of doing it?)
| that, when a server reboots, it will 'ignore' that file system, but I
| can still do a 'mount /fs' after the fact?
|
| I have remote servers that I'd
On Sat, 11 Jun 2005, Bob Bomar wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc G. Fournier wrote:
|
| Is there an option that I can add to fstab (or some way of doing it?)
| that, when a server reboots, it will 'ignore' that file system, but I
| can still do a 'mount /fs' after
At 08:16 PM 6/11/2005, Marc G. Fournier wrote:
Is there an option that I can add to fstab (or some way of doing it?)
that, when a server reboots, it will 'ignore' that file system, but I can
still do a 'mount /fs' after the fact?
in the options column in fstab specify noauto
-Glenn
I have
mail.schatti.ch [EMAIL PROTECTED] writes:
If you had to choose amongst the available filesystems on 5.4 to
contain just about 500kB to a MB, which would you use, and with what
parameters ? Which of these has the lowest administration overhead,
the lowest space overhead ?
Generally I go with
On Fri, May 13, 2005 at 10:29:37PM +, mail.schatti.ch wrote:
If you had to choose amongst the available filesystems on 5.4 to contain
just about 500kB to a MB, which would you use, and with what parameters ?
Which of these has the lowest administration overhead, the lowest space
If you had to choose amongst the available filesystems on 5.4 to contain
just about 500kB to a MB, which would you use, and with what parameters ?
Which of these has the lowest administration overhead, the lowest space
overhead ?
TIA
George
___
the following errors:
'Copying return error status of 1!'
'/: write failed, filesystem is full'
'installInitial: Couldn't clone the bootfloppy onto the root file system.
Aborting!'
An emergency shell shows that the device files 'da0s2a' through
'da0s2f' exist in '/dev'.
What am I missing?
Thanks,
Mike
Is there any way of detecting the type of file system on a disk,
specifically UFS2 or UFS1?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Sat, Mar 19, 2005 at 09:27:57AM -0500, Robert Munn wrote:
Is there any way of detecting the type of file system on a disk,
specifically UFS2 or UFS1?
If all you need to know is wether a UFS file system is UFS1 or UFS2,
you could use /sbin/dumpfs
-cpghost.
--
Cordula's Web. http
Robert Munn wrote:
Is there any way of detecting the type of file system on a disk,
specifically UFS2 or UFS1?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
. Is there a cluster and or file system replication
method that meets these requirements in FreeBSD?
Your help is appreciated!
--Nick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mikkel C. Simonsen
Sent: 25 February 2005 12:12
To: freebsd-questions@freebsd.org
Subject: Re: SCO file system mounting
[EMAIL PROTECTED] skrev:
Hello to all.
Would 'mount' mount the SCO
On Fri, Feb 25, 2005 at 01:13:06AM -0600, Aftab Jahan Subedar typed:
Hauan David A wrote:
-Original Message-
From: Aftab Jahan Subedar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 2:45 AM
To: [EMAIL PROTECTED]
Subject: SCO file system mounting
Hello to all
[EMAIL PROTECTED] skrev:
Hello to all.
Would 'mount' mount the SCO file system ? Does any body know
? I presume the SCO system as partition type 2 or partition type 3 or
partition type 0x63.
If SCO is running...
How about mount -t nfs?
Good idea .
but the bad thing is its only running the serial
David Bear wrote:
On Fri, Feb 25, 2005 at 01:13:06AM -0600, Aftab Jahan Subedar wrote:
Hauan David A wrote:
-Original Message-
From: Aftab Jahan Subedar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 2:45 AM
To: [EMAIL PROTECTED]
Subject: SCO file system
Ruben de Groot wrote:
On Fri, Feb 25, 2005 at 01:13:06AM -0600, Aftab Jahan Subedar typed:
Hauan David A wrote:
-Original Message-
From: Aftab Jahan Subedar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 2:45 AM
To: [EMAIL PROTECTED]
Subject: SCO file system
Dan Nelson wrote:
In the last episode (Feb 23), Aftab Jahan Subedar said:
Dan Nelson wrote:
In the last episode (Feb 23), Aftab Jahan Subedar said:
Would 'mount' mount the SCO file system ? Does any body know ? I
presume the SCO system as partition type 2 or partition type 3
Hauan David A wrote:
-Original Message-
From: Aftab Jahan Subedar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 2:45 AM
To: [EMAIL PROTECTED]
Subject: SCO file system mounting
Hello to all.
Would 'mount' mount the SCO file system ? Does any body know
? I presume
Hello to all.
Would 'mount' mount the SCO file system ? Does any body know ?
I presume the SCO system as partition type 2 or partition type 3 or
partition type 0x63.
Thank you.
-Jahan
___
freebsd-questions@freebsd.org mailing list
http
In the last episode (Feb 23), Aftab Jahan Subedar said:
Would 'mount' mount the SCO file system ? Does any body know ? I
presume the SCO system as partition type 2 or partition type 3 or
partition type 0x63.
Sorry; no-one has written drivers for any of SCO's filesystem types
(htfs is probably
Dan Nelson wrote:
In the last episode (Feb 23), Aftab Jahan Subedar said:
Would 'mount' mount the SCO file system ? Does any body know ? I
presume the SCO system as partition type 2 or partition type 3 or
partition type 0x63.
Sorry; no-one has written drivers for any of SCO's filesystem
In the last episode (Feb 23), Aftab Jahan Subedar said:
Dan Nelson wrote:
In the last episode (Feb 23), Aftab Jahan Subedar said:
Would 'mount' mount the SCO file system ? Does any body know ? I
presume the SCO system as partition type 2 or partition type 3 or
partition type 0x63.
Sorry
-Original Message-
From: Aftab Jahan Subedar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 2:45 AM
To: [EMAIL PROTECTED]
Subject: SCO file system mounting
Hello to all.
Would 'mount' mount the SCO file system ? Does any body know
? I presume the SCO system
I have done quite a bit of searching on the subject and seem to be coming back
to the same conclusion.
I recently accidentally removed a symlink recursively in a sleep deprived
stupor and lost an entire directory of personal music projects. Being that I
had not performed backups for that day,
Is anybody besides *me* having file system corruption problems with FreeBSD
5.3? I've looked around on several of the mailing lists and found no men-
tion of this.
I have two different platforms on which I'm trying to run FreeBSD 5.3. One
is an x86 SMP system (dual AMD Athlon 1900
On Wed, 26 Jan 2005 05:50:02 -0700 (MST), Terry R. Friedrichsen wrote:
Is anybody besides *me* having file system corruption problems with FreeBSD
5.3? I've looked around on several of the mailing lists and found no men-
tion of this.
Not the same problem as you, but I've been getting
I have been testing 5.3 (Standard Install/Default settings) and
haven't had any file system corruption. However, the I/O performance
results from my testing currently show that there is a major
difference between 4.11 and 5.3 (4.11 is much faster!). I have a
suspicion that these issues may
Thanks for responding to my inquiry. If it fits into your testing program,
try running something that works the file system and simply turn off the
system power in the middle of it.
Twice, now, doing this on my Alpha has rendered the system unrecoverable at
boot time, necessitating a reinstall
:
Thanks for responding to my inquiry. If it fits into your testing program,
try running something that works the file system and simply turn off the
system power in the middle of it.
Twice, now, doing this on my Alpha has rendered the system unrecoverable at
boot time, necessitating
On Wed, Jan 26, 2005 at 05:50:02AM -0700, Terry R. Friedrichsen wrote:
Is anybody besides *me* having file system corruption problems with FreeBSD
5.3? I've looked around on several of the mailing lists and found no men-
tion of this.
I have two different platforms on which I'm trying
On Wed, Jan 26, 2005 at 12:42:47PM -0700, Terry R. Friedrichsen wrote:
Thanks for responding to my inquiry. If it fits into your testing program,
try running something that works the file system and simply turn off the
system power in the middle of it.
This is expected if you don't turn off
I wrote:
try running something that works the file system and simply turn off the
system power in the middle of it.
to which [EMAIL PROTECTED] replied:
This is expected if you don't turn off write caching of the hard
disks. It breaks the softupdates consistency model because data
written
On Wed, Jan 26, 2005 at 03:53:46PM -0700, Terry R. Friedrichsen wrote:
I wrote:
try running something that works the file system and simply turn off the
system power in the middle of it.
to which [EMAIL PROTECTED] replied:
This is expected if you don't turn off write caching
On Wed, 26 Jan 2005, Terry R. Friedrichsen wrote:
Is anybody besides *me* having file system corruption problems with
FreeBSD 5.3? I've looked around on several of the mailing lists and
found no men- tion of this.
I have two different platforms on which I'm trying to run FreeBSD 5.3
Hello everyone
I am newbie using FreeBDS 5.3, would apprecate some advice on
the folling problems
First
Is there any way to mount a filesystem, as a generel user? so
that everytime I put a cd in the CD player I dont have to su to
root just to mount it!
Second
I can't find kppp(the
On Wednesday 12 January 2005 6:20 pm, Emon wrote:
Is there any way to mount a filesystem, as a generel user? so
that everytime I put a cd in the CD player I dont have to su to
root just to mount it!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html
I can't find kppp(the dial
I can't find kppp(the dial up connecter that used to come with
KDE) anymore!?? If KDE is not providing it any more, then is
there any other (GUI) substitute for it?
kppp is part of the kdenetwork port. It should automagically appear on
the kde menu under Internet (maybe Network, don't
Dear people,
Does anyone know of a place where they describe the differences between
the commonly known filesystem types - UFS, UFS2, NTFS, EXT2, EXT3,
REISERFS, FAT32 (spit!) .. well, mostly the ones related to Unix I hope.
I would like to know why one type is preferred over the others, or
On Fri, 10 Dec 2004 18:48:37 +0300, Odhiambo Washington
[EMAIL PROTECTED] wrote:
Dear people,
Does anyone know of a place where they describe the differences between
the commonly known filesystem types - UFS, UFS2, NTFS, EXT2, EXT3,
REISERFS, FAT32 (spit!) .. well, mostly the ones related to
On Fri, 26 Nov 2004 01:53:11 -0800, Kevin Smith [EMAIL PROTECTED] wrote:
I am able to mount my windows partition manually by either:
mount -t ntfs /dev/ad0s1 /windows
or by putting an entry in by /dev/fstab that looks like:
/dev/ad0s1 /windows ntfs ro
Kris K. explained the problem earlier in the thread.
The correct entry in your /etc/fstab should be somethig like bellow. I
had a 2 in the 6th field (instead of 0 or leave it out); this causes
the file system to be checked on bootup which fails with the ntfs file
system. If you have
I've been away from FreeBSD for a while and I just loaded 5.3 and
inavertently made an error in rc.conf. Now when I boot up the file
system is read-only and I haven't been able to edit rc.conf to correct
the simple mistake. Any help would be appreciated.
Michael G
I've been away from FreeBSD for a while and I just loaded 5.3 and
inavertently made an error in rc.conf. Now when I boot up the file
system is read-only and I haven't been able to edit rc.conf to correct
the simple mistake. Any help would be appreciated.
mount -a to attempt mounting all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 30 November 2004 23:22, Michael G. wrote:
I've been away from FreeBSD for a while and I just loaded 5.3 and
inavertently made an error in rc.conf. Now when I boot up the file
system is read-only and I haven't been able to edit rc.conf
On Tue, 30 Nov 2004 17:04:03 -0600 (CST), David Kelly
[EMAIL PROTECTED] wrote:
I've been away from FreeBSD for a while and I just loaded 5.3 and
inavertently made an error in rc.conf. Now when I boot up the file
system is read-only and I haven't been able to edit rc.conf to
correct
.
HTH
On Tue, 30 Nov 2004 15:55:04 -0600, Kevin D. Kinsey, DaleCo, S.P.
[EMAIL PROTECTED] wrote:
Kevin Smith wrote:
Hi-- My question is really directed at which type of file system I
should
choose for the shared area (bsd/windows) when I do the partitioning,
rather than access. I
On 2004-11-30 10:31, Kevin Smith [EMAIL PROTECTED] wrote:
Kris K. explained the problem earlier in the thread.
The correct entry in your /etc/fstab should be somethig like bellow. I
had a 2 in the 6th field (instead of 0 or leave it out); this causes
the file system to be checked on bootup
root file system then I
would have liked. I may have also created a separate /usr file
system, but I have /usr in the root file system.
The /usr/ports can take up a lot of space and I'm wondering if
there are limitations to having ports live in a another files
system with a symbolic link
files
system with a symbolic link from /usr/ports to a ports directory
in another file system.
No limitations at all. You can even symlink it over NFS to another
machine if you want (set WRKDIRPREFIX to a local path in
/etc/make.conf though, to speed up builds).
If one is going
After installation and setting up of my BSD system for a while, I've
come to realize that I probably should have organized my disk a bit
differently and I have a smaller root file system then I would have
liked. I may have also created a separate /usr file system, but I have
/usr in the root
In the last episode (Nov 28), Kevin Smith said:
After installation and setting up of my BSD system for a while, I've
come to realize that I probably should have organized my disk a bit
differently and I have a smaller root file system then I would have
liked. I may have also created a separate
I am able to mount my windows partition manually by either:
mount -t ntfs /dev/ad0s1 /windows
or by putting an entry in by /dev/fstab that looks like:
/dev/ad0s1 /windows ntfs ro 2 2
and using command:
mount /windows
-however,
If I leave this entry in
On Fri, Nov 26, 2004 at 01:53:11AM -0800, Kevin Smith wrote:
I am able to mount my windows partition manually by either:
mount -t ntfs /dev/ad0s1 /windows
or by putting an entry in by /dev/fstab that looks like:
/dev/ad0s1 /windows ntfs ro 2 2
Yes, putting a 0 in the sixth field takes care of the problem and the
/windows file system is now mounted. thanks.
P.S. It's usually helpful to transcribe the exact error, instead of
describing vague symptoms.
Yes,I agree. I was not able to retreive the exact error message from
dmesg on boot
On Fri, Nov 26, 2004 at 02:16:45AM -0800, Kevin Smith wrote:
Yes, putting a 0 in the sixth field takes care of the problem and the
/windows file system is now mounted. thanks.
P.S. It's usually helpful to transcribe the exact error, instead of
describing vague symptoms.
Yes,I agree
Hi folks,
I've been installing the i386 port (5.2.1-P11) on my AMD64 (because I got sick
of the cvsup problem). So that all went fine, I've compiled KDE from source
and stuff, no problem. But now I wanted to start KDE (which has been working
fine yesterday). So I tried to login and said that
to me how
a file system can become Read-Only, the file permissions are fine.
Also can this be repaired if so what should I be reading to learn to do
that.
TIA,
Steve B.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
501 - 600 of 822 matches
Mail list logo
