Re: mounting a .iso image? ... missing man page
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 to look to get the magic combination.
>
>> It is possible by using a virtual node "connected" to the
>> ISO file. Without having tested, according to your example:
>>
>> # mdconfig -u 0 -t vnode -f
>> /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso
>
> for the record, that's:
> mdconfig -a -t vnode -u 0 -f
>
>> # mount -o ro -t cd9660 /dev/md0 /mnt/tmp
>> ... do stuff ...
>> # umount /mnt/tmp
>> # mdconfig -u 0 -d
>
> and that one is
> mdconfig -d -u 0
>
> order appears to be important
>
> Thanks again,
>
> Gary
> ___
> 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"
>
>
To avoid having to recall the arguments for mdconfig(8):
#/bin/sh
#start_isofs
#two commands to attach and mount or umount file.iso
#
isofs_stop() {
(umount -f /mnt &&
mdconfig -d -u $NUM)
}
NUM=3
DEV="/dev/md${NUM}"
IMGFS=$1
case $2 in
"start")
# first check whether target mount point is in use
if mount | grep -q "/mnt"; then
printf "Exiting: mount point '/mnt' currently unavailable.\n"
exit 1
fi
(mdconfig -a -t vnode -f "$IMGFS" -u $NUM &&
mount -o ro -t cd9660 $DEV /mnt) ;;
"stop")
isofs_stop ;;
*)
if [ "$IMGFS" = "stop" ]; then
isofs_stop
else
your_script="$(basename $0)"
printf "Usage: %s [isofile] start|stop\n" $your_script
fi
;;
esac
exit
--
c...@sdf.org
SDF Public Access UNIX System - http://sdf.org
--
___
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"
Re: 9.1 - 9.2 upgrade
Polytropon wrote: > On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: >> I tried downloading the src with: >> >> svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src >> >> I didn't get Release 9.2. The first entry in UPDATING is: >> >> 20130705: >> hastctl(8)'s `status' command output changed to terse one-liner >> format. >> Scripts using this should switch to `list' command or be rewritten. >> >> >> There is an entry earlier for Release 9.1. but no entry for Release 9.2. > > You could try downloading and extracting the "src" distribution: > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz > > > > Yes, that might have been simpler. Knew there had to be some other way. :) -- c...@sdf.org SDF Public Access UNIX System - http://sdf.org -- ___ 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"
Re: 9.1 - 9.2 upgrade
Doug Hardie wrote: >>> The Thick Plottens… >>> I received the drives and installed them on a working system. The >>> failed system is structured with a single partition for the system and >>> another for swap. For some unknown reason, the BIOS got left >>> configured to boot the extra disk if its powered up. That turns out >>> to be handy. I can boot a working system with the corrupt drive >>> powered off. >>> Booting from the corrupt drive yields the normal hardware info >>> followed by the Beastie image and immediately by a multitude of lines >>> (repeated many times): >>> Consoles: internal video/keyboard serial port >>> BIOS drive C: is disk0 >>> BIOS drive D: is disk1 >>> BIOS 639kB/1037824kB available memory >>> FreeBSD/x86 bootstrap loader, Revision 1.1 >>> (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) >>> Can't work out which disk we are booting from. >>> Guessed BIOS device 0x not found by probes, defaulting to disk0: >>> I was able to capture these by using a serial console connected to >>> another computer. The lines only appear on the serial console once. >>> They scroll by on the real console many time - all too fast to read >>> anything. Then after a few seconds of that, the screen goes black, >>> and the system reboots. The cycle then repeats… Pressing any key >>> does nothing. I even filled the keyboard buffer with spaces hoping to >>> stop boot, but nothing seems to stop it. >>> I checked and the freebsd-update.conf include world sys and src. I >>> rebuild everything after removing /obj just for grins and giggles. I >>> have installed the kernel and world using DESTDIR to put it on the >>> corrupt drive. Same messages again. >>> I now have the corrupt drive mounted on /mnt and am trying to update >>> the src again. Using: >>> freebsd-update -b /mnt fetch >>> updated files list show /usr/src/sys… >>> and updating to 9.1-RELEASE-p7 >>> freebsd-update -b /mnt install >>> This is running slower than molasses in January. Its run for almost >>> 30 minutes and only 3 files have been updated. There must be network >>> issues between me and the server. I'll let it run tonight but I am >>> going to crash now. Long day. More tomorrow. >>> -- Doug >> >> Have you checked the dmesg output, specifically to see if there are any disk >> errors, perhaps the hard drive is about dead. If you are planning to >> rebuild world and kernel form source, why not just use svn or extract the >> source from the 9.2-RELEASE disk onto the system. > > There are no hardware errors logged. The drive is only a couple months old. > Smart drive status is good. > > I tried downloading the src with: > > svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src > > I didn't get Release 9.2. The first entry in UPDATING is: > > 20130705: > hastctl(8)'s `status' command output changed to terse one-liner > format. > Scripts using this should switch to `list' command or be rewritten. > > > There is an entry earlier for Release 9.1. but no entry for Release 9.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" > > > Hello Doug, Here is a more recent version of the file on svn: http://svnweb.freebsd.org/base/stable/9/UPDATING?revision=255900&view=markup Earlier today I also checked out base for releng/9.2 from the same mirror, svn0.us-west. My UPDATING file is outdated too. Time of the last entry is 20130705. The mirror told me that I had checked out revision 256150. When running "freebsd-update upgrade -r RELEASE-9.2" last night it gave : > WARNING: This system is running a "customcl" kernel, which is not a kernel configuration distributed as part of FreeBSD 9.1-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "/usr/sbin/freebsd-update install". > That might have been expected, but I have read on this list that freebsd-update will sometimes automatically replace a custom kernel with a generic, and in /etc/freebsd-update.conf I had the line: Components src world kernel . HTH, Cary -- c...@sdf.org SDF Public Access UNIX System - http://sdf.org -- ___ 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"
X in Jail?
Is it possible to run an X server/window manager inside a jail(8)? cary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ssh'ing into jail(8)
(I sent this two days ago, when I was not subscribed. As I did not get
any replies, I have subscribed to freebsd-questions and am resending it.)
If this is not the right fourm to ask this question, please redirect me to
the correct place, or documentation which addresses this issue.
I am setting up an internal (192.168.x.x) "network" of computers consisting
of jail(8)'d virtual machines. I have set up djbdns to provide DNS service
for this internal network.
I have assigned my 192.168.x.x addresses to the lo0 interface so I don't
have to make major adjustments to my firewall ruleset.
I am able to ping all my internal machines from the host computer. I am
able to do dns lookups using the dns tools provided with djbdns, and the
nslookup and dig tools. So I am confident that name resolution is working.
Within the jailed hosts, I have turned off the portmap, syslogd, sendmail,
and inetd daemons and am running only cron and sshd daemons upon start up.
But when I attempt to ssh into one of the jailed hosts, the connection
times out and reports: "Connection closed by 192.168.1.100".
A partial sockstat reading while the hosts are attempting to connect
shows:
USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
sshd sshd 596134 tcp4 192.168.1.100:22 192.168.1.100:2604
sshd sshd 596137 udp4 192.168.1.100:2625192.168.1.1:53
root sshd 596124 tcp4 192.168.1.100:22 192.168.1.100:2604
cary ssh 596113 tcp4 192.168.1.100:2604192.168.1.100:22
A quick description of the addresses:
150.252.106.57 - external IP address of host computer, also running
dnscache for external lookups
192.168.1.1 - IP address of internal dnscache for 192.168.x.x addresses
192.168.1.100 - IP address of jail(8)'d host
192.168.53.1 - IP address of jail(8)'d tinydns server host
ssh debugging output shows:
[snip initial key-exchange]
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
{and ssh "hangs" here... Acutally waits and eventually times out.}
The messages, security, and auth logs under /var/log in the jail'd host
are completly empty. Under the host machine logs , there is nothing as
well.
I'm at a loss of what else to trouble shoot. Thank you in advance for any
help offered!
Cary Mathews
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
ssh'ing into jail(8)
If this is not the right fourm to ask this question, please redirect me to
the correct place, or documentation which addresses this issue.
I am setting up an internal (192.168.x.x) "network" of computers consisting
of jail(8)'d virtual machines. I have set up djbdns to provide DNS service
for this internal network.
I have assigned my 192.168.x.x addresses to the lo0 interface so I don't
have to make major adjustments to my firewall ruleset.
I am able to ping all my internal machines from the host computer. I am
able to do dns lookups using the dns tools provided with djbdns, and the
nslookup and dig tools. So I am confident that name resolution is working.
Within the jailed hosts, I have turned off the portmap, syslogd, sendmail,
and inetd daemons and am running only cron and sshd daemons upon start up.
But when I attempt to ssh into one of the jailed hosts, the connection
times out and reports: "Connection closed by 192.168.1.100".
A partial sockstat reading while the hosts are attempting to connect
shows:
USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
sshd sshd 596134 tcp4 192.168.1.100:22 192.168.1.100:2604
sshd sshd 596137 udp4 192.168.1.100:2625192.168.1.1:53
root sshd 596124 tcp4 192.168.1.100:22 192.168.1.100:2604
cary ssh 596113 tcp4 192.168.1.100:2604192.168.1.100:22
A quick description of the addresses:
150.252.106.57 - external IP address of host computer, also running
dnscache for external lookups
192.168.1.1 - IP address of internal dnscache for 192.168.x.x addresses
192.168.1.100 - IP address of jail(8)'d host
192.168.53.1 - IP address of jail(8)'d tinydns server host
ssh debugging output shows:
[snip initial key-exchange]
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
{and ssh "hangs" here...}
The messages, security, and auth logs under /var/log in the jail'd host
are completly empty. Under the host machine logs , there is nothing as
well.
I'm at a loss of what else to trouble shoot. I'm not subscribed to the
list so if you could Cc: me, I would appreciate it.
Thank you in advance for any help offered!
Cary Mathews
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
