For some strange reason, my 9.1 system seems to be missing the section 1
man page for tar, although everything else seems to be there.
I have an iso9660 image of 9.1 release which I tried to mount to copy
the missing file, but that didn't work (can't find the CD I burned...).
#mount -t cd9660
On 10/09/2013 10:14 pm, Gary Aitken wrote:
For some strange reason, my 9.1 system seems to be missing the section
1
man page for tar, although everything else seems to be there.
I have an iso9660 image of 9.1 release which I tried to mount to copy
the missing file, but that didn't work (can't
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
Seems like it must be possible to mount a cd9660 image somehow without
burning an actual disc?
Of course. :-)
It is possible by using a virtual node connected to the
ISO file. Without having tested, according to your example:
#
On 10/09/13 21:25, Polytropon wrote:
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
Seems like it must be possible to mount a cd9660 image somehow without
burning an actual disc?
Of course. :-)
I guess knowing it's possible is a start;
couldn't figure out where to look to get the
On Wed, 09 Oct 2013 22:18:41 -0600, Gary Aitken wrote:
for the record, that's:
mdconfig -a -t vnode -u 0 -f file
Correct, I noticed too late that -a was missing. But man mdconfig
mentions all parts that are needed. :-)
# mount -o ro -t cd9660 /dev/md0 /mnt/tmp
Gary Aitken wrote:
On 10/09/13 21:25, Polytropon wrote:
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
Seems like it must be possible to mount a cd9660 image somehow without
burning an actual disc?
Of course. :-)
I guess knowing it's possible is a start;
couldn't figure out where
2013/4/16 Beeblebrox zap...@berentweb.com:
one thing I'm not sure about is that some people create a dataset root but
that actually mounts at / (and not /root) and some just create others mount
points directly on the zpool
You can do this either way. A ZFS dataset is created at the same time
I've successfully made booting one virtual machine, I tried again and
it failed again. There's one thing I'm not sure about is that some
people create a dataset root but that actually mounts at / (and not
/root) and some just create others mount points directly on the zpool
I've tested the second
is FreeBSD's own docs: https://wiki.freebsd.org/RootOnZFS
-
10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3
xorg.devel
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/ZFS-mounting-failed-with-error-2-tp5802786p5804167.html
Sent from the freebsd
Hello
I have tried to create a GPT partition scheme on my machine. I've
created some dataset like that :
tank/usr
tank/usr/ports
tank/usr/src
tank/var/
tank/var/log
(Please note that is a test on a virtual machine before applying to a
real machine).
I've tried to generate the zpool.cache like
On Wed, 10 Apr 2013 10:16+0200, David Demelier wrote:
Hello
I have tried to create a GPT partition scheme on my machine. I've
created some dataset like that :
tank/usr
tank/usr/ports
tank/usr/src
tank/var/
tank/var/log
(Please note that is a test on a virtual machine before
2013/4/10 Trond Endrestøl trond.endres...@fagskolen.gjovik.no:
On Wed, 10 Apr 2013 10:16+0200, David Demelier wrote:
Hello
I have tried to create a GPT partition scheme on my machine. I've
created some dataset like that :
tank/usr
tank/usr/ports
tank/usr/src
tank/var/
tank/var/log
On Wed, 10 Apr 2013 11:05+0200, David Demelier wrote:
My own blog entry is a bit (out)dated, but maybe it's worth a look:
http://ximalas.info/2011/10/17/zfs-root-fs-on-freebsd-9-0/
Now I currently have 504 Gateway Timeout going to your website, I will
try at home maybe my corporate
zpool import -f zroot
reboot
Without the altroot it replaces the live CD mounts, and basically renders the
system pointless, except that it works on reboot. :) I tried all sorts of
other ways to make it work, mounting zroot and specifying a cache file, then cp
the file over, etc., nothing I did
or reboot
fixes
# this quirk
zpool export zroot
zpool import -f zroot
reboot
Without the altroot it replaces the live CD mounts, and basically renders the
system pointless, except that it works on reboot. :) I tried all sorts of
other ways to make it work, mounting zroot and specifying a cache
On Feb 24, 2013, at 4:42 AM, bw.mail.lists bw.mail.li...@gmail.com wrote:
Basically, I tried to follow
https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE, but ended up with
a system that didn't know how to mount /.
There are two scripts attached.
I did not see any attachments.
On 02/25/2013 03:13 PM, Paul Kraus wrote:
On Feb 24, 2013, at 4:42 AM, bw.mail.lists bw.mail.li...@gmail.com wrote:
Basically, I tried to follow
https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE, but ended up with a
system that didn't know how to mount /.
There are two scripts
On Feb 25, 2013, at 10:14 AM, bw bw.mail.li...@gmail.com wrote:
On 02/25/2013 03:13 PM, Paul Kraus wrote:
On Feb 24, 2013, at 4:42 AM, bw.mail.lists bw.mail.li...@gmail.com wrote:
Basically, I tried to follow
https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE, but ended up
with a
That was my understanding, too, but the instructions on the wiki say there's no
need to copy the cache file. In fact, there is no cache file to copy, since the
pool is created with
zpool create -o altroot=/mnt -O canmount=off zroot mirror /dev/gpt/g0zfs
/dev/gpt/g1zfs
No cache file. The
is
[HEADSUP] zfs root pool mounting, if you chose to search for it on
your own.
on 28/11/2012 20:35 Andriy Gapon said the following:
Recently some changes were made to how a root pool is opened for
root filesystem
mounting. Previously the root pool had to be present in
zpool.cache. Now
Basically, I tried to follow
https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE, but ended up
with a system that didn't know how to mount /.
There are two scripts attached.
zfsnocache.sh follows the instructions on the wiki. The system booted
just fine, but when it got to the part
From: Polytropon free...@edvax.de
To: Bill Tillman btillma...@yahoo.com
Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Sent: Wednesday, December 12, 2012 12:40 AM
Subject: Re: Mounting a samba share on boot?
On Tue, 11 Dec 2012 14:08:38
On Wed, 12 Dec 2012 04:27:31 -0800 (PST)
Bill Tillman articulated:
On Tue, 11 Dec 2012 14:08:38 -0800 (PST), Bill Tillman wrote:
Typically, Samba is used so that Windows or other SMB type
OS'es can access the server. That said, I would simplify all
this with the way I have mine setup. You
On 12/11/2012 10:25 AM, Hanafi Syahroini wrote:
This can be done with appropriate entries in /etc/fstab. However,
I'd recommend against doing so because, if the SMB server
is unreachable when the FreeBSD system boots, the FreeBSD
box will hang looking for the SMB connection.
A better way is to
On Tue, 11 Dec 2012 23:25:56 +0700, Hanafi Syahroini wrote:
[nothing]
First of all, it's not uncommon to place the question into
the message body (which you did not), and using a descriptive
subject (which you did). :-)
So I assume your question is _how_ to mount a SMB share at
boot.
This can
From: Polytropon free...@edvax.de
To: Hanafi Syahroini han...@zigma-jp.com
Cc: freebsd-questions@freebsd.org
Sent: Tuesday, December 11, 2012 11:57 AM
Subject: Re: Mounting a samba share on boot?
On Tue, 11 Dec 2012 23:25:56 +0700, Hanafi Syahroini wrote
On Tue, 11 Dec 2012 14:08:38 -0800 (PST), Bill Tillman wrote:
Typically, Samba is used so that Windows or other SMB type
OS'es can access the server. That said, I would simplify all
this with the way I have mine setup. You will of course need
the shares configured in your smb.conf, then simply
I think that's pretty much standard behaviour. The solution appears to be
to wake it up with the following incantation:
dd if=/dev/null of=/dev/da0 count=0
That's what works here. See the thread starting with
http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/212109.html
On Thursday 15 November 2012 02:06:02 Warren Block wrote:
true /dev/da0
is a little shorter and safer. The search keywords for this are GEOM
retaste or retasting.
Thanks Warren. I wasn't aware of that option, it's certainly much neater and
less prone to typing errors.
--
Mike Clarke
On Thu, 15 Nov 2012 09:43:42 +, Mike Clarke wrote:
On Thursday 15 November 2012 02:06:02 Warren Block wrote:
true /dev/da0
is a little shorter and safer. The search keywords for this are GEOM
retaste or retasting.
Thanks Warren. I wasn't aware of that option, it's certainly
On Thu, 15 Nov 2012, Thomas Mueller wrote:
I think that's pretty much standard behaviour. The solution appears to be
to wake it up with the following incantation:
dd if=/dev/null of=/dev/da0 count=0
That's what works here. See the thread starting with
On Thu, 15 Nov 2012, Polytropon wrote:
Is there a recommended way to automate the GEOM re-tasting so
SD cards can be accessed without further interaction (by simply
using the correct mount command)?
Not AFAIK. Could depend on hardware also; some card readers might not
need it.
On Thu, Nov 15, 2012 at 3:06 AM, Warren Block wbl...@wonkity.com wrote:
On Wed, 14 Nov 2012, Mike Clarke wrote:
On Wednesday 14 November 2012 19:43:30 Fernando Apesteguía wrote:
If I boot the system and plug the SD card in, the green led
doesn't even switch on and there is only a /dev/da0
El día Thursday, November 15, 2012 a las 05:57:45PM +0100, Fernando Apesteguía
escribió:
On Thu, Nov 15, 2012 at 3:06 AM, Warren Block wbl...@wonkity.com wrote:
On Wed, 14 Nov 2012, Mike Clarke wrote:
On Wednesday 14 November 2012 19:43:30 Fernando Apesteguía wrote:
If I boot the
On 16/11/2012 02:25, Warren Block wrote:
On Thu, 15 Nov 2012, Polytropon wrote:
Is there a recommended way to automate the GEOM re-tasting so
SD cards can be accessed without further interaction (by simply
using the correct mount command)?
Not AFAIK. Could depend on hardware also; some card
On Fri, 16 Nov 2012 13:25:28 +1030, Shane Ambler wrote:
On 16/11/2012 02:25, Warren Block wrote:
On Thu, 15 Nov 2012, Polytropon wrote:
Is there a recommended way to automate the GEOM re-tasting so
SD cards can be accessed without further interaction (by simply
using the correct mount
Hi,
I can't make my SD card reader work. It is from a 4 years old Compaq
PC. It works fine in Linux however. I'm using 9.0 release with stock
kernel. If I boot the system and plug the SD card in, the green led
doesn't even switch on and there is only a /dev/da0 that I can not
mount. If I boot the
On Wednesday 14 November 2012 19:43:30 Fernando Apesteguía wrote:
If I boot the system and plug the SD card in, the green led
doesn't even switch on and there is only a /dev/da0 that I can not
mount. If I boot the system with the card plugged in, the green led is
on and there is a /dev/da0s1
Hello,
Well, no I haven't -- I have tried only the fstab route which does serve
the purpose for me.
Thanks nonetheless :)
OriS
On Wednesday, September 5, 2012, andrew clarke wrote:
On Wed 2012-09-05 19:38:54 UTC+0200, OriS (
site.free...@orientalsensation.com javascript:;) wrote:
I've
the
command line, I am even able to mount the remote file system.
I can manually mount the remote file system using:
*sshfs user@host:/ /mnt*
Then, I do 'mount -p' and get:
*/dev/fuse0 /mnt fusefs.sshfs rw,sync 0 0*
This isn't sufficient for mounting/unmounting from fstab since it's
On Wed 2012-09-05 19:38:54 UTC+0200, OriS (site.free...@orientalsensation.com)
wrote:
I've been trying to find a page on the Internet where an example is posted
explaining how to mount sshfs from /etc/fstab, but I can't find any!
Have you tried running sshfs from cron? eg. run crontab -e as
On Thu, 6 Sep 2012 07:43:38 +1000, andrew clarke wrote:
On Wed 2012-09-05 19:38:54 UTC+0200, OriS
(site.free...@orientalsensation.com) wrote:
I've been trying to find a page on the Internet where an example is posted
explaining how to mount sshfs from /etc/fstab, but I can't find any!
In the past I wanted to do so in my system. I had one server called pluto and
I wanted to sshfs one directory from my laptop. The
first thing I had to do was to make passwordless ssh from my laptop to the
server (there are a lot of pages in the internet to explain
how to do this, so I will not
HI,
I had a drive fail recently, it was working fine until I rebooted. After
that the partition map was corrupt and I can't mount either partition on
the disk. So I made a copy of the whole disk using dd to an old USB drive.
There were several IO errors while dd was copying the disk, so I think
for mounting
fileystems. Move it ;-)
mdconfig -a -t vnode -f /new-path/ada1_backup
note the device that's created (probably md0)
you can then operate on /dev/md0 as if it were a disk. In particular, you
might want to fix the partition map, the label info, etc. You can then
fsck the filesystem
On Sun, 5 Aug 2012 23:12:48 -0700, Matthew Navarre wrote:
I can probably fix the partition table using testdisk, but now that I've
got this image file I'd rather work with that instead of the physical disk.
I've read the Handbook section on using mdconfig, but that assumes the
image file is of
1: ID=0xa5, active, starthead
1, startsector 63, 167766732 sectors; partition 2: ID=0xa5, starthead 254,
startsector 167766795, 144809910 sectors, code offset 0x3c, BSD disklabel
Why did you put it in /mnt? That's customarily used for mounting
fileystems. Move it ;-)
Heh, the BSD drive
On Mon, Aug 6, 2012 at 12:08 AM, Polytropon free...@edvax.de wrote:
On Sun, 5 Aug 2012 23:12:48 -0700, Matthew Navarre wrote:
I can probably fix the partition table using testdisk, but now that I've
got this image file I'd rather work with that instead of the physical
disk.
I've read the
I had a drive fail recently, it was working fine until I rebooted. After
that the partition map was corrupt and I can't mount either partition on
the disk. So I made a copy of the whole disk using dd to an old USB drive.
There were several IO errors while dd was copying the disk, so I think the
On Mon, Aug 6, 2012 at 2:55 AM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
I had a drive fail recently, it was working fine until I rebooted. After
that the partition map was corrupt and I can't mount either partition on
the disk. So I made a copy of the whole disk using dd to an
On 21/05/2012 00:11, Chris Brennan (lists) wrote:
Greetings!
I have a FreeBSD 9 system with 3 different ZFS pools on it. I am
booting from a ro CF Card w/o any major issues, the problem I am
encountering is that zroot needs to be mounted at boot first, because
it contains /usr, zhome and tank
Greetings!
I have a FreeBSD 9 system with 3 different ZFS pools on it. I am
booting from a ro CF Card w/o any major issues, the problem I am
encountering is that zroot needs to be mounted at boot first, because
it contains /usr, zhome and tank contain other various sub-partitions
of /usr.
Also,
Hi,
Assuming that you are using some version of diskless (man diskless), I
build NAS boxes using NanoBSD (man nanobsd) and in that setup, I need to
move the cache from /boot/zfs to /etc/zfscache so the cache can be mapped
to the files copied to the cfg partision. So I added the following file
If you move the dataset to a new machine you should also fix
the zpool.cache on the new machine. Boot it with f.e. mfsbsd
cd import the pool and copy the zpool.cache file.
Best regards
Andreas
I have solved it by copying the /boot/zfs/zpool.cache from the
working/running system to the just
Julian H. Stacey j...@berklix.com wrote:
what does lsvfs show ?
Maybe try: dd if=/dev/da0s1 count=20 of=/tmp/t ; file /tmp/t
(it show interesting stuff on my /xp anyway ).
Easier: file -s /dev/da0s1
___
freebsd-questions@freebsd.org mailing list
El día Thursday, April 19, 2012 a las 09:42:22AM -0700, per...@pluto.rain.com
escribió:
Julian H. Stacey j...@berklix.com wrote:
what does lsvfs show ?
Maybe try: dd if=/dev/da0s1 count=20 of=/tmp/t ; file /tmp/t
(it show interesting stuff on my /xp anyway ).
Easier: file -s
On Thu, 19 Apr 2012, Matthias Apitz wrote:
the problem with (this) cardreader seems to be that the card must
already inserted at boot time; a later switch to another card, for
example from a card with 'msdosfs' to a card with 'ext2fs', gives the
problem in my first mail; don't know if this is a
Warren Block wbl...@wonkity.com wrote:
On Thu, 19 Apr 2012, Matthias Apitz wrote:
the problem with (this) cardreader seems to be that the card must
already inserted at boot time; a later switch to another card, for
example from a card with 'msdosfs' to a card with 'ext2fs', gives the
Hello,
I'm trying to mount an ext2fs in 10-CURRENT with:
# fdisk /dev/da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=486 heads=64 sectors/track=32 (2048 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=486 heads=64
# kldload ext2fs
kldload: can't load ext2fs: File exists
what does lsvfs show ?
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below not above, cumulative like a play script, indent with .
Format: Plain text. Not HTML,
what does lsvfs show ?
Maybe try: dd if=/dev/da0s1 count=20 of=/tmp/t ; file /tmp/t
(it show interesting stuff on my /xp anyway ).
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below not above, cumulative like a play script, indent
what does lsvfs show ?
Maybe try: dd if=/dev/da0s1 count=20 of=/tmp/t ; file /tmp/t
(it show interesting stuff on my /xp anyway ).
kldstat # I guess that shows you have the module linked in too ?
or else already compiled in
config -x /boot/kernel/kernel | grep ext
so a puzzle if all that
Hi,
I have a system that successfully booted from system/ROOT/default,
but now failed with system/ROOT/nch (other ROOT installation),
it ends with ERROR 2, what does ERROR 2 means?
Its 9.0-RELEASE.
Reagads and thanks in advance,
vermaden
...
I forgot to attach the screenshot from KVM ...
http://ompldr.org/vZGRxeg
Regards,
vermaden
vermaden verma...@interia.pl pisze:
Hi,
I have a system that successfully booted from system/ROOT/default,
but now failed with system/ROOT/nch (other ROOT installation),
it ends with ERROR 2, what
On 15/04/2012 10:23, vermaden wrote:
I have a system that successfully booted from system/ROOT/default,
but now failed with system/ROOT/nch (other ROOT installation),
it ends with ERROR 2, what does ERROR 2 means?
Setting up for use with boot environments? Can you describe how you did
this,
Hi, thanks for fast response, here is the recipe I used ...
Matthew Seaman matt...@freebsd.org pisze:
On 15/04/2012 10:23, vermaden wrote:
I have a system that successfully booted from system/ROOT/default,
but now failed with system/ROOT/nch (other ROOT installation),
it ends with ERROR 2,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
On Sun, 11 Mar 2012 20:20:15 +0400, Льоша Лоїк wrote:
{ nothing }
Even though you wrote nothing, I assume that the subject
Mounting a samba share on boot? contains your question.
Answer:
You can put the required line in /etc/fstab, and provide
access details (workgroup, user, password
: no host:dirpath nfs-name
Mounting root filesystem rw failed, startup aborted
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to
single user mode
Enter full pathname of shell or RETURN for /bin/sh:
It looks like it's failing
Mounting root filesystem rw failed, startup aborted
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to
single user mode Enter full pathname of shell or RETURN for /bin/sh:
It looks like it's failing to 'remount' / promote
--On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote:
So I recomend you reading last mails of mine in freebsd-hackers...
Hope it helps,
Bye!
For what it's worth - I've resolved the issue I had (which was basically
the system booted, but failed trying to re-mount root as RW, and hence
In the new way of booting... you need to have the cd because the own
cd is the root filesystem... and in fact is live filesystem too so
unless you're booting from mfsroot... I assume you should have that line
in /etc/fstab inside the iso image but if you're using mfsroot... I
really
On Jan 8, 2012, at 11:57 AM, Chris wrote:
Can the upcoming FreeBSD 9 mount ext4 file systems out of the box?
Probably no. There's ext2 backwards-compatibility, but from what I recall, as
soon as someone uses extents under the ext4 filesystem it is no longer
backwards-compatible with ext2/3.
Can the upcoming FreeBSD 9 mount ext4 file systems out of the box?
Sent from my HTC.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
not present)
I notice that the /dev/da0s1.. entries are gone now from my /dev directly
(maybe this is part of the upgrade to 8.2) so all I have in /dev is
/dev/da0
My first thought was using MAKEDEV but that is redundant now I understand.
I also read that mounting drives via usb have to be done
sense: NOT READY
asc:3a,0 (Medium not present)
I notice that the /dev/da0s1.. entries are gone now from my /dev directly
(maybe this is part of the upgrade to 8.2) so all I have in /dev is
/dev/da0
My first thought was using MAKEDEV but that is redundant now I understand.
I also read that mounting
.. entries are gone now from my /dev
directly
(maybe this is part of the upgrade to 8.2) so all I have in /dev is
/dev/da0
My first thought was using MAKEDEV but that is redundant now I
understand.
I also read that mounting drives via usb have to be done with the -a
msdosfs
option because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/23/11 2:49 PM, Ryan Coleman wrote:
I have a folder full of ISOs that we're sharing on the network instead of
having the discs available (seems like a good idea, right?)
But I want to automate the process on boot instead of having to write a
On Wed, 23 Mar 2011 13:49:46 -0500, Ryan Coleman edi...@d3photography.com
wrote:
I have a folder full of ISOs that we're sharing on the
network instead of having the discs available (seems
like a good idea, right?)
Please use the correct terminology: FreeBSD (as any UNIX
operating systems)
I have a folder full of ISOs that we're sharing on the network instead of
having the discs available (seems like a good idea, right?)
But I want to automate the process on boot instead of having to write a static
script to do the work.
Disc images are located in /mount/disc_images/ (all are
Hi--
On Mar 23, 2011, at 11:49 AM, Ryan Coleman wrote:
Disc images are located in /mount/disc_images/ (all are ISOs)
They need to mount into /mount/office_files/images/FILENAME [without the .iso
extension]
How can I do this? I've always been given these types of scripts in the past
at an
On Wed, 23 Mar 2011 13:49:46 -0500, Ryan Coleman edi...@d3photography.com
wrote:
I have a folder full of ISOs that we're sharing on the
network instead of having the discs available (seems
like a good idea, right?)
Please use the correct terminology: FreeBSD (as any UNIX
operating systems)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/23/11 2:49 PM, Ryan Coleman wrote:
I have a folder full of ISOs that we're sharing on the network instead of
having the discs available (seems like a good idea, right?)
But I want to automate the process on boot instead of having to write a
We're close on this (thanks for the push).
It wants to load the entire path up in ${DEST} which is not ideal but I can
live with that.
I am also trying to make the directories right before the attempt to mount the
image (a 'duh' moment just now).
So I'd like to have just the filename, not the
On Wed, 23 Mar 2011 15:06:14 -0500, Ryan Coleman edi...@d3photography.com
wrote:
I am also trying to make the directories right before the attempt
to mount the image (a 'duh' moment just now).
So I'd like to have just the filename, not the full path, made
as a folder...
A directory. :-)
On Mar 23, 2011, at 3:16 PM, Polytropon wrote:
On Wed, 23 Mar 2011 15:06:14 -0500, Ryan Coleman edi...@d3photography.com
wrote:
I am also trying to make the directories right before the attempt
to mount the image (a 'duh' moment just now).
So I'd like to have just the filename, not the
Here's the working script (Yay!)
#! /bin/sh
for FILE in /mount/disc_images/*.iso; do
DEST=$FILE
DIRNAME=`basename ${FILE} .iso`
echo ${DIRNAME} ${FILE}
mkdir /mount/new_brighton/images/${DIRNAME}
mount -t cd9660 /dev/`mdconfig -f ${FILE}`
/mount/new_brighton/images/${DIRNAME}
done
}
mount -t cd9660 /dev/`mdconfig -f ${FILE}`
/mount/new_brighton/images/${DIRNAME}
done
Thanks to Polytropon and Chuck for their guidance.
Just a little note:
Make sure you're mounting the ISOs as -o ro to prevent
write access to them. If users don't have +w access to
the mounted
}
mkdir /mount/new_brighton/images/${DIRNAME}
mount -t cd9660 /dev/`mdconfig -f ${FILE}`
/mount/new_brighton/images/${DIRNAME}
done
Thanks to Polytropon and Chuck for their guidance.
Just a little note:
Make sure you're mounting the ISOs as -o ro to prevent
write access to them
On Wed, 23 Mar 2011 16:05:12 -0500, Ryan Coleman edi...@d3photography.com
wrote:
I did try that once and it didn't strip the directory structure
out so when basename worked I didn't mess with it too much.
I've just checked - you're right. While `basename` works
as intended, ${%} can be applied
On Mar 23, 2011, at 1:06 PM, Ryan Coleman wrote:
I am also trying to make the directories right before the attempt to mount
the image (a 'duh' moment just now).
So I'd like to have just the filename, not the full path, made as a folder...
Ah, yes-- add mkdir -p
On Wed, 23 Mar 2011 14:17:38 -0700, Chuck Swiger cswi...@mac.com wrote:
Ah, yes-- add mkdir -p /mount/office_files/images/${DEST} before the mount
command.
Someone else mentioned a use of basedir command
Prefix it with a test:
[ -d /mount/office_files/images/${DEST} ] mkdir...
On Mar 23, 2011, at 2:21 PM, Polytropon wrote:
Prefix it with a test:
[ -d /mount/office_files/images/${DEST} ] mkdir...
mount...
so there will be no error if the script is started for the
second time (and the directories still exist), means: create
them only if not yet
On Wed, 23 Mar 2011 14:24:43 -0700, Chuck Swiger cswi...@mac.com wrote:
While I agree with this suggested change from the perspective
of only doing work if you actually need to do it, note that
mkdir -p doesn't return an error if the directory already
exists. :-)
You're telling this to a man
shows
that there is CD0 device.
'show' shows that currdev=cd0: and rootdev=cd0:
'boot'
boot process starts system
...
Mounting from (...) failed with error 19
when I press '?' sign it show no CD0 device.
It seems that memory device was destroyd by 'kernel' and on this stage
'mapped by grub
On 01/21/11 07:18, Aryeh Friedman wrote:
A few things:
1. Yes it is required the reason I put it in the first place is ant
refused to build without it. (note 1)
2. How do I check the version on the phone?
Depending on your phone, try pressing menu, settings and it should be at
the bottom:
A few things:
1. Yes it is required the reason I put it in the first place is ant
refused to build without it. (note 1)
2. How do I check the version on the phone?
3. What kind of modifications would be needed to make it work on eclair?
Notes:
1. I eventually (once I get the standard ant
I decided to build the sdk from sources and wondering why it reported
Donut when I told repo -init to checkout Eclair?
-- Forwarded message --
From: Ilias-Dimitrios Vrachnis vrac...@gmail.com
Date: Thu, Jan 20, 2011 at 4:24 PM
Subject: Re: problems mounting android htc
To: Aryeh
Hello.
I'm trying a rescue on a failing drive.
I used ddrescue to get an image (which showed a single unreadable sector).
# file myimage
myimage: x86 boot sector, LInux i386 boot LOader; GRand Unified Bootloader,
stage1 version 0x3, stage2 address 0x2000, stage2 segment 0x200; partition 1:
On Sun, Jan 16, 2011 at 3:36 PM, Chris Brennan xa...@xaerolimit.net wrote:
On Sat, Jan 15, 2011 at 8:27 PM, Patrick Lamaiziere
patf...@davenulle.orgwrote:
Le Sat, 15 Jan 2011 18:57:33 -0500,
Aryeh Friedman aryeh.fried...@gmail.com a écrit :
No idea how but when I plug the USB in it says
1 - 100 of 1114 matches
Mail list logo
