<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support">
    <title>gmane.os.pcbsd.support</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/562"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/561"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/560"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/559"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/557"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/555"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/548"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/546"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/545"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/543"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/542"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/541"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/540"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/539"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/538"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/537"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/536"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/535"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/534"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.os.pcbsd.support/533"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/562">
    <title>Re: Warden fail</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/562</link>
    <description>&lt;pre&gt;shell script
&lt;/pre&gt;</description>
    <dc:creator>Chris</dc:creator>
    <dc:date>2013-05-09T22:27:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/561">
    <title>Re: Warden fail</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/561</link>
    <description>&lt;pre&gt;
Hello.

Out of curiousity, which language is that, in which the above is written?

&lt;/pre&gt;</description>
    <dc:creator>Bret Busby</dc:creator>
    <dc:date>2013-05-09T20:27:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/560">
    <title>Re: Warden fail</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/560</link>
    <description>&lt;pre&gt;Possible patch
--- functions.sh.bak2013-05-09 12:26:29.985910685 -0500
+++ functions.sh2013-05-09 12:27:51.310012437 -0500
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -49,7 +49,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 ### Download the chroot
 downloadchroot() {
 
-  SYSVER="$(uname -r)"
+  SYSVER="$(uname -r | sed 's/\(.*\)\-.*/\1/')"
 
   local dFiles="base.txz doc.txz games.txz"
   if [ "$ARCH" = "amd64" ] ; then
_______________________________________________
Support mailing list
Support-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/support
&lt;/pre&gt;</description>
    <dc:creator>Chris</dc:creator>
    <dc:date>2013-05-09T17:35:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/559">
    <title>Warden fail</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/559</link>
    <description>&lt;pre&gt;

Hi,

Using warden I noticed a bug in it's jail creation code.

Pinpointed to certain lines in the functions.sh file:

### Download the chroot
50 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L50&amp;gt; 
downloadchroot() {
51 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L51&amp;gt; 

52 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L52&amp;gt; 
SYSVER="$(uname -r)"
53 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L53&amp;gt; 

54 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L54&amp;gt; 
localdFiles="base.txz doc.txz games.txz"
55 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L55&amp;gt; 
if [ "$ARCH" = "amd64" ] ;then
56 
&amp;lt;http://trac.pcbsd.org/browser/pcbsd/branches/9.1/src-sh/warden/scripts/backend/functions.sh#L56&amp;gt; 
dFiles="$dFiles lib32.txz"
57 
&amp;lt;http:&lt;/pre&gt;</description>
    <dc:creator>Chris</dc:creator>
    <dc:date>2013-05-09T17:31:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/557">
    <title>Re: A failed drive causes system to hang</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/557</link>
    <description>&lt;pre&gt;Checked: default.
Checked: default.
Nope, smartd doesn't run.
I don't think so. I'm nearly sure it took me longer than that to write
the errors down alone. And when I discovered the system lockup it was in
such state already. The next time I can take precise time measurements.
The disk is out of the array because I didn't put it back after RMA.
I RMA'd it because it used to cause precisely this kind of lockups on a
non-degraded array. And I've seen it in the installer running from an
entirely different device too.
I guess that after reproducing the issue and taking time measurements, I
should put the RMA'd drive back. I expect the problem to keep happening.
&lt;/pre&gt;</description>
    <dc:creator>Radio młodych bandytów</dc:creator>
    <dc:date>2013-04-15T06:24:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/555">
    <title>Re: A failed drive causes system to hang</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/555</link>
    <description>&lt;pre&gt;No.
I looked into BIOS and it can be controlled. 6 ports are divided into 2
triples and I can switch mode of each triple independently. One drive is
connected to one and two to the other.
Looks like there's a bug because both triples are set to ATA.
I left them like that for now.

Anyway, I got the hang again, so I can provide dmesg. I was not at the
computer when it happened, so there's only the last screen though...
pastebin.com/bjYtzPgs
&lt;/pre&gt;</description>
    <dc:creator>Radio młodych bandytów</dc:creator>
    <dc:date>2013-04-14T20:35:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/548">
    <title>Re: A failed drive causes system to hang</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/548</link>
    <description>&lt;pre&gt;No errors on any of these drives.
&lt;/pre&gt;</description>
    <dc:creator>Radio młodych bandytów</dc:creator>
    <dc:date>2013-04-14T18:31:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/546">
    <title>Re: A failed drive causes system to hang</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/546</link>
    <description>&lt;pre&gt;Sorry. I thought just the error was important. So here you are:
dmesg.boot:
http://pastebin.com/LFXPusMX
I haven't changed one bit myself. It may have been a change of defaults 
in PC-BSD. I just asked them about it.
Or maybe different drives use different drivers.

pciconf -lvbc:
http://pastebin.com/vvCKAWm1
zpool status:
http://pastebin.com/D3Av7x9X
zfs get all:
http://pastebin.com/4sT37VqZ
zpool get all tank1:
http://pastebin.com/HZJTJPa2
&lt;/pre&gt;</description>
    <dc:creator>Radio młodych bandytów</dc:creator>
    <dc:date>2013-04-14T10:34:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/545">
    <title>Re: A failed drive causes system to hang</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/545</link>
    <description>&lt;pre&gt;It's my private desktop and it's a semi-test system.
I don't care much if I loose it.
&lt;/pre&gt;</description>
    <dc:creator>Radio młodych bandytów</dc:creator>
    <dc:date>2013-04-14T10:26:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/543">
    <title>A failed drive causes system to hang</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/543</link>
    <description>&lt;pre&gt;Cross-post from freebsd-fs:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=333977+0+archive/2013/freebsd-fs/20130414.freebsd-fs

I have a failing drive in my array. I need to RMA it, but don't have
time and it fails rarely enough to be a yet another annoyance.
The failure is simple: it fails to respond.
When it happens, the only thing I found I can do is switch consoles. Any 
command hangs, login on different consoles hangs, apps hang.
I run PC-BSD 9.1.

On the 1st console I see a series of messages like:

(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Error 5, Periph was invalidated
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED

I've seen it happening even when running an installer from a different 
drive, while preparing installation (don't remember which step).

I have partial dmesg screenshots from an older failure (21st of December 
2012), transcript below:

Screen1:
(ada0:ahcich0:0:0:0): FLUSHCACHE40. ACB: (ea?) 00 00 00 00 (cut?)
(ada0:ahcich0:0:0:0): CAM status: Unconditionally Re-q&lt;/pre&gt;</description>
    <dc:creator>Radio młodych bandytów</dc:creator>
    <dc:date>2013-04-14T10:10:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/542">
    <title>Re: PC BSD 9 don't boot after update</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/542</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I what able to repair the pcbsd 9.1 system through booting
from the intallation iso file and on the first screen by
launching xterm.
I issued:
mount -t ufs /dev/ad0s1 /mnt
and then
cd /mnt/boot
There what a file loader and a file loader.old
I renamed loader to loader.defect and copied loader.old
to loader.

After a reboot the system what booting.

I assume that the new loader file don't work for
VirtualBox vdi files. has any one more informations
has the update process replaced other files ?

Jean-Jacques
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iEYEARECAAYFAlFdhwsACgkQM9JbiR3CwQty9ACcDR/TGUC0fwtqNQ0OaHdw0kVp
D3UAn1H3YIYmG+SAjtJkqck5sqJfSUt1
=UjoR
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Jean-Jacques Sarton</dc:creator>
    <dc:date>2013-04-04T13:58:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/541">
    <title>PC BSD 9 don't boot after update</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/541</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I have a PC-BSD system running within VirtualBox. Today I
have seen that an update is available and I have installed
it.

Trying to boot the system again the loader tell at last:

Can't work out which disk we are booting from.
Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0:

What can I do in order to recover the system ?

Regards
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iEYEARECAAYFAlFdd9MACgkQM9JbiR3CwQu6UQCePY1nhnm+24XipPEWN3Zu0Hnb
VXoAnRm9pHi2USsBhnz/g6radHtdTk3u
=EJI6
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Jean-Jacques Sarton</dc:creator>
    <dc:date>2013-04-04T12:53:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/540">
    <title>Automounting problem usb hd w/ UFS filesystem</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/540</link>
    <description>&lt;pre&gt;Hi,

I have a 1TB usb harddisk which I want to use for backups.
For this purpose I replaced the FAT filesystem by UFS2
w/ softupdates and journaling.

When I replug the device, the Mount Tray suddenly terminates
(segmentation fault, terminal output below). Once restarted, MT is
unable to detect the device, although it shows up in dmesg and can be
mounted manually. MT used to work fine with the FAT filesystem.

Did I format the usb drive incorrectly, or is this a bug in MT?


Commands used for ufs replacement (non-root):

$ fdisk -BIv da0
$ bsdlabel -w -B da0s1
$ newfs -L packardbell -U -j /dev/da0s1a


Outputs:

$ uname -a

FreeBSD pcbsd-3968 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Tue Nov 27
03:45:16 UTC 2012
root&amp;lt; at &amp;gt;darkstar:/usr/obj/pcbsd-build90/fbsd-source/9.1/sys/GENERIC  amd64

$ dmesg

(...)
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0: &amp;lt;Packard Bell Carbon 0000&amp;gt; Fixed Direct Access SCSI-2 device 
da0: 40.000MB/s transfers
da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
(...)


$ fdisk &lt;/pre&gt;</description>
    <dc:creator>Erwin Geerdink</dc:creator>
    <dc:date>2013-03-17T20:41:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/539">
    <title>Re: Sound settings aren't saved after reboot.</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/539</link>
    <description>&lt;pre&gt;
Mmm, I see I've changed this as well. 
hw.snd.default_auto=0

Johann

On Monday 18 February 2013 02:32:18 Ted Hatfield wrote:
on hdaa0
at
Support mailing list
Support-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/support
&lt;/pre&gt;</description>
    <dc:creator>Johann Hugo</dc:creator>
    <dc:date>2013-02-18T09:21:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/538">
    <title>Re: Sound settings aren't saved after reboot.</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/538</link>
    <description>&lt;pre&gt;
After some advice from another forum member I've gotten closer to 
diagnosing the problem as well as creating a work-around.

First of all the sound configuration utility in the PCBSD control panel 
sets the hw.snd.default_unit=0 value in /etc/sysctl.conf.

Unfortunately this setting does not stick.  When I reboot the machine and 
login to the desktop the sysctl value is changed back to 
hw.snd.default_unit=3.

This means one of two things.  The value is never changed when sysctl is 
run during the RC, or the value is changed somtime after sysctl is loaded.

If you can tell me how to stop pcbsd from calling startx, I'll see if the 
sysctl variable is changed before or after x loads.


My workaround was to create a script that calls 
sudo /sbin/sysctl hw.snd.default_unit=0
and then add the script in my .xprofile.

Can someone verify that I need to use sudo to change the sysctl variable 
or can you change that variable with user privileges.  I couldn't find the 
privilege level required to change particular s&lt;/pre&gt;</description>
    <dc:creator>Ted Hatfield</dc:creator>
    <dc:date>2013-02-18T08:32:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/537">
    <title>Re: Sound settings aren't saved after reboot.</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/537</link>
    <description>&lt;pre&gt;Mine also defaults to the last pcm device it detects. 

You can try to add this in /etc/sysctl.conf
hw.snd.default_unit=0

Johann

On Friday 15 February 2013 23:40:30 Ted Hatfield wrote:
hdaa0
Support mailing list
Support-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/support
&lt;/pre&gt;</description>
    <dc:creator>Johann Hugo</dc:creator>
    <dc:date>2013-02-18T06:37:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/536">
    <title>Sound settings aren't saved after reboot.</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/536</link>
    <description>&lt;pre&gt;
I've just recenetly installed PC-BSD on my home machine and I am very 
impressed with the Isotope Edition.

I've run into a problem that I hope someone can help me with.

FreeBSD detects 4 different pcm devices.

pcm0: &amp;lt;Realtek ALC888 (Analog 7.1/2.0)&amp;gt; at nid 20,22,21,23 and 25,26,24 on hdaa0
pcm1: &amp;lt;Realtek ALC888 (Front Analog Headphones)&amp;gt; at nid 27 on hdaa0
pcm2: &amp;lt;Realtek ALC888 (Rear Digital)&amp;gt; at nid 30 and 31 on hdaa0
pcm3: &amp;lt;NVIDIA MCP78 (Digital)&amp;gt; at nid 5 on hdaa1

Once the machine is booted into kde, the default is pcm3.  I load the 
sound configuration in the control panel and change the default to use 
pcm0.

However if I shutdown the machine and reboot it changes the default back 
to pcm3.

Can someone enlighten me as to the specifics of where it's setting this at 
and how to track down what's resetting that parameter.

Thanks,

Ted Hatfield
&lt;/pre&gt;</description>
    <dc:creator>Ted Hatfield</dc:creator>
    <dc:date>2013-02-16T05:40:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/535">
    <title>Warden problem</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/535</link>
    <description>&lt;pre&gt;Hi all,

After applying system update from 9.0 to 9.1 i am having two wardens in my
system.

In Old warden i can't start my jail and new one is not taking it directly.
i don't know what exactly happening how to revert to old warden for time
being for exporting jail then importing back to new one. and removing old
warden from system.

http://forums.pcbsd.org/showthread.php?t=19278
Thanks,
Jay.
_______________________________________________
Support mailing list
Support-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org
http://lists.pcbsd.org/mailman/listinfo/support
&lt;/pre&gt;</description>
    <dc:creator>Jay Patel</dc:creator>
    <dc:date>2013-02-14T12:58:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/534">
    <title>Fwd: [PC-BSD Announce] PC-BSD 9.1 now available!</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/534</link>
    <description>&lt;pre&gt;Hello.

Forwarding the message below to the list, as Reply did not default to the list.

I  downloaded the first ISO from AARnet, which is the source I will
probably use for the second.

I assume (but am not sure) that running it live from the optical disc,
is done from the same ISO as the installation ISO.

&lt;/pre&gt;</description>
    <dc:creator>Bret Busby</dc:creator>
    <dc:date>2013-02-06T13:22:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/533">
    <title>Re: [PC-BSD Announce] PC-BSD 9.1 now available!</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/533</link>
    <description>&lt;pre&gt;Hello

Would the link below not work ?

ftp://mirrors.isc.org/pub/pcbsd/9.1/i386/PCBSD9.1-x86-DVD.iso

I am sure you can use the link below, if your wanting 64bit

ftp://mirrors.isc.org/pub/pcbsd/9.1/

Regards,
Angus
&lt;/pre&gt;</description>
    <dc:creator>Angus Robinson</dc:creator>
    <dc:date>2013-02-06T09:46:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.os.pcbsd.support/532">
    <title>Re: [PC-BSD Announce] PC-BSD 9.1 now available!</title>
    <link>http://permalink.gmane.org/gmane.os.pcbsd.support/532</link>
    <description>&lt;pre&gt;it does appear to require javascript. i turned it off and the list of releases wouldn't appear

you can go to one of the mirrors though. i would usually use mirror.internode.on.net (/pub/pcbsd/9.1/...) however the date on the file is dec 05. the main aust mirror is mirror.aarnet.edu.au , a usa mirror is mirrors.isc.org 

they also have the same datestamp though, perhaps it's just me

hope that helps

regards
andrew



-----Original Message-----
From: support-bounces-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org [mailto:support-bounces-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org] On Behalf Of Bret Busby
Sent: Wednesday, 6 February 2013 5:18 PM
To: support-Fhbtn2kkCAMmbxgs1yVkuA&amp;lt; at &amp;gt;public.gmane.org
Subject: Re: [PC-BSD Support] [PC-BSD Announce] PC-BSD 9.1 now available!

On 19/12/2012, Kris Moore &amp;lt;kris-E1R8x85rdljYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

Hello.

Do we need to be running javascript, to download the ISO's?

I have visited the web site, and the link above, but cannot get to a
web page to download the 9.1 ISO's.
&lt;/pre&gt;</description>
    <dc:creator>Perry, Andrew</dc:creator>
    <dc:date>2013-02-06T06:44:58</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.os.pcbsd.support">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.os.pcbsd.support</link>
  </textinput>
</rdf:RDF>
