Re: where to ask about problems with bsdinstall in 9.0RC2?
On 19/11/2011 00:53, Edward Martinez wrote: As the progress bar moved to the right toward 100% completion, a window popped up telling me that it (bsdinstall) could not handle the base.txz (BTW, what does the suffix .txz mean?) - it could not uncompress it and said something about unable to write and the string was something like: var/base.txz (note the lack of a leading slash in front of var). xz(1) is the latest compression program around. It usually gets better results than bzip2 so lots of usages are being switched to it. .txz is a tar archive compressed with xz. Hmmm.. I wonder if the base.txz file on your install media has become corrupt? If you've got a FreeBSD machine around (any supported 7.x or 8.x would do), you could just mount your 9.0 disk on it, find that file wherever it is in the disk, and see if 'tar -tvf base.txz' will show you the contents without errors. The other possibility is that you ran out of space in the partition you were trying to write to. You'ld have to open an emergency holographic shell to investigate (does the new installer even have that wording? It should...) One thing to check is not only space usage but inode usage too. There's an ongoing discussion about installing onto small drives and whether the bytes-to-inode ratio should be modified there. The lack of a leading '/' on the path you saw is normal -- your hard drive is mounted at something like /mnt while the system is installed onto it. The installer is just using paths relative to that mountpoint. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
Hello, Has anyone else noticed a similar odd behavior with AMD64 and 9.0 prerelease (as well as RCs and betas)? On my 12 core (2*4162EE) the whole system just freezes quite often without any warning, without any messages being logged. Neither is there any panic message from the kernel. The system just suddenly hangs such that there is no alternative but to reboot using the reset button. At the moment I don't have any further info about the cause of the problem, but quite often the freeze has happened when there has been some network activity. Does anyone have an idea how to start tracking down such a problem? I mean anything in addition to this... http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ 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
Syslog server not logging remote machines to file?
Hi,
I've got a really strange problem which seems to either be a bug with
the syslog server service or perhaps because I'm running jails on my
system.
I can log my router syslog information but somehow the syslog server
doesn't put the information into the designated file; which should be
/var/log/cisco857w.log???
This is the syslog definition in my /etc/rc.conf file:
{
syslogd_enable=YES
#syslog_flags=
syslogd_flags=-d -b 192.168.1.120 -a 192.168.1.1/24:* -vv -C
}
Additionally here is my /etc/syslog.conf file:
{
# $FreeBSD: src/etc/syslog.conf,v 1.30.2.1.2.1 2009/10/25 01:10:29
kensmith Exp $
#
#Spaces ARE valid field separators in this file. However,
#other *nix-like systems still insist on using tabs as field
#separators. If you are sharing this file between systems, you
#may want to use only tabs as field separators here.
#Consult the syslog.conf(5) manpage.
#+server.domain
*.err;kern.warning;auth.notice;mail.crit/dev/console
*.notice;local7.none;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages
security.*/var/log/security
auth.info;authpriv.info/var/log/auth.log
mail.info/var/log/maillog
lpr.info/var/log/lpd-errs
ftp.info/var/log/xferlog
cron.*/var/log/cron
*.=debug/var/log/debug.log
*.emerg*
# uncomment this to log all writes to /dev/console to /var/log/console.log
#console.info/var/log/console.log
# uncomment this to enable logging of all log messages to /var/log/all.log
# touch /var/log/all.log and chmod it to mode 600 before it will work
#*.*/var/log/all.log
# uncomment this to enable logging to a remote loghost named loghost
#*.*@loghost
# uncomment these if you're running inn
# news.crit/var/log/news/news.crit
# news.err/var/log/news/news.err
# news.notice/var/log/news/news.notice
!ppp
*.*/var/log/ppp.log
!*
+192.168.1.1
*.*/var/log/cisco857w.log
#local7.* /var/log/cisco857w.log
#!*
#+172.16.0.1
#*.*
}
uname -a shows this:
{
# uname -a
FreeBSD server.domain 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21
15:02:08 UTC 2009
r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
}
The odd thing about this is that I did the same thing on a non-jailed
32bit machine running FreeBSD 8.x and the system worked fine.
In my research for the problem I have covered this material:
{
http://www.freebsd.org/doc/handbook/network-syslogd.html
http://forums.devshed.com/bsd-help-31/remote-syslog-question-router-to-freebsd-118652.html
http://www.freebsd.org/doc/handbook/network-syslogd.html
http://www.daemonforums.org/showthread.php?t=2968
http://bsd.dischaos.com/2009/02/25/logging-cisco-ios-messages-to-external-freebsd-syslog/
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-02/msg00384.html
http://plone.lucidsolutions.co.nz/networking/cisco/ios/logging-to-a-syslog-or-rsyslog-host-from-cisco-ios
http://lists.nycbug.org/pipermail/talk/2007-April/010091.html
http://www.freebsdonline.com/content/view/527/506/
}
They all seem to say more or less the same thing that either putting the:
{
+192.168.1.1
*.*/var/log/cisco857w.log
or
local7.* /var/log/cisco857w.log
}
statements either at the top of the file or changing the syntax slightly
using a + between machines should do the trick; however, non of the
things I tried have worked from any of the material mentioned above!
Here is my debug information:
{
# tcpdump -tlnvv -i em0 port 514
tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 96
bytes
IP (tos 0x0, ttl 255, id 337, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10040: 010027: Nov 19 10:28:04.322: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 338, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10041: 010028: Nov 19 10:28:04.326: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 339, offset 0, flags [none], proto UDP (17),
length 142)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 114
Facility local7 (23), Severity notice (5)
Msg: 10042: 010029: Nov 19 10:28:04.770: %SYS-5-CONFIG[|syslog]
IP (tos 0x0, ttl 255, id 340, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10043: 010030: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 341, offset 0, flags [none], proto UDP
Re: FreeBSD 9.0 RC-2
On Friday 18 November 2011 16:51:39 Matthew Seaman wrote: On 18/11/2011 22:24, ajtiM wrote: I had a problem with memory on y computer with 8.2 and there are some mess. I like to install fresh FreeBSD 9.0. Is it safe to install RC-2 or is better to wait to the final release, please? 9.0-RC2 is (probably) going to be very similar indeed to the eventual 9.0-RELEASE. There will be some bug fixes yet to go in, but it is unlikely these will be show-stoppers. RC2 is not unsafe and there's no reason not to install it for learning or evaluation or development purposes. I wouldn't advise using it for anything your livelihood depends on though. Plan on upgrading to -RELEASE as soon as possible if you do play with -RC2. However, you're unlikely to have a pleasant experience if you've got dodgy RAM in your machine. All bets are off if the computer cannot rely on getting the correct data back from RAM. I wouldn't even try booting up a live CD unless the memory problems have been fixed. Cheers, Matthew Thank you very much. Each school cost something ): Mitja http://jpgmag.com/people/lumiwa ___ 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
qt4-cups
I decided to install FreeBSD 9.0 RC-2. I like to have KDE4 as I have now and my question is: Do I need to have in the make.conf still QT4_OPTIONS=CUPS Thank you. Mitja http://jpgmag.com/people/lumiwa ___ 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
file system on 9.0
Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Thanks in advance. Mitja http://jpgmag.com/people/lumiwa ___ 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: file system on 9.0
On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. Thanks in advance. Mitja http://jpgmag.com/people/lumiwa -- If you've got them by the balls, their hearts and minds will follow. ___ 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: file system on 9.0
On Sat, 19 Nov 2011 20:29:40 +0800 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. UFS_GJOURNAL is for gjournal not soft-update journalling. A file system doesn't actually need to be created with either soft-updates or soft-update journalling- it's something that can be turned of and on. And yes enabling it in the installer should be sufficient. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. There's no point in installing the default tree since portsnap has to do an initial extract. In general I'd suggest starting portsnap on an empty ports directory just to eliminate any minor cruft. ___ 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: file system on 9.0
On Saturday 19 November 2011 06:29:40 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. Thank you and one more, please... Partitioning: if I choose guided than I got: freebsd-boot freebsd-ufs / freebsd-swap If I press enter on freebsd-ufs / than I got options to make moe partitions. Is it okay that I make /, /var, /tmp and /usr as I have now. Thank you very much for the help. Mitja http://jpgmag.com/people/lumiwa ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
William Bulley w...@umich.edu wrote: According to Fbsd8 fb...@a1poweruser.com on Fri, 11/18/11 at 21:02: I think you have under sized /usr and the uncompress ran out of space during the install. Start over again, wipe the disk clean (ie: delete all slices)and re-allocate your slices with larger space allocations. Thanks. IIRC, the error message was out of inodes. This means something was trying to put *lots* (where 'lots' is relative number, depending on the size of the filesystem :) of little files on the filesystem. You were _not_ out of 'free space' on the filesystem, just out of slots for file 'metadata'. Newfs, if not told specifically how many inodes to allocate, makes a 'guess' based on the size of the slice -- thus increasing the size of a partition will have an automatic 'side effect' of increasing the total number of inodes. However, by explicitly stating the number of inodes, or the inodes per unit of storage, when running newfs, one can get more (or fewer) inodew _without_ having to change partition sizes. Most significantly, one can do this -- change the number of inodes, that is -- *without* having to destroy/recreate any other partitions on the same physical device. SECONDLY, if this happened -during- the install, and the complaint was about /var -- as distinct from something like '/a/var', or '/mnt/var' Then the problem is *NOT* on the drives you are installing *ONTO*, but on the media you are installing _from_. At a guess, the installer is using /var -- probably /var/tmp -- to keep scratchpad files in, and there are not enough inodes for the installer. could it be unpacking tarfiles there, move/copy onto the 'target' media? You're installing from a memory stick right? You may need to rebuild the filesystem on the stick, _manually_ specifying a larger number of inodes for the filesystem that /var is part of. ___ 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: Syslog server not logging remote machines to file?
Kaya Saman kayasa...@gmail.com wrote: Hi, I've got a really strange problem which seems to either be a bug with the syslog server service or perhaps because I'm running jails on my system. I can log my router syslog information but somehow the syslog server doesn't put the information into the designated file; which should be /var/log/cisco857w.log??? The -usual- 'gotcha' for this situation is that you have to _create_ the file FIRST, and then tell syslogd to reload it's configuration. (i.e. 'kill -HUP' the PID for syslogd) ___ 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: Syslog server not logging remote machines to file?
On 11/19/2011 05:21 PM, Robert Bonomi wrote: Kaya Samankayasa...@gmail.com wrote: Hi, I've got a really strange problem which seems to either be a bug with the syslog server service or perhaps because I'm running jails on my system. I can log my router syslog information but somehow the syslog server doesn't put the information into the designated file; which should be /var/log/cisco857w.log??? The -usual- 'gotcha' for this situation is that you have to _create_ the file FIRST, and then tell syslogd to reload it's configuration. (i.e. 'kill -HUP' the PID for syslogd) That's ok, however due to me running syslogd in debug mode anyway - ctrl + c should do that anyway. I performed a: ps aux | grep syslog with no result other then my 'grepping' displayed. Meaning that the syslog daemon should have reloaded right? - I mean it's standard for everything else which works in that way! ___ 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: AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
On 11/19/11 03:54, Jukka A. Ukkonen wrote: Hello, Has anyone else noticed a similar odd behavior with AMD64 and 9.0 prerelease (as well as RCs and betas)? On my 12 core (2*4162EE) the whole system just freezes quite often without any warning, without any messages being logged. Neither is there any panic message from the kernel. The system just suddenly hangs such that there is no alternative but to reboot using the reset button. At the moment I don't have any further info about the cause of the problem, but quite often the freeze has happened when there has been some network activity. Does anyone have an idea how to start tracking down such a problem? I mean anything in addition to this... http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ 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 I experienced this a rather long time ago with an AMD X2600 (Barton?) processor. The machine would freeze when I did some rapid mousing/clicking in and out of a window. Nothing in the logs. If I stayed out of X things were just fine but this was my home machine and why should I have to stay out of X? I figured FBSD dev was just running behind the Intel dev and time would fix it. Or Xorg dev would even up. In any case it went away in the next release. It was never *that* much of a problem; consistent but not often. Your freezing appears to be more frequent than was mine. At this point in the release cycle I think the only issues they find are for weird corner cases. Perhaps you have one. Or it's hardware :( Try a different NIC for a while. r ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
--As of November 19, 2011 8:14:56 AM +, Matthew Seaman is alleged to have said: On 19/11/2011 00:53, Edward Martinez wrote: As the progress bar moved to the right toward 100% completion, a window popped up telling me that it (bsdinstall) could not handle the base.txz (BTW, what does the suffix .txz mean?) - it could not uncompress it and said something about unable to write and the string was something like: var/base.txz (note the lack of a leading slash in front of var). xz(1) is the latest compression program around. It usually gets better results than bzip2 so lots of usages are being switched to it. .txz is a tar archive compressed with xz. --As for the rest, it is mine. Just as a quick digression... xz has only marginal improvements in compressed size over bzip2, and takes a lot more cpu/memory resources to compress. In most cases, I'd say it's the wrong choice for a compression format. However, the one place where it is unequivocally the *best* choice is one that will make it well known: Distributing archives. It does beat bzip2 by a small amount, and it's *decompression* time is *much* faster than bzip2 - on par with gzip. Plus decompression can be done in a fixed amount of RAM, regardless of the size of the files being uncompressed. For files that are compressed once and then decompressed many times on many different boxes - like a FreeBSD release - it's a definite win. But for files that will be compressed and uncompressed regularly, or compressed and usually never touched again, it's worth thinking about what's the best balance of resources. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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: file system on 9.0
On 2011/11/19 at 21:18, RW rwmailli...@googlemail.com wrote: On Sat, 19 Nov 2011 20:29:40 +0800 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. UFS_GJOURNAL is for gjournal not soft-update journalling. A file system doesn't actually need to be created with either soft-updates or soft-update journalling- it's something that can be turned of and on. And yes enabling it in the installer should be sufficient. Thanks for clarifying. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. There's no point in installing the default tree since portsnap has to do an initial extract. In general I'd suggest starting portsnap on an empty ports directory just to eliminate any minor cruft. Yes. the ports tree on the installation CD/DVD is always old and only takes longer time to install than without them. -- If you've got them by the balls, their hearts and minds will follow. ___ 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: Syslog server not logging remote machines to file?
On 11/19/2011 06:52 PM, Robert Bonomi wrote:
From kayasa...@gmail.com Sat Nov 19 09:33:08 2011
Date: Sat, 19 Nov 2011 17:31:50 +0200
From: Kaya Samankayasa...@gmail.com
To: Robert Bonomibon...@mail.r-bonomi.com
CC: freebsd-questions@freebsd.org
Subject: Re: Syslog server not logging remote machines to file?
On 11/19/2011 05:21 PM, Robert Bonomi wrote:
Kaya Samankayasa...@gmail.com wrote:
Hi,
I've got a really strange problem which seems to either be a bug with
the syslog server service or perhaps because I'm running jails on my
system.
I can log my router syslog information but somehow the syslog server
doesn't put the information into the designated file; which should be
/var/log/cisco857w.log???
The -usual- 'gotcha' for this situation is that you have to _create_ the
file FIRST, and then tell syslogd to reload it's configuration. (i.e.
'kill -HUP' the PID for syslogd)
That's ok, however due to me running syslogd in debug mode anyway - ctrl
+ c should do that anyway. I performed a: ps aux | grep syslog with
no result other then my 'grepping' displayed.
Meaning that the syslog daemon should have reloaded right? - I mean it's
standard for everything else which works in that way!
Well if ps -aux doesn't show any syslogd entry, then syslogd is -not-
running -- which would explain why it's not logging anything to the file :)
If you're stopping and restarting syslogd, then, yes, that causes it to
re-read the configuration.
This begs the question, however, *DOES* that file exist? syslog does _not_
_create_ a missing logfile, just because it is mentioned in the syslog.conf
file.
g
Robert,
I can assure that syslogd is running, hence the logging posted within my
first email to the list. When run with the -d and -vv flags set in
/etc/rc.conf I need to use ctrl +c to break out of it as it logs
directly to the tty.
Just to go over it again, output from syslogd with -d and -vv flags set
running in debug mode shows:
{
logmsg: pri 56, flags 4, from Server, msg syslogd: restart
syslogd: restarted
logmsg: pri 6, flags 4, from Server, msg syslogd: kernel boot file is
/boot/kernel/kernel
Logging to FILE /var/log/messages
syslogd: kernel boot file is /boot/kernel/kernel
logmsg: pri 166, flags 17, from Server, msg Nov 19 12:33:34 syslog.err
Server syslogd: exiting on signal 2
cvthname(192.168.1.1)
validate: dgram from IP 192.168.1.1, port 59189, name router.domain;
accepted in rule 0.
logmsg: pri 275, flags 0, from cisco857w, msg 10048: 010035: Nov 19
10:33:48.037: %SYS-5-CONFIG_I: Configured from console by admin on vty0
(192.168.1.120)
}
The file is mentioned in syslogd config and seems to be loaded within
the configuration:
{
cfline(*.*/var/log/cisco857w.log, f, *,
+192.168.1.1)
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE:
/var/log/cisco857w.log
}
The file *has* been created also under /var/log/ dir however self
creation is possible using the -C flag within /etc/rc.conf file; and
give 'appropriate' permission 600:
{
# ls -l /var/log | grep cisco857
-rw--- 1 root wheel 0 Nov 18 16:32 cisco857w.log
}
So after all this looks {**perfect**} what can this mysterious problem be??
___
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: file system on 9.0
On 2011/11/19 at 23:03, ajtiM lum...@gmail.com wrote: On Saturday 19 November 2011 06:29:40 Denise H. G. wrote: On 2011/11/19 at 20:09, ajtiM lum...@gmail.com wrote: Hi! One more question before I start installing FreeBSD 9.0 RC-2. Now we have a new bsdinstall and as I red and if I understood correct there is also SU journaling file sistem. I will switch to the GPT partion. If I want to have SU-j file system is it enough that I just choose this option and voila? Yes. I think so. 'options UFS_GJOURNAL' is present in GENERIC kernel config. If you use GENERIC kernel, it is there. And another question is about ports. There is an option ports tree which is marked default. It is okay that I use this later with portsnap? Sure. portsnap is designed to work with the ports tree. Thank you and one more, please... Partitioning: if I choose guided than I got: freebsd-boot freebsd-ufs / freebsd-swap If I press enter on freebsd-ufs / than I got options to make moe partitions. Is it okay that I make /, /var, /tmp and /usr as I have now. I strongly advise that /usr and /usr/local reside on different partitions. Furthermore, If you plan to run a desktop environment, your /usr/local should be big enough, say 8G - 10G, to hold all stuff you built from the ports. And putting /var on a separate partitiion is a good idea, I think. You can find detailed information on how to lay out and size your partitions in tuning(7) either locally or online. Thank you very much for the help. Mitja Regards. -- If you've got them by the balls, their hearts and minds will follow. ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
In freebsd-questions Digest, Vol 389, Issue 8, Message: 6 On Fri, 18 Nov 2011 19:08:22 -0500 William Bulley w...@umich.edu wrote: According to Edward Martinez eam1edw...@gmail.com on Fri, 11/18/11 at 19:53: Have you tried installing with ACPI disabled. http://www.freebsd.org/doc/handbook/bsdinstall-install-trouble.html#Q3.10.2.1. this also may be of some help: http://www.freebsd.org/doc/handbook/bsdinstall-partitioning.html Thanks. I will try disabling ACPI but this wasn't necessary for the install of 8.2-RELEASE from CD which, as I said, went in just as I expected. I doubt that's your problem, going by my experiences with BETA1 and following the freebsd-current archives for a couple of months; others have described similar problems installing over existing slices, and in my mind it points to a relatively large deficiency in bsdinstall versus sysinstall (still available from 'Live CD' mode, at BETA1 anyway) I would not think that much would have changed in 9.0RC2 in this area. Maybe I am wrong about that. The second URL describes the Manual vs. Guided install and partition section of bsdinstall. I had read this several days before the 9.0RC2 install attempt from DVD. It seemed pretty reasonable, but a little bit different from sysinstall. Was worth a try. Unfortunately that concentrates on creating a GPT layout, encouraging a Linux-like single (plus a boot) partition - forget using dump/restore - and says nothing much about installing over an existing setup with MBR partitioning and multiple slices, a not uncommon setup on many existing laptops .. eg here I want to install over a previous 7.2-RELEASE 60GB slice partitioned as I want it - 1GB /, 4GB /var, 16GB /usr and ~37GB /home. Further, I want to preserve /home as is, despite having backups. What I saw when I selected Manual partitioning, was a complete tree: ad0 ad0s1 [FreeBSD Boot Manager from 8.2] ad0s1a [was my previous root partition] ad0s1d [was my previous swap partition] ad0s1d [was my previous /var partition] ad0s1e [was my previous /usr partition] or something very close to that, missing only my mount points from my previous 8.2-STABLE system. I added the mount points (this is the area where I thought bsdinstall had some weaknesses in the User Experience) and went on after selecting Finish. sysinstall's partitioning is more sophisticated; you get to specifically toggle on or off newfs'ing each partition, as well as specifying newfs options if you want. So it's clear whether you'll be newfs'ing / and which other partitions, and which you'll be leaving alone, eg /home. The problem occurred much later after I selected all four install files. When I said the equivalent of Go, it began the process of loading them off the DVD, checking their checksums, and compressing them prior to installing them. It was while processing the first (base.txz) chunk that the popup appeared giving me the unable to write or unable to uncompress message. Can't recall the exact error now some hours later... :-( On BETA1 I recorded Extract Error while extracting base.txz: can't set user=0/group=0 for /var/empty Can't update time for /var/empty .. which someone/s else also reported, which turned out to be misleading .. the basic problem is that the filesystem isn't empty, ie as after newfs. The workaround given then was to boot in Live CD (aka Fixit) mode, and newfs the appropriate partitions, manually or with SADE - in your case probably all of /, /var and /usr - and then rerun the install onto clear partition/s; it's not and never should be required to scrap existing partitioning. Something else not clearly evident to me is (or at least was) that if you don't supply a mountpoint for a partition, it won't be used; in my case I'd have to leave my /home partition unmentioned so it would be left alone .. after all, every partition on every slice is listed as a possible install target. I admit not having tried this again since, after feeling a bit lucky not to have destroyed my whole 7.2 slice, but that was BETA1 after all .. I haven't yet discovered whether or how bsdinstall handles setting boot0cfg for multi-boot systems, and I've seen no mention of boot0cfg or anything similar (apart from Linuxisms like GRUB) for GPT setups at all. So the extraction step failed the first file, and I never made it to the Post-Installation phase, sigh... :-( Yep. I'd hoped this might be fixed (or at least documented?) by now, but I think bsdinstall has to be considered still in development at this stage - ie, for 9.0 - except for such as installing to new systems, for which it appears to be working very well. Some have implied that the sort of installs we're attempting should require prior expertise, but even people who've
BUG: scp -pr does not copy directories that have ':' sign in their names
HI, Tri. scp -pr * name@host:/home/dir does not copy files which have ':' sign in their names -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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
radiusd-cistron
I recently switched from FBSD 7.0 i386 to FBSD 8.2 amd64 my radius only sees garbage in place of the password, so no one can authenticate. Since I changed both OS (7.0-8.2) AND platform (i386-amd64), I am unsure where to start looking for an encryption problem. Any suggestions would be appreciated. Yes, I could switch to freeradius, but would that change/help an encryption issue? 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
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Ian Smith smi...@nimnet.asn.au on Sat, 11/19/11 at 13:29: I doubt that's your problem, going by my experiences with BETA1 and following the freebsd-current archives for a couple of months; others have described similar problems installing over existing slices, and in my mind it points to a relatively large deficiency in bsdinstall versus sysinstall (still available from 'Live CD' mode, at BETA1 anyway) Thanks. This makes me feel better and not so clueless. I had guessed that bsdinstall was ready for prime time, but evidently not. Unfortunately that concentrates on creating a GPT layout, encouraging a Linux-like single (plus a boot) partition - forget using dump/restore - and says nothing much about installing over an existing setup with MBR partitioning and multiple slices, a not uncommon setup on many existing laptops .. eg here I want to install over a previous 7.2-RELEASE 60GB slice partitioned as I want it - 1GB /, 4GB /var, 16GB /usr and ~37GB /home. Further, I want to preserve /home as is, despite having backups. OMG! :-( sysinstall's partitioning is more sophisticated; you get to specifically toggle on or off newfs'ing each partition, as well as specifying newfs options if you want. So it's clear whether you'll be newfs'ing / and which other partitions, and which you'll be leaving alone, eg /home. I will have to revert to the disc1 - but wait, there isn't one!?!?!?! I will have to use the bootonly solution, sigh... :-( On BETA1 I recorded Extract Error while extracting base.txz: can't set user=0/group=0 for /var/empty Can't update time for /var/empty .. which someone/s else also reported, which turned out to be misleading .. the basic problem is that the filesystem isn't empty, ie as after newfs. Most assuredly the problem as my disk partitions were completely full of 8.2-STABLE and useable as such (and still are since the 9.0RC2 install failed). The workaround given then was to boot in Live CD (aka Fixit) mode, and newfs the appropriate partitions, manually or with SADE - in your case probably all of /, /var and /usr - and then rerun the install onto clear partition/s; it's not and never should be required to scrap existing partitioning. This sucks as a workaround IMHO. I agree with you last sentence. Something else not clearly evident to me is (or at least was) that if you don't supply a mountpoint for a partition, it won't be used; in my case I'd have to leave my /home partition unmentioned so it would be left alone .. after all, every partition on every slice is listed as a possible install target. I admit not having tried this again since, after feeling a bit lucky not to have destroyed my whole 7.2 slice, but that was BETA1 after all .. I did, in fact, supply mount points for /, /var and /usr (n/a to swap). However, as I said there was some ugliness in the User Experience with that phase of bsdinstall - there were only two writeable textareas for each partition and when I tried to give the mount point, I found that I was writing into the first textarea which was already filled in with freebsd as I recall. Moving to the second textarea to enter the mount point was successful, but there was no way to move to the OK or cancel buttons at the bottom of this window. Fortunately, I was able to continue by entering the return key on my keyboard, which was not clearly documented. I haven't yet discovered whether or how bsdinstall handles setting boot0cfg for multi-boot systems, and I've seen no mention of boot0cfg or anything similar (apart from Linuxisms like GRUB) for GPT setups at all. Don't have anything to say about those items... Yep. I'd hoped this might be fixed (or at least documented?) by now, but I think bsdinstall has to be considered still in development at this stage - ie, for 9.0 - except for such as installing to new systems, for which it appears to be working very well. Some have implied that the sort of installs we're attempting should require prior expertise, but even people who've been installing FreeBSD for a decade or so have been confused by this one, and you shouldn't need to read current@ to know how to deal with this sort of installation error, in my view. Should require prior expertise!?!?!?!?! I've been building (from source) and using FreeBSD since 2.1.5 back in around 1995 or 1996 as far as I can recall - and I have the CDROMs purchased from Walnut Creek to prove it! :-) And I agree about not having to subscribe to current either (which I don't). Fortunately sysinstall is still there, and while it can't handle GPT partitioning, should still be useful for partitioning and maintaining many existing systems. I've yet to install RC1, and here's RC2, but I'm encouraged to see the memstick.img has dropped GPT partitioning for MBR with a single provider (eg da0a) so it can be again used by sysinstall; in my case I'd rather use that than
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Robert Bonomi bon...@mail.r-bonomi.com on Sat, 11/19/11 at 10:08: IIRC, the error message was out of inodes. This means something was trying to put *lots* (where 'lots' is relative number, depending on the size of the filesystem :) of little files on the filesystem. You were _not_ out of 'free space' on the filesystem, just out of slots for file 'metadata'. Newfs, if not told specifically how many inodes to allocate, makes a 'guess' based on the size of the slice -- thus increasing the size of a partition will have an automatic 'side effect' of increasing the total number of inodes. However, by explicitly stating the number of inodes, or the inodes per unit of storage, when running newfs, one can get more (or fewer) inodew _without_ having to change partition sizes. Most significantly, one can do this -- change the number of inodes, that is -- *without* having to destroy/recreate any other partitions on the same physical device. SECONDLY, if this happened -during- the install, and the complaint was about /var -- as distinct from something like '/a/var', or '/mnt/var' Then the problem is *NOT* on the drives you are installing *ONTO*, but on the media you are installing _from_. At a guess, the installer is using /var -- probably /var/tmp -- to keep scratchpad files in, and there are not enough inodes for the installer. could it be unpacking tarfiles there, move/copy onto the 'target' media? You're installing from a memory stick right? You may need to rebuild the filesystem on the stick, _manually_ specifying a larger number of inodes for the filesystem that /var is part of. No that was not the error. The error was something along the lines of: var/ but I don't recall the exact text of the error message - the main point of my previous messages was to point out the missing leading slash, not /var, but just var - which at the time I thought was most unusual. This was happening during an attempted install of 9.0RC2 from DVD ISO as in: FreeBSD-9.0-RC2-i386-dvd1.iso and was not an attempt from a memory stick. Thanks for the reply, but based on another reply, I think my problem has stemmed from the use of bsdinstall which apparently doesn't do a very good job of installing a subsequent version of FreeBSD on top of an existing (prior) version of same. Had I been able to upgrade using the normal methods (buildworld and installworld) from 8.2-STABLE to 9.0RC1 or 9.0RC2 I would have, but during the kernel compile process I got a compile time error (that was trying to upgrade to RC1 just prior to the arrival of RC2) and there was no way I could deal with that. Interestingly enough, in looking around following that failed upgrade attempt, the RC1 ISOs and so forth were missing from ftp.freebsd.org which I thought was odd. Shortly thereafter RC2 was being seen around *.freebsd.org in various places, so I must have been making this attempt during the transition from RC1 to RC2 in all the distribution places. This convinced me to burn a new DVD (against the RC2 ISO) but then I got hammered by the not-ready-for-prime-time bsdintall program... :-( Thanks again. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
According to Daniel Staal dst...@usa.net on Sat, 11/19/11 at 10:06: --As for the rest, it is mine. Just as a quick digression... xz has only marginal improvements in compressed size over bzip2, and takes a lot more cpu/memory resources to compress. In most cases, I'd say it's the wrong choice for a compression format. However, the one place where it is unequivocally the *best* choice is one that will make it well known: Distributing archives. It does beat bzip2 by a small amount, and it's *decompression* time is *much* faster than bzip2 - on par with gzip. Plus decompression can be done in a fixed amount of RAM, regardless of the size of the files being uncompressed. For files that are compressed once and then decompressed many times on many different boxes - like a FreeBSD release - it's a definite win. But for files that will be compressed and uncompressed regularly, or compressed and usually never touched again, it's worth thinking about what's the best balance of resources. Thanks for that explanation! :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
According to Matthew Seaman m.sea...@infracaninophile.co.uk on Sat, 11/19/11 at 03:14: xz(1) is the latest compression program around. It usually gets better results than bzip2 so lots of usages are being switched to it. .txz is a tar archive compressed with xz. Thanks. Then it is so new that I'd not heard about it while trying to manage my other responsibilities... :-) Hmmm.. I wonder if the base.txz file on your install media has become corrupt? If you've got a FreeBSD machine around (any supported 7.x or 8.x would do), you could just mount your 9.0 disk on it, find that file wherever it is in the disk, and see if 'tar -tvf base.txz' will show you the contents without errors. Possible, but unlikely. Plus I doubt that 'tar -tvf base.txz' without a pipe having an xzcat(1) in front of the tar(1) command. Maybe there is an xz option for tar(1) during extraction mode, but my tar(1) man page doesn't list any, sigh... It does list -y and -z options for other compression/decompression modes, hmmm :-( The other possibility is that you ran out of space in the partition you were trying to write to. You'ld have to open an emergency holographic shell to investigate (does the new installer even have that wording? It should...) One thing to check is not only space usage but inode usage too. There's an ongoing discussion about installing onto small drives and whether the bytes-to-inode ratio should be modified there. As I have previously stated, my root, /var, and swap partitions are all 4 GB in size, and my /usr partition is 99 GB - likely plenty room in all. The lack of a leading '/' on the path you saw is normal -- your hard drive is mounted at something like /mnt while the system is installed onto it. The installer is just using paths relative to that mountpoint. Well, now that is interesting! I hadn't thought of that possibility... Thanks again for your reply. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
On 11/18/11 15:00, William Bulley wrote: I had some User Interface issues with the Manual disk partition screen, I got interested and downloaded it to try myself. I installed 9.0 in virtualbox using the guided option and it installed. just wondering if you tried installing with guided option instead of manual? Now I will try using manual and see what happens ___ 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: Syslog server not logging remote machines to file?
cvthname(192.168.1.1)
validate: dgram from IP 192.168.1.1, port 59189, name router.domain;
accepted in rule 0.
logmsg: pri 275, flags 0, from cisco857w, msg 10048: 010035: Nov 19
10:33:48.037: %SYS-5-CONFIG_I: Configured from console by admin on vty0
(192.168.1.120)
If we take the 'priority' of that message at face value,
it is a facility value of 34
and a logging priority of 3
On the machines I have access to, facility values stop at _24_.
The message may be being discarded because of a 'nonsense' priority.
I changed the 'facility' value within the IOS itself to kernel:
(config)#logging facility kern
- and now the generated message shows this:
accepted in rule 0.
logmsg: pri 15, flags 0, from cisco857w, msg 10146: 010133: Nov 19
23:05:54.538: %SYS-5-CONFIG_I: Configured from console by admin on vty0
(192.168.0.53
still not logging to file though :-( ??
The file is mentioned in syslogd config and seems to be loaded within
the configuration:
{
cfline(*.*/var/log/cisco857w.log, f, *,
+192.168.1.1)
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE:
/var/log/cisco857w.log
_THAT_ lookks like only _24_ known 'facility' values.
# ls -l /var/log | grep cisco857
-rw--- 1 root wheel 0 Nov 18 16:32 cisco857w.log
And, I presume that when you are invoking syslogd in 'debug' mode, you
are running as superuser.
Yep, that is correct! Am using: su -
So after all this looks {**perfect**} what can this mysterious problem be??
I'm _guessing_ that the apparent 'facility' value of 34 is a good candidate.
___
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.2-RELEASE-p4
On Fri, Nov 18, 2011 at 3:50 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: If you compile your own kernel, then freebsd-update will patch the kernel sources, but leave you to rebuild and reinstall your customized kernel. I don't know about the -p4 update. By rights it should have involved updating the kernel by one or other of the two methods shown. So far however, we've seen two reports questioning that[*] and none saying that the -p4 update did in fact update the kernel. Which is suspicious, but hardly conclusive. Do you compile your own kernel, or do you have a machine that uses GENERIC? If you do, what is the output of uname -a on it? ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
On Sat, 19 Nov 2011 11:06:43 -0400, Daniel Staal dst...@usa.net said: D xz has only marginal improvements in compressed size over bzip2, and D takes a lot more cpu/memory resources to compress. In most cases, I'd D say it's the wrong choice for a compression format. However, the one D place where it is unequivocally the *best* choice is one that will make D it well known: Distributing archives. Along these same lines, it works well for large mostly-text files. I have a lot of historical data in text form, 60-100 Mb uncompressed per file, and I get ~18% smaller files using xz instead of bzip2. I know disk space is cheap, but our rack space is limited. -- Karl Vogel I don't speak for the USAF or my company Sorry I'm taking up your ever so valuable disk space! That's okay, /dev/null is pretty big. --ill...@gmail.com, 14 Feb 2011 ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
According to Edward Martinez eam1edw...@gmail.com on Sat, 11/19/11 at 19:02: I got interested and downloaded it to try myself. I installed 9.0 in virtualbox using the guided option and it installed. just wondering if you tried installing with guided option instead of manual? Now I will try using manual and see what happens I did not try guided. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: Webmail for local system mail
sysutils/webmin will work without much configuration. Some of the other more traditional one like squirrelmail will work as well, but some extra config may be required. Webmin++ (and just plain handy for a whole lot more!) Dale ___ 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: AMD64 with 9.0 PRERELEASE freezing/hanging without any messages
On Sat, 19 Nov 2011 12:54:18 +0200 (EET) j...@iki.fi (Jukka A. Ukkonen) wrote: Hello, Has anyone else noticed a similar odd behavior with AMD64 and 9.0 prerelease (as well as RCs and betas)? Yes, I've seen a few of these myself, under both of the RCs and PRERELEASE. No idea what the cause is, though. Impossible to track down. On my 12 core (2*4162EE) the whole system just freezes quite often without any warning, without any messages being logged. Neither is there any panic message from the kernel. The system just suddenly hangs such that there is no alternative but to reboot using the reset button. Yes, exactly the same here. Doesn't happen often, but it does happen. At the moment I don't have any further info about the cause of the problem, but quite often the freeze has happened when there has been some network activity. Does anyone have an idea how to start tracking down such a problem? I mean anything in addition to this... http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html Sorry, wish I had a clue as to how to pinpoint the cause of these hangs. There's no record anywhere of what may have gone wrong. If you find out anything, please let us know. -- Conrad J. Sabatier conr...@cox.net ___ 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: epson printers on amd64
On Sun, 20 Nov 2011, per...@pluto.rain.com wrote: Warren Block wbl...@wonkity.com wrote: On Sat, 19 Nov 2011, David Southwell wrote: Anyone up to date on how to do high quality printing with epson inkjet printers (in my case r2400 and r2880) on amd64 systems. print/pips* reports they require 386 and do not compile on amd64. print/gimp-gutenprint works pretty well from Gimp, although I have not figured out how to get consistent color and brightness. It supports both of those printers. I'm sure I'm not alone in doubting that _any_ ink-spitter is likely to produce high quality printing or consistent color and brightness, regardless of the host support used. Those printers are designed to be manufactured as inexpensively as possible so as to be sold at very low prices, the profit being in the recurring ink sales. Cheap and high quality tend to be incompatible design goals. (Sorry, I hadn't realized I was replying on -emulation, which is meant for computer emulation. CCed to -questions on this reply.) Quality color photos are the one area where inkjets really can do a good job. Experimenting with cheap Epson R200 and R280 has shown that they can print better quality photos than local photo printing places. Color and brightness are consistent until I print a different photo. Gutenprint saves the settings, it's just that they don't work the same with different photos. Possibly this is due to my changing the wrong adjustments. Oh, and I've only used Gutenprint on 32-bit systems so far. ___ 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: where to ask about problems with bsdinstall in 9.0RC2?
On 19/11/2011 22:36, William Bulley wrote: Possible, but unlikely. Plus I doubt that 'tar -tvf base.txz' without a pipe having an xzcat(1) in front of the tar(1) command. Maybe there is an xz option for tar(1) during extraction mode, but my tar(1) man page doesn't list any, sigh... It does list -y and -z options for other compression/decompression modes, hmmm :-( bsdtar(1) -- accept no substitutes. Well, actually, it's libarchive which bsdtar is built on top of. It automatically recognizes most compression formats and most types of data archive -- including a few that you probably wouldn't have thought of in that context. Try running it against a .iso CDRom image. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: 8.2-RELEASE-p4
On 19/11/2011 23:26, Robert Simmons wrote: On Fri, Nov 18, 2011 at 3:50 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: If you compile your own kernel, then freebsd-update will patch the kernel sources, but leave you to rebuild and reinstall your customized kernel. I don't know about the -p4 update. By rights it should have involved updating the kernel by one or other of the two methods shown. So far however, we've seen two reports questioning that[*] and none saying that the -p4 update did in fact update the kernel. Which is suspicious, but hardly conclusive. Do you compile your own kernel, or do you have a machine that uses GENERIC? If you do, what is the output of uname -a on it? Me personally? No, in general I track -STABLE on my systems. Try asking the OP. Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
