Re: Some questions about jails on FreeBSD9.0-RC1
>> I have setup one jail using ezjail. My first surprise is that >> ezjail only installs -RELEASE versions and not RC versions. Ok, I >> supouse that it is normal. But my first question is: can I install a >> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? I have upgraded my ezjails using something like: env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r 9.0-RC1 upgrade install This is some hassle, for example, one has to upgrade /etc and /var in /usr/jails/newjail by hand. (And maybe even more, not completely sure there.) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On Tue, Oct 25, 2011 at 3:15 AM, Claude Buisson wrote: > Hi, > > When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to > ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to > atapicam (and reverting from cdN to acdN of course), vlc was OK again. Hi, Would vlc have worked if, while ATA_CAM was enabled, there was a symlink so that /dev/acd0 -> cd0 ? -- Craig Rodrigues rodr...@crodrigues.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Some questions about jails on FreeBSD9.0-RC1
Le Tue, 25 Oct 2011 22:52:55 +0200, carlopmart a écrit : Hello, > I have installed one FreeBSD 9.0-RC1 host to run different services > (dns, smtp and www only) using jails. This host has two physical > nics: em0 and em1. em0 is assigned to pyhiscal host, and I would like > to assign em1 to jails. But em0 and em1 are on different networks: > em0 is on 192.168.1.0/24 and em1 in 192.168.2.0/29. > > I have setup one jail using ezjail. My first surprise is that > ezjail only installs -RELEASE versions and not RC versions. Ok, I > supouse that it is normal. But my first question is: can I install a > FreeBSD 8.2 jail under a FreeBSD 9.0 host?? You may run 8.2 installed ports on 9.0 by using the port /usr/ports/misc/compat8x/ But I suggest to upgrade the port ASAP. > And the real question: How do I need to configure network under > this jail to access it? I have configured ifconfig param for em1 on > host's rc.conf, but what about the default route under this jail?? I > thought to use pf rules, but I am not sure. jail enforces the use of the jail IP address in the jail, but that's all. Just enable routing on the host. Also be sure that the host's daemons don't bind on the jail IP address, as explained in the man page of jail (Setting up the Host Environment). Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Some questions about jails on FreeBSD9.0-RC1
On Tue, Oct 25, 2011 at 11:52 PM, carlopmart wrote:
> Hi all,
>
> I have installed one FreeBSD 9.0-RC1 host to run different services (dns,
> smtp and www only) using jails. This host has two physical nics: em0 and
> em1. em0 is assigned to pyhiscal host, and I would like to assign em1 to
> jails. But em0 and em1 are on different networks: em0 is on 192.168.1.0/24
> and em1 in 192.168.2.0/29.
>
> I have setup one jail using ezjail. My first surprise is that ezjail only
> installs -RELEASE versions and not RC versions. Ok, I supouse that it is
> normal. But my first question is: can I install a FreeBSD 8.2 jail under a
> FreeBSD 9.0 host??
ezjail doesn't necessarily install a release version. < ezjail-admin
update -p -i > will install the basejail from your source.
> And the real question: How do I need to configure network under this jail
> to access it? I have configured ifconfig param for em1 on host's rc.conf,
> but what about the default route under this jail?? I thought to use pf
> rules, but I am not sure.
gateway_enable="YES"
should take care of this.
>
> Thanks.
> --
> CL Martinez
> carlopmart {at} gmail {d0t} com
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
Regards
--
George Kontostanos
aisecure.net
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 9 IPv6 conformance test report
Since I have been receiving private reports on the test failures, I thought I just post the test report as executed against the upcoming FreeBSD 9.0 release in my own setup, so you can see where the baseline is. More test reports will be posted here. http://people.freebsd.org/~qingli/ct-freebsd-9/ I am going over each failure and providing the fix. Please let me know if you already have a suggested patch that you are willing to share. Thanks. -- Qing ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Some questions about jails on FreeBSD9.0-RC1
Hi all,
I have installed one FreeBSD 9.0-RC1 host to run different services
(dns, smtp and www only) using jails. This host has two physical nics:
em0 and em1. em0 is assigned to pyhiscal host, and I would like to
assign em1 to jails. But em0 and em1 are on different networks: em0 is
on 192.168.1.0/24 and em1 in 192.168.2.0/29.
I have setup one jail using ezjail. My first surprise is that ezjail
only installs -RELEASE versions and not RC versions. Ok, I supouse that
it is normal. But my first question is: can I install a FreeBSD 8.2 jail
under a FreeBSD 9.0 host??
And the real question: How do I need to configure network under this
jail to access it? I have configured ifconfig param for em1 on host's
rc.conf, but what about the default route under this jail?? I thought to
use pf rules, but I am not sure.
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd couldn't resolve host name on system boot
On Tue, 25 Oct 2011, Miroslav Lachman wrote: Paul Schenkeveld wrote: On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote: On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: The one shortcoming of netwait is that it doesn't support waiting for multiple NICs. Some people have dual-homed environments where they really would like to wait for both, say, em0 and em1, to come up and be functional before any more scripts are started. I left that as a project for someone else, but it's something that should be added given its importance. How would you like to see multiple interfaces implemented: - All interfaces must be up at the same time - Probe interfaces one by one, proceed to the next when an interface up or bail out when any interface stays down until the loop times out 1) Each interface should be checked in the order specified. 2) Each ping probe should be done using that interface (ping -I). From ping(8): -I iface Source multicast packets with the given interface address. This flag only applies if the ping destination is a multicast address. I believe that for unicast the interface used is determined by looking up the destination address in the routing table (unless overridden by a packet filter that changes the next hop). Another way to influence the next hop selection and the outgoing interface is using setfib(1) but apart from rc.d/jail I see no fib support in rc.conf at all. OT: Unfortunately there are two PRs with patches to add setfib support to rc.subr, but both of them are laying under the dust without attention of committers. conf/132483 conf/132851 I tried to bring it to attention in freebsd-rc@ without any luck. (same as my attempt to add support for cpuset conf/142434). So we have features / tools without centralized support in rc.subr and if anybody want to use them, must do it by some hacky ways in rc.local etc. http://lists.freebsd.org/pipermail/freebsd-rc/2010-January/001816.html I have not done any debugging, but it seems to me this may be a serialization issue. For me it almost always occurs on MP systems. I have an 8-cpu system that never starts NTP correctly, a 2-cpu laptop that mostly never does. I have never experienced this with a single processor system. My fix is simply to pick a number of geographically close open NTP servers. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd couldn't resolve host name on system boot
Paul Schenkeveld wrote: On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote: On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: The one shortcoming of netwait is that it doesn't support waiting for multiple NICs. Some people have dual-homed environments where they really would like to wait for both, say, em0 and em1, to come up and be functional before any more scripts are started. I left that as a project for someone else, but it's something that should be added given its importance. How would you like to see multiple interfaces implemented: - All interfaces must be up at the same time - Probe interfaces one by one, proceed to the next when an interface up or bail out when any interface stays down until the loop times out 1) Each interface should be checked in the order specified. 2) Each ping probe should be done using that interface (ping -I). From ping(8): -I iface Source multicast packets with the given interface address. This flag only applies if the ping destination is a multicast address. I believe that for unicast the interface used is determined by looking up the destination address in the routing table (unless overridden by a packet filter that changes the next hop). Another way to influence the next hop selection and the outgoing interface is using setfib(1) but apart from rc.d/jail I see no fib support in rc.conf at all. OT: Unfortunately there are two PRs with patches to add setfib support to rc.subr, but both of them are laying under the dust without attention of committers. conf/132483 conf/132851 I tried to bring it to attention in freebsd-rc@ without any luck. (same as my attempt to add support for cpuset conf/142434). So we have features / tools without centralized support in rc.subr and if anybody want to use them, must do it by some hacky ways in rc.local etc. http://lists.freebsd.org/pipermail/freebsd-rc/2010-January/001816.html Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On 10/25/2011 15:08, Daniel O'Connor wrote: On 25/10/2011, at 23:24, Jeremy Chadwick wrote: These may not be the same problem, but I think they are related (a not so well documented change in the kerm interface). You want atapicam(4). This is not the same thing as "options ATA_CAM". See /sys/conf/NOTES. Whether or not it works with audio CDs is unknown to me. atapicam is a bridge for the old ATA code to put ATAPI devices _only_ on CAM (as well as the ATA infrastructure). Hence they appear as /dev/cd0 and so on. As I said: I know it (after 16 years of FreeBSD use ...) ATA_CAM puts _all_ ATA devices on CAM, so you should be able to access your audio CD that way. I just tried and it ripped a CD fine using cdparanoia and cdcontrol seemed to play it OK (although I don't have the analogue output of this drive hooked up to the audio system). I just played a CD with cdcontrol on a ATA_CAMed 9.0 system from Sept 25 (hooked to the audio), but do not know what is proven that way: VLC see the tracks of the audio CD and may even identifiy them with cddb, but cannot play them (see the error messages). So my current conclusion (?) is that the problem lies with the userland librairies (cdda, ..) This is not to say that there isn't a bug in the ATA_CAM code :) I will do another test on 9.0 (after rebuilding the ports), and eventually get rid of ATA_CAM and wait (im)patiently for a knowledgeable one to have a look at the problem. If this is a real problem, I may hope that it will appear after the release of 9.0 and its use in the real world. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
Jeremy Chadwick schreef: On Tue, Oct 25, 2011 at 10:46:55PM +1030, Daniel O'Connor wrote: On 25/10/2011, at 22:32, Miroslav Lachman wrote: Well i did use the single user mode ! And the safe mode ! But they all gave me that error. So the did load the loader.conf file. I think modules are loaded before displaying boot menu, where you can choose to boot in to single user mode. But you can enter the boot loader prompt, where you can unload already loaded modules or load new modules by its name, so you don't need to edit loader.conf for one time boot option. They aren't loaded before displaying the menu, but the list of modules to load is worked out then. If you want to boot without loading the modules listed in loader.conf you need to break into the loader and type.. unload boot -s (or whatever options you want) Yup, correct. The person who said "single-user mode doesn't read loader.conf!" is absolutely incorrect. I really did select number 4 after the reboot, i even rebooted multiple times! I can imagine myself missing number 4 reading the options and not hitting number 4 within the 10 seconds the first time, but not the second and third time. Or my keyboard did not work at the boot loader menu, wich i can not test now because it is recompiling all my ports and i do not want to interupt a working deamon .. But anyhow it gave me the above error! I did not think about going into the loader and unload the iscsi module, so i did remove it with the live cd using fixit from the laoder.conf file. Now all is fine. regards Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd couldn't resolve host name on system boot
On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote: > On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: > > On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: > > > The one shortcoming of netwait is that it doesn't support waiting for > > > multiple NICs. Some people have dual-homed environments where they > > > really would like to wait for both, say, em0 and em1, to come up and be > > > functional before any more scripts are started. I left that as a > > > project for someone else, but it's something that should be added given > > > its importance. > > > > How would you like to see multiple interfaces implemented: > > > > - All interfaces must be up at the same time > > - Probe interfaces one by one, proceed to the next when an interface > > up or bail out when any interface stays down until the loop times > > out > > 1) Each interface should be checked in the order specified. > 2) Each ping probe should be done using that interface (ping -I). >From ping(8): -I iface Source multicast packets with the given interface address. This flag only applies if the ping destination is a multicast address. I believe that for unicast the interface used is determined by looking up the destination address in the routing table (unless overridden by a packet filter that changes the next hop). Another way to influence the next hop selection and the outgoing interface is using setfib(1) but apart from rc.d/jail I see no fib support in rc.conf at all. > 3) In the case of success, the next interface should be checked (e.g. go > back to step #1 but for the next interface defined. > 4) In the case of failure, output a message on-screen (similar to what > we already do) and continue on with the next interface check. > > So I imagine the variables for this would need to become something like: > > netwait_em0_ip="4.2.2.1 4.2.2.2" > netwait_em1_ip="192.168.1.1 192.168.1.2" > > You get the idea -- think ifconfig_* in style. This also suggests that ping can be forced to send out packets thru a certain interface which I think is misleading. Where I see the testing of multiple interfaces becoming important is in the case where interfaces are bonded using lagg(4). I usually have RTP disabled on server ports but started to see problems with ntpd and other services when I started to use LACP trunks. Paul Schenkeveld ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On 10/25/2011 14:54, Jeremy Chadwick wrote: On Tue, Oct 25, 2011 at 01:18:47PM +0200, Claude Buisson wrote: On 10/25/2011 12:52, Daniel O'Connor wrote: On 25/10/2011, at 20:45, Claude Buisson wrote: When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to atapicam (and reverting from cdN to acdN of course), vlc was OK again. It seems that I am not the only one having this kind of problem, as I found (for example) this message on questions@ (for releng9): http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html Is this a known problem ? Is somebody working on it ? Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC) It may be trying old style ATA ioctls based on the device name. VLC recognize the tracks and jump quickly from one to the following, without playing it, and with a flow of messages: [0x2caf2a3c] cdda access error: Could not set block size [0x2caf2a3c] cdda access error: cannot read sector n where the sector number is incremented, and then emit (2 times if I remenber): [0x2af28bc] es demux error: cannot peek Sorry for having ommited these messages in the previous mail. I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a proposal by avg@ related to libxine: http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html These may not be the same problem, but I think they are related (a not so well documented change in the kerm interface). You want atapicam(4). This is not the same thing as "options ATA_CAM". See /sys/conf/NOTES. Whether or not it works with audio CDs is unknown to me. I *know* the difference between atapicam and ATA_CAM ;-) I have done other tests on 8.X and 7.X, and found that audio CDs cannot be played with atapicam. BUT, I understood (wrongly ?) that ATA_CAM was the way to go starting with 9.X, which imply that the traditionnal acdN interface will disappear. A valid answer to my question may be: "we - kernel developpers - know about it, but we don't care, and the problem must be solved by the userland/applications developpers". With some obvious consequences on the upgrading or not upgrading of end users systems. Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
2011/10/25 Jeremy Chadwick > On Tue, Oct 25, 2011 at 10:46:55PM +1030, Daniel O'Connor wrote: > > > > On 25/10/2011, at 22:32, Miroslav Lachman wrote: > > > > > >> Well i did use the single user mode ! > > >> And the safe mode ! > > >> But they all gave me that error. > > >> So the did load the loader.conf file. > > > > > > I think modules are loaded before displaying boot menu, where you can > choose to boot in to single user mode. > > > But you can enter the boot loader prompt, where you can unload already > loaded modules or load new modules by its name, so you don't need to edit > loader.conf for one time boot option. > > > > They aren't loaded before displaying the menu, but the list of modules to > load is worked out then. > > > > If you want to boot without loading the modules listed in loader.conf you > need to break into the loader and type.. > > unload > > boot -s > > (or whatever options you want) > > Yup, correct. The person who said "single-user mode doesn't read > loader.conf!" is absolutely incorrect. > Sorry I thought so =( > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On 25/10/2011, at 23:24, Jeremy Chadwick wrote: >> These may not be the same problem, but I think they are related (a not so >> well >> documented change in the kerm interface). > > You want atapicam(4). This is not the same thing as "options ATA_CAM". > See /sys/conf/NOTES. > > Whether or not it works with audio CDs is unknown to me. atapicam is a bridge for the old ATA code to put ATAPI devices _only_ on CAM (as well as the ATA infrastructure). Hence they appear as /dev/cd0 and so on. ATA_CAM puts _all_ ATA devices on CAM, so you should be able to access your audio CD that way. I just tried and it ripped a CD fine using cdparanoia and cdcontrol seemed to play it OK (although I don't have the analogue output of this drive hooked up to the audio system). This is not to say that there isn't a bug in the ATA_CAM code :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On Tue, Oct 25, 2011 at 01:18:47PM +0200, Claude Buisson wrote: > On 10/25/2011 12:52, Daniel O'Connor wrote: > > > >On 25/10/2011, at 20:45, Claude Buisson wrote: > >>When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to > >>ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to > >>atapicam (and reverting from cdN to acdN of course), vlc was OK again. > >> > >>It seems that I am not the only one having this kind of problem, as I found > >>(for > >>example) this message on questions@ (for releng9): > >> > >>http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html > >> > >>Is this a known problem ? Is somebody working on it ? > > > >Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? > > > > Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building > VLC) > > > >It may be trying old style ATA ioctls based on the device name. > > > > VLC recognize the tracks and jump quickly from one to the following, without > playing it, and with a flow of messages: > > [0x2caf2a3c] cdda access error: Could not set block size > [0x2caf2a3c] cdda access error: cannot read sector n > > where the sector number is incremented, and then emit (2 times if I remenber): > > [0x2af28bc] es demux error: cannot peek > > Sorry for having ommited these messages in the previous mail. > > I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a > proposal by avg@ related to libxine: > > http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html > > These may not be the same problem, but I think they are related (a not so well > documented change in the kerm interface). You want atapicam(4). This is not the same thing as "options ATA_CAM". See /sys/conf/NOTES. Whether or not it works with audio CDs is unknown to me. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
On Tue, Oct 25, 2011 at 10:46:55PM +1030, Daniel O'Connor wrote: > > On 25/10/2011, at 22:32, Miroslav Lachman wrote: > > > >> Well i did use the single user mode ! > >> And the safe mode ! > >> But they all gave me that error. > >> So the did load the loader.conf file. > > > > I think modules are loaded before displaying boot menu, where you can > > choose to boot in to single user mode. > > But you can enter the boot loader prompt, where you can unload already > > loaded modules or load new modules by its name, so you don't need to edit > > loader.conf for one time boot option. > > They aren't loaded before displaying the menu, but the list of modules to > load is worked out then. > > If you want to boot without loading the modules listed in loader.conf you > need to break into the loader and type.. > unload > boot -s > (or whatever options you want) Yup, correct. The person who said "single-user mode doesn't read loader.conf!" is absolutely incorrect. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd couldn't resolve host name on system boot
On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote:
> On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
> > The one shortcoming of netwait is that it doesn't support waiting for
> > multiple NICs. Some people have dual-homed environments where they
> > really would like to wait for both, say, em0 and em1, to come up and be
> > functional before any more scripts are started. I left that as a
> > project for someone else, but it's something that should be added given
> > its importance.
>
> How would you like to see multiple interfaces implemented:
>
> - All interfaces must be up at the same time
> - Probe interfaces one by one, proceed to the next when an interface
> up or bail out when any interface stays down until the loop times
> out
1) Each interface should be checked in the order specified.
2) Each ping probe should be done using that interface (ping -I).
3) In the case of success, the next interface should be checked (e.g. go
back to step #1 but for the next interface defined.
4) In the case of failure, output a message on-screen (similar to what
we already do) and continue on with the next interface check.
So I imagine the variables for this would need to become something like:
netwait_em0_ip="4.2.2.1 4.2.2.2"
netwait_em1_ip="192.168.1.1 192.168.1.2"
You get the idea -- think ifconfig_* in style.
> Another shortcoming: ipv6 support...
>
> The patch below adds ipv6.
>
> One caveat, ping6 is used if a word in netwait_ip contains at least a
> colon so hostnames in netwait_ip are always pinged using ipv4.
>
> {snip}
Others will need to test IPv6 support -- I do not use it/have it
available.
It's a matter of opinion, but for IPv6 hosts/addresses, there should be
a separate variable, probably netwait_ipv6 (or netwait_XXX_ipv6 if you
go with the above ideal). The problem is that our existing ipv6
variables in rc.conf all conform with ipv6_*, so I'm not sure what
people prefer. But then maybe the netwait_ip variable should be named
netwait_*_ipv4... I'll let others hash this out, but I would prefer the
former, since then you end up with something like this:
netwait_em0_ipv4="4.2.2.1 4.2.2.2"
netwait_em0_ipv6="fe80::202:b3ff:fe1e:8329"
(And in this case you would want to test IPv4 connectivity *as well* as
IPv6; two separate IP layers, thus both be tested separately; e.g. if
4.2.2.1 responds, don't just consider em0 working necessarily, because
there may be daemons that are IPv6-centric that depend on packets flowing
through em0. Those using tunnel brokers, however, probably won't
benefit from this since netwait starts before such brokers/daemons).
You get the idea.
The problem is that this breaks the existing variable syntax and will
upset a lot of existing users. Hmm... Not sure about this one. Gosh,
I could really go either way.
One final point, regarding ping6:
ping6 lacks the -t argument that ping has. This is bad bad bad. In
fact, I have to state up front that adding IPv6 support **should not**
be done to this script until ping6 supports -t. I cannot stress this
enough. The -t 1 piece is *very* important for proper behaviour. The
nuances of the flag often come as a surprise to people. I can look at
the ping code to figure out how -t works internally and probably submit
a patch for ping6 that does this, but of course I have no way to test
it. :-)
IPv6 support is something that others will need to work on in general
though -- I do not use it, so others are better-suited.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, US |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
On 25/10/2011, at 22:32, Miroslav Lachman wrote: > >> Well i did use the single user mode ! >> And the safe mode ! >> But they all gave me that error. >> So the did load the loader.conf file. > > I think modules are loaded before displaying boot menu, where you can choose > to boot in to single user mode. > But you can enter the boot loader prompt, where you can unload already loaded > modules or load new modules by its name, so you don't need to edit > loader.conf for one time boot option. They aren't loaded before displaying the menu, but the list of modules to load is worked out then. If you want to boot without loading the modules listed in loader.conf you need to break into the loader and type.. unload boot -s (or whatever options you want) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
Johan Hendriks wrote: timp schreef: For installworld you should boot to 'single user mode'. This mode doesn't read loader.conf and much more. [...] Well i did use the single user mode ! And the safe mode ! But they all gave me that error. So the did load the loader.conf file. I think modules are loaded before displaying boot menu, where you can choose to boot in to single user mode. But you can enter the boot loader prompt, where you can unload already loaded modules or load new modules by its name, so you don't need to edit loader.conf for one time boot option. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On 10/25/2011 12:52, Daniel O'Connor wrote: On 25/10/2011, at 20:45, Claude Buisson wrote: When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to atapicam (and reverting from cdN to acdN of course), vlc was OK again. It seems that I am not the only one having this kind of problem, as I found (for example) this message on questions@ (for releng9): http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html Is this a known problem ? Is somebody working on it ? Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC) It may be trying old style ATA ioctls based on the device name. VLC recognize the tracks and jump quickly from one to the following, without playing it, and with a flow of messages: [0x2caf2a3c] cdda access error: Could not set block size [0x2caf2a3c] cdda access error: cannot read sector n where the sector number is incremented, and then emit (2 times if I remenber): [0x2af28bc] es demux error: cannot peek Sorry for having ommited these messages in the previous mail. I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a proposal by avg@ related to libxine: http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html These may not be the same problem, but I think they are related (a not so well documented change in the kerm interface). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can audio CDs be played with ATA_CAM ?
On 25/10/2011, at 20:45, Claude Buisson wrote: > When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to > ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to > atapicam (and reverting from cdN to acdN of course), vlc was OK again. > > It seems that I am not the only one having this kind of problem, as I found > (for > example) this message on questions@ (for releng9): > > http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html > > Is this a known problem ? Is somebody working on it ? Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? It may be trying old style ATA ioctls based on the device name. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
can audio CDs be played with ATA_CAM ?
Hi, When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to atapicam (and reverting from cdN to acdN of course), vlc was OK again. It seems that I am not the only one having this kind of problem, as I found (for example) this message on questions@ (for releng9): http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html Is this a known problem ? Is somebody working on it ? Thanks, Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
timp schreef: For installworld you should boot to 'single user mode'. This mode doesn't read loader.conf and much more. Look to the handbook or /usr/src/Makefile for upgrage instructions $ cat /usr/src/Makefile ... # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3.& 4. can be combined by using the "kernel" target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) ... -- View this message in context: http://freebsd.1045724.n5.nabble.com/From-8-stable-to-9-0-RC1-iscsi-panic-tp4935512p4935645.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Well i did use the single user mode ! And the safe mode ! But they all gave me that error. So the did load the loader.conf file. Gr Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
For installworld you should boot to 'single user mode'. This mode doesn't read loader.conf and much more. Look to the handbook or /usr/src/Makefile for upgrage instructions $ cat /usr/src/Makefile ... # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. & 4. can be combined by using the "kernel" target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) ... -- View this message in context: http://freebsd.1045724.n5.nabble.com/From-8-stable-to-9-0-RC1-iscsi-panic-tp4935512p4935645.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd couldn't resolve host name on system boot
On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
> The one shortcoming of netwait is that it doesn't support waiting for
> multiple NICs. Some people have dual-homed environments where they
> really would like to wait for both, say, em0 and em1, to come up and be
> functional before any more scripts are started. I left that as a
> project for someone else, but it's something that should be added given
> its importance.
How would you like to see multiple interfaces implemented:
- All interfaces must be up at the same time
- Probe interfaces one by one, proceed to the next when an interface
up or bail out when any interface stays down until the loop times
out
Another shortcoming: ipv6 support...
The patch below adds ipv6.
One caveat, ping6 is used if a word in netwait_ip contains at least a
colon so hostnames in netwait_ip are always pinged using ipv4.
Paul Schenkeveld
--- src/etc/rc.d/netwait.orig 2011-06-22 08:27:32.0 +0200
+++ src/etc/rc.d/netwait2011-10-25 11:09:16.0 +0200
@@ -21,7 +21,7 @@
netwait_start()
{
- local ip rc count output link
+ local ip rc count output link ping_cmd
if [ -z "${netwait_ip}" ]; then
err 1 "You must define one or more IP addresses in netwait_ip"
@@ -72,7 +72,13 @@
count=1
while [ ${count} -le ${netwait_timeout} ]; do
- /sbin/ping -t 1 -c 1 -o ${ip} >/dev/null 2>&1
+ case ${ip} in
+ *:*)
+ ping_cmd="/sbin/ping6 -c 1 -o";;
+ *)
+ ping_cmd="/sbin/ping -t 1 -c 1 -o";;
+ esac
+ ${ping_cmd} ${ip} >/dev/null 2>&1
rc=$?
if [ $rc -eq 0 ]; then
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd couldn't resolve host name on system boot
Jeremy Chadwick wrote: On Tue, Oct 25, 2011 at 12:50:29AM +0200, Miroslav Lachman wrote: I have a problem with ntpd on many of our servers running 8.2-RELEASE or newer. Some of them are newly installed, most of them are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC. Ntpd can't resolve host names on boot. This error did not existed on 7.x [...] I know there is rc.d/netwait in 8-STABLE, but it is not available on 8.2-RELEASE and I think that there is some regression as this error was not there in the time of FreeBSD 7.x. The problem is that the networking layer is not TRULY available by the time ntpd starts. This does have to do with NIC drivers, but the same behaviour can be seen on all NICs, including excellent ones like em(4). You can use the rc.conf netwait_* variables to solve this problem. I'm the author of the script that got committed so that's how I know. :-) An example: netwait_enable="yes" netwait_ip="4.2.2.1 4.2.2.2" netwait_if="em0" If you need help setting this up, let me know. Yes, I know you are the author and I tested one of the earlier version floating around a mailing list, and I already have it on some 8-STABLE machines where it is included in base /etc/rc.d - thank you for your work! My main concern is that I never needed it on previous FreeBSD versions. I am using ntpdate / ntpd from FreeBSD 4.x days and it always worked fine. So there is some "bad change" on FreeBSD 8.x. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: From 8-stable to 9.0 RC1 iscsi panic
Johan Hendriks schreef: I have a desktop test machine, and i decided to do a upgarde to 9.0RC1. I dis the buildworld, build kernel, and installkernel step, Then the reboot to do the installworld step. But it panics And it stops very early at the boot process. The console looks like the following (typed by hand) Copyright (c) 1992-2011 The FreeBSD project. Copyright (c) 1979 ... The regents of the Uni FreeBSD is a regited trade. FreeBSD 9.0-RC1 #0: Tue Oct 25 08:58:57 CEST 2011 root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL amd64 can't re-use a leaf (geom_label)! can't re-use a leaf (iscsi_initiator_max_pdus)! can't re-use a leaf (iscsi_initiator_max_sessions)! can't re-use a leaf (iscsi_initiator)! module_register: module iscsi already excists! Module iscsi failed to register: 17 module_register: module g_label already excists! Module g_label failed to register: 17 CPU: intel(R) Core(TM)2 Quad CPU origen ... Features= ... Features2= AMD Features= AMD Featurres2= .. TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 3298799616 (3145 MB) iscsi: version 2.2.4.2 module_register_init: MOD_LOAD (kdbmux, 0x8058522d, 0) error 6 panic: make_dev_credv: bad si_name (error=17, si_name=iscsi) cpuid = 0 Uptime: 1s Automatic reboot in 15 second - press a key on the console to abort Any idea what i can do? regards Johan A reply to myself. I booted with the live cd. I removed the iscsi part in /boot/loader.conf and now it is doing the installworld step. The ad10s1a partition was not clean maybe it got something to do with that. I will try to load the iscsi initiator after the installworld part and see how it goes. thanks regards Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
From 8-stable to 9.0 RC1 iscsi panic
I have a desktop test machine, and i decided to do a upgarde to 9.0RC1. I dis the buildworld, build kernel, and installkernel step, Then the reboot to do the installworld step. But it panics And it stops very early at the boot process. The console looks like the following (typed by hand) Copyright (c) 1992-2011 The FreeBSD project. Copyright (c) 1979 ... The regents of the Uni FreeBSD is a regited trade. FreeBSD 9.0-RC1 #0: Tue Oct 25 08:58:57 CEST 2011 root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL amd64 can't re-use a leaf (geom_label)! can't re-use a leaf (iscsi_initiator_max_pdus)! can't re-use a leaf (iscsi_initiator_max_sessions)! can't re-use a leaf (iscsi_initiator)! module_register: module iscsi already excists! Module iscsi failed to register: 17 module_register: module g_label already excists! Module g_label failed to register: 17 CPU: intel(R) Core(TM)2 Quad CPU origen ... Features= ... Features2= AMD Features= AMD Featurres2= .. TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 3298799616 (3145 MB) iscsi: version 2.2.4.2 module_register_init: MOD_LOAD (kdbmux, 0x8058522d, 0) error 6 panic: make_dev_credv: bad si_name (error=17, si_name=iscsi) cpuid = 0 Uptime: 1s Automatic reboot in 15 second - press a key on the console to abort Any idea what i can do? regards Johan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
