Re: Portupgrade Utility
While portupgrade is a fantastic tool, don't forget it's _port_upgrade and only applies to ports, so isn't really much use as a base tool, nevermind issues about its dependencies. Since I've not had the newbie experience for a while, I don't know where the typical new user would first find out about portupgrade. I'd consider it on a par with mergemaster for the base system in terms of utility, but a quick look around the docs doesn't turn up any mention of it. Where would the typical new user first find out about portupgrade? Would additional documentation be useful and if so, then where: sysinstall, *.TXT, /usr/share/doc, handbook or elsewhere? One concern is the frequent updates to portupgrade and its dependencies, although I haven't noticed any functional changes or significant breakage affecting my usage. -Andrew- -- ___ | -Andrew J. Caines- Unix Systems Engineer [EMAIL PROTECTED] | | "They that can give up essential liberty to obtain a little temporary | | safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Is VESA_800x600 hardcoded to 80x25? patch @100 Hz
On Sun, Jan 06, 2002 at 05:42:48PM +0100, Andreas Ntaflos wrote:
| On Sun, Jan 06, 2002 at 03:42:30PM +, Nuno Teixeira wrote:
| >
| > Hello to all,
| >
| > For the first time I configured VESA and SC_PIXEL_MODE in kernel to reach
| > VESA_800x600 (100x37).
| >
| > When I used vidcontrol to do this I noted that I only can get a smaller
| > "window" in the middle of the screen (80x25).
| > [snip]
| > ---
| > Message:
| > >... knowing that 800x600 / 8x16 = 100x37.5 I should be able to do better.
| > >I switched to VESA_800x600, but instead of getting 100x37 I just get 80x25
| > >in a smaller "window" in the middle of the screen.
| > >
| > >1) Is VESA ... hardcoded to 80x25?
| > >
| > >2) Is this combo hardcoded to 4-bit color?
| >
| > 1) Yes, VESA_800x600 is hardcoded to 80x25 in vidcontrol.c, but it is easy
| > to fix. Just make the following change and recompile:
| >
| > if (mode == SW_VESA_800x600) {
| > [snip]
|
| In order to have VESA_800x600 use the full screen of the virtual console,
| run the following:
|
| # vidcontrol -g 100x37 VESA_800x600 -f whatever_font_you_want
|
| This will resize it to the said geometry of 100x37 chars at a resolution
| of 800x600.
|
| The rc.conf entries look like this on my box:
|
| allscreens_flags="-g 100x37 VESA_800x600"
| font8x16="/usr/share/syscons/fonts/iso15-8x16.fnt"
|
| This should work just fine and fill up the whole available screen.
|
| I just don't like the low refresh rate of 60Hz, after some time, it blinds
| my head :)
|
| Does anyone know how to increase the vert. refresh at 800x600?
|
| regards
| --
| Andreas "ant" Ntaflos
| [EMAIL PROTECTED]
| Vienna, AUSTRIA
Hi,
I've found a patch to VESA_800x600 @100Hz
Here is the link if you are interested:
http://groups.google.com/groups?threadm=87bsxsnoxm.fsf%40rnd.donetsk.ua&rnum=11&prev=/groups%3Fq%3Dfreebsd%252Bconsole%252Bvesa%252Brefresh%26start%3D10%26sa%3DN
Bye,
--
Nuno Teixeira
pt-quorum.com
/*
PGP Public Key:
http://www.pt-quorum.com/pgp/nunoteixeira.asc
Key fingerprint:
8C2C B364 D4DC 0C92 56F5 CE6F 8F07 720A 63A0 4FC7
*/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Could someone commit the change suggested in PR bin/32420?
recently we setup msyslog-1.08a on a number of freebsd and solaris based boxes, syslogging to a mysql backend. this makes it easy to setup notification mechanisms, do ad hoc queries and reporting. a web front end to the database is easily done with php :^) for a help desk to use for problem research. On 1/5/02 at 3:21 PM Brett Glass wrote: > >At 02:38 PM 1/5/2002, Jordan Hubbard wrote: > >>Of course, collecting log data for analysis from syslog is pretty >>low-tech when it comes to detecting and/or stopping attacks in >>real-time and I'd hope this wouldn't be encouraged as a general >>practice. > >I can't see any reason not to use syslogd, or something like it, >as a source of information for an IDS or log monitor, though there >may of course be other sources of input for these facilities too. > >>If that's your aim then you should be campaigning for a >>/dev/audit device and the instrumenting of suitable logpoints in the >>kernel and various utilities. Then your stuff just opens /dev/audit, >>registers an event selection mask with it, and goes to sleep waiting >>for events. > >The situation is a bit more complex than this. One will also want >the ability to do remote auditing -- something that a /dev/audit >wouldn't by itself allow. My personal opinion is that the architecture >of syslogd itself was fine when Eric created it but is now probably out >of date, and that a new backward compatible facility should be >crafted. But for the nonce, other things can be layered on top of >syslogd so long as the compression is disabled. This allows new ideas >to be tested without unduly perturbing anything. > >The repeat counter causes log messages to be delayed for an indeterminate >amount of time and so one should be able to disable it. Archie's new >command line option does this. The only hitch I can foresee is that it >is global; that is, it applies to every destination. I'd like even more >to be able to disable compression on a per-line basis in syslog.conf. >(The internal data structures of syslogd make this convenient to >implement, because one struct is maintained per destination.) I've toyed, >for example, with the idea of using a single character prefix to indicate >that a file, remote machine, or piped app should not get log compression. >For example, a file with log compression would be designated as before -- >e.g. /var/log/foo.log -- while one with no compression would be specified >as +/var/foo.log. Likewise, a piped app without compression would be >+|/usr/local/bin/mylogmonitor, and a remote machine that didn't want >compression (perhaps because it was running a log monitor at the >other end) would be [EMAIL PROTECTED] The plus character is unambiguous >and so there wouldn't be problems with backward compatibility. > >--Brett > > > >--Brett > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message -- __ / )_/_ It is a capital mistake to theorise before one has data. /--/ __ /Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, WH7N - FISTS #7448 Bank of Hawaii Network Services http://www.pilikia.net [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: how to tell if 'make buildworld' finished?
Christopher Schulte <[EMAIL PROTECTED]> wrote:
> At 10:37 PM 1/6/2002 +0100, you wrote:
> >I usually run a shell command like this ('#' is the prompt):
> ># (date; make buildworld; date) | tee /var/tmp/buildworld.log
>
> You can also look at the `script` command. When executed, a new shell will
> begin and all output to terminal is stored in a file which can be checked
> after the fact.
I know about script, but I don't like it that much.
It tends to destroy my carefully crafted zsh prompt
(which is not simply a "#", of course). :-}
Regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
"All that we see or seem is just a dream within a dream" (E. A. Poe)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Status, USB/Olympus E-10
(cc'ed to -scsi) Hello, A couple of committers & I were working last July (2001) with support for the Olympus E-10 digital camera in FreeBSD. This is a USB device. I just saw some commits in cam/scsi_da for Nikon & I'm wondering what the situation is wrt Olympus? The problem I was having was that even though FreeBSD (then 4.3-stable) would recognise the camera, if I tried to mount() it the os would reboot(!) :(( No panic, no nothing, just a hard freeze & rebooting. Obviously, this is Very Very Bad. I've seen Linux (2.4-something) working with this just fine. Linux sees this camera as a SCSI device with a MS-DOS filesystem. I'm now running a 4.5-PRERELEASE & wonder if, assuming this hasn't been fixed since 4.3, that this might be fixed in 4.5? At least if the camera isn't/can't be supported in time (for 4.5), is there some way we could at least protect the system from the rebooting? I can probably help test. I'm thinking of filing a PR, but seek advice before doing that. Many thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: how to tell if 'make buildworld' finished?
in message <[EMAIL PROTECTED]>,
wrote Christopher Schulte thusly...
>
> At 10:37 PM 1/6/2002 +0100, you wrote:
> >Hi,
> >
> >I usually run a shell command like this ('#' is the prompt):
> ># (date; make buildworld; date) | tee /var/tmp/buildworld.log
>
> You can also look at the `script` command. When executed, a new shell will
> begin and all output to terminal is stored in a file which can be checked
> after the fact.
christopher, i know about the command "script". i avoid it whenever
i can for two reasons: (1) sometimes it's impossible to send SIGTSTP
(STOP signal from keyboard) and (2) control characters at the end of
line.
i use following syntax as appropriate...
# command >& log
# command > log 2>&1
# command | tee [-a] log
thanks anyway.
- parv
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: how to tell if 'make buildworld' finished?
in message <[EMAIL PROTECTED]>,
wrote Oliver Fromme thusly...
>
> Hi,
hi there.
> I usually run a shell command like this ('#' is the prompt):
> # (date; make buildworld; date) | tee /var/tmp/buildworld.log
>
> So you have a datestamp output at the very beginning and at
> the very end.
thanks oliver. somebody, off the list, contacted me w/ similar
clue. he preferred to use this syntax...
# date && command && date
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: building kernel problem w/ linux_proto.h
in message <[EMAIL PROTECTED]>, wrote Brian T. Schellenberger thusly... > > On Sunday 06 January 2002 10:28 am, parv wrote: > > hi, > > > > i cvsup'd old sources (4-stable oct 13 2001) to current (4-stable > > 2002.01.05.15.45.19). at this point i am stuck at errors w/ > > linux_proto.h ... > > first i ran make cleandir in /usr/src, removed /usr/obj/*, and tried > > to build kernel. after first snag, i searched the internet which > > indicated to read src/UPDATING. > > > > well, first i did "make modules-clean" in > > src/sys/compile/$KERNCONF as i do not have MODULES_WITH_WORLD=yes in > > /etc/make.conf. after that when i tried again, it failed. so i > > tried again after running "make cleandir" in src/sys/modules/linux > > w/o any success. > > This is probably a more subtle fix than this, but the following is what > finally worked for me: > > rm -r /usr/obj > rm -r /usr/src > cvsup /root/sup/conf > ln -s /root/BTS /usr/src/sys/i386/conf ... > CAUTION2: Without a broadband, this would be tiresome--it causes the entire > source to be re-downloaded from the net. you know what, that's exactly what i am doing right now... it started at 2.43p edt, and currently cvsup is downloading src/contrib/ncurses; time now is 6.23p. a long way to go on dial up connection. > NOTE: There is almost certainly a more subtle solution. But if you have a > fast connection, just doing the above is probably a lot easier & less > frustrating than tracking it down. i would sure hope that somebody else will track it down, as doing fresh cvsup of src tree needs patience, at least on dial up connection. thanks brian. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: building kernel problem w/ linux_proto.h
The UPDATING instructions also didn't work for me, though I did this over a month ago. I seem to recall that rm -rf /usr/src/sys/modules/linux /usr/src/sys/compat/linux followed by a cvsup; make buildworld && make buildkernel got things going again. A bit of a sledgehammer, I admit. jay parv wrote: > in message <[EMAIL PROTECTED]>, > wrote M. Warner Losh thusly... > >>In message: <[EMAIL PROTECTED]> >>parv <[EMAIL PROTECTED]> writes: >> > ... > >>: well, first i did "make modules-clean" in src/sys/compile/$KERNCONF >>: as i do not have MODULES_WITH_WORLD=yes in /etc/make.conf. after >>: that when i tried again, it failed. so i tried again after running >>: "make cleandir" in src/sys/modules/linux w/o any success. >> >>If you are building the kernel by hand, try rm -rf modules in >>src/sys/compile/$KERNCONF. >> > > yes, sometimes i build kernel by hand; and since 4-stable, i build > kernel w/ world every time via KERNCONF. > > i did try that; didn't work. then i tried after obliterating the > src/sys/compile/$KERNCONF, that didn't work either. unless, > somebody has any other option, i will try w/ clean cvsup'd "src" > tree. > > before i do that, is there anything else that i could do manually? > > - parv > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Could someone commit the change suggested in PR bin/32420?
At 03:01 PM 1/6/2002, Arthur W. Neilson III wrote: >recently we setup msyslog-1.08a on a number of freebsd and solaris >based boxes, syslogging to a mysql backend. I'd be concerned about the overhead of a full-fledged SQL database Seems like overkill to me. Also, I believe that "msyslog" and "mySQL" are both GPLed. No commercial programmer can safely look GPLed code, because if he does so he may later be sued for creating a "derivative work" if he writes something containing similar algorithms or functionality. Thus, we could only use such software as a "black box;" if there were a bug, we couldn't fix it due to the risk of GPL contamination. We'd rather use code that's licensed under a truly free (TF) license, such as the BSD License. --Brett To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: zh_CN support in tcsh (was: Re: Fwd: Re: FreeBSD ja_JP.eucJP and ko_KR.eucKR)
hello, At Sun, 6 Jan 2002 20:38:45 +0200, Alexey Zelkin wrote: > I've extended patch for tcsh which includes autodetection of eucXX > like locales for ja_JP and ko_JR. This patch includes detection > of alias for ja_JP.SJIS (ja_JP.Shift_JIS) locale and *most important* > detection of Chinese EUC locale (zh_CN.EUC and zh_CN.eucCN) in same > manner as Japanese and Korean. > It would be nice if someone familiar with Chinese check original > version of tcsh (chinese support) and with this patch and notice > me any improvement/problems in results :-) For zh_CN.eucCN and zh_CN.EUC, it does the same thing as doing set dspmbyte=euc and it should allow input and editing of multibyte characters on the command line. As I do not use (and do not know) Chinese, I am not sure if it works with zh_CN.eucCN locale. Can anybody confirm that dspmbyte=euc feature works with zh_CN.eucCN (EUC-CN)? (i.e. can you input and edit zh_CN.eucCN characters on the tcsh command line when "set dspmbyte=euc"?) or does it anything wrong? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: building kernel problem w/ linux_proto.h
On Sunday 06 January 2002 10:28 am, parv wrote: > hi, > > i cvsup'd old sources (4-stable oct 13 2001) to current (4-stable > 2002.01.05.15.45.19). at this point i am stuck at errors w/ > linux_proto.h -- which had been reported at least since nov. 2001 > to this month. > > first i ran make cleandir in /usr/src, removed /usr/obj/*, and tried > to build kernel. after first snag, i searched the internet which > indicated to read src/UPDATING. > > well, first i did "make modules-clean" in > src/sys/compile/$KERNCONF as i do not have MODULES_WITH_WORLD=yes in > /etc/make.conf. after that when i tried again, it failed. so i > tried again after running "make cleandir" in src/sys/modules/linux > w/o any success. > > at this point would above two steps help if i revert to earlier > sources, and then back to current -stable? any other pointers? This is probably a more subtle fix than this, but the following is what finally worked for me: rm -r /usr/obj rm -r /usr/src cvsup /root/sup/conf ln -s /root/BTS /usr/src/sys/i386/conf CAUTION1: This wipes out your kernel configuration. I keep mine in /root all the time (I back up /root but not /usr/src), so I could just re-link it after the wipe (my kernel config is called BTS). If you don't, stuff it away someplace safe. CAUTION2: Without a broadband, this would be tiresome--it causes the entire source to be re-downloaded from the net. NOTE: There is almost certainly a more subtle solution. But if you have a fast connection, just doing the above is probably a lot easier & less frustrating than tracking it down. -- Brian T. Schellenberger . . . . . . . [EMAIL PROTECTED] (work) Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) http://www.babbleon.org ---> Free Dmitry Sklyarov! (let him go home) <--- http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Could someone commit the change suggested in PR bin/32420?
msyslog is pretty cool, it's modular and has a bunch of different input modules for tcp, udp, streams and unix domain sockets also output modules for mysql, postgres, peo (hash protection) and regex. it is worth exploring and actually is BSD licensed, as shown on the freshmeat homepage for the msyslog project http://freshmeat.net/projects/msyslog as for mysql, it's very fast and we already had it on our mrtg/rrdtool webserver which snmp monitors a number of machines. msyslog uses the c api in the mysql client library for database access. mysql is fully threaded and handles the load well. the COPYING file in the msyslog distribution describes the licensing terms thusly: msyslog source code files have either traditional BSD license, on the cases of files based on previous BSD syslog (syslogd.c, syslogd.h, ttymsg.c and om_classic.c), or a more permisive license known as modified BSD license, or MIT license, for the rest of the source files. However, this licensing scheme may change in the future, as BSD license has been changed by the Regent of the University of California. For more information on this, take a look at http://www.opensource.org/licenses the BSD license used is the following: Copyright (c) 1983, 1988, 1993, 1994 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors. 4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. MIT license used is: Copyright (c) 2001, Core SDI S.A., Argentina All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither name of the Core SDI S.A. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. It goes on to include the standard On 1/6/02 at 4:41 PM Brett Glass wrote: > >At 03:01 PM 1/6/2002, Arthur W. Neilson III wrote: > >>recently we setup msyslog-1.08a on a number of freebsd and solaris >>based boxes, syslogging to a mysql backend. > >I'd be concerned abou
Re: Could someone commit the change suggested in PR bin/32420?
At 05:10 PM 1/6/2002, Arthur W. Neilson III wrote: >msyslog is pretty cool, it's modular and has a bunch of different input >modules for tcp, udp, streams and unix domain sockets also output >modules for mysql, postgres, peo (hash protection) and regex. it is worth exploring >and actually is BSD licensed, as shown on the freshmeat homepage >for the msyslog project > >http://freshmeat.net/projects/msyslog I stand corrected. I was confusing it with "newsyslog," which is GPLed. --Brett To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
