Re: FTP stopped working - resend
(Resent as I didn't get a copy) Giorgos and Derek, Thank you for your replies. I don't know what happened, but all of a sudden ftp started working again. It could have been the Win XP machine I was using to access ftp on my server, I don't know. It was working fine, using WS_FTP Pro, to my other servers over the internet, but it wouldn't work here on its own LAN. I looked at xferlog, and saw that connection lines were entered, but the FTP LOGIN line wasn't there. Now that it is working, both lines show up in xferlog, as before. Giorgos, thanks for the example commands; All agree with your example returns except 'netstat -na | fgrep LISTEN | grep [:.]21', which returns 'grep: No match'. Am I missing something here? Thanks for the troubleshooting steps, I will review those commands and see what they do for me. Giorgios, you say "Stability is nice, isn't it? :)". Yes. But the problem is that it works so well for so long that I forget all I ever knew, and now it is obvious that I should update the system. I guess it's time to dust off the FreeBSD hat. Darek, It stopped working before I rebooted, and I have done literally nothing to this machine, except use Apache and ftp, for nearly a year. What is frustrating is that the problem went away! What now concerns me is that I did not receive a copy of my own post on this problem from the mailing list server, and I didn't get Giorgos' cc sent to [EMAIL PROTECTED] I used to get my posts back, but that was before I changed to this gmail account. If I don't receive this post, I'll go after that as a different problem. My ftp problem is "gone", but now a mailing list problem? Thanks again for the assistance. Jay O'Brien Rio Linda, California, USA Original Message Subject: Re: FTP stopped working Date: Mon, 9 Jan 2006 10:06:46 +0200 From: Giorgos Keramidas <[EMAIL PROTECTED]> To: Jay O'Brien <[EMAIL PROTECTED]> CC: freebsd-questions@freebsd.org References: <[EMAIL PROTECTED]> On 2006-01-08 23:44, Jay O'Brien <[EMAIL PROTECTED]> wrote: > I'm embarassed to say that FreeBSD was working so good for me > that I forgot how to make it work. It was up for over 300 days > when I rebooted today. Oops :) > All of a sudden I cannot access the computer via ftp. I have > been able to do so using WS_FTP Pro on my Windows CP Pro > computer, but now it doesn't even seem to accept the connect. > The connect is via a local LAN, using fixed IPs. > > Guidance in a troubleshooting mode would really be appreciated. First check that you truly have the ftpd binary: [EMAIL PROTECTED]:/root# ls -l /usr/libexec/ftpd -r-xr-xr-x 1 root wheel 96360 Jan 8 13:00 /usr/libexec/ftpd Then see if ftpd is supposed to start as 'standalone' or as a service controlled by inetd: [EMAIL PROTECTED]:/root# grep ftp /etc/rc.conf [EMAIL PROTECTED]:/root# grep inetd /etc/rc.conf inetd_enable="YES" [EMAIL PROTECTED]:/root# pgrep inet 651 [EMAIL PROTECTED]:/root# grep '^[[:space:]]*ftp' /etc/inetd.conf ftp stream tcp nowait root/usr/libexec/ftpd ftpd -l If inetd is running, pgrep should report its PID as above. Seeing no PID means that inetd failed to start. Your system logs at /var/log/messages will almost certainly have clues about the reason of the failure. Then, start checking if something *is* listening at port 21: [EMAIL PROTECTED]:/root# netstat -na | fgrep LISTEN | grep [:.]21 tcp4 0 0 *.21 *.*LISTEN [EMAIL PROTECTED]:/root# sockstat -4 -l -p 21 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root inetd 651 5 tcp4 *:21 *:* [EMAIL PROTECTED]:/root# If you don't have any indication how ftpd was started it's possible that you manually fired up ftpd and then promptly forgot about it, until you had to reboot. Stability is nice, isn't it? :) Original Message Subject:Re: FTP stopped working Date: Mon, 09 Jan 2006 10:29:58 -0600 From: Derek Ragona <[EMAIL PROTECTED]> To: Jay O'Brien <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Jay, By default ftp logs in the system log so tail that log file as you try to ftp. That should point you to the problem. As it was working until you rebooted, what changed before the reboot? Did you add tcp wrappers or other security measures? -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FTP stopped working
I'm embarassed to say that FreeBSD was working so good for me that I forgot how to make it work. It was up for over 300 days when I rebooted today. All of a sudden I cannot access the computer via ftp. I have been able to do so using WS_FTP Pro on my Windows CP Pro computer, but now it doesn't even seem to accept the connect. The connect is via a local LAN, using fixed IPs. Guidance in a troubleshooting mode would really be appreciated. Thanks, Jay O'Brien Rio Linda, CA , USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audit tools?
Clifton Royston wrote: > On Sun, Apr 24, 2005 at 01:08:55PM -0700, Jay O'Brien wrote: > >>Erik Trulsson wrote: >> >>>On Sun, Apr 24, 2005 at 08:02:39AM -0700, Jay O'Brien wrote: >>> >>>>What are the tools that I should use to audit an existing >>>>FreeBSD installation? Without changing anything, I wish >>>>to quickly determine what is installed, i.e., the basic >>>>system, ports and packages, and then to compare what is >>>>installed to the currently available versions. >>> >>>For ports/packages you can use pkg_info(1) to see what is installed, >>>and pkg_version(1) to compare what is installed to what is in the ports >>>tree. >>> >>>For the base system there is no corresponding way to see what is >>>installed or not. 'uname -a' will show which version of FreeBSD is >>>installed, but after that you will have to check manually to see if all >>>components are installed or not. >> >>Erik, >>Thanks; I was hoping that there were some additional tools that >>I hadn't found so far. At least you have confirmed that I'm >>following a reasonable procedure. >>Jay > > > You can check out the portupdate package, but of course if it's not > already installed, it doesn't meet your criteria of "without changing > anything." > > BTW, the above discussion is assuming you mean audit in the "taking > an inventory" sense. If you're talking about audit in the security > sense, the above doesn't do it, and you need to look at tools like > mtree (should be there as built-in), Tripwire (extra package), etc. > > -- Clifton > Clifton, You are right, I wasn't specific enough. By audit, I mean "taking an inventory", not looking for security holes. Thanks for your input! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audit tools?
Erik Trulsson wrote: > On Sun, Apr 24, 2005 at 08:02:39AM -0700, Jay O'Brien wrote: > >>What are the tools that I should use to audit an existing >>FreeBSD installation? Without changing anything, I wish >>to quickly determine what is installed, i.e., the basic >>system, ports and packages, and then to compare what is >>installed to the currently available versions. > > > For ports/packages you can use pkg_info(1) to see what is installed, > and pkg_version(1) to compare what is installed to what is in the ports > tree. > > For the base system there is no corresponding way to see what is > installed or not. 'uname -a' will show which version of FreeBSD is > installed, but after that you will have to check manually to see if all > components are installed or not. > > Erik, Thanks; I was hoping that there were some additional tools that I hadn't found so far. At least you have confirmed that I'm following a reasonable procedure. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Audit tools?
What are the tools that I should use to audit an existing FreeBSD installation? Without changing anything, I wish to quickly determine what is installed, i.e., the basic system, ports and packages, and then to compare what is installed to the currently available versions. Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: > Jay O'Brien píše v po 11. 04. 2005 v 00:43 -0700: >> >>Michal, >> >>The md5 results for vidcontrol.diff.20050215 are the same as yours. The other >>files, however, are different. I first did >>fetch >>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c >>fetch >>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1 >>to get the files. I now see this doesn't get the correct files. Rather, it >>gets >>files marked up for the web. Obviously that was a big problem. >> >>Then, using WinXP Pro and Mozilla, I downloaded the files again from >>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ >>and I moved them to the FreeBSD machine using WS_FTP Pro. >>Different md5 results again. >> >>I found that now the first hunk of the patch on vidcontrol.1 failed. >> >>After much file comparing, I found the differences in the files. The >>"$FreeBSD" >>line near the beginning of each file had "/repoman/r/ncvs/" in front of >>src/user.sbin/... and when I edited those characters out, the md5 results >>were >>the same as yours, and the patch completed without errors. I found that the >>vidcontrol.c file would patch ok without editing out those characters, but >>the >>vidcontrol.1 file would error in hunk #1 if "/repoman/r/ncvs/" was present. > > > I see. Sorry about that. I didn't actually retrieve my files from > cvsweb, I have a local copy of the repository. > > >>I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got >>16 lines of "vidcontrol: showing the mouse: Invalid argument" which I see >>from a google search is a common problem. > > > Yes. I didn't look into it. Do you see this problem on your system? > > >>Whenever I select a mode with more than 80 characters the screen goes black. > > > I'm afraid I've never seen this. > > >>I loaded cp837-8x8 font, but no change. > > > I suppose you mean 437. It shouldn't be important. > Yes, 437. My typo. sorry. > >>I have the following in /etc/rc.conf, to set up 80x50, could it be the >>problem? >>font8x8="iso08-8x8" >>font8x14="iso08-8x14" >>font8x16="iso08-8x16" >>scrnmap="iso-8859-1_to_cp437" >>allscreens_flags="-m on 80x50 white black" > > > I didn't try it lately. I just used vidcontrol manually. > > >>Or perhaps this that I have now in /etc/ttys? >>ttyv0 "/usr/libexec/getty Pc" cons50 on secure >># Virtual terminals >>ttyv1 "/usr/libexec/getty Pc" cons50 on secure >>ttyv2 "/usr/libexec/getty Pc" cons50 on secure >>ttyv3 "/usr/libexec/getty Pc" cons50 on secure >>ttyv4 "/usr/libexec/getty Pc" cons50 on secure >>ttyv5 "/usr/libexec/getty Pc" cons50 on secure >>ttyv6 "/usr/libexec/getty Pc" cons50 on secure >> >>At least now I can see what MAY be possible; vidcontrol -i mode returns a >>screenful of fonts to try. Tomorrow I'll identify which ones work and >>which ones don't. > > > This is a part of my 'vidcontrol -i mode' command output: > Where is this display explained? flags, type, window, linear buffer? It isn't in MAN VIDCONTROL > mode# flags type size font window linear > -- > > 24 (0x018) 0x0001 T 80x25 8x16 0xb8000 > 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000 > 32 (0x020) 0x0001 T 80x30 8x16 0xb8000 > 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 My modes 24,30,32 and 34 are identical to yours. > 259 (0x103) 0x000f G 800x600x8 1 8x14 > 275 (0x113) 0x000f G 800x600x15 1 8x14 > 276 (0x114) 0x000f G 800x600x16 1 8x14 > 277 (0x115) 0x000f G 800x600x24 1 8x14 My modes 259,275,276,277 all show 0x000b and 8x16; otherwise the same. > 290 (0x122) 0x000f G 800x600x32 1 8x14 I don't have mode 290. > To set the desired mode use vidcontrol MODE_mode#. From the modes listed > here mode 259 can't be used (it's 8bpp mode which isn't supported). > Yes, that works fine. > To be able to use a mode you must have the appropriate font loaded. > > Command 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x14.fnt' may be > used to use some 8x14 font. You should have loaded all for resolutions' > fonts though because they're l
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: > Jay O'Brien wrote: > >>Michal Mertl wrote: >> >>> >>>>What? I don't know how the patching of vidcontrol ended but you'd >>>>better redo it with fresh files from current. Go download vidcontrol.c >>>>v 1.48 and vidcontrol.1 from >>>>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ >>>> >>>>Then run the patch on it again and recompile/reinstall vidcontrol >>>>binary. >>> >>I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. >>Now all hunks failed. The results are below. > > > I don't know. The text before the line starting with "Patching" is taken > from the patch file. The patch program doesn't retrieve any files. So I > think you either used bad files to patch or bad patchfile. > > You need to have the original files. To check they're correct you can > use md5 utility. > > md5 vidcontrol.c > MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1 > md5 vidcontrol.1 > MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406 > md5 vidcontrol.diff.20050215 > MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021 > > You need to see the same strings. > > Then command 'patch < /path/to/vidcontro.diff.20050215' must work. > > Michal > Michal, The md5 results for vidcontrol.diff.20050215 are the same as yours. The other files, however, are different. I first did fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1 to get the files. I now see this doesn't get the correct files. Rather, it gets files marked up for the web. Obviously that was a big problem. Then, using WinXP Pro and Mozilla, I downloaded the files again from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ and I moved them to the FreeBSD machine using WS_FTP Pro. Different md5 results again. I found that now the first hunk of the patch on vidcontrol.1 failed. After much file comparing, I found the differences in the files. The "$FreeBSD" line near the beginning of each file had "/repoman/r/ncvs/" in front of src/user.sbin/... and when I edited those characters out, the md5 results were the same as yours, and the patch completed without errors. I found that the vidcontrol.c file would patch ok without editing out those characters, but the vidcontrol.1 file would error in hunk #1 if "/repoman/r/ncvs/" was present. I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got 16 lines of "vidcontrol: showing the mouse: Invalid argument" which I see from a google search is a common problem. Whenever I select a mode with more than 80 characters the screen goes black. I loaded cp837-8x8 font, but no change. I have the following in /etc/rc.conf, to set up 80x50, could it be the problem? font8x8="iso08-8x8" font8x14="iso08-8x14" font8x16="iso08-8x16" scrnmap="iso-8859-1_to_cp437" allscreens_flags="-m on 80x50 white black" Or perhaps this that I have now in /etc/ttys? ttyv0 "/usr/libexec/getty Pc" cons50 on secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons50 on secure ttyv2 "/usr/libexec/getty Pc" cons50 on secure ttyv3 "/usr/libexec/getty Pc" cons50 on secure ttyv4 "/usr/libexec/getty Pc" cons50 on secure ttyv5 "/usr/libexec/getty Pc" cons50 on secure ttyv6 "/usr/libexec/getty Pc" cons50 on secure At least now I can see what MAY be possible; vidcontrol -i mode returns a screenful of fonts to try. Tomorrow I'll identify which ones work and which ones don't. What next? Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: > > You haven't read the thread in the archives carefully enough, have you? Yes, but unfortunately I didn't comprehend. > Here is what I wrote (privately to the original poster but I explained > the error to the mailing list too): > > >>What? I don't know how the patching of vidcontrol ended but you'd >>better redo it with fresh files from current. Go download vidcontrol.c >>v 1.48 and vidcontrol.1 from >>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ >> >>Then run the patch on it again and recompile/reinstall vidcontrol >>binary. > I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. Now all hunks failed. The results are below. What did I screw up this time? Jay |Index: vidcontrol.1 |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v |retrieving revision 1.55 |diff -u -r1.55 vidcontrol.1 |--- vidcontrol.1 2 Mar 2003 21:04:21 - 1.55 |+++ vidcontrol.1 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.1 using Plan A... Hunk #1 failed at 11. Hunk #2 failed at 88. Hunk #3 failed at 297. Hunk #4 failed at 532. 4 out of 4 hunks failed--saving rejects to vidcontrol.1.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |Index: vidcontrol.c |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v |retrieving revision 1.48 |diff -u -r1.48 vidcontrol.c |--- vidcontrol.c 13 Jan 2005 03:59:44 - 1.48 |+++ vidcontrol.c 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.c using Plan A... Hunk #1 failed at 24. Hunk #2 failed at 48. Hunk #3 failed at 66. Hunk #4 failed at 187. Hunk #5 failed at 223. Hunk #6 failed at 239. Hunk #7 failed at 257. Hunk #8 failed at 297. Hunk #9 failed at 332. Hunk #10 failed at 348. Hunk #11 failed at 377. Hunk #12 failed at 419. Hunk #13 failed at 507. Hunk #14 failed at 572. Hunk #15 failed at 669. Hunk #16 failed at 722. Hunk #17 failed at 743. Hunk #18 failed at 806. Hunk #19 failed at 891. Hunk #20 failed at 900. Hunk #21 failed at 933. Hunk #22 failed at 950. Hunk #23 failed at 962. Hunk #24 failed at 985. Hunk #25 failed at 1035. Hunk #26 failed at 1050. Hunk #27 failed at 1148. Hunk #28 failed at 1173. Hunk #29 failed at 1217. Hunk #30 failed at 1234. 30 out of 30 hunks failed--saving rejects to vidcontrol.c.rej done ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: > There's no standard VGA 132 character text mode. It's either provided by > VESA or emulated using some graphics mode. Newer graphics hardware > stopped supporting extended text modes. If you want such modes you need > to emulate them (render the characters using lots of small dots instead > of just writing characters to the adapter which renders them for you). > Support for this functionality is included in syscons/vga driver when > you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar > graphics mode 800x600 dots with 4 bits (16) of color information per > pixel which can be run on old plain VGA with 256KB of memory. > > The patches we are talking about add support for rendering the > characters in any graphics mode your card supports (through VESA) with > >= 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions > of colours) for a text mode console. You can't use any graphics there > but the textual resolution will be bigger. There also isn't support for > using simultaneously more than 16 (or is it 15?) different colors for > characters even when milions are technically possible. > Thanks for the explanation, it is appreciated. I tried the process and encountered errors. Here's what happened: patch http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: > Jay O'Brien wrote: > >>Michal Mertl wrote: >> >> >>>Didier Wiroth wrote: >>> >>> >>> >>>>Hi, >>>> >>>>I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati >>>>mobility radeon 9600. >>>>Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does >>>>not work, 90x60 is the highest resolution I can get for now. >>>>It looks like I'm not the only one having this problem with ati >>>>chipsets: >>>>http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w >>>>ww/db/text/2005/freebsd-questions/20050123.freebsd-questions >>>> >>>> >>>>I saw this posting: >>>>http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht >>>>ml >>>> >>>>Unfortunately I'm not a programmer and have no ... to very poor patching >>>>skills. >>>>It looks to me, that in this posting(s) a "few" patches are grouped >>>>together to enable vesa 1024x768. >>>> >>>>1) Has someone applied this patches? >>>>2) As the patch(es) is/are on the entire page, I don't know how to >>>>separate them. Would someone mail me as an attachment the different >>>>patches and tell me how I should apply them: >>>>for example, mail me patch1, patch2, patch3 >>>>and the explanation how to patch them: >>>>cd /usr/src >>>>patch < ~/patch1 >>>>patch < ~/patch2 ...etc >>> >>> >>>I think the newest and probably best (?) patch was prepared by Xin Li >>>([EMAIL PROTECTED]) who is also committer. I sent this email to him >>>(or she? - sorry about that) in case he has some comments. Beware that >>>he said he experienced some problems with previous version of the patch. >>> >>>I haven't tested this version of the patch myself but it at least >>>compiles. >>> >>>It's available at http://people.freebsd.org/~delphij/vesa/ >>>in files syscons.diff.20050215 and vidcontrol.diff.20050215 >>> >>>You would apply them with: >>> >>>cd /usr/src/sys/dev/syscons >>>patch < /path/syscons.diff.20050215 >>>cd /usr/src/usr.sbin/vidcontrol >>>patch >>make clean >>>make all >>>make install >>> >>>You need also to rebuild and reinstall the kernel. You must have >>>'options SC_PIXEL_MODE' in your kernel config. You also need to have >>>VESA available - you can load it with kldload vesa or include it in the >>>kernel with 'options VESA'. >>> >>>After reboot with the new kernel you should be able to get list of all >>>VESA and standard modes your card support with 'vidcontrol -i mode'. To >>>be able to use them as your console mode you need to have the >>>appropriate font loaded. The font resolution is seen in vidcontrol >>>output in the 'font' column. To load the font 8x8 you can use >>>'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To >>>set the mode use 'vidcontrol MODE_$num' where $num is the mode number >>>(first column in 'vidcontrol -i mode' output). >>> >>>HTH >>> >>>Michal >>> >>> >> >> >>I feel like I am missing a lot here. I want to display 132 characters per >>line on my console. I am not running X Windows and it is not a notebook. > > > It doesn't matter. I only saw the most complaints from notebook owners > who didn't have text mode console covering all LCD surface. > > >>I am running 5.3-RELEASE-p5 #0. >> >>What is this SC_PIXEL_MODE and where may I find documentation on it? I >>don't find it in /usr/src/sys/i386/conf/NOTES. > > > man syscons(4). It's also mentioned in NOTES although not the NOTES you > were looking at. Don't forget that on 5.x there are two conf directories > - one platform independent in /sys/conf and other in /sys/$ARCH/conf. > Common (platform independent) options like this one are > in /sys/conf/NOTES. > Thanks! Now that I see that it is perhaps not required for my system, that is not a laptop, is it possible that I don't need this at all? Is it definitely needed to support 132 character terminal mode, or is just needed for laptops? > >>To "rebuild and reinstall the kernel", after editing my >>/usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I >>'make buildkernel' and then 'make installkernel' or is there something >>else I'm missing? > > > No, that's the way to do it. > > >>I note that some of the messages are posted to multiple mailing lists, >>and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing >>the entire story. > > > I'm afraid that's quite possible. Please go search the archives. > > >>Jay O'Brien >>Rio Linda, California USA > > > Michal Mertl > > Prague, Bohemia, Czech Republic :-) > It is wonderful to be a part of a caring community that spans the world, without concern for international borders. Fortunately for me, everyone uses english; I'm stuck with only one language (plus international morse code, but that's another story). Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: > Didier Wiroth wrote: > > >>Hi, >> >>I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati >>mobility radeon 9600. >>Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does >>not work, 90x60 is the highest resolution I can get for now. >>It looks like I'm not the only one having this problem with ati >>chipsets: >>http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w >>ww/db/text/2005/freebsd-questions/20050123.freebsd-questions >> >> >>I saw this posting: >>http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht >>ml >> >>Unfortunately I'm not a programmer and have no ... to very poor patching >>skills. >>It looks to me, that in this posting(s) a "few" patches are grouped >>together to enable vesa 1024x768. >> >>1) Has someone applied this patches? >>2) As the patch(es) is/are on the entire page, I don't know how to >>separate them. Would someone mail me as an attachment the different >>patches and tell me how I should apply them: >>for example, mail me patch1, patch2, patch3 >>and the explanation how to patch them: >>cd /usr/src >>patch < ~/patch1 >>patch < ~/patch2 ...etc > > > I think the newest and probably best (?) patch was prepared by Xin Li > ([EMAIL PROTECTED]) who is also committer. I sent this email to him > (or she? - sorry about that) in case he has some comments. Beware that > he said he experienced some problems with previous version of the patch. > > I haven't tested this version of the patch myself but it at least > compiles. > > It's available at http://people.freebsd.org/~delphij/vesa/ > in files syscons.diff.20050215 and vidcontrol.diff.20050215 > > You would apply them with: > > cd /usr/src/sys/dev/syscons > patch < /path/syscons.diff.20050215 > cd /usr/src/usr.sbin/vidcontrol > patch make clean > make all > make install > > You need also to rebuild and reinstall the kernel. You must have > 'options SC_PIXEL_MODE' in your kernel config. You also need to have > VESA available - you can load it with kldload vesa or include it in the > kernel with 'options VESA'. > > After reboot with the new kernel you should be able to get list of all > VESA and standard modes your card support with 'vidcontrol -i mode'. To > be able to use them as your console mode you need to have the > appropriate font loaded. The font resolution is seen in vidcontrol > output in the 'font' column. To load the font 8x8 you can use > 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To > set the mode use 'vidcontrol MODE_$num' where $num is the mode number > (first column in 'vidcontrol -i mode' output). > > HTH > > Michal > > I feel like I am missing a lot here. I want to display 132 characters per line on my console. I am not running X Windows and it is not a notebook. I am running 5.3-RELEASE-p5 #0. What is this SC_PIXEL_MODE and where may I find documentation on it? I don't find it in /usr/src/sys/i386/conf/NOTES. To "rebuild and reinstall the kernel", after editing my /usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 'make buildkernel' and then 'make installkernel' or is there something else I'm missing? I note that some of the messages are posted to multiple mailing lists, and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing the entire story. Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
Alex de Kruijff wrote: > > You told your system to install portmanager and the ports that > it needs, but also all the ports that are based on it. Please > check 'man portupgrade' about the options. > Good point, That is a man page I hadn't thought to review. Thank you! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
Francisco Reyes wrote: > On Sun, 27 Mar 2005, Jay O'Brien wrote: > > >>Thanks for the heads up on 'make search', even if I can't find a complete >>description of the command. I find that it is referenced in the manual, >>however. > > > Also check out the port > /usr/ports/sysutils/pkg_tree > > It's very usefull to see dependencies. > > -- > http://stringsutils.com > Utility for developers. Compute length, MD5, CRC and more. Interesting. Thanks! I wonder how that compares to portmanager. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
Randy, Mike: Thanks for the explanation. I hadn't considered a dependency that goes away after the dependent port is built. Now it makes perfect sense. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
RW wrote: > make seach is documented in man ports It sure is! THANK YOU! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd-questions Digest, Vol 92, Issue 40
Christopher Kelley wrote: > Jay, > > I have found the FreeBSD basics articles over at onlamp.com to be > invaluable. > > Linky: http://www.onlamp.com/pub/ct/15 > > The two articles "portupgrade" and "Ports Tricks" (currently about 13 > articles down) are valuable enough to me that I printed them out! > > I know it does sometimes seem that you need to know the answer before > you know what to google for, but until someone invents a better way to > search (e.g. somehow knowing the context of your search), it's worth > trying a few different things in google. > > Christopher > Christopher, Thanks. I thought I had caught all of Dru Lavigne's articles that applied, but I missed the "Ports Tricks" one. A good read. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
Michael C. Shultz wrote: > It would be nice if the ports make options were better documented, but > you can read through /usr/ports/Mk/bsd.port.mk and find information > on the various options. > > here is an example: > > # all-depends-list > # - Show all directories which are dependencies > # for this port. > > then > > cd /usr/ports/lang/ezm3/ > make all-depends-list > > result: > > /usr/ports/converters/libiconv > /usr/ports/devel/gettext > /usr/ports/devel/gmake > /usr/ports/devel/libtool15 > > -Mike > Mike, That's great info, thank you. It really helps put this into perspective. I did portmanager -sl and it identifies 7 candidates for deletion. It identifies cvsup-without-gui and also identifies ezm3 upon which it depends. Am I missing something here or shouldn't ezm3 not been identified as a "leaf port"? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
stheg olloydson wrote: > Hello, > > They are recursive dependencies. Check each ports requirements. > cvsup-without-gui depends on ezm3. ezm3 depends on gmake, > gettext and libiconv. libiconv depends on libtool...and the foot > bone's connected to the toe bone :). > > hth, > > stheg > stheg, Thank you. Great learning experience. Especially 'make search'. That is very useful. But how does it work (/usr/ports/Makefile doesn't have a SEARCH statement) and is it documented somewhere, like in a MAN page? The handbook, ¶4.3, mentions 'make search' but doesn't explain how it works. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
Abu Khaled wrote: > ezm3, gettext, gmake, libiconv, libtool are the build dependencies for > cvsup-without-gui. > > # cd /usr/ports > # make search name="cvsup-without-gui" > Abu, I don't get that result. I only show ezm3-1.2. # cd /usr/ports # make search name="cvsup-without-gui" Port: cvsup-without-gui-16.1h_2 Path: /usr/ports/net/cvsup-without-gui Info: General network file distribution system optimized for CVS (non-GUI version) Maint: [EMAIL PROTECTED] B-deps: ezm3-1.2 R-deps: WWW:http://www.cvsup.org/ # > If you updated your soirces/ports "cvsup" then portupgrade did what > you asked it to do. It Updated all outdated packages/ports and there > dependencies. I'm convinced that you are right. However, why don't I show the other dependencies? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade (vs. Portmanager) question
Alec Berryman wrote: > Jay O'Brien on 2005-03-27 18:20:00 -0800: > > >>Now, pkg_info says I have 10 packages installed; added were ezm3, >>gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If >>these all required to make portupgrade or perl work, where is that >>reference? > > > They are required to build and run portupgrade. If you do a 'make search > name=portupgrade' from /usr/ports, it will list all the dependencies. > > >>PS.. I tried to install portmanager again, and this time it got the >>files immediately and installed fine. It took about a minute, not two >>hours. It reports that all my ports are up to date. Whew. > > > That's because portupgrade did all the work :) If you had run > portmanager before running portupgrade, you would have seen something > similar - portmanager taking two hours and portupgrade taking almost > no time at all. Alec, Thanks, I searched the FreeBSD Handbook for "dependency" and didn't find any reference to "make search". I guess it is one of those things that once you know about it you don't have to look for it any more. Unfortunately a lot of the documentation I can review is written for those folks who already know the answers. Thanks for the heads up on 'make search', even if I can't find a complete description of the command. I find that it is referenced in the manual, however. I see that several of the packages that were installed aren't listed in the dependencies for portupgrade. Only the two ruby programs are listed. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Portupgrade (vs. Portmanager) question
Updating a computer, pkg_info reported I only had two packages, cvsup-without-gui-16.1h and perl-5.8.5, both of which were out of date as reported by pkg_version. I tried to install portmanager, but it was not able to get the needed files from http://portmanager.sunsite.dk. So, I installed portupgrade. Those files came in fine. I then did "portupgrade -a -N -vu -rR", which was successful for me several months ago on another computer. The computer ran for over nearly two hours, with messages scrolling by so fast it was nearly impossible to read, filling up the screen with text. I used script so as to capture the screen messages; the capture file of the screen is 1.2MB in size! Now, pkg_info says I have 10 packages installed; added were ezm3, gettext, gmake, libiconv, libtool, portupgrade,ruby and ruby18. If these all required to make portupgrade or perl work, where is that reference? Help! What did I do? Jay O'Brien Rio Linda, California, USA PS.. I tried to install portmanager again, and this time it got the files immediately and installed fine. It took about a minute, not two hours. It reports that all my ports are up to date. Whew. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup questions
Subhro wrote: > Jay O'Brien wrote: /snip/ > >>I built src-all and ports-all. Now, there is a /usr/ports >>directory and and lots of directories and files therein. In >>/usr/ports, I did make fetchindex. It failed. The >>/usr/ports/Makeindex file was really Makeindex,v. I copied it >>as Makeindex, and tried make fetchindex again. It showed many >>errors, finally "fatal errors encountered -- cannot continue". >> > > You probably used CVS instead of cvsup. CVS, also known as Concurrent > Version System is a mechanism which allows developers to manage codebase > on which more than one individual is working simultaneously. When some > change is made to a file "foo.bar" managed by a CVS, a file called > "foo.bar,v" is created by the CVS. This file contains all the > information about what changed and who changed it along with the > comments which a developer might have provided during updating the file > "foo.bar". Just to add, using the foo.bar,v file along with foo.bar, any > version of the file may be created that ever existed. > > No, I used cvsup. However, I was idly reading through all of the CVSup FAQ, and I found my problem. It explained that my supfile didn't have "tag=." and I knew that it did. Sure enough, a typo. I used a - instead of an =. It read "tag-.". Now, with it correct, pkg_version works. And now I understand the ,v indicates RCS files. /snip/ > > Best of Luck and welcome to the wonderful world where most of the things > are free :-) Thank you very much, I really appreciate your quick and thoughtful answer. Jay > > Best Regards, > S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup questions
When 5.3 RELEASE first came out, I used the miniinst.iso CD to install 5.3 on a spare computer for tests. It installed ok and based on how it worked, I updated my primary computer. Now I have an application for the spare computer, and I thought I would use it to verify my understanding of how CVSup works. I installed cvsup-without-gui. pkg_info shows cvsup installed. pkg_version, however, failed. "Unable to open INDEX in pkg_do" I found that pkg_version http://www.FreeBSD.org/ports/INDEX-5 ran ok, so the problem was the missing /usr/ports/INDEX-5. In fact there was no /usr/ports directory. I built src-all and ports-all. Now, there is a /usr/ports directory and and lots of directories and files therein. In /usr/ports, I did make fetchindex. It failed. The /usr/ports/Makeindex file was really Makeindex,v. I copied it as Makeindex, and tried make fetchindex again. It showed many errors, finally "fatal errors encountered -- cannot continue". Obviously I need to start over, this time using the CD with the full iso image. I'll do that, but What did I do wrong? And, What is the significance of the ",v" (comma, v) tacked on to several of the files in /usr/ports when the files were placed there by CVSup? Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Security for webserver behind router?
Anthony Atkielski wrote: > Jay O'Brien writes: > > JOB> Thanks, but what I want to know is what risk I have with port 80, > JOB> and only port 80 open. > > The risk depends on Apache, since that's the daemon answering the phone > when someone calls in on port 80. > > Just make sure you're using the latest version of Apache (1.3.33, if you > want the 1.x version, or 2.0.52, if you want the 2.x version). Some > earlier versions are vulnerable. As long as Apache is secure, port 80 > can be open. > I am running Apache 1.3.33, as you suggest I should. You say "as long as Apache is secure"; what should I do to be sure that Apache is secure? If there isn't a security risk with the FreeBSD system I've described, maybe this question belongs on the Apache mailing list, not here? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Security for webserver behind router?
RW wrote: > On Wednesday 19 January 2005 07:21, Jay O'Brien wrote: > >>I've brought up a 5.3 Release machine as a learning tool, >>with apache 1.3. It is on a LAN with Windows machines, and >>port 80 (and only port 80) is open and directed by the >>Linksys router to the FreeBSD machine. It is working fine so >>far, but my learning curve is slower than I would like. >> >>I know that there's lots to learn and do later about >>security, when I bypass the Router and use the FreeBSD box >>as the NAT device, but for now I would like to confine my >>learning to Apache, with only port 80 open. I do have ftp >>and ssh enabled on the LAN for access by the Windows boxes. >> >>As I haven't done anything for security on the FreeBSD >>machine, am I exposed to anything by having port 80 open? Is >>there anything I should do now? > > > It's in the nature of any webserver software that it provides rich picking > for > hackers. > > If it's a learning tool, don't expose apache to the internet, you can test it > perfectly well from your local network. If you want to access it from a > remote location, then setup your FreeBSD firewall to allow access from a > limited range of ip addresses. > Thanks, but what I want to know is what risk I have with port 80, and only port 80 open. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Security for webserver behind router?
I've brought up a 5.3 Release machine as a learning tool, with apache 1.3. It is on a LAN with Windows machines, and port 80 (and only port 80) is open and directed by the Linksys router to the FreeBSD machine. It is working fine so far, but my learning curve is slower than I would like. I know that there's lots to learn and do later about security, when I bypass the Router and use the FreeBSD box as the NAT device, but for now I would like to confine my learning to Apache, with only port 80 open. I do have ftp and ssh enabled on the LAN for access by the Windows boxes. As I haven't done anything for security on the FreeBSD machine, am I exposed to anything by having port 80 open? Is there anything I should do now? Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh file transfers - how to?
joseph kacmarcik wrote: >>For purposes of discussion, I'm logged into the distant machine >>as [EMAIL PROTECTED] I'm logged in to the directory /www/jay >>and my localmachine directory (now empty) is /home/www/jay. I want >>everything in the www/jay directory on distantmachine to be copied >>as the home/www/jay directory on localmachine. > > > this depends whether you want a backup or if you want to have a live copy, > there > are a few ways (more on that later). > > for a backup, you could (test first please): > ssh remotehost "tar cf - /www/jay" > /path/to/tarfile Thanks, this will come later - It's now on my to do list. > or for live copy, two methods would be: > ssh remotehost "tar cf - /www/jay" | tar -C /home/www/jay -xf - > scp -pr remotehost:/www/jay /home/www/jay > > Interesting, I ran it with only the -r argument and saw the file date/times were current; I read the MAN page and found the -p argument, and found it worked as promised. Thanks for confirming! >>My follow-on question is -- Is there a way to synchronize the local >>machine with the distant machine if changes are made on the distant >>machine, and vice-versa, on a generic basis, i.e. "distantmachine >>is now the master, correct localmachine to agree"? > > > if you're trying to get a working copy and not backup, use rsync. this would > be > much easier, and it's easy to make it bi-directional (or more). > > there are many ways to do this, one is: > rsync -azvprt -e ssh [EMAIL PROTECTED]:/www/jay /home/www > The rsync program sounds like what I will need once I get things working. I'm building a duplicate of my web site, here on my local computer, and ultimately it will be a working copy at a slightly different URL. > you could use -n and --progress when you're doing the debugging getting it > right > for your situation and environment. > > you'll still be transporting over ssh, but IMO rsync is a better choice. > > good luck! > joe Joe, thanks. I can't go wrong with the support team here on questions. This is fun! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh file transfers - how to?
Jeremy Faulkner wrote: > Jay O'Brien wrote: > >>I'm using ssh to connect from my local FreeBSD machine to a >>distant FreeBSD machine. I want to copy a file structure, i.e., >>a directory and its subdirectories, from the distant machine >>to my local machine. >> >>I can do this fine using WS_FTP Pro in Windows, using another >>local Windows machine, and then use WS_FTP Pro to copy the files >>to the FreeBSD local machine from the Windows computer. It seems >>like I should be able to perform the same copy process directly, >>from one FreeBSD machine to the other, using ssh. >> >>I can connect to the distant machine just fine using ssh. >> >>For purposes of discussion, I'm logged into the distant machine >>as [EMAIL PROTECTED] I'm logged in to the directory /www/jay >>and my localmachine directory (now empty) is /home/www/jay. I want >>everything in the www/jay directory on distantmachine to be copied >>as the home/www/jay directory on localmachine. >> > > > scp -r [EMAIL PROTECTED]:/home/www/jay /home/www/jay > Jeremy, That works like a champ. Exactly what I was looking for. Thank you! Wow. There's so much to learn. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ssh file transfers - how to?
I'm using ssh to connect from my local FreeBSD machine to a distant FreeBSD machine. I want to copy a file structure, i.e., a directory and its subdirectories, from the distant machine to my local machine. I can do this fine using WS_FTP Pro in Windows, using another local Windows machine, and then use WS_FTP Pro to copy the files to the FreeBSD local machine from the Windows computer. It seems like I should be able to perform the same copy process directly, from one FreeBSD machine to the other, using ssh. I can connect to the distant machine just fine using ssh. For purposes of discussion, I'm logged into the distant machine as [EMAIL PROTECTED] I'm logged in to the directory /www/jay and my localmachine directory (now empty) is /home/www/jay. I want everything in the www/jay directory on distantmachine to be copied as the home/www/jay directory on localmachine. Guidance on the commands and syntax to use will be much appreciated. My follow-on question is -- Is there a way to synchronize the local machine with the distant machine if changes are made on the distant machine, and vice-versa, on a generic basis, i.e. "distantmachine is now the master, correct localmachine to agree"? Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: grep help RESOLVED
Tillman Hodgson (and others!)wrote: > On Wed, Jan 05, 2005 at 08:27:51PM -0800, Jay O'Brien wrote: > >>I want to look at all of the lines in a FreeBSD log file that do not >>have an entry from an IP, example 1.2.3.4. Some basic help with the >>use of grep would be appreciated. This is one of the arguments I've >>tried that didn't work: >> >>grep ^[^1.2.3.4]*$ logfile.log > > > I like `grep -v` for "not" operations. Also note that "." is itself a > special character. > > grep -v 1\.2\.3\.4 logfile.log > > might be closer to what you want. > > -T > > Thank you! The problem I was having was that I completely overlooked the fact that "." needs to be escaped. grep -v 1\.2\.3\.4 logfile.log as you suggested, works fine. I'm looking at an apache access log, and I want to exclude accesses that I made from my IP. Thanks, everyone! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
grep help
I want to look at all of the lines in a FreeBSD log file that do not have an entry from an IP, example 1.2.3.4. Some basic help with the use of grep would be appreciated. This is one of the arguments I've tried that didn't work: grep ^[^1.2.3.4]*$ logfile.log Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade time, xorg ports
Kirk Strauser wrote: > On Saturday 25 December 2004 12:29, Jay O'Brien wrote: > > >>But it is there, so it will stay. > > > I doesn't *have* to stay, though: > > 1) Add 'WITHOUT_X11="YES"' to /etc/make.conf . > 2) Use You can use 'pkg_info -rR xorg-[whatever]' to see which ports depend > on a each of the X.org ports. > > For each "dependent" port, there will be three possible states: > > 1) You don't use it anymore (eg you used to use Firefox, but haven't in a > long time) and no other port depends on it. If this is true, then use > pkg_delete to remove that port. > > 2) You still use it, but don't use the X11 version of it (eg you want to use > ImageMagick for automated image processing, but don't need the 'display' > command which depends on X.org). In this case, you can rebuild the port > and with WITHOUT_X11="YES" setting above will remove its dependency on > X.org. > > 3) You still the X11 version of it. In this case, you won't be removing > X.org any time soon. > > Note that in case #2 above, you don't necessarily have to rebuild it *right > now*. A lot of ports are updated regularly and might be updated the next > time you run portupgrade anyway. If removing X.org isn't a high priority, > then you can always check back every month or so to see when the list of > packages that need X11 is small enough that you can force-upgrade them in a > reasonably short amount of time. > > Also note that this general approach works for pretty much any other large > system that you might want to remove, not just X.org. Kirk, Thanks for answering questions I didn't know how to ask. However, now that I realize I have xorg installed, I've been playing with it and I think I'll keep it around for now. I may even install Mozilla or Firefox. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Non-Profit Status
And thanks to Troy Mills, who posted the alert here Wednesday morning. I was not aware of the foundation, and I appreciate the opportunity to provide some small measure of support. $30,400 was needed, and 839 people contributed 123% of that amount, or an average of $47USD each, in FOUR DAYS. Congratulations to us all for surpassing the goal. Wow. Jay O'Brien Rio Linda, California USA Reference links: http://www.freebsdfoundation.org/ The FreeBSD Foundation http://www.freebsdfoundation.org/donating.shtml FreeBSD Foundation Donations http://www.freebsdfoundation.org/press/20041221-newsletter.shtml December 21, 2004: FreeBSD Foundation Quarterly Newsletter, December 21, 2004 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache trailing slash - was web server permissions
Bill Moran wrote: > > Is IE involved in this anywhere? > > I've noticed that IE tends to have problems with certian URLs. > The "trailing slash" issue sounds familiar as an IE problem (although > I'm not sure). > > Have you tried other browsers from the location that doesn't work? > Interesting! I only use Mozilla, V1.7.2. On your suggestion, I tried IE and it works fine! Strange... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd non-profit stat OT
Bill Moran wrote: > Again. I understand, and it _should_ work. But it doesn't for me. > > I've been having this problem with Paypal for several months. I once > had a paypal account, then they changed the TOS in a way I didn't like > and I refused to agree to, so I requested that they terminate my account. > Of course, they claimed they did. > > However, any time I try to use my CC to make a paypal "accountless" > payment, I hit up against this problem. Apparently, the people at > paypal are incapable of following their own rules (which state that I > can't have an account if I don't agree to their TOS) > > Anyway, it's between PayPal and I, but I don't suppose it will ever > get resolved, unless I sue or something, and I can't imagine there's > any justification for suing. > Now, I also understand. Maybe you could try a different credit card? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache trailing slash - was web server permissions
Jay O'Brien wrote: > changing the links to add a trailing / "fixed" the > problem, and if I didn't want to use existing web pages with shortened > relative links without the trailing / character, it wouldn't be a > problem. > > I would like to understand what is causing this to work the way it is. > I now understand it is either an Apache problem, perhaps related to the fact I'm using an IP number as ServerName, not a URL, and perhaps related to the fact that I'm behind a NAT firewall (linksys router) that passes port 80 to my FreeBSD machine on 192.168.1.9. What's happening is that the client on the internet is being redirected to the 192.168.1.9 address, not to the IP number in the ServerName line in httpd.conf. That works fine on my LAN, but not out on the internet. Google returns hundreds of answers for apache "trailing slash", and I'm following up. Any ideas would be appreciated, but as this is clearly not a FreeBSD problem, I'll drop the issue here until I find a solution. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd non-profit stat OT
Bill Moran wrote: > Unfortunatley, PayPal (who I don't have an account with) insists that I > have an account and refuses to process my transaction unless I log in > (to the account that doesn't exist). > > Am I the only one they're doing this to? Doesn't seem like it's the > Foundation's fault, but it's preventing me from making a donation. Bill, To test the system, I made a small contribution tonight in my wife's name using a credit card. She doesn't have a PayPal account, and didn't sign up for one. >From http://www.freebsdfoundation.org/donating.shtml click on DONATE, Then click on the "If you do not currently have a PayPal account" button, give it the amount, click on the "Don't Have a PayPal Account" secure checkout button, and give it the typical credit card info. The only catch appears to be that the credit card billing address must be in the USA, but I believe you are in PA. The PayPal process I used was simpler, but a PayPal account isn't required. Jay O'Brien ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: web server permissions question
Bill Moran wrote: > Sounds like your links are pointing to the private IP address, which > isn't accessable from the Internet at large. > > If this is the case, fix your links. Otherwise, please provide some > more information about the symptoms. I doubt there is any sort of > permission problem. > Bill, The problem links are shortened relative links. See my additional post with more symptoms that I posted before I realized you had responded. As you suggest, changing the links to add a trailing / "fixed" the problem, and if I didn't want to use existing web pages with shortened relative links without the trailing / character, it wouldn't be a problem. I would like to understand what is causing this to work the way it is. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: web server permissions question
Jay O'Brien wrote: > I think this is a permissions issue. I just installed Apache13, > and it works fine on my LAN using a fixed local IP. I opened > port 80 in my Linksys router, and from the internet I can now > get to my home page over the internet, using my fixed IP. > >>From my local LAN I can use links on my home page to display > html files in directories under the directory where my home > page lives. However, from over the internet I can only get to > my home page. Except, I can go to IP/manual/ and apache shows > me the apache manual pages by virtue of an alias in httpd.conf. > > So, I know it is possible to access other web pages via the > internet connection; I just don't know how to allow access to > my subdirectories. > > Jay O'Brien > Rio Linda, California USA > More data on this issue I found how to get around this problem, and it isn't permissions at all. On the other web server I use, I use relative and shortened addressing on links, for example /xyz which, when selected by the user, would then send the user the /xyz/home.html file, in the xyz subdirectory under the directory where the home page lives. Now, with this version, I find that I must add a trailing /, using /xyz/ instead of /xyz, and with that change everything works as expected. I can now access home.html files in subtending directories with such shortened relative links from my LAN and from the internet. This doesn't explain why the link without the trailing / works fine on my local LAN but not when accessed over the internet. I would prefer to have it work without the trailing / because I want to copy many existing pages with such relative addresses from my other server. I'm not sure where to look in them, but... now to the Apache manuals! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
web server permissions question
I think this is a permissions issue. I just installed Apache13, and it works fine on my LAN using a fixed local IP. I opened port 80 in my Linksys router, and from the internet I can now get to my home page over the internet, using my fixed IP. >From my local LAN I can use links on my home page to display html files in directories under the directory where my home page lives. However, from over the internet I can only get to my home page. Except, I can go to IP/manual/ and apache shows me the apache manual pages by virtue of an alias in httpd.conf. So, I know it is possible to access other web pages via the internet connection; I just don't know how to allow access to my subdirectories. Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade time, xorg ports
RW wrote: > On Friday 24 December 2004 21:54, Jay O'Brien wrote: > >>Running FreeBSD 5.3-RELEASE-p2 #0, i386 P3-667MHz, 512MB RAM. >> >>This is my first experience using portupgrade. >> >>I ran cvsup successfully for ports-all. I ran pkg_version -v. >>It showed a total of 28 ports, 20 needed updating. Of those, >>16 were xorg- ports; the others were xterm, freetype2, imake >>and png. >> >>I ran portupgrade -a -N -vu -rR, and it tried several times > > > You dont need the -N switch, it's only used for new port installations, not > upgrades. Using it carelessly is a bit dangerous, you may find youself > installing ports you don't want. Thanks, I wasn't sure about that. I saw an example that used -N and followed it. I'm not clear on what -N really does, but for now I just won't use it! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade time, xorg ports
Frank Staals wrote: > Jay O'Brien wrote: > > >>albi wrote: >> >> >> >> >>>Jay O'Brien wrote: >>> >>>hi, >>> >>> >>> >>> >>> >>>>Running FreeBSD 5.3-RELEASE-p2 #0, i386 P3-667MHz, 512MB RAM. >>>> >>>> >>> >>>- cut for brevity >>> >>> >>> >>> >>>>-I didn't install xorg. Why are the 16 xorg ports present? >>>> >>>> >>> >>>a fresh FreeBSD 5.3 has xorg by default instead of XFree86 >>> >>> >>> >> >>So X is installed by default whether or not I wish to use X? >> >>Jay >> >> >> > > No, FreeBSD prior to 5.3 had XFree86 as X-server, but since XFree86 > changed their licenses FreeBSD switched to X.org. If you installed X.org > depends on what install you choose. If you choose 'minimal install' you > don't have X.org installed ( if you didn't do it yourself later ) but if > you choose 'X-user' or anything like that you do have X.org. You can > check it by running 'pkg_info | grep xorg. If you get something like > this you have installed X.org: > > bash-3.00$ pkg_info | grep xorg > xorg-clients-6.7.0_4 X client programs and related files from X.Org > xorg-documents-6.7.0 Documentation of X11 protocol and libraries from X.Org > xorg-fonts-100dpi-6.7.0 X.Org 100dpi bitmap fonts > xorg-fonts-75dpi-6.7.0 X.Org 75dpi bitmap fonts > xorg-fonts-cyrillic-6.7.0 X.Org Cyrillic bitmap fonts > xorg-fonts-encodings-6.7.0 X.Org font encoding files > xorg-fonts-miscbitmaps-6.7.0 X.Org miscellaneous bitmap fonts > xorg-fonts-truetype-6.7.0 X.Org TrueType fonts > xorg-fonts-type1-6.7.0 X.Org Type1 fonts > xorg-fontserver-6.7.0 X font server from X.Org > xorg-libraries-6.7.0_2 X11 libraries and headers from X.Org > xorg-manpages-6.7.0 X.Org library manual pages > xorg-server-6.7.0_9 X.Org X server and related programs > xorg-vfbserver-6.7.0 X virtual framebuffer server from X.Org > > Merry X-mas btw :) > > Frank, That's what I have. I *Thought* I had not selected X, but your words caused me to review my installation notes. My face is *red*. I did select "All system sources, binaries and X window system". My intent with this computer is for it to be a web and mail server; when I did the install I probably accepted the X because someday I want to run Mozilla for local html viewing. I sure didn't know the consequences of that selection! But it is there, so it will stay. Thanks for answering my question. X is there because I asked for it! And Merry Christmas to you too! Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade time, xorg ports
Kris Kennaway wrote: > On Fri, Dec 24, 2004 at 01:54:04PM -0800, Jay O'Brien wrote: > > >>I ran portupgrade -a -N -vu -rR, and it tried several times >>to fetch X11R6.8.1-src1.tar.gz, each time taking over an hour, >>and when the file failed, it failed showing a checksum mismatch. > > >>I tried it again today, and it was able to fetch the three >>remaining files. SLOW. I have a DSL connection, and usually >>see 1.5MB speeds or more. Two of the files came in at 6kBps, >>one at 26 kBps. This Portupgrade session, including downloading >>the files detailed below, took 3 hours and 38 minutes; 1.5 hours >>was spent just downloading the three files. >> >>>From the script file of the session: >>=> X11R6.8.1-src(#).tar.gz doesn't seem to exist in >>/usr/ports/distfiles/xorg. >>=> Attempting to fetch from ftp://ftp.x.org/pub/X11R6.8.1/tars/ >> >>files fetched and time for download: >>filesizeend speedtime >>X11R6.8.1-src1.tar.gz29MB 6510 Bps 80 min >>X11R6.8.1-src6.tar.gz 3106kB 6298 Bps 8 min >>X11R6.8.1-src2.tar.gz 5672kB 26 kBps 4 min >> >>I have two questions: >> >>-Is this typical to see such slow download speeds > > > Sometimes; it's not unusual for a popular ftp site to be heavily > loaded. There are various variables you can set to control fetching > from different sites; see the ports(7) manpage and the comments in > bsd.port.mk. > Wow. And after I decode that somehow I have to know an alternate site. It appeared to me that as it was fetching from x.org (see above) that the ftp site was not something I could change. 6500 Bps is much slower than an ancient dialup connection; a big waste of time, it appeared, as I am not using X at all. > >>and for the >> portupgrade process to take so much time? > > > X is a large set of applications, so it's going to take a little while > to compile it all :-) > > >>-I didn't install xorg. Why are the 16 xorg ports present? > > > I don't understand what you're asking here. In my install of FreeBSD I did not select any flavor of X at all, and I would like to learn why it was installed "by default". > > Kris Thanks for your answer, it has pointed me at more things I didn't know were there that I have to learn about. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade time, xorg ports
albi wrote: > Jay O'Brien wrote: > > hi, > > >>Running FreeBSD 5.3-RELEASE-p2 #0, i386 P3-667MHz, 512MB RAM. > > - cut for brevity > >>-I didn't install xorg. Why are the 16 xorg ports present? > > > a fresh FreeBSD 5.3 has xorg by default instead of XFree86 > So X is installed by default whether or not I wish to use X? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Simple program to check for problems prior to running portupgrade
Bill Moran wrote: > http://www.potentialtech.com/wmoran/portupgrade-check.php > Very nice. I just waded through /usr/ports/UPDATING for the first time, and seeing your extracting tool immediately after that exercise shows me how valuable your tool will be in the future. It also forced me to learn how to use gunzip and chmod, but those were trivial compared to the portupgrade process. Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade time, xorg ports
Running FreeBSD 5.3-RELEASE-p2 #0, i386 P3-667MHz, 512MB RAM. This is my first experience using portupgrade. I ran cvsup successfully for ports-all. I ran pkg_version -v. It showed a total of 28 ports, 20 needed updating. Of those, 16 were xorg- ports; the others were xterm, freetype2, imake and png. I ran portupgrade -a -N -vu -rR, and it tried several times to fetch X11R6.8.1-src1.tar.gz, each time taking over an hour, and when the file failed, it failed showing a checksum mismatch. I tried it again today, and it was able to fetch the three remaining files. SLOW. I have a DSL connection, and usually see 1.5MB speeds or more. Two of the files came in at 6kBps, one at 26 kBps. This Portupgrade session, including downloading the files detailed below, took 3 hours and 38 minutes; 1.5 hours was spent just downloading the three files. >From the script file of the session: => X11R6.8.1-src(#).tar.gz doesn't seem to exist in /usr/ports/distfiles/xorg. => Attempting to fetch from ftp://ftp.x.org/pub/X11R6.8.1/tars/ files fetched and time for download: filesizeend speedtime X11R6.8.1-src1.tar.gz29MB 6510 Bps 80 min X11R6.8.1-src6.tar.gz 3106kB 6298 Bps 8 min X11R6.8.1-src2.tar.gz 5672kB 26 kBps 4 min I have two questions: -Is this typical to see such slow download speeds and for the portupgrade process to take so much time? -I didn't install xorg. Why are the 16 xorg ports present? Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade vs. portmanager
RW wrote: > On Friday 24 December 2004 07:38, Michael C. Shultz wrote: > >>On Thursday 23 December 2004 11:16 pm, Jay O'Brien wrote: >> >>>Michael C. Shultz wrote: >>> >>>>On Thursday 23 December 2004 10:01 pm, Jay O'Brien wrote: >>>> >>>>>I'm running 5.3 RELEASE and trying to learn. I did a ports cvsup. >>>>>Following the Dru Lavigne article on portupgrade at >>>>>http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html?page >>>>>=1 I installed portupgrade and then ran portsdb -Uu. It errored >>>>>out, telling me that I shouldn't use my "refuse" file that stopped >>>>>the non- english docs and ports from being loaded on my HD. >>>>> >>>>>In trying to understand this issue, I found portmanager, and it >>>>>looks like it would perform the same function as portupgrade. >>>>> >>>>>My questions: Is there a way around the "refuse" file prohibition, >>>>>perhaps with portmanager? Does portmanager replace portupgrade? >>>> >>>>portmanager doesn't require the INDEX files to keep ports up to >>>>date, so the refuse file is a non issue with it. >>>> >>>>-Mike >>> >>>Sounds good. What's the downside, if any, to using portmanager >>>instead of portupgrade? >> >>All of your ports will be built with the correct dependencies, they will >>work better leaving you less to complain about in the mail lists and so >>you will become bored. Because everything is working exactly as it >>should you may begin to think you are a Maytag repair man, nothing much >>to do, just always setting around waiting for something to break. > > > I don't use portmanager myself, but isn't it the case that portmanager > rebuilds not just ports that have newer versions in the ports tree, but also > all ports that recursively depend on those ports. > > I just updated kdehier with portupgrade in about a minute. The whole of KDE > depends on kdehier, so presumably portmanager would have taken several days, > and kdehier isn't particularly unusual. I would see that as a major downside. > > When it's necessary UPDATING will suggest running portupgrade -rf to force > rebuilding. That kind of UPDATING entry is in a small minority, which > suggests to me that most of the problems with ports don't stem from the > sequence of their updating, so I can't see how portmanager is any kind of > magic-bullet. > > So portmanager rebuilds whether it needs it or not, and portupgrade only rebuilds when there is a later distribution of the software? The distinction between the two is not clear to me. This is my first try to update ports, and I want to set up a procedure for updating that I can follow in the future. Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade vs. portmanager
Michael C. Shultz wrote: > On Thursday 23 December 2004 10:01 pm, Jay O'Brien wrote: > >>I'm running 5.3 RELEASE and trying to learn. I did a ports cvsup. >>Following the Dru Lavigne article on portupgrade at >>http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html?page=1 >>I installed portupgrade and then ran portsdb -Uu. It errored out, >>telling me that I shouldn't use my "refuse" file that stopped the >>non- english docs and ports from being loaded on my HD. >> >>In trying to understand this issue, I found portmanager, and it looks >>like it would perform the same function as portupgrade. >> >>My questions: Is there a way around the "refuse" file prohibition, >>perhaps with portmanager? Does portmanager replace portupgrade? > > > portmanager doesn't require the INDEX files to keep ports up to date, so > the refuse file is a non issue with it. > > -Mike > Sounds good. What's the downside, if any, to using portmanager instead of portupgrade? Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade vs. portmanager
I'm running 5.3 RELEASE and trying to learn. I did a ports cvsup. Following the Dru Lavigne article on portupgrade at http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html?page=1 I installed portupgrade and then ran portsdb -Uu. It errored out, telling me that I shouldn't use my "refuse" file that stopped the non- english docs and ports from being loaded on my HD. In trying to understand this issue, I found portmanager, and it looks like it would perform the same function as portupgrade. My questions: Is there a way around the "refuse" file prohibition, perhaps with portmanager? Does portmanager replace portupgrade? Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Foundation
Gary Kline wrote: >if the freebsdfoundation set up a paypal button and asked >$5, i'd chip in my niickle. i bet at least thousands of others >would too. Go to: http://www.freebsdfoundation.org/donating.shtml and click on donate. I did, using PayPal. Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSup questions
Kevin, Stheg; Wow. You answered questions I didn't know how to ask. I was confused between src-all and cvs-all. The confusion is because of the example supfile /usr/share/examples/cvsup/cvs-supfile. It calls for the src- all collection, which I mistakenly thought would get everything. Now I see that it also individually calls for ports-all, doc-all and others. Obviously I didn't read that file carefully enough. I now have read the stable and standard supfiles and understand the reasons for them all. And, I now know to put them somewhere that they won't be eaten by an upgrade if I edit them. I also now see the need for different tags; I'll use RELENG_5_3 and . Thanks for the lead to "script". Another useful new command to me. I hadn't seen Dru Lavigne's article on portupgrade. Good read. And this wasn't "well documented" with me (yet), but it is now: > the well documented "make buildworld, make buildkernel, > make installkernel, reboot single user, mergemaster -p, > make installworld, reboot, mergemaster" cycle I haven't had so much fun since CP/M (on 8" floppy disks)! Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup questions
I have a system that right now I'm using to learn FreeBSD. I want to go through the update process that I assume I'll have to follow regularly once the computer is up and running as a web and mail server. Right now I'm not concerned about backups; that's my next project. I'm attempting to follow "Using CVSup" and learn how CVSup works. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Questions about CVSup: 1. Where should I place supfile? Obviously I could put it anywhere and make it work, but is there a usual place for it? I can't find where the manual makes a suggestion. Do I have a need for more than one supfile? 2. I am running 5.3 RELEASE. It appears that if I specify "*default tag=." that I will be getting updates from "current". Is this what I should do, given that I want to stay current on security and bug fixes, but I don't (at this time) intend to get involved with beta testing? Or should I specify *default tag=RELENG_5_3? And, if I do that, will the ports be updated, including adding new ports? 3. The tutorial at http://www.us-webmasters.com/FreeBSD/Install/ after item 68 describes CVSup. It suggests using the supfile /usr/share/examples/cvsup/ports-supfile which gets the "ports-all" collection. However, the Using CVSup manual says to get "src-all", that includes ports-all. Is there some reason to use ports-all, not src-all as suggested by the handbook? 4. The tutorial (see 3 above) item 97 concludes, after running cvsup, "FreeBSD is installed, CONGRATULATIONS!" Isn't this a bit premature? It seems to me that at that point I need to rebuild world per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#MAKEWORLD to apply the new files and bring the system up to date. Am I missing something? Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sysinstall - why two different programs in 5.3 RELEASE?
Kevin,
Thanks for adding the historical view to the answer. Wow. All
I wanted to do was learn enough about FreeBSD to run a web
server and host mailing lists. Instead, I find myself immersed
in an interesting and challenging new culture with knowledgeable
mentors.
Unfortunately, given my engineering background (I retired in
1985), I have to know "why"; I'm not satisfied with "just do it
and don't ask". As a result, this isn't going to be as simple
as I thought!
Regards,
Jay
Kevin D. Kinsey, DaleCo, S.P. wrote:
> Jay O'Brien wrote:
>
>
>>Why are there two versions of sysinstall, one five times the
>>size of the other, and what are the differences between them
>>other than file size and time?
>>
>>Jay O'Brien
>>Rio Linda, California, USA
>>
>>
>
>
> Sorry I'm late on this ... you've got a good technical
> answer already; I thought maybe I could add more
> detail; there is, apparently, a more or less historical
> reason, as well as the practical one. The practical
> one: it's a Good Thing(tm) to have sysinstall(8) in
> /stand/ (on the root partition) where you can get at it
> in the event /usr is unavailable. Indeed, it pretty
> much *has* to be under / to install the system
>
> History wise, sysinstall started out 10 years ago
> in /sbin. Looks as if Poul-Henning-Kamp and either
> Bill Paul (or Paul Traina?) did the work. From the
> oldest dusty attic:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/sysinstall/Attic/
>
> Then, for 2.0, Jordan Hubbard "birthed the monster"
> that, I guess, is still sysinstall today ... although it's
> morphed so many times, it's probably not recognizable
> as the same beast any longer[?] {Basically, how could I
> know, as a relative newb with Neandertal C skills?}
> For a long time afterwards, sysinstall lived in
> /usr/src/release:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/release/sysinstall/Attic/
>
> Both of these sysinstalls, near as I can tell, built their
> binary(ies) into /stand/, but nowhere else.
>
> Now, sysinstall doesn't inhabit "userland", per se.
> AFAIK /usr/src/release doesn't get rebuilt during
> a "make world" cycle; furthermore, though slightly
> less relevant, /stand/ isn't in $PATH --- if you try
> "whereis sysinstall" on a 4.X box:
>
> #whereis sysinstall
> sysinstall: /usr/share/man/man8/sysinstall.8.gz
>
> Perhaps I'm reading history wrongly, but it seems the
> Project wanted to DTRT and make sure that if an
> updated manpage was installed for sysinstall, the
> updated binary was, also. To have the manpage
> say something the binary can't/won't do violates
> the POLA, something the Project is exceptionally
> loath to do in almost every situation
>
> So, the bikeshed got painted again: sysinstall
> was moved to /usr/sbin, where it would be
> rebuilt when the system was updated. Prior to
> that time (Jan. 2001), you had to go to
> /usr/src/release/sysinstall and "make all install" to
> update the binary under /stand/ --- leading to a
> situation where you might have, say, 4.2 installed,
> but have a sysinstall binary left over from 3.0 or
> something, and it wasn't very useful. Furthermore,
> you can still have a similar situation in 4.X, because
> the change was never MFC'd to -STABLE, and therefore
> hasn't appeared until 5.X; (Hmm, will this become a FAQ?)
> Note I didn't say "same problem", but "same situation";
> I don't personally know if any additional work on
> sysinstall during the 4.X's reign as production
> release would have rendered an older version
> obsolete or not. I'm tempted to say it hasn't much,
> because the "libh" project was supposed to complete
> reimplement the installer, and I think the old
> monster had been more/less left to hide in his
> cave and blow smoke at passers-by (complaining
> about the installer *IS* a FAQ)
>
> You can find the discussion about the change at:
>
> http://docs.freebsd.org/mail/archive/2001/freebsd-current/20010114.freebsd-current.html
>
> The second "sysinstall" thread ("sysinstall.8 breaking buildworld") kind
> of shows how it got hashed out amongst the committers, and has some
> other factoids that I found educational. I hope my penchant for historical
> digression hasn't annoyed you, and welcome corrections to what I've
> presented as facts (though we needn't be pedantic, IMHO)
>
> Kevin Kinsey
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sysinstall - why two different programs in 5.3 RELEASE?
Adam Fabian wrote: > On Mon, Nov 22, 2004 at 07:12:04PM -0800, Jay O'Brien wrote: > >>However, the FreeBSD Handbook says to type /stand/sysinstall: >>I find the following files are present: >> >> 403488 Nov 4 17:27 /usr/sbin/sysinstall >>2046148 Nov 4 20:22 /stand/sysinstall >> >>When I invoke these programs, the screens that come up are >>identical, and the functions seem to be the same. >> >>Why are there two versions of sysinstall, one five times the >>size of the other, and what are the differences between them >>other than file size and time? > > > Everything in /stand is statically linked, which means that corrupt > libraries or libraries on an unavailable partition will not affect > their operation. That also means they're larger. This could be > useful if you bring the system up single-user and /usr, on a separate > partition, is corrupt or destroyed. > > [EMAIL PROTECTED] /home/afabian $ ldd /stand/sysinstall > ldd: /stand/sysinstall: not a dynamic executable > [EMAIL PROTECTED] /home/afabian $ ldd /usr/sbin/sysinstall > /usr/sbin/sysinstall: > libdialog.so.4 => /usr/lib/libdialog.so.4 (0x280b9000) > libncurses.so.5 => /lib/libncurses.so.5 (0x280d2000) > libutil.so.4 => /lib/libutil.so.4 (0x28111000) > libftpio.so.5 => /usr/lib/libftpio.so.5 (0x2811d000) > libc.so.5 => /lib/libc.so.5 (0x2812200 Adam, Thank you very much. That is a very clear explanation, and you exposed me to a new command, ldd. I'll also review the directory structure to better understand "/stand/". There's sure a lot to learn, but how can I go wrong with such a great support staff? Regards, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sysinstall - why two different programs in 5.3 RELEASE?
When I installed 5.3 RELEASE, the installation program, when it was finished installing, said "Congratulations... to re-enter utility after the system is up, type /usr/sbin/sysinstall." However, the FreeBSD Handbook says to type /stand/sysinstall: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-final-warning.html The Handbook makes no mention of /usr/sbin/sysinstall. I find the following files are present: 403488 Nov 4 17:27 /usr/sbin/sysinstall 2046148 Nov 4 20:22 /stand/sysinstall When I invoke these programs, the screens that come up are identical, and the functions seem to be the same. Why are there two versions of sysinstall, one five times the size of the other, and what are the differences between them other than file size and time? Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bsdlabel messages? (resolved)
I asked about error messages displayed by disklabel; after much on- line searching, I found that several others reported the same problem; I couldn't find that any of the others found a resolution. I've found an answer; it may well be an oversight in bsdlabel and it's MAN file. Example error messages are as follows: partition a: partition extends past end of unit partition b: offset past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities Here's the story for anyone else that may run into the problem. The command 'disklabel ad0' worked fine in 4.10 using disklabel. The same command or 'bsdlabel ad0' doesn't work for me in 5.3 using bsdlabel; instead, I get a "no valid label found" message. Referring to MAN BSDLABEL, I found that it says to use the command 'bsdlabel disk', where "disk represents the disk in question, and may be in the form da0 or /dev/da0." Using the da0 form didn't work, so I arbitrarily tried 'bsdlabel ad0s1a' and got the expected display plus an additional 17 error lines. Had I read farther into MAN BSDLABEL, I would have found the example 'bsdlabel da0s1'. That form provides the expected results, without the extra error lines. Only the argument 'ad1s1' gives the expected results when using 5.3's bsdlabel. Using 'ad1s1a' or 'ad1s1c' returns the expected results and adds troubling additional error lines. Using 'ad0' alone fails. Disklabel, in 4.10, seems more tolerant of user input, displaying the correct report when the disk, slice, or any valid partition is used as the "disk" argument. Bsdlabel, however, works differently. If this issue was created to get this new user to experiment and to Read The Freebsd MANual, it worked. Whew. Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bsdlabel messages?
Trying to understand what bsdlabel is telling me, I did some experimenting. The computer has a working installation of Vers. 4.10 on ad1, so I booted to ad1 and ran 4.10. Using 4.10 and disklabel (replaced by bsdlabel in 5.3), I find that disklabel seems happy with my ad0 disk, as compared to what bsdlabel says about the same disk when running 5.3. Perhaps this is a problem with bsdlabel? I don't know enough about what I am seeing to suggest that, but I don't understand what bsdlabel is reporting to me. Below are outputs from disklabel and bsdlabel, reporting on the same disk. I used bsdlabel -A this time to make the displays similar. When I don't use the -A argument, I get many more lines describing problems; please refer to my November 16 message to see those lines. Help please? Jay O'Brien Rio Linda, California, USA === The following output is obtained while running FreeBSD)4.10 on disk ad1 and typing 'disklabel ad0s1a'. Note that FreeBSD 5.3 is installed on ad0, but the 4.10 installation on ad1 was selected via boot manager. # /dev/ad0s1a: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14592 sectors/unit: 234436482 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 419430404.2BSD 2048 16384 28552 # (Cyl.0 - 261*) b: 6291456 4194304 swap# (Cyl. 261*- 652*) c: 2344364820unused0 0# (Cyl.0 - 14592*) d: 20971520 104857604.2BSD 2048 16384 28552 # (Cyl. 652*- 1958*) e: 20971520 314572804.2BSD 2048 16384 28552 # (Cyl. 1958*- 3263*) f: 4194304 524288004.2BSD 2048 16384 28552 # (Cyl. 3263*- 3524*) g: 83886080 566231044.2BSD 2048 16384 28552 # (Cyl. 3524*- 8746*) h: 83886080 1405091844.2BSD 2048 16384 28552 # (Cyl. 8746*- 13967*) === uname-a running 4.10: FreeBSD server1.jayobrien.net 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 === The following output is obtained while running FreeBSD 5.3 on disk ad0 and typing 'bsdlabel -A ad0s1a'. # /dev/ad0s1a: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14593 sectors/unit: 234441648 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 4194304 634.2BSD 2048 16384 28552 b: 6291456 4194367 swap c: 234436482 63unused0 0 # "raw" part, don't edit d: 20971520 104858234.2BSD 2048 16384 28552 e: 20971520 314573434.2BSD 2048 16384 28552 f: 4194304 524288634.2BSD 2048 16384 28552 g: 83886080 566231674.2BSD 2048 16384 28552 h: 83886080 1405092474.2BSD 2048 16384 28552 bsdlabel: partition c doesn't start at 0! bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities === uname -a running 5.3: FreeBSD server1.jayobrien.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 === ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bsdlabel messages?
What is bsdlabel trying to tell me? This is the display from bsdlabel ad0s1a. I also have ad1 and ad2; they also give the same errors. Outputs from bsdlabel and uname are below. The system seems to be running ok; a second machine, also running 5.3-RELEASE, exhibits the same behavior. Jay O'Brien Rio Linda, California, USA server1# bsdlabel ad0s1a # /dev/ad0s1a: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 4194304 634.2BSD 2048 16384 28552 b: 6291456 4194367 swap c: 234436482 63unused0 0 # "raw" part, don't edit d: 20971520 104858234.2BSD 2048 16384 28552 e: 20971520 314573434.2BSD 2048 16384 28552 f: 4194304 524288634.2BSD 2048 16384 28552 g: 83886080 566231674.2BSD 2048 16384 28552 h: 83886080 1405092474.2BSD 2048 16384 28552 partition a: partition extends past end of unit partition b: offset past end of unit partition b: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities partition d: offset past end of unit partition d: partition extends past end of unit partition e: offset past end of unit partition e: partition extends past end of unit partition f: offset past end of unit partition f: partition extends past end of unit partition g: offset past end of unit partition g: partition extends past end of unit partition h: offset past end of unit partition h: partition extends past end of unit server1# uname -a FreeBSD server1.jayobrien.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to make configuration changes without a reboot?
Eric Kjeldergaard wrote: >>I learned that in order to make changes to the screen saver, >>I had to reboot the computer. Those changes, made by >>sysinstall, appear in /etc/rc.conf. >> >>Is there a way to make such changes take effect without >>rebooting? (Version 5.3 RELEASE, i386) > > > Of course there are. Reboots are only really necessary for switching > kernels. Unfortunately, this often takes a bit more knowledge. In > the case of screensavers, a combination of kldload (to load the > desired screensaver) and vidcontrol (to set timeouts and such). man > kldload and man vidcontrol should get you going on this. > Eric, Thanks for the vidcontrol reference. I didn't realize that screensaver timeout was in vidcontrol; that will give me easy control of screensaver on/off when I want it. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Which Apache version to use?
Tabor Kelly wrote: > > The apache13 port is just apache. The apache-x ports also include x. For > example, I run apache-modssl, because I needed ssl support. mod_ssl > isn't really a module since it (also) requires patching the base apache > code. > > As for apache2, I think it is still marked as unstable (though some > people successfully use it in production environments). The main > "advantage" of apache2 over apache1.3 has to do with multi-threading vs. > having multiple processes (apache 1.3 is not threaded). This isn't > actually an advantage in FreeBSD because their is not much process > overhead, this is mainly intended for the windows users. > > Also, some apache13 modules have not been ported to apache2 yet, notably > mod_perl. > > In short, IMHO, install apache13 unless you need SSL support, then > install apache13-modssl. > Daniel Bye wrote: > > If this is to be a dedicated server machine, you don't really need X11 > installed. My opinion, others will surely differ. > >>As I'm learning from scratch, am I correct in assuming that I would >>be better off to start with apache2, or should I use one of the >>flavors of apache13 (1.3) and perhaps upgrade later? > > There are fairly large differences between the two, but if you can learn > how to use and look after one, then you can learn the other one without > too much hassle, too. > >>If I use 1.3, why would I use anything other than the apache13 port? > > Take a look in each port's pkg-descr file for a little more information. > For example, apache13-modperl embeds a perl interpreter in Apache to cut > out the startup overheads of running perl CGI scripts. Apache13-ssl > includes support for encrypted session (https). Thanks, folks! I'll use apache13 and see what happens. Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to make configuration changes without a reboot? (resolved)
Jay O'Brien wrote: >> I learned that in order to make changes to the screen saver, >> I had to reboot the computer. Those changes, made by >> sysinstall, appear in /etc/rc.conf. >> >> Is there a way to make such changes take effect without >> rebooting? (Version 5.3 RELEASE, i386) Matthew T. Lager wrote: > You can do a shutdown now to get to single user mode, then > execute an exit which will boot back into multi-user mode. > All rc scripts will be re-initilized and you won't have to > reboot the entire system (be sure to only do this on the > console obviously)... Olivier Nicole wrote: > Maybe you can try to unload the screen saver module and > reload it, look at kldload(8), kldstat(8) and kldunload(8) Matt, Oliver: Thanks! I found that the shutdown/exit worked fine for changing the blanktime, but it wouldn't change the logo unless the logo was first unloaded using first kldstat and then kldunload. I needed guidance from both of you, thanks very much! Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to make configuration changes without a reboot?
I learned that in order to make changes to the screen saver, I had to reboot the computer. Those changes, made by sysinstall, appear in /etc/rc.conf. Is there a way to make such changes take effect without rebooting? (Version 5.3 RELEASE, i386) Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Which Apache version to use?
My purpose: Learn FreeBSD, learn Apache, build simple web server. Hardware: Dedicated i386 machine, three big HDs (120GB, 120GB, 200GB) OS: FreeBSD 5.3. No X windows installed (maybe later?) Apps: Also intend to use postfix, majordomo, samba LAN:Serve LAN with Windows machines, all LAN IPs are fixed. Internet: Fixed IPs available to be used later. Web pages: I have many web pages (no java) that I would like to copy from their present server to a local server. My new 5.3 installation includes these ports: apache-contrib apache-forrest apache-jserv apache13 apache13+ipv6 apache13-modperl apache13-modssl apache13-modssl+ipv6 apache13-ssl apache2 As I'm learning from scratch, am I correct in assuming that I would be better off to start with apache2, or should I use one of the flavors of apache13 (1.3) and perhaps upgrade later? If I use 1.3, why would I use anything other than the apache13 port? Links to "how to do it" web pages would be appreciated. Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with boot0 (resolved)
Jay O'Brien wrote: Thanks again Henrik and Ruben, you found the problem for me. I've now built a new installation of 5.3 on ad0, and I have a copy of the 4.10 install on ad1. Now there's no question about which is running. I edited ad1's /etc/fstab to change all instances of ad0 to ad1, and now when I hit F5 during bootup to select drive 1, 4.10 boots and runs fine on ad1. If I hit F1 during bootup, then 5.3 boots and runs fine on ad0. To recap, I only installed boot0 (using boot0cfg) on ad0, not on both drives. My computer BIOS boots the ad0 drive, and boot0 gives me a chance to select the ad1 drive. I note that boot0 remembers my last selection, and makes it the default on the next boot. Nice touch. Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bootonly.iso?
Jay O'Brien wrote: > Matthew T. Lager wrote: > > >>Did you be sure you were downloading the .iso in binary format? If your >>FTP client was transferring at ASCII, that would be your prob... >> >>Matt L >> >> >> >>>I have successfully burned iso CDs from FreeBSD files, so I know >>>my process for burning the CDs works. >>> >>>I burned Release 5.3's bootonly.iso file to a CD. When I put that >>>CD back into my Windows machine that burned it, it is recognized >>>as a blank CD. >>> >>>When I put that CD into my FreeBSD computer that was built from >>>FreeBSD iso CDs, it doesn't work, as if it were a blank CD. >>> >>>What am I missing? >>> >>>Jay O'Brien >>> >>>PS.. I did try it a second time, just in case I had a bad blank CD. >>> > > > > I downloaded this file exactly as I did the other iso images that I > successfully burned and used. I'll download it again. > Downloaded again, and checksum ok again. I burned it on a different computer, and now I see an iso image in windows. The new CD works, and boots me into the install menu. I sure don't know what was wrong with the other two CDs I burned, but this one works. Now to find out I can use it for! Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bootonly.iso?
Matthew T. Lager wrote: > Did you be sure you were downloading the .iso in binary format? If your > FTP client was transferring at ASCII, that would be your prob... > > Matt L > > >>I have successfully burned iso CDs from FreeBSD files, so I know >>my process for burning the CDs works. >> >>I burned Release 5.3's bootonly.iso file to a CD. When I put that >>CD back into my Windows machine that burned it, it is recognized >>as a blank CD. >> >>When I put that CD into my FreeBSD computer that was built from >>FreeBSD iso CDs, it doesn't work, as if it were a blank CD. >> >>What am I missing? >> >>Jay O'Brien >> >>PS.. I did try it a second time, just in case I had a bad blank CD. >> I downloaded this file exactly as I did the other iso images that I successfully burned and used. I'll download it again. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bootonly.iso?
I have successfully burned iso CDs from FreeBSD files, so I know my process for burning the CDs works. I burned Release 5.3's bootonly.iso file to a CD. When I put that CD back into my Windows machine that burned it, it is recognized as a blank CD. When I put that CD into my FreeBSD computer that was built from FreeBSD iso CDs, it doesn't work, as if it were a blank CD. What am I missing? Jay O'Brien PS.. I did try it a second time, just in case I had a bad blank CD. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with boot0
Thanks Henrik and Ruben, Good input from you both. To be sure which HD I'm on, I made (empty) directories in the root of each drive, called (either) ..AD0 or ..AD1. In this way the HD's aren't completely identical, and I can see which one boots. I agree that boot0 shouldn't be on the second drive and I fixed that. However, I couldn't restore the standard mbr until I went to /stand/sysinstall, selected Configure, selected fdisk, ad1, set bootable, write changes, yes, standard mbr, ok. This worked fine. If I interrupt the boot process, at the command prompt I can use the ls command to list files and see the empty directory that confirms which drive has booted. If I boot from the second drive, ad1, then fstab and other files point to ad0, not ad1, and I wind up on ad0, regardless of which drive actually boots. It seems to me that the boot0cfg -o option should force the drive in use to be referred to the boot0cfg option -b 0x80, and then the second drive would be used but called 0x80. This doesn't seem to be the case. Apparently I will have to make some changes to the files on the second drive so that the first drive won't be used at all when the system is booted from the second drive. Which files? To recap, I can use boot0 to boot from either HD. However, when the boot is on the second HD, it still points to (and uses) the first drive as if it was booted there. I have identical files on ad0 and ad1. I would like to be able to boot from (and use the files on) either ad0 or ad1. Help? Jay O'Brien Rio Linda, CA, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Help with boot0
I have two identical hard drives on the same IDE controller; The file systems are identical. I can move the "Master" jumper from one HD to the other and the computer will boot on the HD with the jumper. It becomes ad0 and the other HD is ad1. I have installed boot0cfg on both drives with the -B option. Booting with either drive gives me a F1 (FreeBSD) option and a F5 (Disk1) option. F1 boots the drive set up with the hardware jumper to be the IDE controller master. F5 gives another selection, F1 (FreeBSD) and F5 (Disk2). F1 boots on the IDE master, and F5 won't boot. I would like to be able to boot from either drive using the bootup selection. I know both drives work fine as the boot drive when selected by the hardware drive jumper. What am I missing, why doesn't boot0 work for me? Jay O'Brien PS.. I'm using 4.10, and this exercise is so I can build 5.3 on one of the Hard drives and be able to boot to either version. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mount hides underlying files
Chris Hill wrote: > On Thu, 11 Nov 2004, Jay O'Brien wrote: > > >>If I mkdir /test and then place files in /test, those files >>are no longer visible when I use /test as a mount point. The >>files become visible again when I unmount the device. >> >>I have read documentation explaining this phenomenon, and I >>would like to review that documentation again. Is it in the >>handbook? > > > Yes. There is a discussion of this at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disk-organization.html > > Also see the following page. > Chris, Thank you, that answers the basic question, with the word "replaces". That is, when a filesystem is "mounted" to a directory, it "replaces" what was there, it doesn't add to it. This is different from my experience with other operating systems, and was confusing to me. I do remember seeing a more verbose description, however, that discusses what happens to the underlying files when something is mounted over the top of their directory; I also vaguely remember something suggesting that this is a way to "hide" files from the casual observer, revealing the files by unmounting the file system that caused them to be hidden. I don't have a reason to hide files; I remember reading the discussions, and would like to read them again. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mount hides underlying files
If I mkdir /test and then place files in /test, those files are no longer visible when I use /test as a mount point. The files become visible again when I unmount the device. I have read documentation explaining this phenomenon, and I would like to review that documentation again. Is it in the handbook? A reference or link would be appreciated. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-release-i386-disc2.iso will not burn
Karel Miklav wrote: > j&kcooke wrote: > >>I have downloaded both of the 5.3 i386 isos and the miniinstall iso, >>disc1 and the miniinstall burn an image, disc 2 does not. I downloaded >>disc2 from two additional ftp sites with the same result. > > > There's probably nothing wrong with the image, I had the same issue with > Nero. Check signature with some utility (md5, gpg...) just to be sure > than burn with cdrecord (http://www.fokus.gmd.de/research/cc/ > glone/employees/joerg.schilling/private/cdrecord.html): > > cdrecord -help > cdrecord -scanbus > cdrecord dev=1,1,0 5.3-release-i386-disc2.iso > > Put the value returned by -scanbus in the dev parameter upthere. > > I'd still like to know what is the problem with this ISO as I didn't > find a Windows utility to handle it sucessfuly. Beside cdrecord :) > > Regards, > Karel > I've successfully burned 5.3-RELEASE ISO disks 1, 2 and miniinst using Sonic Record now Version 6. The computer runs XP Pro SP1. No problems. The CDs read fine in a Windows machine, and I've used the miniinst CD to install V5.3. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get out of GNOME?
Frank Knobbe wrote: > On Sun, 2004-10-31 at 00:27, Jay O'Brien wrote: > >>There's got to be a way to shut GNOME and XFree86 down without >>rebooting! At least that works. I wonder if this may be the time >>to go to version 5 and the newer version of X? > > > Manually? > > To stop Gnome: /usr/X11R6/etc/rc.d/gdm.sh stop > To start Gnome: /usr/X11R6/etc/rc.d/gdm.sh start > > Permanently? Remove the gdm.sh file. > > Regards, > Frank > Frank, that works perfectly. However, copying gdm.sh.sample as gdm.sh so that "stop" will work also starts gdm on boot, and I don't want that. However, I now see what gdm.sh is doing. The command, from that file, is 'killall -m gdm 2' and that is much simpler than running top, identifying the PID and then killing the gdm binary. Thanks for showing me the way! Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Video monitor parameters
Running 5.3 RELEASE. My LCD monitor is running 720x400 @ 70Hz. It suggests I should use 1280x1024 @ 60 Hz. I'm running in 50 line mode, and no X stuff yet. Is there a way to change the video parameters to 1280x1024 and make the monitor happy? Otherwise, every time I boot I have to go through a setup process with the monitor to get all of the 50 lines completely on screen. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: console error message
Dan Nelson wrote: > In the last episode (Nov 06), Jay O'Brien said: > >>Dan Nelson wrote: >> >>>In the last episode (Nov 06), Jay O'Brien said: >>> >>>>I get this message regularly, even when the computer is sitting >>>>idle. The date and time changes, but the text stays the same. >>>> >>>>edna# Nov 6 18:17:29 edna inetd[438]: ssh/tcp: bind: Address already in use >>>> >>>>The only lines in /src/etc/inetd.conf that do not start with a # >>>>are the ftp, ssh, and telnet (tcp, not tcp6) lines. >>> >>>ssh is usually started as a daemon during bootup by /etc/rc.d/sshd, >>>not via inetd. Just comment those inetd.conf lines out again. >> >>Thank you! That fixed it and ssh still works, incoming and outgoing. >>What was the error message telling me, and why was it repeating? And >>why was I prompted to "uncomment" services by the install program? > > > inetd was complaining that it couldn't listen on port 22 because > another process (sshd) was already there. I'm not sure about the > uncommenting bit. > Dan, Thanks. I appreciate your help. Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
console error message
This is on a new install of 5.3 RELEASE on a computer that has not run FreeBSD previously. The computer name is edna. I get this message regularly, even when the computer is sitting idle. The date and time changes, but the text stays the same. edna# Nov 6 18:17:29 edna inetd[438]: ssh/tcp: bind: Address already in use The only lines in /src/etc/inetd.conf that do not start with a # are the ftp, ssh, and telnet (tcp, not tcp6) lines. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 RELEASE downloaded
I just downloaded 5.3-RELEASE-i386-miniinst.iso from ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/5.3/ . File attributes are: 274400 KB 11/5/2004 5:46:00 AM. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: memory requirements?
Danny MacMillan wrote: > On Fri, Nov 05, 2004 at 10:17:59PM -0700, Jay O'Brien wrote: > >>Kris Kennaway wrote: >> >>> >>>It all depends what you want to do with it...it's the applications you >>>run that take up most of the memory. 128MB is a bit on the small side >>>if you're going to be doing memory-heavy desktop work (e.g. running >>>mozilla, KDE, etc), but there are plenty of lighter-weight >>>alternatives to those applications. >>> >>>Kris >> >>Good point. I am bringing up another (very capable) machine and learning >>as I go; I set it up with 4.10 and I now think I should be running 5.2.1. >>It will ultimately be a mail and web server. >> >>I thought I would bring this old machine (inherited from my 89 yr old >>m-i-l who passed away in August) on 5.2.1 to get a feel for it; I would >>probably not do much more than use it as a SSH terminal to connect to >>the other machine and as a learning tool to learn (or re-learn) unix >>commands. It presently runs Win98SE, had a CD reader and a NIC card, >>so I know it has working hardware. >> >>The bottom line is that 128MB seems adequate for FreeBSD itself? > > > More than adequate. I have a 300MHz 64MB machine with a 7GB hard drive > running 5.2.1 handily. I don't have much on there besides dovecot, but I > do use it as an installation and configuration testbed for new software > I'm interested in. I don't have X installed. There is no difference in > apparent speed at the console or through SSH between this machine and my > other much more capable (800MHz, 384MB) 5.2.1 machine. > > Unless your needs are more substantial than they would appear, your > machine is overpowered. I would just go ahead and try it. If you find > that you need more power you haven't closed the door on any opportunities > by trying it. As another poster has mentioned, you might want to wait > for 5.3, or put a pre-release version of 5.3 on it. > Chad Leigh -- Shire.Net LLC wrote: > you may want to put 5.3 on it. Supposed to release this weekend > according to a note earlier. > > I only use FreeBSD for server work so I cannot comment on memory > requirements for running X etc > > Chad > Thanks, folks! I hadn't considered 5.3, but as this is really only a test bed, I might as well go for it. I see 5.3-RC2 is available, I'll grab it and burn an ISO CD. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: memory requirements?
Kris Kennaway wrote: > On Fri, Nov 05, 2004 at 08:49:56PM -0800, Jay O'Brien wrote: > >>I inherited a 400 MHz Pentium II with 128MB of RAM >>and a 20GB HD. >> >>Is this an adequate configuration to run 5.2.1, or >>do I need to add memory? > > > It all depends what you want to do with it...it's the applications you > run that take up most of the memory. 128MB is a bit on the small side > if you're going to be doing memory-heavy desktop work (e.g. running > mozilla, KDE, etc), but there are plenty of lighter-weight > alternatives to those applications. > > Kris Good point. I am bringing up another (very capable) machine and learning as I go; I set it up with 4.10 and I now think I should be running 5.2.1. It will ultimately be a mail and web server. I thought I would bring this old machine (inherited from my 89 yr old m-i-l who passed away in August) on 5.2.1 to get a feel for it; I would probably not do much more than use it as a SSH terminal to connect to the other machine and as a learning tool to learn (or re-learn) unix commands. It presently runs Win98SE, had a CD reader and a NIC card, so I know it has working hardware. The bottom line is that 128MB seems adequate for FreeBSD itself? Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
memory requirements?
I inherited a 400 MHz Pentium II with 128MB of RAM and a 20GB HD. Is this an adequate configuration to run 5.2.1, or do I need to add memory? Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to print to hp JetDirect/LaserJet 1300 Network printer (RESOLVED)
I now have my JetDirect hp LaserJet 1300 working over my LAN. There's lots of tweaking yet to do, but here's what I had to do to make it print. The printer name is hp1300, its IP is 192.168.1.40. The FreeBSD (4.10) computer is server1.xyz.net (xyznet substituted for real URL) and its IP is 192.168.1.9. 1. add to /etc/printcap: lp|hp1300:\ :lp=:rm=192.168.1.40:rp=text:lf=/var/log/lpd-errs:\ :sd=/var/spool/lpd:mx#0:sh: 2. add to /etc/hosts file: 192.168.1.9server1.xyz.net server1 3. As root, type lpd to start master lpd process (later I added lpd_enable="YES" to rc.conf 4. Test printer by typing: lptest 20 5 | lpr Thanks to all who have assisted with responses; your help has been invaluable. Oh yes, I don't understand why the addition was necessary to the hosts file; I now see I can remove it and the printer continues to work. I was prompted by an error message to define server1 and I believe it was necessary for the initial print job. Can anyone explain this? Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to print to hp JetDirect/LaserJet
Mike Jeays wrote: > Add rm=192.168.1.40 to the /etc/printcap entry. > > My example is (faraday is the name of the machine with the printer): > > lp|hp710c:\ > :lp=::rm=faraday:rp=lp:lf=/var/log/lpd-errs:sd=/var/spool/lpd:mx#0: > Mike, Thanks much, but that doesn't work for me. I also tried rm=http://192.168.1.40 and that produced some error results; I'll experiment more tomorrow. Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get out of GNOME? (resolved)
Jonathan Chen wrote: > On Sat, Oct 30, 2004 at 10:27:41PM -0700, Jay O'Brien wrote: > >>Andrew Jones wrote: >> >>>Jay O'Brien wrote: >>> >>>>Ok, what DO I do to shut down gnome if I don't want it running? >>>> >>> >>>ctrl+alt+backspace. It crashes the xserver though, but it'll exit. >> >>Nope. It doesn't work for me. With gdm/X running, ctl+alt+bksp goes >>first to black screen then comes back with a new logon window. If I >>do it enough times, it reports to the virtual terminal "The display >>server has been shut down about 6 times in the last 90 seconds, it >>is likely that something bad is going on. I will wait for two minutes >>before trying again on display :0." and then it comes back on. > > > Turn the gdm entry in /etc/ttys to "off". kill -HUP 1. Then kill the > gdm process. There is no gdm entry in /etc/ttys. kill -HUP 1 doesn't seem to have any effect. However. In top, killing XFree86 or gdmlogin restarts GNOME. killing them both results in a "No such process" error on gdmlogin process and GNOME restarts. However, killing the gdm binary that is in "poll" state does the job; killing it causes all four of the processes to drop out of the top display. Interesting. Thanks everyone, your suggestions helped me find an answer that works. I don't think it should be this difficult, tho! Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get out of GNOME?
Andrew Jones wrote: > Jay O'Brien wrote: >> >>Ok, what DO I do to shut down gnome if I don't want it running? >> > > ctrl+alt+backspace. It crashes the xserver though, but it'll exit. Nope. It doesn't work for me. With gdm/X running, ctl+alt+bksp goes first to black screen then comes back with a new logon window. If I do it enough times, it reports to the virtual terminal "The display server has been shut down about 6 times in the last 90 seconds, it is likely that something bad is going on. I will wait for two minutes before trying again on display :0." and then it comes back on. If I use ctl+alt+F1 to go from GNOME to a virtual terminal, then try ctl+alt+backspace, it does nothing (except beep). Top reports that the processes that come up when I start gdm are XFree86, gdmlogin, and two gdm-binary processes. KILL seems to have no effect on them. There's got to be a way to shut GNOME and XFree86 down without rebooting! At least that works. I wonder if this may be the time to go to version 5 and the newer version of X? Jay O'Brien Specs: FreeBSD V4.10, GNOME package obtained today via the Internet using pkg_add -r gnome2. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get out of GNOME?
Matt Navarre wrote: > On Saturday 30 October 2004 05:51, Jay O'Brien wrote: > >>WHERE should I have found the magic ctl+alt+F1? Nowhere in the GNOME >>help, is it to be found, Google "exit gnome" and the like didn't find >>it > > > ctl+alt+F1 doesn't really quit Gnome. It switches to a virtual terminal that > has getty instead of GDM running on it. > So I see h Ok, what DO I do to shut down gnome if I don't want it running? Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to get out of GNOME?
pete wright wrote: > On Sat, 30 Oct 2004 17:11:23 -0700, Jay O'Brien <[EMAIL PROTECTED]> wrote: > >>Running 4.10. >> >>I added the GNOME package, updated the files it said to edit >>when it was installing, and now I can't get out of GNOME, >>even with editing (via ftp) the files back as they were in >>the first place and rebooting. >> >>How can I get back to a command line terminal? > > > ctl+alt+F1 should bring you to a virtual terminal. i bet gnome is > launching GDM or XDM on boot, if you take that out of your startup > scrips you should be all set. > Pete, Thank you. Now I can get control again. And yes, it had me copy /X11R6/etc/rc.d/gdm.sh.sample as gdm.sh. I deleted the gdm.sh and now it doesn't boot into GNOME. WHERE should I have found the magic ctl+alt+F1? Nowhere in the GNOME help, is it to be found, Google "exit gnome" and the like didn't find it Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to get out of GNOME?
Running 4.10. I added the GNOME package, updated the files it said to edit when it was installing, and now I can't get out of GNOME, even with editing (via ftp) the files back as they were in the first place and rebooting. How can I get back to a command line terminal? Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to print to hp JetDirect/LaserJet 1300 Network printer?
Kent Stewart wrote: > On Saturday 30 October 2004 12:56 pm, Jay O'Brien wrote: > >>I'm confused, as there seem to be many conflicting directions >>out there. http://Linuxprinting.org is overwhelming. >> >>I'm a new user of 4.10. I want to print to my hp 1300 LaserJet, >>which has a JetDirect network server and is connected to my LAN. >>The Win machines on the LAN print fine to the printer. >> >>The printer is assigned the fixed IP 192.168.1.40. I can ping >>that address from my FreeBSD computer. >> >>Suggestions? > > > It is about as simple a printer to print to that you can get. On the other > hand, you have problems configuring all possibilities. I use > > lp|HPLJ2:\ > :lp=:\ > :rm=psrvr:\ > :rp=L1:\ > :if=/var/spool/lpd/lj.sh:\ > :lf=/var/log/lpd-errs:\ > :sd=/var/spool/lpd:\ > :mx#0 > for my printcap entries. I have a netgear printsever and it is l1 on the > server. I can't lp a file because it stairsteps but I want to print from > kword and don't have any problem. > > Kent > > >>Jay O'Brien >>Rio Linda, CA USA Kent, How does that send the files to be printed to 192.168.1.40? Stairsteps? Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to print to hp JetDirect/LaserJet 1300 Network printer?
I'm confused, as there seem to be many conflicting directions out there. http://Linuxprinting.org is overwhelming. I'm a new user of 4.10. I want to print to my hp 1300 LaserJet, which has a JetDirect network server and is connected to my LAN. The Win machines on the LAN print fine to the printer. The printer is assigned the fixed IP 192.168.1.40. I can ping that address from my FreeBSD computer. Suggestions? Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Reinstalling, then upgrading (Was Re: Salvageable? (Was Re:make installworld error))
Charles Ulrich wrote: > The phrase "ports > build packages" is a neat and efficient way of rectifying the > misunderstandings that can occur when trying to give a proper > explanation of FreeBSD package management. > Charles, Thank you for concisely answering a burning question I didn't know how to ask. I had gathered the concept that if I built a "port" I was stuck with it, because it couldn't be removed as easily as something installed as a package. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
XFree86 -- next step?
I finally have XFree86 working, at least to the point that I can type "X" and get the expected grid and "X" mouse cursor. That in itself doesn't seem very useful, but it works. As a learning exercise, which Desktop environment should I install as a first effort, and how do I run it? I'm referring to the FreeBSD Handbook at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html Desktop Environments I intend to install Mozilla as a browser, in case that makes any difference. Also, what is the mechanism that interprets the "X" command to run XFree86? Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to view .ascii file?
Jay O'Brien wrote: > I'm trying to read the 'paper.ascii' file contained in > /usr/share/doc/psd/12.make/paper.ascii.gz and it is > a mess. This is a tutorial on "make". I've unzipped > the file in a WinXP machine and I can't find a display > tool that will not show the formatting stuff in the file. Thanks to all for the fixes; they all work except lynx, apparently because lynx isn't present. I didn't realize there's such a difference in "plain ascii" between FreeBSD and Windows. Now that I can read the file, I see that it isn't what I thought it would be; it is referred to at the end of MAN MAKE and I thought it would be useful, as it was called a "tutorial". It reads like a foreign language to me, however, as I don't (yet) have the basic understanding of "MAKE" that it expects. This all started as follows: I did a make install clean of XFree86, hoping to start over and take another shot at LCD display parameters. The message I received said it was already installed, and "You may wish to 'make deinstall' and install this port again by 'make reinstall' to upgrade it properly. I want to know how 'make deinstall' and 'make reinstall' operate before I use them. But that's another subject. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to view .ascii file?
ashadul hoque wrote: > > Have you tried opening it with wordpad. Yes. Wordpad, Notepad, Word. It's a mess in all of them. Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
how to view .ascii file?
I'm trying to read the 'paper.ascii' file contained in /usr/share/doc/psd/12.make/paper.ascii.gz and it is a mess. This is a tutorial on "make". I've unzipped the file in a WinXP machine and I can't find a display tool that will not show the formatting stuff in the file. What is the "right" way to read this file? Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mouse problems with KVM switch
I had the same problems with a 4-port KVM. I am using a 2-port KVM successfully between an XP box and a FreeBSD 4.10 box. I've found that the scroll wheel doesn't work after switching back to Windows unless I also "reset" the KVM (Scroll Lock twice + End), but that's not a big deal. Here's the 2-port KVM switch: http://airlinkplus.com/kvm/akvm2.htm It's available at Fry's: http://shop1.outpost.com/product/3891817 Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: keyboard history buffer setting
Jan Christian Meyer wrote: > If you still need to do shell stuff on startup, slapping > together a script and putting it in rc.d is the way to go. > The man pages of rc explain the works, and include a > template script which you can copy and fill in. Wow! There's a lot there, in man rc. I'll play with that. Is there a way to force the startup files to be re-read without completely rebooting the system? That would help while I'm learning. Thank you! Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scrollback history buffer setting (was keyboard)
Jay O'Brien wrote: > I can run kbdcontrol -h 500 or vidcontrol -h 500 to set the > scroll back keyboard history buffer to 500 lines for the > virtual terminal I'm using. How can I make that happen at > boot, in the same manner as I run allscreens_flags in > rc.conf to set other terminal parameters? I don't need > this to set all of the virtual terminals; it would be > nice if each terminal could be set separately. > > It doesn't work for me when placed in rc.conf, with either > a direct command or attempting to use allscreens_flags. > > I'm using 4.10. > > Jay O'Brien > Rio Linda, CA USA Follow-up: Re-reading the above could be interpreted that I want to be able to review more keyboard lines; not so. I should not have used the word "keyboard". I'm looking for redisplay of the screen lines. Both kbdcontrol and vidcontrol perform that function. I've built a workaround by adding this to root and user .cshrc: alias bu vidcontrol -h (with a space following). This allows me to type 'bu 500' to set the buffer to 500 lines. In addition, I would like to be able to set it during boot. Is that possible? Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
keyboard history buffer setting
I can run kbdcontrol -h 500 or vidcontrol -h 500 to set the scroll back keyboard history buffer to 500 lines for the virtual terminal I'm using. How can I make that happen at boot, in the same manner as I run allscreens_flags in rc.conf to set other terminal parameters? I don't need this to set all of the virtual terminals; it would be nice if each terminal could be set separately. It doesn't work for me when placed in rc.conf, with either a direct command or attempting to use allscreens_flags. I'm using 4.10. Jay O'Brien Rio Linda, CA USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X configuration problem - new info
Luke Kearney wrote: > On Tue, 17 Aug 2004 01:31:30 -0700 > Jay O'Brien <[EMAIL PROTECTED]> spake thus: > > >>Initial 4.10 installation. Trying to configure XFree86. >>from /stand/sysinstall, select Configure | XFree86. >> >>I THINK I've tried every possible combination. I couldn't >>use the "Fully graphical XFree86 configuration tool" as >>the graphic was partially off-screen and the monitor was >>"out of range". I used the textmode tool and the shell- >>script tool, settling on the shell-script tool. After >>agreeing that it should write /etc/X11/XF86, and selecting >>a desktop to use, many different attempts all result in >>this error: >> >>"Error mounting /dev/acd0c on /dist: Input/output error (5)" >> >>And the next screen is: >> >>"An error occurred while adding the package(s) required by >>this desktop type. Please change installation media and/or >>select a different, perhaps simpler, desktop environment >>and try again." >> >>I don't find a /etc/X11/ directory, much less a XF86 file. >> >>Video card is ati XPERT 98, monitor is 1280x1024 LCD. >> >>A suggestion for what to try next? >> >>Jay O'Brien >>Rio Linda, CA USA > > > Yes, download and burn yourself another install disk or change the media > source in the install screen and then make it download the sources from > the internet. Sounds like you've got bad media rather than a config that > can't be done. > > HTH > > LukeK > Ok, I did as you suggested and I'm presently getting stuff via ftp. It looks like it will be downloading all day. I thought the ISO image CD would avoid this; what is all the stuff that is downloading? Isn't there a way to just replace the XF86 stuff that may be bad? Where are all these files going, and why do I need to download them all? Once this is done, will I have to do it all over again when I rebuild again from scratch, or is there a way, like on the CD, that I can store just those files I need? There's got to be a better way! Jay After over an hour and a half of downloading (and I have a 1.3MHz DSL) I tried again. Now I get different error messages, and I don't understand at all what this unwanted download has done to my computer. The errors are: VGA(0): Virtual height (0) is too small for the hardware (min 1) Screen(s) found, but none have a usable configuration. I'm going to wipe the HD clean again and start over, using my current ISO CD. This download, with many separate unrelated files, has me really concerned about what I unwittingly added to my HD. I don't even know where all the files I saw come in are now placed on the HD! Is there any disadvantage to installing XFree86 with # pkg_add -r XFree86 as compared to using /stand/sysinstall, select Configure | XFree86 ? Jay PS.. I'm really frustrated, so obviously I'm learning... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X configuration problem
Luke Kearney wrote: > On Tue, 17 Aug 2004 01:31:30 -0700 > Jay O'Brien <[EMAIL PROTECTED]> spake thus: > > >>Initial 4.10 installation. Trying to configure XFree86. >>from /stand/sysinstall, select Configure | XFree86. >> >>I THINK I've tried every possible combination. I couldn't >>use the "Fully graphical XFree86 configuration tool" as >>the graphic was partially off-screen and the monitor was >>"out of range". I used the textmode tool and the shell- >>script tool, settling on the shell-script tool. After >>agreeing that it should write /etc/X11/XF86, and selecting >>a desktop to use, many different attempts all result in >>this error: >> >>"Error mounting /dev/acd0c on /dist: Input/output error (5)" >> >>And the next screen is: >> >>"An error occurred while adding the package(s) required by >>this desktop type. Please change installation media and/or >>select a different, perhaps simpler, desktop environment >>and try again." >> >>I don't find a /etc/X11/ directory, much less a XF86 file. >> >>Video card is ati XPERT 98, monitor is 1280x1024 LCD. >> >>A suggestion for what to try next? >> >>Jay O'Brien >>Rio Linda, CA USA > > > Yes, download and burn yourself another install disk or change the media > source in the install screen and then make it download the sources from > the internet. Sounds like you've got bad media rather than a config that > can't be done. > > HTH > > LukeK > Ok, I did as you suggested and I'm presently getting stuff via ftp. It looks like it will be downloading all day. I thought the ISO image CD would avoid this; what is all the stuff that is downloading? Isn't there a way to just replace the XF86 stuff that may be bad? Where are all these files going, and why do I need to download them all? Once this is done, will I have to do it all over again when I rebuild again from scratch, or is there a way, like on the CD, that I can store just those files I need? There's got to be a better way! Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
