thank you very much. i solved that problem other way, finally ending in
NFS root.
but i still need raw block device as swap device, which will (rarely) be
in active use.
What do you recommend - iscsi or geom_gate.
the latter is 100 times more simple, and i like simple solutions.
but
how to do it?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
On 23/02/2013 10:52, Wojciech Puchar wrote:
how to do it?
Only way I know to get iscsi that early would be to use
http://freebsd.1045724.n5.nabble.com/iSCSI-boot-driver-0-2-5-isboot-ko-has-been-released-td5736301.html
I never did get round to trying it myself though
Vince
is in vfs_mount code. ?The idea is to re-try a mount call
if we
get the ENODEV error, and mounting was not already in read-only mode, and
there
was no explicit rw or noro option; the second try is changed to ro.
I did only basic testing with an SD card in write-protected mode and a USB
card-reader
on 08/04/2011 05:16 Garrett Cooper said the following:
Yeah. It seems like something else like EINVAL (just an example --
probably a bad one) would be better. Also, please be careful as
returning ENODEV seems to be UFS-specific:
I wonder how you arrived at that conclusion.
See intro(2) or
additional
options.
Google for block device ... is write-protected, mounting read-only.
But yes, it seems that they handle this situation entirely in userland.
And I am not against it.
--
Andriy Gapon
___
freebsd-hackers@freebsd.org mailing list
http
On Fri, 8 Apr 2011, Andriy Gapon wrote:
on 08/04/2011 03:00 Jeremy Chadwick said the following:
On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote:
As a generic question / observation, maybe we should just
implement 'errors=remount-ro' (or a reasonable facsimile) like Linux
Chadwick; FreeBSD Hackers
Subject: Re: retry mounting with ro when rw fails
On Fri, 8 Apr 2011, Andriy Gapon wrote:
on 08/04/2011 03:00 Jeremy Chadwick said the following:
On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote:
As a generic question / observation, maybe we should just
more work
than the auto-mounting.
--
Andriy Gapon
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
on 08/04/2011 15:36 Andrew Duane said the following:
What I was hoping to do was design a better mechanism for passing that R/O
detection from the device to the filesystem code. Our implementation uses a
platform sysctl that checks the incoming device name against some hardware or
software
...@freebsd.org]
Sent: Friday, April 08, 2011 11:23 AM
To: Andrew Duane
Cc: Bruce Evans; freebsd...@freebsd.org; FreeBSD Hackers;
freebsd-s...@freebsd.org
Subject: Re: retry mounting with ro when rw fails
on 08/04/2011 15:36 Andrew Duane said the following:
What I was hoping to do was design
or similar, plus majority (all?) of
USB Mass Storage devices.
The second part is in vfs_mount code. The idea is to re-try a mount call if we
get the ENODEV error, and mounting was not already in read-only mode, and there
was no explicit rw or noro option; the second try is changed to ro.
I did only
in SCSI should cover real SCSI
devices,
as well as ATAPI through ahci/siis/atapicam or similar, plus majority (all?)
of
USB Mass Storage devices.
The second part is in vfs_mount code. The idea is to re-try a mount call if
we
get the ENODEV error, and mounting was not already in read-only mode
a mount call
if we
get the ENODEV error, and mounting was not already in read-only mode, and
there
was no explicit rw or noro option; the second try is changed to ro.
I did only basic testing with an SD card in write-protected mode and a USB
card-reader. ?Since I am not very familiar
Storage devices.
The second part is in vfs_mount code. ?The idea is to re-try a mount call
if we
get the ENODEV error, and mounting was not already in read-only mode, and
there
was no explicit rw or noro option; the second try is changed to ro.
I did only basic testing with an SD card
Hi!
On Mon, 24 de Noviembre de 2008, 12:19 am, Jiawei Ye wrote:
On Mon, Nov 24, 2008 at 1:21 PM, Mike Meyer
[EMAIL PROTECTED] wrote:
--snip--
So while a Darwin (the OS underneath OSX) ABI would be possible -
though it's not clear how painful because it's not clear how visible
the MACH APIs
Hi,
On 22 Nov 2008, at 11:00, Christoph Kukulies wrote:
Since the underlying OS of Mac OS is FreeBSD I'm wondering whether
itr is possible to mount a
.dmg file as it is used in Apple software distribution for the Mac
OS. I would like to install an
Apple iPhone configuration utility on my
On Sat, 22 Nov 2008, Erik Trulsson wrote:
Which version of FreeBSD was used in OSX will almost certainly depend on
which version of MacOS X you look at.
It is quite possible that the latest version of OSX uses code from FreeBSD
5.x, but I guarantee that the first release of OSX did not.
On Sun, 23 de Noviembre de 2008, 5:22 am, Bob Bishop wrote:
On 22 Nov 2008, at 11:00, Christoph Kukulies wrote:
Since the underlying OS of Mac OS is FreeBSD I'm wondering whether
itr is possible to mount a
.dmg file as it is used in Apple software distribution for the Mac
OS. I would like to
On Sun, 23 Nov 2008 19:15:54 -0600 (CST)
Braulio José Solano Rojas [EMAIL PROTECTED] wrote:
I have an innocent question. I have read on the handbook and the thesis
about the Linux ABI technical explanations that lead me to think that it
could be possible to run Mac OS binaries on FreeBSD. I
On Mon, Nov 24, 2008 at 1:21 PM, Mike Meyer
[EMAIL PROTECTED] wrote:
--snip--
So while a Darwin (the OS underneath OSX) ABI would be possible -
though it's not clear how painful because it's not clear how visible
the MACH APIs are - it's not clear how useful it would be by
itself. You could
Since the underlying OS of Mac OS is FreeBSD I'm wondering whether itr
is possible to mount a
.dmg file as it is used in Apple software distribution for the Mac OS. I
would like to install an
Apple iPhone configuration utility on my FreeBSD box
(iPhoneConfigurationUtility.dmg). It consists of a
possible - depends which actual fs is stored in
.dmg file. Some time ago there was utility in development which allowed
mounting of hfs+ on FreeBSD.
There is dmg2iso (but it is not in ports )
--
Paul
___
freebsd-hackers@freebsd.org mailing list
http
Christoph Kukulies [EMAIL PROTECTED] writes:
Since the underlying OS of Mac OS is FreeBSD
It isn't, as someone else pointed out, and hence...
I'm wondering whether itr is possible to mount a .dmg file as it is
used in Apple software distribution for the Mac OS. I would like to
install an
Dag-Erling Smørgrav schrieb:
Christoph Kukulies [EMAIL PROTECTED] writes:
Since the underlying OS of Mac OS is FreeBSD
It isn't, as someone else pointed out, and hence...
Always thought that at some point in time it was derived from an earlier
version of FreeBSD (4.x)
I'm
On Sat, Nov 22, 2008 at 03:01:44PM +0100, Christoph Kukulies wrote:
Dag-Erling Smørgrav schrieb:
Christoph Kukulies [EMAIL PROTECTED] writes:
Since the underlying OS of Mac OS is FreeBSD
It isn't, as someone else pointed out, and hence...
Always thought that at some
Am 22.11.2008 um 15:01 schrieb Christoph Kukulies:
I would like to
install an Apple iPhone configuration utility on my FreeBSD box
(iPhoneConfigurationUtility.dmg).
...Mac OS applications won't run on FreeBSD, so there's no point in
even
trying.
It may be some java stuff.
It is not. It's a
Erik Trulsson [EMAIL PROTECTED] writes:
Parts of it was derived from FreeBSD (mainly userland stuff.) Other
parts of MacOS X (including the kernel) was mainly derived from Mach,
and some parts were of course written by Apple themselves (or taken
from other places.)
You got it almost entirely
On Sat, Nov 22, 2008 at 3:00 AM, Christoph Kukulies [EMAIL PROTECTED] wrote:
Since the underlying OS of Mac OS is FreeBSD I'm wondering whether itr is
possible to mount a
.dmg file as it is used in Apple software distribution for the Mac OS. I
would like to install an
Apple iPhone
On Sat, Nov 22, 2008 at 02:06:39PM -0800, Garrett Cooper wrote:
On Sat, Nov 22, 2008 at 3:00 AM, Christoph Kukulies [EMAIL PROTECTED] wrote:
Since the underlying OS of Mac OS is FreeBSD I'm wondering whether itr is
possible to mount a
.dmg file as it is used in Apple software distribution
Kris Kennaway wrote:
On Mon, Dec 25, 2006 at 11:17:21PM +0200, Erik Udo wrote:
I'm making a live cd and i just hit a wall with uzip.
I started by creating a null 1GB file, which i filled with FreeBSD.
After that i compressed the file with mkuzip.
Any attempts to mount this compressed image
On Mon, Dec 25, 2006 at 11:17:21PM +0200, Erik Udo wrote:
I'm making a live cd and i just hit a wall with uzip.
I started by creating a null 1GB file, which i filled with FreeBSD.
After that i compressed the file with mkuzip.
Any attempts to mount this compressed image has failed, here is
I'm making a live cd and i just hit a wall with uzip.
I started by creating a null 1GB file, which i filled with FreeBSD.
After that i compressed the file with mkuzip.
Any attempts to mount this compressed image has failed, here is the
output of truss when using mount_cd9660 to mount the
I'm making a live cd and i just hit a wall with uzip.
I started by creating a null 1GB file, which i filled with FreeBSD.
After that i compressed the file with mkuzip.
Any attempts to mount this compressed image has failed, here is the
output of truss when using mount_cd9660 to mount the
On Sat, Apr 15, 2006 at 01:05:45AM -0400, Joe Marcus Clarke wrote:
Based on feedback I received on my initial diff, I took another crack at
user mounting. To address Robert's concerns, I drop the setuid
permissions until needed. Therefore, all permission checks are now done
in the kernel
On Sat, Apr 15, 2006 at 01:05:45AM -0400, Joe Marcus Clarke wrote:
Finally, in testing this, I found a problem with smbfs, msdosfs, and
ntfs relating to the statfs(2) f_flags field. smbfs always set this to
0, msdosfs didn't set this at all, and ntfs set this to all flags (not
just those
Joe Marcus Clarke wrote:
//[EMAIL PROTECTED]/homes/home/%u/smb_homesmbfsrw,noauto,user
0 0
Then, a user could just run, for example:
mount /home/marcus/smb_home
And their SMB home directory would get mounted (~/.nsmbrc is also
respected).
Nice. Very nice. A couple
On Sat, 2006-04-15 at 11:13 +0100, Matthew Seaman wrote:
Joe Marcus Clarke wrote:
//[EMAIL PROTECTED]/homes/home/%u/smb_homesmbfsrw,noauto,user
0 0
Then, a user could just run, for example:
mount /home/marcus/smb_home
And their SMB home directory would get
Based on feedback I received on my initial diff, I took another crack at
user mounting. To address Robert's concerns, I drop the setuid
permissions until needed. Therefore, all permission checks are now done
in the kernel. The same is true for umount(8).
silby asked for wildcard support
Darren Pilgrim [EMAIL PROTECTED] writes:
GEOM doesn't automatically read the partition table and create the
slice device [...]
Yes, it does. When the umassX provider shows up, GEOM immediately
tastes it and creates geoms for the individual slices.
If it really doesn't on your system, try the
From: Dag-Erling Smørgrav [mailto:[EMAIL PROTECTED]
Darren Pilgrim [EMAIL PROTECTED] writes:
GEOM doesn't automatically read the partition table and create the
slice device [...]
Yes, it does. When the umassX provider shows up, GEOM immediately
tastes it and creates geoms for the
Darren Pilgrim [EMAIL PROTECTED] writes:
Attached as named above. The logs show the da0 DISK class in the GEOM
config, but no MBR class entry.
Take a closer look at geom-logs. It shows a slew of CAM errors.
There's something wrong with your fob, or possibly (but not likely)
with the USB
-Original Message-
From: Dag-Erling Smørgrav [mailto:[EMAIL PROTECTED]
Sent: Friday, June 10, 2005 12:16 AM
To: Darren Pilgrim
Cc: freebsd-hackers@freebsd.org
Subject: Re: Determining disk device and kicking GEOM when
doing automatic mounting of umass devices
Darren Pilgrim
the slice device, so the script forces it to
do so by trying to mount the base device before mounting the actual
partition.
These tricks are ridiculous, IMO. There has to be a more intelligent means
of going about this. How do I get the scsi disk device name created for a
umass device as soon
In message: [EMAIL PROTECTED]
Darren Pilgrim [EMAIL PROTECTED] writes:
: These tricks are ridiculous, IMO. There has to be a more intelligent means
: of going about this. How do I get the scsi disk device name created for a
: umass device as soon as it's created? How do I inform
Quick question regarding nfs. As far as I can tell, it isn't possible
to mount nfs shares from within a jail. Is this correct? Is there any
way around this limitation? A way to browse network shares without
mounting? Or some such trickery? Thanks
In [EMAIL PROTECTED], Bagus [EMAIL PROTECTED] typed:
Hi,
When I built my box, I split the disk into two partitions, one 8 gig
partition for freebsd and one 2 gig fat one in case I ever wanted to change
my mind and install a different operating system on the box. Of course, I've
never
--- Thierry Herbelot [EMAIL PROTECTED] wrote:
Le Thursday 08 April 2004 02:01, Tadimeti Keshav a
écrit :
I am running x86, not sparc.
Any solns?
Thx in advance...
try using fdisk on da0 : fdisk will tell you if
there are any partition on
your disk
TfH
Thanks folks.
I can
Hi all,
I am doing the following to mount a 10GB Quantum
Fireball FAT32 HDD via firewire as root.
FreeBSD 5.2.1, lucent F322/323 (firewire card). This
setup works under Windows 2000.
#camcontrol devlist -v
#camcontrol start da0
#mount_msdosfs /dev/da0 /bck
mount_msdosfs: /dev/da0: operation not
Le Wednesday 07 April 2004 20:02, Tadimeti Keshav a écrit :
Hi all,
I am doing the following to mount a 10GB Quantum
Fireball FAT32 HDD via firewire as root.
FreeBSD 5.2.1, lucent F322/323 (firewire card). This
setup works under Windows 2000.
#camcontrol devlist -v
#camcontrol start da0
Thanks. But when I do: ls /dev/da*, I can only see
/dev/da0, not /dev/da0s1.
Do I need to give some command to have that appear?
is it camcontrol start da0?
--- Thierry Herbelot [EMAIL PROTECTED] wrote:
Le Wednesday 07 April 2004 20:02, Tadimeti Keshav a
écrit :
Hi all,
I am doing the
[...reformated to remove top posting...]
On Apr 07, Tadimeti Keshav wrote:
Le Wednesday 07 April 2004 20:02, Tadimeti Keshav a
?crit :
Hi all,
I am doing the following to mount a 10GB Quantum
Fireball FAT32 HDD via firewire as root.
FreeBSD 5.2.1, lucent F322/323 (firewire card).
I am running x86, not sparc.
Any solns?
Thx in advance...
--- Mathew Kanner [EMAIL PROTECTED] wrote:
[...reformated to remove top posting...]
On Apr 07, Tadimeti Keshav wrote:
Le Wednesday 07 April 2004 20:02, Tadimeti Keshav
a
?crit :
Hi all,
I am doing the following to mount a
Le Thursday 08 April 2004 02:01, Tadimeti Keshav a écrit :
I am running x86, not sparc.
Any solns?
Thx in advance...
try using fdisk on da0 : fdisk will tell you if there are any partition on
your disk
TfH
___
[EMAIL PROTECTED] mailing list
Hello All,
FreeBSD 5.1 newb here, who managed to install it a
month ago but hasnt used it much cause of the mounting
problems.
Can anyone tell me how to mount my Primary master
(hda1-vfat partition) in FreeBSD.
will mount -t vfat /dev/sd01 work as in linux?
or should I change anything.
Also I
hey,
Thanks for the info.
will keep it in mind. Also I did go through the
handbook but (I think) didnt find anything on
mounting(may be wrong) though.
cheers,
--- slick [EMAIL PROTECTED] wrote:
first of all if your a newbie i would suggest using
freebsd-stable cause 5.X
is still development
# [EMAIL PROTECTED] / 2003-06-23 11:45:37 -0400:
On Mon, 23 Jun 2003, Socketd wrote:
Would it be possible to have this configuration and not having the
system fail (because of lacking rights or something):
/var/mail noexec
nosuid would be fine here also.
# [EMAIL
On Mon, 23 Jun 2003, Robert Watson wrote:
RW Can nodev also be added to all above + /usr?
RW
RW nodev prevents opening specfs character devices, but doesn't prevent
RW opening fifos or UNIX domain sockets, so is generally fine for all file
RW systems except /dev. The common exceptions I bump
On Mon, 23 Jun 2003, Socketd wrote:
Hi again
Would it be possible to have this configuration and not having the
system fail (because of lacking rights or something):
/tmp and /var/tmp noexec (I know /tmp has to be execuable to make
world)
nosymfollow. I've not found anything that this
On Tue, 24 Jun 2003 16:31:33 +0100 (BST)
Jan Grant [EMAIL PROTECTED] wrote:
/tmp and /var/tmp noexec (I know /tmp has to be execuable to make
world)
nosymfollow. I've not found anything that this breaks (except a
gazillion symlink race exploits).
Great! Thanks :-)
br
socketd
Hi again
Would it be possible to have this configuration and not having the
system fail (because of lacking rights or something):
/tmp and /var/tmp noexec (I know /tmp has to be execuable to make
world)
/varnosuid (what about even noexec?)
/var/mail
fine for all
file systems except /dev. The common exceptions I bump into are:
(1) If you have per-user chroots, make sure wherever their custom /dev
is
isn't nodev.
(2) The linux port used to (may still) install with a null device
under
/usr in the compat tree. Mounting
message from Daniel O'Connor [EMAIL PROTECTED] -
Date: 06 Feb 2003 14:27:53 +1030
From: Daniel O'Connor [EMAIL PROTECTED]
To: Craig Sebenik [EMAIL PROTECTED]
Cc: USB BSD List [EMAIL PROTECTED]
Subject: Re: mounting a pen drive
Content-Type: text/plain
Organization:
X-Mailer: Ximian Evolution 1.2.0
Why does the kernel still tries to mount root from fd0c first when i set
options ROOTDEVNAME=\cd9660:acd0\ ? And when fd0c fails, THEN he
mounts it from acd0.
thx for any help
--
www.bsdaemon.be - securax.org - docs.bsdaemon.be
keyserver: pgpkeys.mit.edu PGP keyID: DA07EAE9
As said below, modify usbdevs/umass.c to recognise your device and then
see whether it behaves. If not, try adding the quirks to scsi_da.c (no
READS_6 and no cache sync) and see whether that improves things.
If it is an ATAPI based device it might be more work to get this device
working.
Nick
Nick,
As said below, modify usbdevs/umass.c to recognise your device and then
see whether it behaves. If not, try adding the quirks to scsi_da.c (no
READS_6 and no cache sync) and see whether that improves things.
Since I started this, I ought to say that while I enjoy new challenges I
don't
* Andrew J Caines [EMAIL PROTECTED] [010902 22:12] wrote:
Nick,
As said below, modify usbdevs/umass.c to recognise your device and then
see whether it behaves. If not, try adding the quirks to scsi_da.c (no
READS_6 and no cache sync) and see whether that improves things.
Since I
Hackers,
The overwhelming lack of response on -questions suggests I might do better
here. I though this would be an easy one.
In short, I simply want to know what device to mount and what to do get
that device configured.
# usbdevs -v
Controller /dev/usb0:
addr 1: self powered, config
Matthew Emmerton wrote:
Hackers,
The overwhelming lack of response on -questions suggests I might do better
here. I though this would be an easy one.
In short, I simply want to know what device to mount and what to do get
that device configured.
# usbdevs -v
Controller /dev/usb0:
addr 1: self
: CDROM FX240S at ata1-slave using PIO3
Waiting 2 seconds for SCSI devices to settle
Mounting root from ufs:/dev/ad0s1a
da1 at sym0 bus 0 target 2 lun 0
da1: SEAGATE ST34520W 1487 Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
da1
Hi,
I've sent this to freebsd-questions but no luck yet.
I am using freebsd 4.0. and failed to mount a Linux partition on
the second hard disk. Could you please shed some light?
Thanks very much
Weiguang
==
bash-2.04# fdisk
Hello!
I have a machine here that has a SCSI disk that used to have Linux installed on
it.
When i check fdisk, it appears that there are two partitions, 1 with 23M that
seems to have the boot stuff and kernel, and then one with several Gigs with
the actual data (i booted into Linux to make
On Sun, Apr 15, 2001 at 09:56:45PM -0400, Will Mitayai Keeso Rowe wrote:
Hello!
I have a machine here that has a SCSI disk that used to have Linux
installed on it.
When i check fdisk, it appears that there are two partitions, 1 with
23M that seems to have the boot stuff and kernel, and
On Sun, 8 Apr 2001, Attila Nagy wrote:
With the appearing of the jail() in 4.0 I think it would be very good to
have the functionality of mounting already mounted (RW) filesystems read
only to another directory.
Many people agree with you -- this is one reason why the fixing of nullfs
On Sun, 8 Apr 2001, Alex Zepeda wrote:
On Sun, Apr 08, 2001 at 09:13:15PM +0200, Attila Nagy wrote:
So I am wondering, why the unices block mounting an already mounted
partition read only again.
Have you considered using ACLs perhaps? Sure it's not in -STABLE, but
it's a thought
Hello,
So I am wondering, why the unices block mounting an already mounted
partition read only again.
Have you considered using ACLs perhaps? Sure it's not in -STABLE, but
it's a thought..
It's a good thing, but I need to solve this problem on -STABLE, not on
-CURRENT :(
I think running
On 08-Apr-01 Attila Nagy wrote:
So I am wondering, why the unices block mounting an already mounted
partition read only again.
Would it be possible to solve this under FreeBSD?
Loopback NFS mount, maybe ?
--
E-Mail: Kenneth P. Stox [EMAIL PROTECTED]
Date
Hello,
I have a really stupid question, so please forgive me if the answer is
trivial for you...
With the appearing of the jail() in 4.0 I think it would be very good to
have the functionality of mounting already mounted (RW) filesystems read
only to another directory.
For example
Attila Nagy writes:
I have a really stupid question, so please forgive me if the answer is
trivial for you...
With the appearing of the jail() in 4.0 I think it would be very good to
have the functionality of mounting already mounted (RW) filesystems read
only to another directory
Hello,
Would it be possible to solve this under FreeBSD?
I am second for it.
I hope somebody will enlighten my dark mind, because I am really curious
about this :)
I am using some partition "magic" and know dark side of it.
What the problem is with it besides the ugly hacking and the small
Attila Nagy writes:
Would it be possible to solve this under FreeBSD?
I am second for it.
I hope somebody will enlighten my dark mind, because I am really curious
about this :)
I am using some partition "magic" and know dark side of it.
What the problem is with it besides the ugly
On Sun, Apr 08, 2001 at 09:13:15PM +0200, Attila Nagy wrote:
So I am wondering, why the unices block mounting an already mounted
partition read only again.
Have you considered using ACLs perhaps? Sure it's not in -STABLE, but
it's a thought..
- alex
To Unsubscribe: send mail to [EMAIL
mouss wrote:
and you must make sure your kernel is compiled with
options CD9660
Err... no. The kld gets autoloaded if the kernel doesn't have cd9660
compiled-in.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"There
In message [EMAIL PROTECTED], "Daniel C. Sobral" writes:
and you must make sure your kernel is compiled with
options CD9660
Err... no. The kld gets autoloaded if the kernel doesn't have cd9660
compiled-in.
The error message that is printed is misleading though, and gives the
impression that
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] writes:
Please send the response directly back to me, in addition to sending
it to hackers , as the volume of mail to hackers is so great that I could
very easily miss the response if it were only sent there.
I just
and you must make sure your kernel is compiled with
options CD9660
At 18:08 16/01/01 +0100, Philippe CASIDY wrote:
The naming of the cdrom has changed from 3.x to 4.x. I do not remember the old
name but the new name is /dev/acd0c for an ATAPI cdrom. So you must have
in /etc/fstab something
I'd like to thank every one who responded, and all those who were
willing to respond but saw that they would be repeating information already
sent.
It turns out that the designation of the CDROM drive changed between
versions 3.3 and 4.2 , and the only one I knew was the
Please send the response directly back to me, in addition to sending
it to hackers , as the volume of mail to hackers is so great that I could
very easily miss the response if it were only sent there.
I just installed freeBSD 4.2 and found that I couldn't mount a
CDROM even
It seems gerald stoller wrote:
Please send the response directly back to me, in addition to sending
it to hackers , as the volume of mail to hackers is so great that I could
very easily miss the response if it were only sent there.
I just installed freeBSD 4.2 and found
From: Soren Schmidt [EMAIL PROTECTED]
To: [EMAIL PROTECTED] (gerald stoller)
CC: [EMAIL PROTECTED]
Subject: Re: Mounting a CDROM in freeBSD 4.2
Date: Mon, 15 Jan 2001 19:50:59 +0100 (CET)
It seems gerald stoller wrote:
Please send the response directly back to me, in addition
I'm having trouble mounting an MD as a root filesystem from 5.0.
Can anyone tell me what I'm doing wrong please?
/boot/loader:
# load /kernel
# load -t md /filesystemfile
# boot
PROBES,etc.
Manual root filesystem specification:
fstype:device Mount device using filesystem fstype
etc...
Yes
Josef Karthauser [EMAIL PROTECTED] writes:
# load -t md /filesystemfile
Shouldn't that be 'load -t md_root'?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On 7 Nov 2000, Dag-Erling Smorgrav wrote:
Josef Karthauser [EMAIL PROTECTED] writes:
# load -t md /filesystemfile
Shouldn't that be 'load -t md_root'?
Actually, it's md_image or mfs_root (see /sys/dev/md/md.c:446). Both of
these are mentioned in md(4).
Andrzej Bialecki
// [EMAIL
Are we able to mount Solaris/x86 disk slices?
I'm thinking about trying use FreeBSD as an installation crutch to mirror
a Solaris/86 installation to 60-odd PCs (I can have FreeBSD netbooted to
a diskless workstation configuration by the time solaris is 1/2 way
through reading its secondary
(Trying -hackers since -current wasn't very interested. Maybe
someone might actually see it this time.)
I've modified the fdesc file system so that it will be mounted
on /dev/fd directly (rather than as a union mount on /dev) and
have fixed a lot of items relating to missing data and
Hi!
I want to mount one filesystem rw once and ro multiple times
(lets say, 500 times). Can I do it? And if yes, will it slow
FreeBSD down and will it use additional memory, cpu and other
system resources in this case?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Fri, 4 Feb 2000, Warner Losh wrote:
I have a need to mount a disk that was partitioned and labeled on
OpenBSD. I'm getting the following errors when I try:
# disklabel ad2
disklabel: ioctl DIOCGDINFO: Invalid argument
root@earth:~# disklabel ad1
disklabel: ioctl DIOCGDINFO: Invalid
In message [EMAIL PROTECTED] "Chris D. Faulhaber"
writes:
: root@earth:~# disklabel ad1
: disklabel: ioctl DIOCGDINFO: Invalid argument
: root@earth:~# disklabel /dev/ad1s4
disklabel /dev/ad2s2 (which is the OpenBSD partition) fails with the
same error. Mounting claims a bad ma
I have a need to mount a disk that was partitioned and labeled on
OpenBSD. I'm getting the following errors when I try:
# disklabel ad2
disklabel: ioctl DIOCGDINFO: Invalid argument
Any chance I can tweak something small and get access to these disks.
Here's what fdisk has to say:
Information
On Mon, 13 Sep 1999, Tony Finch wrote:
Well, in the absence of any comments I hacked around a bit and ended
up with the following patch (against 3.3-RC), which permits the same
block device to be mounted read-only more than once. The motivation
for this is to permit multiple chrooted
1 - 100 of 112 matches
Mail list logo
