Re: Regarding MANCOLOR
Hi, On Sun, Feb 12, 2012 at 05:10:44PM -0600, Germán M. Bravo wrote: > Hello, I saw you wronte something in the mailing lists, some time ago, > regarding MANCOLOR in FreeBSD... however, I've tried in every way I > can to make it work, but I cant. > > I'm using TERM=xterm-256color and if I have MANCOLOR=1, I see no > coloring in my man pages. If I don't set MANCOLOR, and instead set > LESS_TERMCAP_* env variables, I do see colors in my terminal (it > doesn't start with less by default, so I have to use MANPAGER=less > too, if I want it to use less)... If I set both LESS_TERMCAP_* and > also MANCOLOR=1, man starts with the `less` pager by default, but I > see no colors (even with LESS_TERMCAP_* added) > > Could you shed some light in this issue if you can? > I'm trying all this under FreeBSD 9.0 in a remote SSL terminal > (xterm-256color) Support for colors in man(1) and groff(1) doesn't mean that manpages got painted. One manpage is sure colorized, one that talks about color support. Try it: man grotty ___ 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: who do you install freebsd without sysinstall?
On Thu, Aug 31, 2006 at 08:24:45AM -0700, backyard wrote:
> how does cron save entropy??? I've noticed "saving
> entropy files" at shutdown but have always wondered
> what it is using. or does it just read from
> /dev/random?
>
# Save some entropy so that /dev/random can re-seed on boot.
*/11* * * * operator /usr/libexec/save-entropy
The latter saves some amount of /dev/random for further
seeding. /entropy is saved by /etc/rc.d/random, when
it stops.
random_stop()
{
# Write some entropy so when the machine reboots /dev/random
# can be reseeded
#
I think two mechanisms exist because a solution involving
cron(8) works better, but cron(8) is not guaranteed to be
up and running (untypical but anyway), so additionally an
entropy is also saved once on shutdown.
Cheers,
--
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer
pgp9wxz9np6t0.pgp
Description: PGP signature
Re: who do you install freebsd without sysinstall?
On Thu, Aug 31, 2006 at 07:53:28AM -0700, backyard wrote: > Out of curiosity... > > So If I made a custom boot cd I could boot a dead box, > setup the drives and slices, CVSUP the system I want > to build, tweak the build environment for the proper > temporary build locations and build a system from > source and install that system to the now live box, > boot it and be done? > Basically yes. When booting from CD though, I'll have to mdconfig(8) and re-mount at least /tmp, maybe /var as well. > also along these lines how do I make the system allow > me to seed the entropy engine? Usually after an > install it asks to fill in a screen full of junk, but > with a custom install it doesn't do this for me, at > least not the last time I tried. Just curious, > especially if I attempt the above procedure. > Well, it does this only if the below conditions are met: 1) You have enabled sshd(8) in sysinstall(8), so it's enabled in /etc/rc.conf. 2) This is the first boot, /etc/rc.d/sshd needs to generate new SSH keys but random(4) hasn't been seeded yet. (random(4) is seeded by the /random and /var/db/random/* files.) So, if you did a custom install and then rebooted for the first time, but did not yet enable sshd(8), the cron(8) will save some entropy, so the time you need it to generate SSH keys there will already be some entropy available. But if you absolutely need to reseed manually, boot into single-user mode, and type rm /entropy /var/db/entropy/* Then proceed with normal booting. If sshd(8) is enabled, it will ask you to enter some entropy. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpqXXoIcTwku.pgp Description: PGP signature
Re: who do you install freebsd without sysinstall?
[ added freebsd-questios@ ] On Thu, Aug 31, 2006 at 02:08:59AM +0200, Thomas Vogt wrote: > Hello > > In this emails > <http://docs.freebsd.org/cgi/getmsg.cgi?fetch=244762+0+current/cvs-src> you > wrote that you don't install freebsd with sysinstall. May I ask you how you > do this? Maybe in some way like this: > <http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/>? > > I'm just curious. > Plenty of options, depending on the available environment and needs. 1) Add a spare disk to an existing FreeBSD box, and populate it using installworld/installkernel/distribution targets and specifying DESTDIR pointing to a mounted spare disk. 2) Boot from live-system on CD-ROM, prepare and partition the disk(s), install distributions manually through install.sh scripts. 3) Boot from live-system on CD-ROM, prepare and partition the disk(s), CVSup, build/install from sources. 4) Boot in a PXE/TFTP/NFS diskless environment (details are in the Handbook), install distributions using a shell script as above. Distributions may come from either remote CD-ROM media, or be prepared by "make release" and made available over NFS to diskless clients. A modification of this approach includes a mass deployment option that involves writing (relatively simple) local installation scripts that automate the tasks. Many other options... Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpE96BCik3vq.pgp Description: PGP signature
Re: bad udp cksum 26ff!
On Mon, Nov 28, 2005 at 10:46:38AM -0800, John Palmer wrote: > I am running FreeBSD 5.4 p8. I did a tcpdump -vv -i em0. The output > produced > a "bad udp cksum" with my DNS server. Does anyone know what it means? Or, > how I can > correct the problem? > Turn off hardware checksums on em0, to make tcpdump(1) happy. Harmless otherwise. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpi6S3ZEt6Tj.pgp Description: PGP signature
Re: issues with installworld on fbsd6 & libcom_err
On Fri, Nov 11, 2005 at 09:17:10AM -0500, Eric Ekong wrote: > I had no errors when building world, but it seems each time I have > tried to installworld I come up with the same error. It shows up in > the lib/libcom_err directory. No matter what shell I try fixes the > issue. I have gone as far as to delete all the directories in /usr/src > and re cvsup. I have no options in /etc/make.conf outside of the > ones put there by perl and KERNCONF=KERNELNAME. Like I said it builds > with no problem, but error code 1 outs each time during make > installworld. > You're probably using -jX with installworld. If so, a fix for this has been in HEAD as of a few days: : ru 2005-11-03 08:56:39 UTC : : FreeBSD src repository : : Modified files: : .Makefile.inc1 : share/mk bsd.info.mk : Log: : Serialize access to the info/dir file; needed for parallel installs. : : Reported by:scottl : : I'm not very fond of using the non-standard lockf(1) here, but I : have no better idea at the moment. NetBSD uses ln(1) to create a : lock file, but this approach can result in a deadlock if make is : interrupted, leaving an orphaned lock file. : : Revision ChangesPath : 1.514 +1 -1 src/Makefile.inc1 : 1.72 +1 -0 src/share/mk/bsd.info.mk I'm not happy with this because it broke NFS installs. Once I find a proper fix, I will also make sure to MFC it to RELENG_6. > ===> lib/libcom_err (install) > install -C -o root -g wheel -m 444 libcom_err.a /usr/lib > install -C -o root -g wheel -m 444 libcom_err_p.a /usr/lib > install -s -o root -g wheel -m 444 libcom_err.so.3 /usr/lib > ln -fs libcom_err.so.3 /usr/lib/libcom_err.so > install -C -o root -g wheel -m 444 > /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h > /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include > install -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 > ===> lib/libcom_err/doc (install) > install-info --quiet --defsection="Programming & development tools." > --defentry="* libcom_err: (com_err).A Common Error Description > Library for UNIX." com_err.info /usr/share/info/dir > install-info: /usr/share/info/dir: empty file > *** Error code 1 > > Stop in /usr/src/lib/libcom_err/doc. > *** Error code 1 > > Stop in /usr/src/lib/libcom_err. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > Any suggestions on how to fix this so I can get fbsd 6 world installed > so I can run portmanger to update a crap load of ports would be > appreciated. -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpqb6qBHT61e.pgp Description: PGP signature
Re: Periodic Weekly Report
On Sun, Oct 02, 2005 at 06:57:33AM -0400, Gerard Seibert wrote: > On Sat, 1 Oct 2005 21:22:39 +0300, Ruslan Ermilov <[EMAIL PROTECTED]> > Subject: Re: Periodic Weekly Report > Wrote these words of wisdom: > > > On Sat, Oct 01, 2005 at 01:51:19PM +0300, Giorgos Keramidas wrote: > > > On 2005-10-01 06:18, Gerard Seibert <[EMAIL PROTECTED]> wrote: > > > > I received this report after 'periodic weekly' had completed its run. > > > > > > > > Cleaning up kernel database files: > > > > > > > > Rebuilding locate database: > > > > > > > > Rebuilding whatis database: > > > > > > > > Reformatting manual pages: > > > > Usage: .Ft function_type ... (#284) > > > > Usage: .Ft function_type ... (#348) > > > > > This is a markup bug in some manpage. > > > > > > mdoc warning: .Fx: Unknown FreeBSD version `5.4' (#94) > > > > mdoc warning: .Fx: Unknown FreeBSD version `5.4' (#94) > > > > > This is a result of FreeBSD 5.4 being mistakenly remove from > > mdoc-local. I've re-added it to the RELENG_5 now, so it > > should be fixed if oyu're tracking RELENG_5. > > > > > > catman: /usr/local/lib/perl5/5.8.7/man/cat3: mkdir: Permission denied > > > > catman: /usr/local/lib/perl5/5.8.7/perl/man/cat3: mkdir: Permission > > > > denied > > > > > This is a bug in the use.perl script: it should also create the > > "cat3" directory mentioned above, with "man:wheel" ownership. > First, do I have to rebuild world to correct the "mdoc warning: .Fx: > Unknown FreeBSD version `5.4' (#94)" error? > You should cvsup to the latest RELENG_5 (assuming you were tracking it). Then after the next buildworld/installworld this problem will go away. OTOH, it doesn't do any harm and you can safely ignore it. > Second, regarding the bug in "use.perl.script", exactly how do I go > about correcting that, or don't I? > Either fix the port (one line), or create the said directory manually with the correct ownership. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpzKNSWP8xcx.pgp Description: PGP signature
Re: Periodic Weekly Report
On Sat, Oct 01, 2005 at 01:51:19PM +0300, Giorgos Keramidas wrote: > On 2005-10-01 06:18, Gerard Seibert <[EMAIL PROTECTED]> wrote: > > I received this report after 'periodic weekly' had completed its run. > > > > Cleaning up kernel database files: > > > > Rebuilding locate database: > > > > Rebuilding whatis database: > > > > Reformatting manual pages: > > Usage: .Ft function_type ... (#284) > > Usage: .Ft function_type ... (#348) > This is a markup bug in some manpage. > > mdoc warning: .Fx: Unknown FreeBSD version `5.4' (#94) > > mdoc warning: .Fx: Unknown FreeBSD version `5.4' (#94) > This is a result of FreeBSD 5.4 being mistakenly remove from mdoc-local. I've re-added it to the RELENG_5 now, so it should be fixed if oyu're tracking RELENG_5. > > catman: /usr/local/lib/perl5/5.8.7/man/cat3: mkdir: Permission denied > > catman: /usr/local/lib/perl5/5.8.7/perl/man/cat3: mkdir: Permission denied > This is a bug in the use.perl script: it should also create the "cat3" directory mentioned above, with "man:wheel" ownership. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpYzynkFNVBn.pgp Description: PGP signature
Re: error when use table option with ipfw
On Tue, Aug 23, 2005 at 11:10:33AM +0300, vladone wrote:
> Hi!
> I try to use table option but not work.
> First, i use Freebsd 5.4 release.
> In short i have:
> cmd="ipfw -q"
>
> $cmd table 1 add 192.168.0.0/24
> $cmd table 1 add 192.168.2.0/24
> $cmd table 1 add 192.168.3.0/24
> $cmd table 1 add 192.168.4.0/24
>
> $cmd add 700 count ip from table(1) to any via $lif
>
> When i run the script i receive an error about syntax error "ipfw.sh: 78:
> Syntax error: "(" unexpected".
> I dont understand where is error?
> Need some compiler options to work with this option?
> If i give:
> #ipfw table 1 list
> i have list of entries in this table without any error.
>
Since this is a shell script, `(' has a special meaning to group
commands for executing them in a sub-shell. To cancel a special
meaning, you can prefix it with the `\' character.
Cheers,
--
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer
pgplCf2upFVBV.pgp
Description: PGP signature
Re: buildworld error in Makefile.inc1
On Thu, Feb 03, 2005 at 10:53:24AM -0500, Glenn Sieb wrote: > Kris Kennaway said the following on 2/3/2005 12:29 AM: > > >On Wed, Feb 02, 2005 at 10:25:38PM -0500, Glenn Sieb wrote: > > > > > >>Stop in /usr/src. > >># > >> > >>So, should this upgrade be this painful? 5.1-RELEASE-p17 isn't _that_ > >>old.. I kind of wonder now what's going to happen when I upgrade one of > >>my boxes from 4.11-RELEASE to 5.3-RELEASE? :-/ > >> > >> > >Typically we only support source upgrades from systems after a certain > >point. Talk to [EMAIL PROTECTED] about the status of upgrading from > >5.1-RELEASE. > > > > > Thanks, Kris.. it appears that doing make -DALWAYS_CHECK_MAKE did the > trick for me (which would have happened had I just done a buildworld, > from what Ruslan said). > > Great appreciation from me to everyone who helped out on this issue. > This makes my life MUCH easier tonight. :) > Don't ask me why ALWAYS_CHECK_MAKE was invented, I pathologically hate it. :-) Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgp20z2buH81k.pgp Description: PGP signature
Re: Micronet SP 2610/2612 10/100/1000 with FreeBSD 4.9 Stable :: Which driver to load?
On Sat, Apr 03, 2004 at 04:11:33AM -0600, [EMAIL PROTECTED] wrote: > Dear All > Please DO NOT cross-post! > Hellow. Neither google nor the search facility in this list returned any > answer. > > I am trying to install the Micronet SP 2610/2612 gigabit NIC. But it is not at > all loaded. During boot, it goes like > [...] > pci0: (vendor=0x100b, dev=0x0022) at 8.0 irq 11 According to the PCI database, this is the National Semiconductor DP83820/1 10/100/1000 Gigabit Ethernet Adapter. As such, it should be supported by the nge(4) driver. The reason why it's not detected during the initial installation is because the GENERIC kernel doesn't include this driver [sic]. Just type ``ifconfig nge0'' under root, and the driver will be loaded automatically. You can then either put the following line in your /boot/loader.conf file, nge_load="YES" or compile a custom kernel which includes the nge(4) driver. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: FreeBSD 5.2-RELEASE buildworld failure.
On Fri, Jan 23, 2004 at 06:13:24PM -0800, erek wrote: > I cvsuped today using tag RELENG_5_2 (i'm already using 5.2-RELEASE), [...] > During the buildworld I get this VERY odd error: [...] > /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use poisoned > "malloc" [...] > mkdep: compile failed > *** Error code 1 [...] > any suggestions? > Go to /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus, and compare parse.c and parse+%DIKED.c there. They should be different, "xmalloc" vs "malloc", "xrealloc" vs "realloc. If they are identical, chances are your /usr/bin/sed is probably broken, and you should read this entry from src/UPDATING: : 20030613: [retrospective] : There was a small window in which sed(1) was broken. If you : happen to have sed(1) installed during that window, which is : evidenced by an inability to build world with the failure : given below, you need to manually build and install sed(1) : (and only sed(1)) before doing anything else. This is a one- : time snafu. Typical failure mode: : : In file included from /usr/src/contrib/binutils/bfd/targets.c:1092: : targmatch.h:7:1: null character(s) ignored : targmatch.h:12:1: null character(s) ignored : targmatch.h:16:1: null character(s) ignored : : : : The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC : to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of : usr.bin/sed/process.c). To see if you're affected, run this: ident /usr/bin/sed And see which process.c revision your sed(1) has. It if's 1.30, you're affected. Cheers, -- Ruslan Ermilov FreeBSD committer [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Strange problem with "make clean"
On Fri, Jun 13, 2003 at 03:59:06PM +0200, Alessandro de Manzano wrote: > Hello, > > I'm experiencing a weird problem doing "make clean" in "/usr/src". > > It happens on a couple of FreeBSD 4.8-RELEASE machines (RELENG_4_8 to > be precise). > > Cvsup, build & install phases all went fine, just "make clean" went > wrong. > > I tried rm-ing the incriminated subdirectory and even rm-ing the > checkout.cvs:RELENG_4_8 file and re-cvsupping but nothing changes. > > > Here is the error log: > > [...] > rm -f telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o > telnet.o terminal.o utilities.o telnet.1.gz telnet.1.cat.gz > ===> secure/usr.bin/openssl > rm -f buildinf.h openssl/opensslconf.h openssl/evp.h xopenssl > app_rand.o apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o > dhparam.o dsa.o dsaparam.o enc.o engine.o errstr.o gendh.o gendsa.o > genrsa.o nseq.o ocsp.o openssl.o passwd.o pkcs12.o pkcs7.o pkcs8.o > rand.o req.o rsa.o rsautl.o s_cb.o s_client.o s_server.o s_socket.o > s_time.o sess_id.o smime.o speed.o spkac.o verify.o version.o x509.o > CA.pl.1.gz asn1parse.1.gz ca.1.gz ciphers.1.gz crl.1.gz crl2pkcs7.1.gz > dgst.1.gz dhparam.1.gz dsa.1.gz dsaparam.1.gz enc.1.gz gendsa.1.gz > genrsa.1.gz nseq.1.gz ocsp.1.gz openssl.1.gz passwd.1.gz pkcs12.1.gz > pkcs7.1.gz pkcs8.1.gz rand.1.gz req.1.gz rsa.1.gz rsautl.1.gz > s_client.1.gz s_server.1.gz sess_id.1.gz smime.1.gz speed.1.gz > spkac.1.gz verify.1.gz version.1.gz x509.1.gz CA.pl.1.cat.gz > asn1parse.1.cat.gz ca.1.cat.gz ciphers.1.cat.gz crl.1.cat.gz > crl2pkcs7.1.cat.gz dgst.1.cat.gz dhparam.1.cat.gz dsa.1.cat.gz > dsaparam.1.cat.gz enc.1.cat.gz gendsa.1.cat.gz genrsa.1.cat.gz > nseq.1.cat.gz ocsp.1.cat.gz openssl.1.cat.gz passwd.1.cat.gz > pkcs12.1.cat.gz pkcs7.1.cat.gz pkcs8.1.cat.gz rand.1.cat.gz > req.1.cat.gz rsa.1.cat.gz rsautl.1.cat.gz s_client.1.cat.gz > s_server.1.cat.gz sess_id.1.cat.gz smime.1.cat.gz speed.1.cat.gz > spkac.1.cat.gz verify.1.cat.gz version.1.cat.gz x509.1.cat.gz > rm: openssl/opensslconf.h: Not a directory > rm: openssl/evp.h: Not a directory > *** Error code 1 > > Stop in /usr/src/secure/usr.bin/openssl. > *** Error code 1 > This means that either /usr/obj/usr/src/secure/usr.bin/openssl or /usr/src/secure/usr.bin/openssl have the "openssl" file, where it's supposed to be a directory in /usr/obj/... rm -r /usr/obj/usr/src/secure/usr.bin/openssl What "make clean" is trying to do is equivalent to trying to "rm /COPYRIGHT/foo". Note that "make clean" is only guaranteed to work if the object tree was populated using this same sources; everything else is not guaranteed to work, and "make cleandir" is advised instead, though even this may break when the types of some files change from "file" to "directory", like has happened with /usr/obj/usr/src/secure/usr.bin/openssl/openssl. Are you perhaps downgrading from 5.x? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: natd and logging
[Redirected to -questions] On Tue, Jun 03, 2003 at 01:48:57PM -0700, Sean Murphy wrote: > I have setup natd, enabled logging with -l and it is working > perfectly. However is there a more detailed log to see the translation > tables. I need to log the ipaddress internal 172.*.*.* to the outside with > what port is being used. natd just seems to log the statistics such as > icmp=5 and so on. If natd does not have this function what does? > You can have it run in the -verbose mode; that will show all the alterations it's doing. The output is to standard output, please refer to the natd(8) manpage for details. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Remote power control / serial console
Hi! Can anyone recommend a good and relatively cheap 4-port remote power control / serial console solution? (All four manageable boxes are running FreeBSD.) Has anyone by chance had an experience with http://www.dataprobe.com/share/4pk415.html Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
