Exhibiting in June
Exhibiting in June? I'd love to help and its what I do best. I help exhibitors with banner stands, portable displays, custom displays, and shipping or freight coordination. I can always be reached on my cell phone: 818-519-2336. Please check out our website, but more importantly if you have any questions please feel free to call me or send a message and I will stand ready to help from start to finish. www.productionprints.com Thanks! Jeff Andrews Important Sales Guy (866) 398-5938 Production Prints, Inc 150 Wood Rd, Ste G Camarillo, CA 93010 To No longer Receive Emails from me, please click the link below and enter your email: http://productionprints.wufoo.com/forms/unsubscribe/ ___ 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: Ping from jail not permitted error
On Sun, Apr 18, 2010 at 12:39 AM, Aiza aiz...@comclark.com wrote: My jail has public internet access because i can do pkg_add -r unix2dos and the package does install. But when I enter ping -c 2 freebsd.org I get message ping: socket: Operation not permitted There is no firewall running in the jail. Any ideas would be helpful. there is a reason people write man pages; honor their hard work by reading them first! From jail(8): security.jail.allow_raw_sockets This MIB entry determines whether or not prison root is allowed to create raw sockets. Setting this MIB to 1 allows utilities like ping(8) and traceroute(8) to operate inside the prison. If this MIB is set, the source IP addresses are enforced to comply with the IP address bound to the jail, regardless of whether or not the IP_HDRINCL flag has been set on the socket. Since raw sockets can be used to configure and interact with various network subsystems, extra caution should be used where privileged access to jails is given out to untrusted parties. As such, by default this option is disabled. Regards, aaron.glenn ___ 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: Loader, MBR and the boot process
In message cf9b1ee01001240759j2476cf3es2babd8b32a90f...@mail.gmail.com, Dan N
aumov writes:
On Sun, Jan 24, 2010 at 5:29 PM, John j...@starfire.mn.org wrote:
On Fri, Jan 22, 2010 at 07:02:53AM +0200, Dan Naumov wrote:
On Fri, Jan 22, 2010 at 6:49 AM, Dan Naumov dan.nau...@gmail.com wrote=
:
On Fri, Jan 22, 2010 at 6:12 AM, Thomas K. f...@gothschlampen.com wro=
te:
On Fri, Jan 22, 2010 at 05:57:23AM +0200, Dan Naumov wrote:
Hi,
I recently found a nifty FreeBSD ZFS root installation script and
been reworking it a bit to suit my needs better, including changing =
it
from GPT to MBR partitioning. However, I was stumped, even though I
had done everything right (or so I thought), the system would get
stuck at Loader and refuse to go anywhere. After trying over a dozen
probably this line is the cause:
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s1a skip=3D1 seek=
=3D1024
Unless by swap first you meant the on-disk location, and not the
partition letter. If swap is partition a, you're writing the loader
into swapspace.
Regards,
Thomas
At first you made me feel silly, but then I decided to double-check, I
uncommented the swap line in the partitioning part again, ensured I
was writing the bootloader to ${TARGETDISK}s1b and ran the script.
Same problem, hangs at loader. Again, if I comment out the swap,
giving the entire slice to ZFS and then write the bootloader to
${TARGETDISK}s1a, run the script, everything works.
I have also just tested creating 2 slices, like this:
gpart create -s mbr ${TARGETDISK}
gpart add -s 3G -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s1
gpart add -t freebsd-swap ${TARGETDISK}s1
gpart add -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s2
gpart add -t freebsd-zfs ${TARGETDISK}s2
gpart set -a active -i 2 ${TARGETDISK}
gpart bootcode -b /mnt2/boot/boot0 ${TARGETDISK}
and later:
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s2 count=3D1
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s2a skip=3D1 seek=3D=
1024
Putting the swap into it's own slice and then putting FreeBSD into
it's own slice worked fine. So why the hell can't they both coexist in
1 slice if the swap comes first?
I know what the answer to this USED to be, but I don't know if it is
still true (obviously, I think so, I or wouldn't waste your time).
The filesystem code is all carefully written to avoid the very
first few sector of the partition. =A0That's because the partition
table is there for the first filesystem of the slice (or disk).
That's a tiny amout of space wasted, because it's also skipped on
all the other filesystems even though there's not actually anything
there, but it was a small inefficency, even in the 70's.
Swap does not behave that way. =A0SWAP will begin right at the slice
boundry, with 0 offset. =A0As long as it's not the first partition, no
harm, no foul. =A0If it IS the first partition, you just nuked your parti=
tion
table. =A0As long as SWAP owns the slice, again, no harm, no foul, but
if there were filesystems BEHIND it, you just lost 'em.
That's the way it always used to be, and I think it still is. =A0SWAP can
only be first if it is the ONLY thing using that slice (disk), otherwise,
you need a filesystem first to protect the partition table.
--
John Lind
j...@starfire.mn.org
This explanation does sound logical, but holy crap, if this is the
case, you'd think there would be bells, whistles and huge red label
warnings in EVERY FreeBSD installation / partitioning guide out there
warning people to not put swap first (unless given a dedicated slice)
under any circumstances. The warnings were nowhere to be seen and lots
of pointy hair first greyed and were then lost during the process of
me trying to figure out why my system would install but wouldn't boot.
From man bsdlabel.
offset The offset of the start of the partition from the beginning of
the drive in sectors, or * to have bsdlabel calculate the correct
offset to use (the end of the previous partition plus one, ignor-
ing partition `c'. For partition `c', * will be interpreted as
an offset of 0. The first partition should start at offset 16,
because the first 16 sectors are reserved for metadata.
- Sincerely,
Dan Naumov
___
freebsd-sta...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
Re: [solved] Re: Re: Re: diskless - NFS root mount problem
In message 4b01c4df.4040...@freebsd.org, Doug Barton writes: Mario Pavlov wrote: Hi, it turned out I was stupid enough to misconfigure the kernel...I forgot that I had left the IPFIREWALL options turned on You're not a real sysadmin until you've firewalled yourself out of at least one mission-critical system. Bonus points if it has no out-of-band control plane. Further bonus points if it is more than 100 miles away, and you are the one who has to drive to the data center. Triple bonus points if it is +20 hours of flight time away. Home data center and angry wife w/o Internet access. Yes I managed to stuff up a home machine while in Ireland. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.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: Upgrade Xorg 7.2.0 - mergebase.sh problems
On 27/05/07, Christopher Prance [EMAIL PROTECTED] wrote: I thought I was so close, nope not yet. I finally got my server upgraded with no problem. Well a few minor setbacks, but I got it done. Of course it won't run on my Sony 19 monitor which I have yet to figure out, but wil l in due time, but my server is not of importance, because I don't run X on it, it is just a webserver for now. My Thinkpad is a different story, I am trying to move away from my Windows laptop and rely on only FreeBSD so I would really like to get X up and running again. The file I'm attaching is a script of the mergebase.sh tool. It listed several files that exist in both /usr/local and /usr/X11R6 and it will not continue until I move or remove them. I don't know which ones to remove and which ones to just move. Not too mention I did it by hand on my server, because there was not that many. So any help here would be appreciated. Is there are way I could mak e a script to move all these files for me? Which I'm sure there is but my scripting skills are beginners at best. :( Sorry for the long post, just had to get it out. Thanks again ahead of time! Christopher Prance From your attachment, in part: . . . CONFLICTING FILES: ./bin/appres ./bin/assistant ./bin/atobm ./bin/bdftopcf ./bin/bdftruncate ./bin/beforelight ./bin/bitmap ./bin/bmtoa ./bin/cxpm ./bin/designer ./bin/dga . . . % wc -l xorg-update 3421 xorg-update It looks like most, if not all, of your old xorg install is still under /etc/X11R6, which should not be if you followed /usr/ports/UPDATING. It may be safe to delete if xorg 7.2 was otherwise properly installed in /usr/local, though I suspect some (perhaps very long list of) things might have to be recompiled (again!). It can still be there even if you followed /usr/ports/UPDATING I followed UPDATING. xorg-clients was still there post portupgrade -a. portupgrade bombed out on me but you will note that the xorg meta port did update. This was with portupgrade-devel and after a clean portupgrade -Rf libXft. Note also this was before cd /usr/ports make index was added to UPDATING. Mind you I did run make index prior to the entire upgrade process. I've found the indexs return by fetchindex to cause problems in the past so I just rebuild them even it they do take some time on my older boxes. ** Listing the failed packages (*:skipped / !:failed) ! audio/nas (nas-1.8) (X libraries missing) ! sysutils/xbatt (xbatt-1.2.1) (X libraries missing) * x11-toolkits/qt33 (qt-3.3.8_2) * security/qca-tls (qca-tls-1.0_1) * devel/qca (qca-1.0) * net/kphone (kphone-4.2) * net-im/psi (psi-0.10) ! mail/thunderbird (thunderbird-2.0.0.0)(missing header) * devel/tmake (tmake-1.7_2) * devel/doxygen (doxygen-1.5.1) Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
booting from second drive/operating system not found
Hey, I've got a six drive RAID 10 array on the first SCSI channel that shows up as da0, and a single SCSI drive on the second SCSI channel that shows up as da1. I can run the regular installer on da1 just fine - everything copies over, disklabels are made, MBR is written, yadda yadda. but no matter what I do I continually get operating system not found when I try to boot the installation. this happens with dragonfly too, I dont get it. I understand the boot strap process well, I just dont understand why after even installing a proper MBR on da0, I can't boot into freebsd. help? tia, eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re-setting root password for MYSQL win 2003
in order to access the MYSQL control centre and MYSQL administrator I need to be able to re-set the root userpassword, can someone please advise on how this is done in win2003 server admin tools/computer management/ local users and groups does not disclose the MYSQL root user see print screen. TIA john -- Disclaimer: The information contained in this document is confidential to the addressee(s) and may be legally privileged. Any view or opinions expressed are those of the author and may not be those of the organisation to which the author belongs. No guarantee or representation is made that this communication is free of errors, viruses or interference. If you have received this e-mail message in error please delete it and notify me. Thank you. -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Errata Branch
Matthew, Thanks for the information. You might have already answered this but I'm not 100% sure, once I have cvsup RELENG_4_10 do I need to buildworld just to get the errata branch installed or can I just do as: make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC or is it better to do make buildworld make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC reboot (signal user) mergemaster -p make installworld mergemaster reboot Also is it necessary to do the mergemater part of the buildworld process. Thanks again for the assistance. Paul Matthew Seaman wrote: On Thu, Sep 02, 2004 at 10:39:04PM -0600, Paul Andrews wrote: I'm looking for some information on the Errata Branch for 4.10. I just re-installed my FreeBSD system and am now running 4.10-RELEASE. I want to make sure that I am running with the most-up-to-date security patches applied. Yes. All you need to do is cvsup to the head of the RELENG_4_10 branch, and compile and install using that code. I would like to know the steps necessary for appling the changes in RELENG_4_10. Also how can I tell if the security patchs and code fixes have been applied. Just using cvsup will get you all of the security and other fixes. That includes all of the patches included in the various security advisories issued by the FreeBSD project. To get a newly installed system up to the latest patch level, using cvsup and doing a complete buildworld cycle is your best bet. For any further Errata or Security Advisories, you can always do another buildworld cycle, or there will usually be instructions in the advisory on how to just recompile only the affected bits. If you go the whole 'buildworld' route each time, the uname(1) output will show the patchlevel of the system: currently that's 4.10-RELEASE-p2 after the release of FreeBSD-SA-04:13 on June 30th. Instructions on how to do a buildworld can be found in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html and also be sure to read /usr/src/UPDATING after cvsup'ing to see if there are any special instructions. My stable-subfile: *default host=cvsup12.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4_10 *default delete use-rel-suffix src-all That looks fine to me. Cheers, Matthew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Errata Branch
Hello All, I'm looking for some information on the Errata Branch for 4.10. I just re-installed my FreeBSD system and am now running 4.10-RELEASE. I want to make sure that I am running with the most-up-to-date security patches applied. I would like to know the steps necessary for appling the changes in RELENG_4_10. Also how can I tell if the security patchs and code fixes have been applied. My stable-subfile: *default host=cvsup12.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4_10 *default delete use-rel-suffix src-all All assistance is very much appericated. Thanks in advance. Paul Andrews ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem installing/upgrading QT3.2
On Sun, Sep 21, 2003 at 03:22:40PM +0900, Rob Lahaye wrote: Dragoncrest wrote: I agree. I'm waiting till someone totally sorts this out. Cause it seems like the Band-Aid to get one thing fixed breaks something else. So for the time being I'm not touching anything. At 08:19 PM 9/20/03 -0500, Larry Rosenman wrote: and then Arts blows up trying to configure from Ports. This is a MESS. I did not have this Arts problem (though Arts was initially not installed on the machine). I deinstalled Qt and did a portinstall of kde3. That is going well so far; still compiling, but I have passed the Arts install already, flawlessly! Yes, right now you have to delete the old qt install before configuring/building qt32. On -CURRENT: don't even bother until after the ports freeze. KF is looking into the qt31-qt32 upgrade problem but the fix is not obvious, yet. For now please just use this workaround. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd]
On Thu, Aug 21, 2003 at 11:01:35AM +0900, Rob Lahaye wrote: What news-server is this on? I use news.gmane.org and news.easysw.com, but qt-freebsd is on neither. Freebsd-questions and kde-freebsd are both on gmane! I set up qt-freebsd about a year ago with the intention of putting qt-specific topics on that list for those who aren't interested in KDE but are in Qt... however, I never got around to telling people (most notably qt-dependent port maintainers) about it... Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dynamic Rules with IPFW
I use Dynamic rulesets with IPFW: ipfw add check-state ipfw add deny tcp from any to any established ipfw add allow tcp from my-net to any setup keep-state But I also have services I need anyone on the net to get to, without me makin g a connection first from my-net . I allow such services with: allow tcp from any to my-net 25,80,443 setup in via xl0 keep-state This works fine for 25,80, and 443. However, when I apply the same rule for S SH, and login to my box remotely, about 10 minutes later, the connection just dies, and it dies with every connection. Removing the keep-state option for ssh effectively closes 22 obviously. Would check-state be a better option he re? Michael To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-security in the body of the message smtp, http and https are short lived connections with very little idle time. ssh is a long lived connection with large amounts of idle time. You need to have the dynamic lifetime exceed the keep alive timer or allow established ssh connections to continue to exist. Mark -- Mark Andrews, Internet Software Consortium 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
