9.0 install and journaling
I bit the bullet and installed the rc3, after spending half the day fighting to get atheros 9285 working on a new laptop. I have to do another as well, so... After recovering myself from the shock of the new bsdinstall (not bad. A little confusing after using sysinstall for so long), I installed the system with 1 (thats right One! Ah ha ha) partition - yet another shock to figure through. What I'm staggered about is I was using fdisk to setup journaling on the usr and var partitions. So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. And before I do- I looked up journaling on 9. I couldn't quite get to the bottom of whether it is or isn't available/standard, or how to determine its happening. I'm only interested because of unexpected shutdowns/battery dead on the laptop- I also have 500G which is a while to wait for fsck. Speed I'd like, but I have to consider system integrity first. Little light, please? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On Sat, Dec 10, 2011 at 07:51:50PM +1000, R Skinner wrote: I bit the bullet and installed the rc3, after spending half the day fighting to get atheros 9285 working on a new laptop. I have to do another as well, so... After recovering myself from the shock of the new bsdinstall (not bad. A little confusing after using sysinstall for so long), I installed the system with 1 (thats right One! Ah ha ha) partition - yet another shock to figure through. What I'm staggered about is I was using fdisk to setup journaling on the usr and var partitions. So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. And before I do- I looked up journaling on 9. I couldn't quite get to the bottom of whether it is or isn't available/standard, or how to determine its happening. I'm only interested because of unexpected shutdowns/battery dead on the laptop- I also have 500G which is a while to wait for fsck. Speed I'd like, but I have to consider system integrity first. Little light, please? Cheers I'm unfamiliar with the new bsdinstaller but AFAIK it sets up a UFS2 filesystem for you. This comes with background fsck and softupdates which achieve the objective of not having to wait for a lengthy foreground fsck if you don't shutdown your laptop cleanly. As for filesystem integrity, I've occasionally not shutdown properly and the system has subsequently come up quickly again with the background fsck doing it's stuff. I don't remember anybody posting to this list saying: Help! I didn't shutdown my machine properly and now my filesystem is toast. At the worst you may have to run a foreground fsck. You can set up a proper journal: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-gjournal.html but to be honest, I wouldn't bother in your position: it's just more stuff to go wrong for no appreciable gain to you. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgp5taXd3fBLr.pgp Description: PGP signature
Re: 9.0 install and journaling
On Sat, 10 Dec 2011 11:40:53 + Frank Shute wrote: On Sat, Dec 10, 2011 at 07:51:50PM +1000, R Skinner wrote: possibly could, but it escaped me as to how. And before I do- I looked up journaling on 9. I couldn't quite get to the bottom of whether it is or isn't available/standard, or how to determine its happening. I'm only interested because of unexpected shutdowns/battery dead on the laptop- I also have 500G which is a while to wait for fsck. Speed I'd like, but I have to consider system integrity first. I'm unfamiliar with the new bsdinstaller but AFAIK it sets up a UFS2 filesystem for you. This comes with background fsck and softupdates which achieve the objective of not having to wait for a lengthy foreground fsck if you don't shutdown your laptop cleanly. but to be honest, I wouldn't bother in your position: it's just more stuff to go wrong for no appreciable gain to you. 9.0 also supports soft-update journalling which eliminates the background fsck. If you don't know whether it's on or not you can run tunefs -p / If it's not on then tunefs can turn it on, but you will presumably need to reboot into single user mode. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 10.0-CURRENT/AMD64 (CLANG): lang/gcc46 fails to build
On 12/07/11 07:11, Steve Kargl wrote: On Wed, Dec 07, 2011 at 05:56:31AM +0100, O. Hartmann wrote: config.status: creating ada/Makefile config.status: creating auto-host.h config.status: executing default commands gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc46. *** Error code 1 Stop in /usr/ports/lang/gcc46. === make failed for lang/gcc46 === Aborting update See if setting DISABLE_MAKE_JOBSi helps. This doesn't work, either. In /etc/src.conf, I use WITH_ICONV=YES and _WITH_BSD_GREP=YES. Switching off WITH_ICONV seems to solve the problem on FreeBSD 10.0-CURRENT/amd64. I do not know whether OS versions below 10.0 do support the WITH_ICONV knob. This maybe is a hint to the problem. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: 9.0 install and journaling
On 12/10/11 22:20, RW wrote: On Sat, 10 Dec 2011 11:40:53 + Frank Shute wrote: On Sat, Dec 10, 2011 at 07:51:50PM +1000, R Skinner wrote: possibly could, but it escaped me as to how. And before I do- I looked up journaling on 9. I couldn't quite get to the bottom of whether it is or isn't available/standard, or how to determine its happening. I'm only interested because of unexpected shutdowns/battery dead on the laptop- I also have 500G which is a while to wait for fsck. Speed I'd like, but I have to consider system integrity first. I'm unfamiliar with the new bsdinstaller but AFAIK it sets up a UFS2 filesystem for you. This comes with background fsck and softupdates which achieve the objective of not having to wait for a lengthy foreground fsck if you don't shutdown your laptop cleanly. but to be honest, I wouldn't bother in your position: it's just more stuff to go wrong for no appreciable gain to you. 9.0 also supports soft-update journalling which eliminates the background fsck. If you don't know whether it's on or not you can run tunefs -p / If it's not on then tunefs can turn it on, but you will presumably need to reboot into single user mode. So how does soft-update journaling compare to gjournal? I'm using gjournal now and it runs a bit of a dog, but it is reliable (until another ufs filesystem turns up at boot) and necessary in my environment. Can I dump it for this new one? Its used on a laptop with heavy load on the disk, the power on the battery can run out too quick for batterymon to shut it down- plus kids that play silly monkeys with daddy's laptop... :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 10.12.2011 15:44, Da Rock wrote: So how does soft-update journaling compare to gjournal? I'm using gjournal now and it runs a bit of a dog, but it is reliable (until another ufs filesystem turns up at boot) and necessary in my environment. Can I dump it for this new one? Its used on a laptop with heavy load on the disk, the power on the battery can run out too quick for batterymon to shut it down- plus kids that play silly monkeys with daddy's laptop... :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I am not an expert, but this is how I currently understand this: Geom-journal is a block level journaling mechanism. It means that all data written on a journaled provider will be first written to the providers journal and then later commited to the provider. Thus data is written twice to provide more redundancy. Soft-updates by itself has nothing to do with any journaling. It simply makes synchronous writes faster. When a filesystem is mounted synchronously, each write to a file first updates the metadata of the file, such a file size, and after that writes the actual data into the disk. When doing operations on thousands of small files, the overhead from synchronous writing is considerable. Bring forth soft-updates, which caches the metadata (file size etc.) updates into ram, and commits these updates into disk later when a delay and some conditions trigger; actual data is written into disk as soon as possible. Thus append/random access operations on gazillion of files are a lot faster. From this I would conclude that soft-updates journaling tries to write the metadata updates into a filesystem spesific soft-update journal (the soft-update journal being a file maybe?) sooner than they are actually committed. I also suspect that soft-updates journaling has some clever way of detecting when it is, performance wise, okay to update the journal and/or commit updates. In short: - gjournal writes both data and metadata, providing more redundancy to the actual data AND filesystem integrity while slowing down write operations (although I do not have data how much it slows down disk i/o) - journaled soft-updates writes metadata updates twice on the disk, providing redundancy to file system integrity, but does not prevent actual data loss. I do not even use FreeBSD 9.0 myself, my information is totally third party, second hand, wise-cracks and guessing. Any expert consultation would be appreciated. -- Arto Pekkanen ksym@IRCnet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 10/12/2011 5:19 μμ, Warren Block wrote: On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. As Warren says, you can still create /usr and /var and all the other legacy partitions if you so wish - and you may even use the full journaling (gjournal) on them. But the default for bsdinstall is to use gpart, install everything on a big / and create UFS2 partitions with the new soft-updates journaling system (on by default). Compared to gjournal, soft-updates journaling only journals metadata and not everything like gjournal does. This will definitely make it faster although probably less safe than gjournal. It should be good for most purposes though and needs no additional steps after install (unlike gjournal). Since it's the default, the decision to go for one big / seems ok after all. I believe this is more or less what Linux is doing with Ext3/Ext4 filesystems (metadata journaling). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 12/11/11 02:09, Manolis Kiagias wrote: On 10/12/2011 5:19 μμ, Warren Block wrote: On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. As Warren says, you can still create /usr and /var and all the other legacy partitions if you so wish - and you may even use the full journaling (gjournal) on them. But the default for bsdinstall is to use gpart, install everything on a big / and create UFS2 partitions with the new soft-updates journaling system (on by default). Compared to gjournal, soft-updates journaling only journals metadata and not everything like gjournal does. This will definitely make it faster although probably less safe than gjournal. It should be good for most purposes though and needs no additional steps after install (unlike gjournal). Since it's the default, the decision to go for one big / seems ok after all. I believe this is more or less what Linux is doing with Ext3/Ext4 filesystems (metadata journaling). GPT is cool - no problems there. The main thing I want to know is if I need to run fsck every time the system dies unexpectedly (which is a higher occurrence on a laptop)? GJournal helps in that it takes care of that. The growing size of drives is another concern given the time it takes to check a 500G disk (my smallest atm), although this is way down on the list for the moment. As for one big / partition- linux may be using it: and its their biggest failing! I've had a system lockup due to lack of space. Never a problem with bsd as logs will only fill up var, a user won't break it with filling up usr, etc. And root always stays protected! Its saved my life a number of times... I can quickly fill TB's of data in no time, and if something goes bang the logs can be a silent killer too. My 2c's anyway... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 10/12/2011 11:41 μμ, Da Rock wrote: On 12/11/11 02:09, Manolis Kiagias wrote: On 10/12/2011 5:19 μμ, Warren Block wrote: On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. As Warren says, you can still create /usr and /var and all the other legacy partitions if you so wish - and you may even use the full journaling (gjournal) on them. But the default for bsdinstall is to use gpart, install everything on a big / and create UFS2 partitions with the new soft-updates journaling system (on by default). Compared to gjournal, soft-updates journaling only journals metadata and not everything like gjournal does. This will definitely make it faster although probably less safe than gjournal. It should be good for most purposes though and needs no additional steps after install (unlike gjournal). Since it's the default, the decision to go for one big / seems ok after all. I believe this is more or less what Linux is doing with Ext3/Ext4 filesystems (metadata journaling). GPT is cool - no problems there. The main thing I want to know is if I need to run fsck every time the system dies unexpectedly (which is a higher occurrence on a laptop)? GJournal helps in that it takes care of that. The growing size of drives is another concern given the time it takes to check a 500G disk (my smallest atm), although this is way down on the list for the moment. It does the fsck automatically and it seems to be fast. As with other metadata journaled filesystems you will probably have to do a full check occasionally. Can't you give you any times atm, I need to dump /repartition/restore some of my systems to use su+j. Only tested on virtual machines. As for one big / partition- linux may be using it: and its their biggest failing! I've had a system lockup due to lack of space. Never a problem with bsd as logs will only fill up var, a user won't break it with filling up usr, etc. And root always stays protected! Its saved my life a number of times... I can quickly fill TB's of data in no time, and if something goes bang the logs can be a silent killer too. My 2c's anyway... I am used to the separate partitions too, although I realize a single big / would be suitable for more than a few systems. It's nice we have a choice here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 12/11/11 08:02, Manolis Kiagias wrote: On 10/12/2011 11:41 μμ, Da Rock wrote: On 12/11/11 02:09, Manolis Kiagias wrote: On 10/12/2011 5:19 μμ, Warren Block wrote: On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. As Warren says, you can still create /usr and /var and all the other legacy partitions if you so wish - and you may even use the full journaling (gjournal) on them. But the default for bsdinstall is to use gpart, install everything on a big / and create UFS2 partitions with the new soft-updates journaling system (on by default). Compared to gjournal, soft-updates journaling only journals metadata and not everything like gjournal does. This will definitely make it faster although probably less safe than gjournal. It should be good for most purposes though and needs no additional steps after install (unlike gjournal). Since it's the default, the decision to go for one big / seems ok after all. I believe this is more or less what Linux is doing with Ext3/Ext4 filesystems (metadata journaling). GPT is cool - no problems there. The main thing I want to know is if I need to run fsck every time the system dies unexpectedly (which is a higher occurrence on a laptop)? GJournal helps in that it takes care of that. The growing size of drives is another concern given the time it takes to check a 500G disk (my smallest atm), although this is way down on the list for the moment. It does the fsck automatically and it seems to be fast. As with other metadata journaled filesystems you will probably have to do a full check occasionally. Can't you give you any times atm, I need to dump /repartition/restore some of my systems to use su+j. Only tested on virtual machines. I'll have to try it out then; give it a chance. As for one big / partition- linux may be using it: and its their biggest failing! I've had a system lockup due to lack of space. Never a problem with bsd as logs will only fill up var, a user won't break it with filling up usr, etc. And root always stays protected! Its saved my life a number of times... I can quickly fill TB's of data in no time, and if something goes bang the logs can be a silent killer too. My 2c's anyway... I am used to the separate partitions too, although I realize a single big / would be suitable for more than a few systems. It's nice we have a choice here. True. But as a new user it was the separate partitions that attracted me, having been burned with linux's megaroot. And a new user would have trouble setting up the partitions. Not to mention the break with tradition (what is happening to this world)! :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On Sun, 11 Dec 2011, Da Rock wrote: GPT is cool - no problems there. The main thing I want to know is if I need to run fsck every time the system dies unexpectedly (which is a higher occurrence on a laptop)? GJournal helps in that it takes care of that. The growing size of drives is another concern given the time it takes to check a 500G disk (my smallest atm), although this is way down on the list for the moment. SUJ speeds up the check a lot, seconds as opposed to minutes. If something happens to the journal, it falls back to a standard fsck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 12/11/11 08:14, Warren Block wrote: On Sun, 11 Dec 2011, Da Rock wrote: GPT is cool - no problems there. The main thing I want to know is if I need to run fsck every time the system dies unexpectedly (which is a higher occurrence on a laptop)? GJournal helps in that it takes care of that. The growing size of drives is another concern given the time it takes to check a 500G disk (my smallest atm), although this is way down on the list for the moment. SUJ speeds up the check a lot, seconds as opposed to minutes. If something happens to the journal, it falls back to a standard fsck. But fsck needs to be run manually- I have users that can't do that, and the filesystem corrupts. Ergo gjournal; it boots up and fixes on the fly. So SU+J needs a manual fsck before booting proper or can it just boot and be done? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: 9.0 install and journaling
True. But as a new user it was the separate partitions that attracted me, having been burned with linux's megaroot. And a new user would have trouble setting up the partitions. Not to mention the break with tradition (what is happening to this world)! :) I prefer having separate partitions because it's more in line with traditional unix systems, and in particular, I don't like letting users have unlimited access to /tmp. /tmp isn't a place for people to dump their downloads, large file copies, etc. They should do that in their home directories. Having one big partition only allows people to abuse /tmp, among other things. _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On Sun, 11 Dec 2011 08:17:41 +1000 Da Rock wrote: SUJ speeds up the check a lot, seconds as opposed to minutes. If something happens to the journal, it falls back to a standard fsck. But fsck needs to be run manually- I have users that can't do that, and the filesystem corrupts. Ergo gjournal; it boots up and fixes on the fly. So SU+J needs a manual fsck before booting proper or can it just boot and be done? It's not very different; gjournal and SU both attempt to leave the filesystem in an coherent state, but both still need a preen to recover lost space. In either case the preen can fail requiring a full fsck. Journalled SU make SU behave more like gjournal in that you can do a fast foreground check which avoids the lengthy background fsck and avoids deferring the handling of unexpected inconsistencies to the next boot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 10.0-CURRENT/AMD64 (CLANG): lang/gcc46 fails to build
[-questions to bcc] On Sat, 10 Dec 2011, O. Hartmann wrote: On 12/07/11 07:11, Steve Kargl wrote: On Wed, Dec 07, 2011 at 05:56:31AM +0100, O. Hartmann wrote: config.status: creating ada/Makefile config.status: creating auto-host.h config.status: executing default commands gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc46. *** Error code 1 Stop in /usr/ports/lang/gcc46. === make failed for lang/gcc46 === Aborting update See if setting DISABLE_MAKE_JOBSi helps. This doesn't work, either. The end of the build log from that case should be more enlightening than the one you originally posted, as it is more likely to actually contain the actual error (which is not present in the snippet above). In /etc/src.conf, I use WITH_ICONV=YES and _WITH_BSD_GREP=YES. Switching off WITH_ICONV seems to solve the problem on FreeBSD 10.0-CURRENT/amd64. I do not know whether OS versions below 10.0 do support the WITH_ICONV knob. This maybe is a hint to the problem. iconv was only added to base in r219019 | gabor | 2011-02-24 19:04:39 -0500 (Thu, 24 Feb 2011) so it will first appear in the imminent 9.0 release. Assuming that the error remains reproducible with an up-to-date tree, the end of the build log from the DISABLE_MAKE_JOBS case would be useful to see. I've added gabor as a cc, since he seems to be doing most of the iconv work. -Ben Kaduk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Printer issue on FreeBSD
Aloha Gurus... I had a a print server power supply burn out and took the HD and motherboard board with it. The box I replaced it with took the install of Manolis 8.0 Release DVD ok for the base and I used portsnap to bring apfilter on board. Thats all there is on it. /etc hosts lists all boxes that were served by the old box (see below) and I am using the same server IP 192.168.1.50. /etc/ hosts.lpd host.hdk5.net 192.168.1.50 host2.intra.net 192.168.1.23 host3.intra .net 192.168.1.35 wireless_host. 192.168.1.2 (linux laptop not on printer but on the lan) The FreeBSD worked fine on the box that burned up. Printer is HP laserjet1100 Settings in /etc/printcap (on the server) lp|ljet4q|ljet4d... :lp/dev/lpt0:\ :if=/usr/local/etc/apsfilter/basedir/bin/apsfilter:\ :sd=/var/spool/lpd/ljet4q:\ :lf=/var/spool/lpd/ljet4q/log:/ :af=/var/spool/lpd/let4q/acct:\ :mx=:#0\ :sh: This all prints ok test from the server using command line lpr -P ljet4q /etc/rc.conf This does not work from any other hosts on the lan as it used to on the old server. (not working from xorg or text from command line on the hosts on the line to be clear.) I can ping from box to box and can use ftp to print from the server by sending a text file to it from the other hosts on the lan. Any help appreciated. Thanks. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0 install and journaling
On 12/11/11 10:23, RW wrote: On Sun, 11 Dec 2011 08:17:41 +1000 Da Rock wrote: SUJ speeds up the check a lot, seconds as opposed to minutes. If something happens to the journal, it falls back to a standard fsck. But fsck needs to be run manually- I have users that can't do that, and the filesystem corrupts. Ergo gjournal; it boots up and fixes on the fly. So SU+J needs a manual fsck before booting proper or can it just boot and be done? It's not very different; gjournal and SU both attempt to leave the filesystem in an coherent state, but both still need a preen to recover lost space. In either case the preen can fail requiring a full fsck. Journalled SU make SU behave more like gjournal in that you can do a fast foreground check which avoids the lengthy background fsck and avoids deferring the handling of unexpected inconsistencies to the next boot. Yes, but I don't do a fsck to recover gjournal- it has a miniscule blurp for a nanosecond and prints a message at boot and thats it. Is it the same with su+j? If it does then I'll drop gjournal (and the performance hit) and I'll use su+j when I jump to 9.0. I've never done fsck on a gjournal (yet). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Installation difficulties
Hello; I am not new to FreeBSD, but it has been a while since I worked with it. The last version I obtained from FreeBSD Mall is 7.2. The jewel case is marked with a date of May 2009, so it is a little behind. But I expected it to boot the i386 version installer, which it did on an Intel 64 bit processor. The 64 bit version is marked 'AMD64'. I would have gotten a laptop with AMD but this particular seller (Linux Certified) did not have one available when I was ready to buy. So now I am at it because the warrantee on the laptop has expired. So, I installed x-developer and attempted to install Apache from the included ports. None of the listed version would install: error code -1. I also tried MySQL. The first time it also failed to install. But did sysinstall and tried a different version than originally selected, and it did install. Since I wanted the GUI, I ran xinit when I got a shell prompt and xwindows failed to load and run, the error is failed to load module fbdev (module does not exist). Perhaps this is not an issue that can be addressed practically, here, which is alright with me. But short of getting another DVD and trying to install from that is there a way to deal, at least with the fbdev complaint? My experience with FreeBSD goes back to 6.0, setting up and running servers, specifically web servers. This is going to be a development server, as it had been when it had Ubuntu Linux. Thank you for time and attention; JK ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
