Re: Best procedure for full backup of live system
Thanks again guys. My final series of steps to take full backups: bsdlabel ad4s1| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/bsdlabel_ad4s1 dmesg -a | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dmesg dd if=/dev/ad4 bs=512 count=1 | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/MBR cat /etc/fstab| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/fstab dump -0Lan -f - / | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-root.gz dump -0Lan -f - /tmp | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-tmp.gz dump -0Lan -f - /var | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-var.gz dump -0Lan -f - /usr | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-usr.gz ... where port 2 on localhost is a pipe to my remote desktop with the 500 GB harddrive. If I missed anything important please let me know. ___ 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: Security blocking question
Aflatoon Aflatooni wrote: Is there a way that I could configure the server so that if there are for example X attempts from an IP address then for the next Y hours all the SSH requests would be ignored from that IP address? There are only a handful of people who have access to that server. Yes. In pf.conf: table persist [...] block drop in log quick on $ext_if from [...] pass in on $ext_if proto tcp \ from any to $ext_if port ssh \ flags S/SA keep state\ (max-src-conn-rate 3/30, overload flush global) plus you'll need to add a cron job to clear old entries out of the ssh-bruteforce table after a suitable amount of time has passed. Use expiretable to do that. Note: in practice I've found that it's a *really good idea* to implement a SSH whitelist of addresses that will never be bruteforce blocked like this -- it's very easy to lock yourself out even if everything you're doing is entirely legitimate. Coding that is left as an exercise for the reader. What is the best way of testing the PF rule? Is there a quick way to mimic a brute force? Is there a way that I could review the content of the table through pfctl -s all To test, you need access to a machine not in your whitelist from where you can try ssh'ing into the protected machine several times in rapid sequence. 3 times in 30s sounds quite fast, but it is actually not to hard to achieve accidentally, especially if you use tools like rsync over SSH transport. You should have a login concurrently from some other IP or on the console, otherwise you will lock yourself out. To see what IPs have been added to the ssh-bruteforce table and when and what traffic has been blocked: # pfctl -vv -t ssh-bruteforce -T show To manually delete an IP from the ssh-bruteforce table: # pfctl -t ssh-bruteforce -T delete 12.34.56.78 As noted elsewhere in this thread, instead of using expiretable, you can run this out of cron to expire addresses over a day old from the ssh-bruteforce blocklist: # pfctl -t ssh-bruteforce -T expire 86400 The pfctl(8) man page is pretty illuminating. Cheers, Matthew PS. Got to love the way that HTML-ising e-mail has deleted the table name from the examples above. I hope you could actually read it unmunged. Plain text rools! -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Best procedure for full backup of live system
Warren Block wrote: Lastly, it says save all boot messages. Do they mean the output of dmesg? Why is this useful? It would show what hardware was in the old machine and what services are running on startup. Backup in general is making copies of information you won't need as long as you have a backup of it. The system already creates a copy of the first part of the system boot output for you: /var/run/dmesg.boot -- this shows you what hardware the kernel discovered as it probed all of the buses and so forth. It doesn't contain the rest of the output from all of the /etc/rc.d/* and /usr/local/etc/rc.d/* startup scripts. The simple way to capture all that is to enable console.log in /etc/syslog.conf -- you want to uncomment this line: console.info/var/log/console.log and make sure that /var/log/console.log exists, then restart syslog. This will log all console output, including the boot-up output. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: phpMyAdmin install stopped in dependency 'libXau-1.0.4'
Kikachi Kozumi wrote: Hi, I tried installing phpMyAdmin in an ezjail created jail already installed with apache22, mysql and php5 running FreeBSD 7.1-RELEASE i386 with no X11 (headless). The port install failed when dependency 'libXau-1.0.4' configure couldn't find gnome-config: ... checking for XAU... gnome-config: not found configure: error: Package requirements (xproto) were not met. ... I'm not sure if this issue is specific to my system or is it a ports issue but I found that libXau-1.0.4 was in the ports tree since January 2009 so it's less likely to be an issue with the port itself. Right now I'm not sure if the required gnome-config is lost from my system or was never there in the 1st place. What can I do to continue with phpMyAdmin installation? I'm also curious why the phpMyAdmin port requires libX11 libraries to build while the phpMyAdmin website states that php, mysql and apache are the requirements for running phpMyAdmin? phpMyAdmin only depends on X through one of the optional extensions: php5-gd. If you disable the GD and PDF options in the configuration dialogue you'll not need to install any X related dependencies. Or you can rebuild graphics/gd using 'WITHOUT_X11=yes' if you want to be able to generate PDF of database schemas etc through phpMyAdmin. Hmmm... as far as I can tell, gnome-config is not a run-time dependency of phpMyAdmin even when compiled with all options enabled and with X11 support in the gd libraries. Either gnome-config is a build dependency from somewhere way down the dependency tree (ie. only needed to build something, not needed to run it) or you've got a misplaced 'USE_GNOME' somewhere. In general, USE_FOO is for port maintainers only and shouldn't appear in /etc/make.conf or any other Makefile that gets generally included everywhere. Use WITH/WITHOUT_FOO in /etc/make.conf to indicate global preferences. (Gentoo we ain't) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
RE: Unknown devices
Fogot to ask. When I login as a root I see invitation sign %, not #. What it means? Arkady Tokaev From: tok...@hotmail.com To: free...@edvax.de CC: freebsd-questions@freebsd.org Subject: RE: Unknown devices Date: Thu, 15 Oct 2009 16:15:58 +0400 Grate thanks!I had installed from 3 CD FreeBSD 7.2 with default (I hope) options.I don't understand - why it occurs, but now I understand - where to look.I think - I will reinstall the system, but if You have idea about this trouble - say me.Unfortunately I can not ask your last question because I very novice in FreeBSD. I just followed the instruction for FreeBSD router. Once more thanks, Arkady Tokaev Date: Thu, 15 Oct 2009 00:38:03 +0200 From: free...@edvax.de To: tok...@hotmail.com CC: freebsd-questions@freebsd.org Subject: Re: Unknown devices On Wed, 14 Oct 2009 23:04:51 +0400, Arkady Tokaev tok...@hotmail.com wrote: While I was trying to update ports I have received message about absence disk space.It's impossible, I thought.But df command said: $ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 23G3.5G 18G16%/ devfs 1.0K1.0K 0B 100%/dev /dev/md0 9.4M2.8M6.5M30%/etc /dev/md131M 16M 13M55%/usr/local/etc /dev/md219M 18K 19M 0%/root /dev/md331M6.1M 24M20%/var $ What is the md devices?How I can remove them? See man md: The md devices refer to memory disks, RAM that emulates a hard disk. Sadly, I don't recognize a reason why your /etc, /usr/local/etc, /root and /var subtrees are mounted onto memory disks... seems that you're not running a default install, do you? Regarding your initial problem - updating ports - this involves writing operations in the ports directory (usually /usr/ports which may be a subtree of /dev/ad0s1a on / in your setting) as well as in /var, especially /var/db/pkg, the installed packages database, and /var/ports. When /var is a memory disk with 30 MB, it may be too small for such a process. Furthermore, if I see this correctly, you're loosing the content of the package database on reboot; is this intended? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... _ Не хотите, чтобы кто-то знал, что вы делали в Интернете вчера? Вам нужен Internet Explorer 8. http://www.microsoft.ru/ie8___ 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: torrentflux
2009/10/15 Dánielisz László laszlo_daniel...@yahoo.com I found out that there is an httpd.conf problem, I fixed that but now I'm thinking how to put php module in apache without reinstalling apache. From: Polytropon free...@edvax.de To: Dánielisz László laszlo_daniel...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Thu, October 15, 2009 8:22:04 PM Subject: Re: torrentflux On Thu, 15 Oct 2009 10:19:55 -0700 (PDT), Dánielisz László laszlo_daniel...@yahoo.com wrote: Hello, Ok, I know it sounds numb, but how can I actually start torrentflux on my freebsd machine? I haven't used this torrent client so far (ctorrent is my choice at the moment), but according to # pkg_info |grep torrent torrentflux-2.0.b1 A PHP based BitTorrent client that runs on a web server it seems that you have to run a web server (I think locally), e. g. Apache, and then connect to this server in order to perform the actions with your client, such as entering http://127.0.0.1 in your web browser - this assumes that the web server is running and the PHP script is properly installed. It's possible that you need to connect to a specific port (e. g. :631 after the local IP). but I can not find how to start it and torrentflux forum is down, do you have any idea? Doesn't torrentflux come with some documentation? Have a look for it in /usr/local/share/doc where it should be. The packagin list in the port's directory mentions install.txt, maybe this file contains the information needed? Finally, does torrentflux.com (the homepage of the project) have some information? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 ___ 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 cd /usr/port/www/mod_php5 ; make install ___ 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: CMS
I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Due using Postgres, I've had experience on both Drupal and Serendipity, both installed mostly from ports and seem to be updated pretty regularly - although Serendipity can self repair - i.e. load updates for plugins and itself automatically. Both have functioned well enough, although with Drupal if you need more exotic array of plugins, they have to be installed manually as ports seem to miss several. In addition, some of the Drupal plugins need a bit of tweaking (getting rid of mysqlisms) if used under Postgres, although the main application works good enough. -Reko ___ 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: CMS
Hi If I were you I use Plone CMS on FreeBSD. Its one among the good CMSs available and doesn't require to configure a DataBase separately. Zope server has its DB named as ZODB, you can use with any database with APIs and Security shows pretty good record. - dhanesh From: reko.tu...@liukuma.net To: pschmehl_li...@tx.rr.com; freebsd-questions@freebsd.org Date: Fri, 16 Oct 2009 12:13:12 +0300 CC: Subject: Re: CMS I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Due using Postgres, I've had experience on both Drupal and Serendipity, both installed mostly from ports and seem to be updated pretty regularly - although Serendipity can self repair - i.e. load updates for plugins and itself automatically. Both have functioned well enough, although with Drupal if you need more exotic array of plugins, they have to be installed manually as ports seem to miss several. In addition, some of the Drupal plugins need a bit of tweaking (getting rid of mysqlisms) if used under Postgres, although the main application works good enough. -Reko ___ 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 _ Great events make grand headlines – read them all on MSN India http://in.msn.com___ 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
All in one printer?
Hello, I'm looking for an all in one printer (scanner + printer). Do you know some models well supported by our favorit OS (8.0) (and a cheep one of course)? Thanks, regards. ___ 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: All in one printer?
On Fri, Oct 16, 2009 at 6:45 AM, Patrick Lamaiziere patf...@davenulle.org wrote: Hello, I'm looking for an all in one printer (scanner + printer). Do you know some models well supported by our favorit OS (8.0) (and a cheep one of course)? Brother has a few MFC7820N works for me (not network scanning) Sam Fourman Jr. Fourman Networks ___ 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: All in one printer?
Patrick Lamaiziere wrote: Hello, I'm looking for an all in one printer (scanner + printer). Do you know some models well supported by our favorit OS (8.0) (and a cheep one of course)? I've had 2 HP cheap printer/scanners that have both worked well using the hplip port with cups and sane. Off hand I cant remember model numbers but http://hplipopensource.com/hplip-web/supported_devices/index.html should list most if not all the ones it supports. Vince Thanks, regards. ___ 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 ___ 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: All in one printer?
HP printers are quite good indeed, and they've got cheap stuff. They provide softs drivers for linux/unix users. Setup is easy. What else? Samuel Martín Moro CamTrace {EPITECH.} tek4 On Fri, Oct 16, 2009 at 1:55 PM, Vincent Hoffman vi...@unsane.co.uk wrote: Patrick Lamaiziere wrote: Hello, I'm looking for an all in one printer (scanner + printer). Do you know some models well supported by our favorit OS (8.0) (and a cheep one of course)? I've had 2 HP cheap printer/scanners that have both worked well using the hplip port with cups and sane. Off hand I cant remember model numbers but http://hplipopensource.com/hplip-web/supported_devices/index.html should list most if not all the ones it supports. Vince Thanks, regards. ___ 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 ___ 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 ___ 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
export PATH in script called via Cron.
I have a script that I call via Cron. It wont work unless I include a path: #!/usr/local/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin export $PATH which is fine and works. Out of curiosity though, why is it that if I call it from the cl like ./test.sh I get this error: ./test.sh: line 3: export: `/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin': not a valid identifier The script still works but it does drop that error. What does it mean? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CMS
On Oct 15, 2009, at 10:38 PM, Paul Schmehl wrote: I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Pros? Cons? Any known security issues? Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying Paul, I've used both Wordpress and Drupal. Both are good and both are bad. Because both are PHP based, they are not dependent on the port maintainer, if you are comfortable with keeping things up to date yourself. Both have made huge strides in the last few months to improve their systems to require less work on the command line in regards to updating. I recommend that you test drive both systems and determine what you are comfortable with. Most canned themes are available in both systems. Regards, Mikel King CEO, Olivent Technologies Senior Editor, BSD News Network Columnist, BSD Magazine 6 Alpine Court, Medford, NY 11763 o: 631.627.3055 skype:mikel.king http://olivent.com http://bsdnews.net http://mikelking.com http://twitter.com/mikelking ___ 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: export PATH in script called via Cron.
2009/10/16 Paul Halliday paul.halli...@gmail.com I have a script that I call via Cron. It wont work unless I include a path: #!/usr/local/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin export $PATH which is fine and works. Out of curiosity though, why is it that if I call it from the cl like ./test.sh I get this error: ./test.sh: line 3: export: `/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin': not a valid identifier The script still works but it does drop that error. What does it mean? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org drop the $ in front of path in the export line ___ 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
print the PKGNAME of a port
Hello, For the ports in /usr/ports is there a way to print the resulting PKGNAME of a given port, like: # cd /usr/ports/x11/kde3 # make name kde-3.5.10_2 # for this test above I just added the following lines at the end of the Makefile after the include line: .include bsd.port.mk name: @echo ${PKGNAME} I have had a look into bsd.port.mk but could not see anythink like the silly output (without making the port). Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ 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: Best procedure for full backup of live system
On Fri, 16 Oct 2009, Nerius Landys wrote: Thanks again guys. My final series of steps to take full backups: bsdlabel ad4s1| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/bsdlabel_ad4s1 dmesg -a | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dmesg dd if=/dev/ad4 bs=512 count=1 | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/MBR cat /etc/fstab| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/fstab dump -0Lan -f - / | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-root.gz dump -0Lan -f - /tmp | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-tmp.gz dump -0Lan -f - /var | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-var.gz dump -0Lan -f - /usr | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-usr.gz ... where port 2 on localhost is a pipe to my remote desktop with the 500 GB harddrive. If I missed anything important please let me know. The dump man page recommends always using -C with snapshot dumps. The Handbook has an example of dump over ssh that shows a couple of speed optimizations: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/backup-basics.html#AEN25817 gzip -2 and bluefish instead of 3des should be faster than the default. -Warren Block * Rapid City, South Dakota USA___ 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: print the PKGNAME of a port
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 16 Oct 2009, Matthias Apitz wrote: Hello, For the ports in /usr/ports is there a way to print the resulting PKGNAME of a given port, like: # cd /usr/ports/x11/kde3 # make name kde-3.5.10_2 # Try the following: # cd /usr/ports/x11/kde3 # make -V PKGNAME kde-3.5.10_2 # also read the manpage of make(1) for detailed information of the -V option. Kind regards Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQFK2IR8SPOsGF+KA+MRAtgRAJ9roqjLIe0tRKOwf13CEd0xUtihBACgtqIr tvWxZBTXUE7mE73k/fCv/rU= =hARq -END PGP SIGNATURE- ___ 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: Best procedure for full backup of live system
On Fri, Oct 16, 2009 at 12:12:56AM -0700, Nerius Landys wrote: You can do all this though it might be more than needed. Only the level 0 dumps are needed. Thanks again guys. My final series of steps to take full backups: bsdlabel ad4s1| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/bsdlabel_ad4s1 dmesg -a | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dmesg dd if=/dev/ad4 bs=512 count=1 | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/MBR cat /etc/fstab| ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/fstab dump -0Lan -f - / | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-root.gz dump -0Lan -f - /tmp | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-tmp.gz dump -0Lan -f - /var | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-var.gz dump -0Lan -f - /usr | gzip | ssh -p 2 nlan...@localhost dd of=/home/nlandys/backup/dump0-usr.gz ... where port 2 on localhost is a pipe to my remote desktop with the 500 GB harddrive. If I missed anything important please let me know. Are you clear about what you have to run on the other machine to receive the data and put it where you want? jerry ___ 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
A new FreeBSD Project
Hello the FreeBSD team, I am attempting to start a new project/private business of which I am wiling to give a share in return for skills (mainly as I currently have nothing else to offer). At the core of the project will be a new FreeBSD distribution, therefore I need FreeBSD developers,kernel hackers, or anyone who can rip apart the OS and put it back together with part missing, and who are based in the UK. I believe this will be an exciting project, that at-least for the foreseeable future would be part time; in return for a proportion of the business. I would be extremely grateful if you could forward this to anyone who you think would benefit from this email, or anyone's contact details who you think could help my cause. Thank you, Ashley Diamond ___ 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: Best procedure for full backup of live system
On Thu, 15 Oct 2009 21:47:57 -0600 (MDT), Warren Block wbl...@wonkity.com wrote: Just a general note: backup to a hard drive isn't bad, but it's not the same as removable media. One failure can kill all of your backups... That's why it's often a good choice two have at least two hard disks (maybe external ones) for backup, so if one fails (which seems to be a problem of modern disks rather than older ones), there's still an intact backup on the other one (or on one of the others). Backup in general is making copies of information you won't need as long as you have a backup of it.a A wise summary. :-) dump(8) doesn't do all sectors, just ones used by the filesystem. Also, dump doesn't cross filesystems. In a typical FreeBSD install, /, /var, and /usr are separate filesystems. A dump of / won't get them all at once. The dump utility is good when you want to work partition-wise. If you have a setting where everything goes into a big /, dumping it will get all data - from that partition. Slices and MBR are out of dump's scope. My server should boot fine with the FreeBSD CDROM (fixit), because it uses a subset of the GENERIC kernel device drivers. If you can, try that before an actual emergency. Furthermore, it's good to check backups regularly. A defective backup is NO backup. If data doesn't restore as intended (e. g. to a testing system), then...? A situation that many of you surely have come across, as I have: Operator: The hard disk crashed, we need to restore from backups. Customer: Of course I have backups! Here! Customer hands over three tapes. Operator starts restore with tape #1. Operator: First tape is through. Good. Next one. Computer displays rroor reading /dev/nsa0: Tape is defect, cannot read. Operator: Do you have other set of tapes? This #2 is defective. Customer: Yes! Tape #3! Operator: I need a working tape #2. Customer: BUT I *HAVE* BACKUPS!!! Testing the backups may take some time, I agree, but it's mostly worth it - it's worth as much as your data is to you. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Unknown devices
On Fri, 16 Oct 2009 12:14:29 +0400, Arkady Tokaev tok...@hotmail.com wrote: Fogot to ask. When I login as a root I see invitation sign %, not #. What it means? The prompt character shows if you are logged in as root or not. Most shells use $ or % for non-root, and # for root. Which shell are you using? % echo $SHELL If you're using the C shell, make sure there's no overriding setting in your /root/.cshrc that as something like set prompt = % in it - this would override the default # sign. The most convenient form is to use those two lines in /etc/csh.cshrc in order to make them available globally: set promptchars = %# set prompt = %...@%m:%~%# The first line contains the prompting character for non-root users first, for root next. The second line forms a comfortable C shell prompt, containing the user and the hostname, the current working directory and the prompt character (automatically depending on root or non-root). It looks like this: u...@host:/the/current/path% _ or r...@mysystem:~# _ The user's home directory is shown as ~ so that the directory element won't be too long. Keep in mind that if /root/.cshrc exists and contains different settings, it will override the global defaults. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: All in one printer?
2009/10/16 Samuel Martín Moro faus...@gmail.com: HP printers are quite good indeed, and they've got cheap stuff. They provide softs drivers for linux/unix users. Setup is easy. What else? Samuel Martín Moro CamTrace {EPITECH.} tek4 Please don't top post, it makes the conversation difficult to follow. What about Epson printers? They're usually fine with Gutenprint CUPS, and my CX3650's scanner works fine. This is a change in 7.2 (I think) when suddenly they both started being detected, rather than only one (scanner or printer) being allowed to work at a time. Chris ___ 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: CMS
On 10/15/09, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Pros? Cons? Any known security issues? If it's your server and you're the guy, (or your friends) needing content management abilities... a simple SSH connection cannot be beat. But maybe that's not what you had in mind :p -Modulok- ___ 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
讓大腦快速動起來的方法只要 1600元 邀請您到 Plurk.com 註冊帳 號
我玩 Plurk 好一陣子了,希望你也來試試! 按這裡接受我的邀請: http://www.plurk.com/pbms1/invite/2 到這裡看看我的個人頁面: http://www.plurk.com/pbms1 Plurk.com - 您的“線上”人生 _ Opt Out of Plurk emails: This email was sent in connection with you Plurk.com membership. To stop receiving emails from Plurk, click this link: http://www.plurk.com/unsubscribe?bemail=cXVlc3Rpb25zQEZyZWVCU0Qub3Jnkey=726e3e49a5870b1221e960197b8d8eb0 You can contact us at http://www.plurk.com/contact Plurk.com, 2425 Matheson Blvd 8th Floor, Suite 813 Mississauga, Ontario L4W 5K4 Canada ___ 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: usb key problem
Message: 11 Date: Fri, 16 Oct 2009 01:32:46 +0200 From: Polytropon free...@edvax.de Subject: Re: usb key problem To: PJ af.gour...@videotron.ca Cc: freebsd-questions@freebsd.org Message-ID: 20091016013246.c0e022e5.free...@edvax.de Content-Type: text/plain; charset=US-ASCII On Thu, 15 Oct 2009 19:18:45 -0400, PJ af.gour...@videotron.ca wrote: Now that I have had a few moments to think about it, maybe I have to give good old cruze and enema and format it under XP ... maybe all it needs is a clean system on it. ;-) I'm not sure if USB sticks tend to degrade filesystem-wise, but when you put such a stick into random Windows PCs, it's quite possible that data gets messed up. The most ideal solution of course is to simply newfs the stick and give it a UFS file system, but sadly, Windows PC are resistent to standards, so they won't read it, but will force you to use old-fashioned MS-DOS-like file systems. :-) To be fair, Windows XP supports the NTFS filesystem that is very feature-rich. Although, I recall making a XP machine unbootable trying to format removable media with NTFS because only the installer woulds use that filesystem. The format utility let me choose between Fat16 and FAt32 or something :P A better tool, under both Windows (via Cygwin) and BSD, would be ntfsprogs. http://www.linux-ntfs.org/doku.php?id=ntfsmount Regards, James Phillips -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. ___ 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
GEOM label clarification
If I understand correctly from the manual, giving the labels their slice name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that regardless of the disk, the boot will be from the disk being booted and not from another disk as happened to me recently - the fstab on disk ad4 was referncing ad12 so the boot was from ad12 rather than ad4. The handbook says: By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even if the disk is moved to another controller or transferred to a different system. For this example, it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. If the disk is moved to another system, it may no longer be ad0... So will it still boot correctly? Or should the ufsid labels be used? Will both of these contortions work? ___ 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: GEOM label clarification
PJ wrote: If I understand correctly from the manual, giving the labels their slice name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that regardless of the disk, the boot will be from the disk being booted and not from another disk as happened to me recently - the fstab on disk ad4 was referncing ad12 so the boot was from ad12 rather than ad4. The handbook says: By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even if the disk is moved to another controller or transferred to a different system. For this example, it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. If the disk is moved to another system, it may no longer be ad0... So will it still boot correctly? In short, yes. I do this routinely all the time. Assuming of course that the device is connected to a controller that FreeBSD recognizes. This should be a non-issue for standard ATA/SATA disks. Or should the ufsid labels be used? The ufsid is also an option if you do not wish to create the labels yourself. The advantage of user-created labels is that they are not 'cryptic' like the ufsid ones and you may actually remember them :) Will both of these contortions work? Yes, both will do. ___ 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: All in one printer?
Le Fri, 16 Oct 2009 13:45:39 +0200, Patrick Lamaiziere patf...@davenulle.org a écrit : I'm looking for an all in one printer (scanner + printer). Thanks guys, so I bought today a HP PhotoSmart C4680 all in one. It mostly works fine (printing and scanning) out of the box. I ran into issues with the hplip tools (hp-setup, ...) because they use the user locale when connecting to cups (here ISO-8859-15). Cups rejects this. I have to set my locale to LC_ALL=C. It looks ok with this work-around. I'm able to use the hp-systray tool. Also I'm not able to start hpssd (hplip3) and it says nothing (no errors...)? ___ 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: CMS
--On Friday, October 16, 2009 11:27:12 -0500 Modulok modu...@gmail.com wrote: On 10/15/09, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Pros? Cons? Any known security issues? If it's your server and you're the guy, (or your friends) needing content management abilities... a simple SSH connection cannot be beat. But maybe that's not what you had in mind :p YeahI'm not the content guy. I'm the server admin. I'm also not the ower. The owner likes CMS products since he's now using one, and wants to install the one he uses on his server. But the one he uses is only for Windows. Thus the question. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson ___ 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: usb key problem
On Fri, 16 Oct 2009 11:05:01 -0700 (PDT), James Phillips anti_spam...@yahoo.ca wrote: To be fair, Windows XP supports the NTFS filesystem that is very feature-rich. And prone to file system corruption, as well as not very performant speed-wise (which doesn't count in regards of backups). :-) Although, I recall making a XP machine unbootable trying to format removable media with NTFS because only the installer woulds use that filesystem. The format utility let me choose between Fat16 and FAt32 or something :P What a bug... erm, feature! :-) A better tool, under both Windows (via Cygwin) and BSD, would be ntfsprogs. http://www.linux-ntfs.org/doku.php?id=ntfsmount Yes, FreeBSD let's you even mount NTFS volumes via smbfs, so you don't have to care for the file system used. This is because Windows does not support standard NFS out of the box. This way would be interesting if your machine that holds the backup files is a Windows PC. As far as I know, there's a fuse module (ntfs3g?) in the ports. But I have to admit that I've never tried it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Security blocking question
Aflatoon Aflatooni wrote: Is there a way that I could configure the server so that if there are for example X attempts from an IP address then for the next Y hours all the SSH requests would be ignored from that IP address? There are only a handful of people who have access to that server. Yes. In pf.conf: table persist [...] block drop in log quick on $ext_if from [...] pass in on $ext_if proto tcp \ from any to $ext_if port ssh \ flags S/SA keep state \ (max-src-conn-rate 3/30, overload flush global) plus you'll need to add a cron job to clear old entries out of the ssh-bruteforce table after a suitable amount of time has passed. Use expiretable to do that. Note: in practice I've found that it's a *really good idea* to implement a SSH whitelist of addresses that will never be bruteforce blocked like this -- it's very easy to lock yourself out even if everything you're doing is entirely legitimate. Coding that is left as an exercise for the reader. What is the best way of testing the PF rule? Is there a quick way to mimic a brute force? Is there a way that I could review the content of the table through pfctl -s all To test, you need access to a machine not in your whitelist from where you can try ssh'ing into the protected machine several times in rapid sequence. 3 times in 30s sounds quite fast, but it is actually not to hard to achieve accidentally, especially if you use tools like rsync over SSH transport. You should have a login concurrently from some other IP or on the console, otherwise you will lock yourself out. To see what IPs have been added to the ssh-bruteforce table and when and what traffic has been blocked: # pfctl -vv -t ssh-bruteforce -T show To manually delete an IP from the ssh-bruteforce table: # pfctl -t ssh-bruteforce -T delete 12.34.56.78 As noted elsewhere in this thread, instead of using expiretable, you can run this out of cron to expire addresses over a day old from the ssh-bruteforce blocklist: # pfctl -t ssh-bruteforce -T expire 86400 The pfctl(8) man page is pretty illuminating. Cheers, Matthew Thanks, I have the following in my pf.conf: ext_if=bge0 # Public Services -- smtp, http, pop3s tcpPubServices = { 25, 80, 995 } set timeout { interval 10, frag 30 } set timeout { tcp.first 120, tcp.opening 30, tcp.established 86400 } set timeout { tcp.closing 900, tcp.finwait 45, tcp.closed 90 } set limit { states 1, frags 5000 } #set loginterface none set optimization normal set block-policy drop #set require-order yes #set fingerprints /etc/pf.os set skip on lo0 # Normalization: reassemble fragments and resolve or reduce traffic ambiguities. scrub in all pass out all block in log all table sshBruteForce { } block in quick from sshBruteForce to any pass in on $ext_if inet proto tcp from any to any port $tcpPubServices flags S/SA synproxy state pass in on $ext_if inet proto tcp from any to any port ssh modulate state (source-track rule max-src-nodes 8 max-src-conn 8 max-src-conn-rate 3/60 overload sshBruteForce flush global) And I have tried to make a lot of ssh connections to the box and killing them with ctrl-c or bad-password but nothing gets added to the table. There isn't anything in the log either. How would I go about figuring out what is wrong? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: GEOM label clarification
Manolis Kiagias wrote: PJ wrote: If I understand correctly from the manual, giving the labels their slice name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that regardless of the disk, the boot will be from the disk being booted and not from another disk as happened to me recently - the fstab on disk ad4 was referncing ad12 so the boot was from ad12 rather than ad4. The handbook says: By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even if the disk is moved to another controller or transferred to a different system. For this example, it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. If the disk is moved to another system, it may no longer be ad0... So will it still boot correctly? In short, yes. I do this routinely all the time. Assuming of course that the device is connected to a controller that FreeBSD recognizes. This should be a non-issue for standard ATA/SATA disks. Or should the ufsid labels be used? The ufsid is also an option if you do not wish to create the labels yourself. The advantage of user-created labels is that they are not 'cryptic' like the ufsid ones and you may actually remember them :) Will both of these contortions work? Yes, both will do. Thanks for the reassurance. Now to start labelling. Uh.. I guess that means that if I label 1 disk and then clone it to several others, they wil all work from any system... Well, I guess I'll try it. Thanks again. ___ 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: CMS
Paul Schmehl wrote: --On Friday, October 16, 2009 11:27:12 -0500 Modulok modu...@gmail.com wrote: On 10/15/09, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Pros? Cons? Any known security issues? If it's your server and you're the guy, (or your friends) needing content management abilities... a simple SSH connection cannot be beat. But maybe that's not what you had in mind :p YeahI'm not the content guy. I'm the server admin. I'm also not the ower. The owner likes CMS products since he's now using one, and wants to install the one he uses on his server. But the one he uses is only for Windows. Thus the question. It is my opinion that they (CMSs) are nearly to the point it will take a quadcore CPU and 4GB or memory to serve a single html page containing the words Hello World. Code light, they are not. My experience with CMS such as Joomla, SurgarCRM, etc is that they are to crackers as a lone lightbulb in the forest is to bugs. - Keep them up to date. - Subscribe to, and be attentive to, their security mailings. - If you do not use a feature/module, remove it. - Do not under any circumstances install PhpMyAdmin. My logs show if a IP gets a hit on a CMS page, they immediately search for PhpMyAdmin next. If you must install it, install it on another machine or under a different domain. Then turn access on and off at the SQL server when needed. We have a few CMSs that I could not talk Sales out of, two have had problems. One was moved to it's on VPS because of issues. Best of luck. DAve -- Posterity, you will know how much it cost the present generation to preserve your freedom. I hope you will make good use of it. If you do not, I shall repent in heaven that ever I took half the pains to preserve it. John Quincy Adams http://appleseedinfo.org ___ 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: GEOM label clarification
PJ wrote: Manolis Kiagias wrote: PJ wrote: If I understand correctly from the manual, giving the labels their slice name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that regardless of the disk, the boot will be from the disk being booted and not from another disk as happened to me recently - the fstab on disk ad4 was referncing ad12 so the boot was from ad12 rather than ad4. The handbook says: By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even if the disk is moved to another controller or transferred to a different system. For this example, it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. If the disk is moved to another system, it may no longer be ad0... So will it still boot correctly? In short, yes. I do this routinely all the time. Assuming of course that the device is connected to a controller that FreeBSD recognizes. This should be a non-issue for standard ATA/SATA disks. Or should the ufsid labels be used? The ufsid is also an option if you do not wish to create the labels yourself. The advantage of user-created labels is that they are not 'cryptic' like the ufsid ones and you may actually remember them :) Will both of these contortions work? Yes, both will do. Thanks for the reassurance. Now to start labelling. Uh.. I guess that means that if I label 1 disk and then clone it to several others, they wil all work from any system... Well, I guess I'll try it. Thanks again. How are going to clone it? Will the clone also copy the labels? For example, if doing a dump / restore (which I often do) I recreate the partitions manually, newfs them, label them and then restore the contents. In many cases I use a live (Fixit) system for this. ___ 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: GEOM label clarification
Manolis Kiagias wrote: PJ wrote: Manolis Kiagias wrote: PJ wrote: If I understand correctly from the manual, giving the labels their slice name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that regardless of the disk, the boot will be from the disk being booted and not from another disk as happened to me recently - the fstab on disk ad4 was referncing ad12 so the boot was from ad12 rather than ad4. The handbook says: By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even if the disk is moved to another controller or transferred to a different system. For this example, it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. If the disk is moved to another system, it may no longer be ad0... So will it still boot correctly? In short, yes. I do this routinely all the time. Assuming of course that the device is connected to a controller that FreeBSD recognizes. This should be a non-issue for standard ATA/SATA disks. Or should the ufsid labels be used? The ufsid is also an option if you do not wish to create the labels yourself. The advantage of user-created labels is that they are not 'cryptic' like the ufsid ones and you may actually remember them :) Will both of these contortions work? Yes, both will do. Thanks for the reassurance. Now to start labelling. Uh.. I guess that means that if I label 1 disk and then clone it to several others, they wil all work from any system... Well, I guess I'll try it. Thanks again. How are going to clone it? Will the clone also copy the labels? For example, if doing a dump / restore (which I often do) I recreate the partitions manually, newfs them, label them and then restore the contents. In many cases I use a live (Fixit) system for this. I'm looking into that just now. I am playing with two disks... one is 80gb sata on USB... and the second is 250Gb sata on USB. I had tried to set them up with livefs but the 80Gb is all wrong... I usually set up 2Gb on /, 3Gb on swap, 2gb on /tmp, 2gb on /var and 50gb on /usr . But I just newfsd the partitions on the 80gb and found that the da0s1d was 50gb which doesn't make sense as I had set it for 2gb and d should have been /tmp, e = /var, f= usr and g=/home. That explains why I ran out of space when trying to restore to the disk. So now I'm going to try to redo the disk manually with fdisk, bsdlabel and newfs. We'll see... ___ 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: Security blocking question
Aflatoon Aflatooni wrote: I have the following in my pf.conf: ext_if=bge0 # Public Services -- smtp, http, pop3s tcpPubServices = { 25, 80, 995 } set timeout { interval 10, frag 30 } set timeout { tcp.first 120, tcp.opening 30, tcp.established 86400 } set timeout { tcp.closing 900, tcp.finwait 45, tcp.closed 90 } set limit { states 1, frags 5000 } #set loginterface none set optimization normal set block-policy drop #set require-order yes #set fingerprints /etc/pf.os set skip on lo0 # Normalization: reassemble fragments and resolve or reduce traffic ambiguities. scrub in all pass out all block in log all table sshBruteForce { } ^^^ this needs to be 'table sshBruteForce persist' or the OS will delete it if it's empty. block in quick from sshBruteForce to any pass in on $ext_if inet proto tcp from any to any port $tcpPubServices flags S/SA synproxy state pass in on $ext_if inet proto tcp from any to any port ssh modulate state (source-track rule max-src-nodes 8 max-src-conn 8 max-src-conn-rate 3/60 overload sshBruteForce flush global) And I have tried to make a lot of ssh connections to the box and killing them with ctrl-c or bad-password but nothing gets added to the table. There isn't anything in the log either. How would I go about figuring out what is wrong? Usually if you leave your machine connected to the internet, some awfully helpful people in China or some other far off place will test it for you within a day or so... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: All in one printer?
Le Fri, 16 Oct 2009 20:52:47 +0200, Patrick Lamaiziere patf...@davenulle.org a écrit : Thanks guys, so I bought today a HP PhotoSmart C4680 all in one. It mostly works fine (printing and scanning) out of the box. Hmmm, in fact no. There are some problems on printing (missing part). ___ 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
small question about tape-based dumps
Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? With regards Stevan Tiefert ___ 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: GEOM label clarification
NOW THIS SUCKS. SUM # glabel label rootfs/dev/ad12s1a glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted This is direct from the manual what the $#*(@)! is going on? No identical post on web, but similar say to ignore: it's harmless? I so, why is it there? There seem to be quite a lot of these kinds of stumbling blocks that are just plalin annoying... Is this an annoyance or what for the above situation? ___ 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: small question about tape-based dumps
On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry With regards Stevan Tiefert ___ 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 ___ 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: GEOM label clarification
PJ wrote: NOW THIS SUCKS. SUM # glabel label rootfs/dev/ad12s1a glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted This is direct from the manual what the $#*(@)! is going on? No identical post on web, but similar say to ignore: it's harmless? I so, why is it there? There seem to be quite a lot of these kinds of stumbling blocks that are just plalin annoying... Is this an annoyance or what for the above situation? Is this your normal '/' filesystem, and is it mounted? If it is reboot your system and select 'single user mode' from the loader.menu Then use glabel in the single user mode prompt. This will not work if you just 'shutdown now', you have to reboot into single user mode. If it is not your real '/' at the moment, and it is not mounted, you should be able to do it. Booting from the fixit LiveCD will also work in any case. ___ 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: small question about tape-based dumps
Am Freitag, den 16.10.2009, 17:37 -0400 schrieb Jerry McAllister: On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry With regards Stevan Tiefert ___ 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 ___ 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 Hello Jerry, The world can be so easy!!! Thanks for this hint :-) With regards Stevan Tiefert ___ 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: GEOM label clarification
Manolis Kiagias wrote: PJ wrote: NOW THIS SUCKS. SUM # glabel label rootfs/dev/ad12s1a glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted This is direct from the manual what the $#*(@)! is going on? No identical post on web, but similar say to ignore: it's harmless? I so, why is it there? There seem to be quite a lot of these kinds of stumbling blocks that are just plalin annoying... Is this an annoyance or what for the above situation? Is this your normal '/' filesystem, and is it mounted? If it is reboot your system and select 'single user mode' from the loader.menu Then use glabel in the single user mode prompt. This will not work if you just 'shutdown now', you have to reboot into single user mode. If it is not your real '/' at the moment, and it is not mounted, you should be able to do it. Booting from the fixit LiveCD will also work in any case. I appreciate your holding my hand as I will otherwise fall on my ass or off my donkey... whatever... I need a big stiff drink...it's been a heady week... I already tried, screwed up the fstab, fixed it and booted up just fine. Don't want to screw it up again. See my bithing in another post... you'll understand how reading the manuals and man pages can be depressing. Shit, shit, shit. ___ 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: usb key problem
Polytropon wrote: On Thu, 15 Oct 2009 20:06:08 -0400, PJ af.gour...@videotron.ca wrote: Anyway, I found the solution on the web... couldn't belive it was that simple: just ignore the crap spewed out on the screen and just mount iit as you would any other disk. # mount -t msdosfs /dev/da0s1 /mnt and that's it Additionally, when you use mount_msdosfs, you can specify masks (-m and -M) in order not to have +x attributes on all the files; the MS-DOS file system on the stick could give you unwanted results, for example if you have a .jpg file on the stick and want to open it (with the default app for .jpg file type), the system will try to execute it. Now to see how I can use it to restore stuff. :-D If you want to use the stick for FreeBSD operations, why not give it a real file system (i. e. UFS) instead of some old FAT? You can simply # newfs /dev/da0 and then access it in the standard way: # mount /dev/da0 /mnt See that file owner:group, permissions and flags are now supported, and files that are not supposed to be executables don't have +x attribute (as in opposite to FAT / msdosfs). You could even add an entry in /etc/fstab like this: /dev/da0s1 /media/stick msdosfs rw,noauto,noatime 0 0 or, for proper UFS: /dev/da0 /media/stick ufs rw,noauto,noatime 0 0 Keep in mind that when using device names, it's a matter of in which sequence device are detected that result in the corresponding device name (da0, da1 etc.); using labels is the more elegant way here. How do you mean, using labels; could you illustrate or clarify? for the above, I mean. I'm trying to set up labels for my normal systems with glabel and struggling... ___ 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 hate to bitch but bitch I must
Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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: I hate to bitch but bitch I must
PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Relax. You are having a bad day, and you are topping it by trying to perform some stuff while you are not in the right state of mind. If you do insist on continuing with this, do the following: Make a list of your partitions - I'll assume a device name of /dev/ad1 for the disk. You should have: ad1s1a for root = Label this as rootfs ad1s1b for swap = Label this as swap ad1s1e for tmp = Label this as tmpfs ad1s1d for var = Label this as varfs ad1s1f for usr = Label this as usrfs If you are unsure of the device names, try ls /dev/ad* (or ls /dev/da* if you are using SCSI disks, which I think you are not) Now, reboot: shutdown -r now Press 4 and enter single user mode in the loader. In the single user mode prompt type: glabel label rootfs /dev/ad1s1a glabel label swap /dev/ad1s1b glabel label tmpfs /dev/ad1s1e glabel label varfs /dev/ad1s1d glabel label usrfs /dev/ad1s1f You should get no error messages from these. Type exit and continue to multiuser boot. Change /etc/fstab: change /dev/ad1s1a to /dev/label/rootfs /dev/ad1s1b to /dev/label/swap and so on. Reboot once again. Everything should work. Do people who write this stuff ever read it? Tell me t Yes, we do. All the time actually. hat its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results!___ You will have best results when trying with a clear mind. Also having a test system (or a VMware / Virtualbox machine) will help you learn and practice unknown procedures without the anxiety of breaking something on your production system. ___ 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: I hate to bitch but bitch I must
2009/10/16 PJ af.gour...@videotron.ca Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE . what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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 think your in that zone before the penny drops. It happens to us all 8) Its quite simple if you are dealing with a new install add the label when you format the fs eg new -L somelabel somedev if the fs already exists unmount it (anoying I know) and then tunefs it eg tunefs -L somelabel somedev then in both cases mount it via the appropriate glabel dev in this case its ufs so the dev is /dev/ufs/somelabel I generally dont bother labeling devices like ads1 da0 etc as thete isnt much point I just stick the to the file systems. The exception is the swap partition eg glabel label -v swap /dev/da2p2 i then swapon the device /dev/label/swap note as there is not file system on this dev it takes the label subdir other fs like ntfs vfat take different subdirs ___ 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: GEOM label clarification
On Sat, 17 Oct 2009 00:43:37 +0300, Manolis Kiagias son...@otenet.gr wrote: Is this your normal '/' filesystem, and is it mounted? If it is reboot your system and select 'single user mode' from the loader.menu Then use glabel in the single user mode prompt. This will not work if you just 'shutdown now', you have to reboot into single user mode. Isn't it sufficient to unmount any partitions and keep / in -o ro mode, and then perform the glabel command, which is obviously best done in single user mode? # shutdown now # umount /home /usr /var /tmp # mount -r / # glabel label rootfs /dev/ad0s1a # glabel label tmp /dev/ad0s1d # glabel label var /dev/ad0s1e # glabel label usr /dev/ad0s1f # glabel label home /dev/ad0s1g For example like this? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: GEOM label clarification
Polytropon wrote: On Sat, 17 Oct 2009 00:43:37 +0300, Manolis Kiagias son...@otenet.gr wrote: Is this your normal '/' filesystem, and is it mounted? If it is reboot your system and select 'single user mode' from the loader.menu Then use glabel in the single user mode prompt. This will not work if you just 'shutdown now', you have to reboot into single user mode. Isn't it sufficient to unmount any partitions and keep / in -o ro mode, and then perform the glabel command, which is obviously best done in single user mode? I had variable results on a few systems and feel it is safest to perform a clean single user mode 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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. A common misunderstanding about manpages can be that they are often (wishfully?) seen as a tutorial or a howto. In fact, they are references. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? That's confusing... man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? No. Active file system refers to a file system that is mounted rw - the common method of using a file system. But in order to run a program from a file system, the file system can as well be mounted ro. This still allows running programs. A setting you'll often find is maintenance done in single user mode; here, / is mounted ro to give access to the basic programs in /bin and /sbin. All other partitions, including /usr, are not mounted. They don't need to be for having a fully functional system in maintenance mode. but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Nice you found this. :-) Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? The volume name, according to the manual, is /home/ now, isn't it? from manual: # tunefs -L /home/ //dev/da3/ I cannot find this in the tunefs manual in group 8... It seems that there are too many /s in it... Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! Wow... I'm having problems now, too. Maybe I should re-read the manpages a few times... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: I hate to bitch but bitch I must
Manolis Kiagias wrote: PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Relax. You are having a bad day, and you are topping it by trying to perform some stuff while you are not in the right state of mind. If you do insist on continuing with this, do the following: Make a list of your partitions - I'll assume a device name of /dev/ad1 for the disk. You should have: ad1s1a for root = Label this as rootfs ad1s1b for swap = Label this as swap ad1s1e for tmp = Label this as tmpfs ad1s1d for var = Label this as varfs ad1s1f for usr = Label this as usrfs If you are unsure of the device names, try ls /dev/ad* (or ls /dev/da* if you are using SCSI disks, which I think you are not) Now, reboot: shutdown -r now Press 4 and enter single user mode in the loader. In the single user mode prompt type: glabel label rootfs /dev/ad1s1a glabel label swap /dev/ad1s1b glabel label tmpfs /dev/ad1s1e glabel label varfs /dev/ad1s1d glabel label usrfs /dev/ad1s1f You should get no error messages from these. Type exit and continue to multiuser boot. Ok, but that is exactly what I did. Exactly that and that is what is in the manual. And I can read and I did check and recheck my input for typos. But, I did get error messages! # glabel label rootfs/dev/ad12s1a glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted and the message was the same for all partitions! So, you must wonder as I did why was I getting error messages. I looked on the web and there was nothing directly related to the errors.So what is going on? Since the web gurus were saying that the error messages were not important and to ignore them, I tried that and continued through with the boot and changed the fstab entries and rebooted and the boot failed. So I had to fix the fstab and fortunately I was able to boot ok... Something is warped here... and I hope it isn't my little brain. :-( Change /etc/fstab: change /dev/ad1s1a to /dev/label/rootfs /dev/ad1s1b to /dev/label/swap and so on. Reboot once again. Everything should work. Do people who write this stuff ever read it? Tell me t Yes, we do. All the time actually. hat its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results!___ You will have best results when trying with a clear mind. Also having a test system
Re: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 19:10:58 -0400 PJ af.gour...@videotron.ca wrote: *** Snip*** You will have best results when trying with a clear mind. Also having a test system (or a VMware / Virtualbox machine) will help you learn and practice unknown procedures without the anxiety of breaking something on your production system. Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? ... try your left mind or even, wrong mind?! -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments There's no place like 127.0.0.1 ___ 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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 19:10:58 -0400, PJ af.gour...@videotron.ca wrote: Ok, but that is exactly what I did. Exactly that and that is what is in the manual. And I can read and I did check and recheck my input for typos. But, I did get error messages! # glabel label rootfs/dev/ad12s1a Exactly? I think a whitespace (after rootfs) is missing. glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted and the message was the same for all partitions! And you ran this command in single user mode with no partitions mounted, except / in ro mode? (You can use mount -v to check.) Since the web gurus were saying that the error messages were not important and to ignore them, [...] I cannot imagine this. It looks like an error message. Such as if Cannto save file wouldn't suggest you that the file has been successfully save, woult it? [...] I tried that and continued through with the boot and changed the fstab entries and rebooted and the boot failed. Of course. Obviously, the label has NOT being written, so the reference in /etc/fstab leads to failure. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: I hate to bitch but bitch I must
PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* ___ 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: I hate to bitch but bitch I must
Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. A common misunderstanding about manpages can be that they are often (wishfully?) seen as a tutorial or a howto. In fact, they are references. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? That's confusing... man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? No. Active file system refers to a file system that is mounted rw - the common method of using a file system. But in order to run a program from a file system, the file system can as well be mounted ro. This still allows running programs. A setting you'll often find is maintenance done in single user mode; here, / is mounted ro to give access to the basic programs in /bin and /sbin. All other partitions, including /usr, are not mounted. They don't need to be for having a fully functional system in maintenance mode. but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Nice you found this. :-) Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? The volume name, according to the manual, is /home/ now, isn't it? from manual: # tunefs -L /home/ //dev/da3/ I cannot find this in the tunefs manual in group 8... It seems that there are too many /s in it... typo, sorry Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! Wow... I'm having problems now, too. Maybe I should re-read the manpages a few times... I agree that the manual is not intended as a tutorial... but then what is a manual but a source for a tutorial... ;-) ___ 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: I hate to bitch but bitch I must
Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* Shortly... have to reconfigure GAG. ___ 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: I hate to bitch but bitch I must
PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done If you feel that you've found a 'bug' within the manual/documentation of a piece of software or function, I highly recommend that you pass it by other users/developers ( as you've kind-of done here ), and then contact the person who is normally listed in the AUTHOR section of the man page after you get a consensus on whether the manual, the code or you have the bug :) If you believe the problem is an engish-linguistic one (and the man page is written in english), let the author know this. Provide the correct verbiage, and an explanation of what your words mean compared to theirs (remember, english may not be their first language). Also, take a look at RFC 2119 for the keyword 'SHOULD' and 'SHOULD NOT'. RFC 2119 is highly regarded as the authority for many keywords, and a quick reference of it may help when trying to explain to an author where you feel their documentation is incorrect (or lacking). Cheers, Steve ___ 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: I hate to bitch but bitch I must
On Fri, Oct 16, 2009 at 07:27:42PM -0400, PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. ___ 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: I hate to bitch but bitch I must
Bob Hall wrote: On Fri, Oct 16, 2009 at 07:27:42PM -0400, PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. fwiw, upon first reading, I got the exact same impression about the writing under its context as Bob did. Steve ___ 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: sysinstall colours
On Friday 16 October 2009, Randi Harper wrote: Personally if I spent a lot of time on such a project, I'd be sure to have the is this going to make it into freebsd base? conversation first. I think there's no doubt about it that 'sysinstall' will feature in the next FreeBSD too. It will! Keep up the good work! It's worth it. The sysinstall manual page makes two apocalyptical remarks about itself: 1. This product is currently at the end of its life cycle and will eventually be replaced. 2. This utility is a prototype which lasted several years past its expiration date and is greatly in need of death. These doomsayings are wrong. To date no serious contenders have surfaced and up until that time sysinstall does its job, underappreciated perhaps, but it does it reasonably well, and adequately. Now that it is back in the focus, we can look to a bright, evolutionary future for sysinstall. alexbes...@math.uni-muenster.de wrote: personally if i spent a lot of time on such a project i'd be expecting it to get integrated into the base system. if not i'd get rather upset and would probably switch to linux or opensolaris. I wouldn't switch operating systems just because something in the installer bugged me. Some enhancements I made to OSS and were rejected by the maintainers also didn't make me abandon that software. Greetings, Michiel Overtoom, Software developer. -- The ability of the OSS process to collect and harness the collective IQ of thousands of individuals across the Internet is simply amazing. - Vinod Valloppillil http://www.catb.org/~esr/halloween/halloween4.html ___ 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: I hate to bitch but bitch I must
Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* it'll have to be later - tomorrow or monday... I'm fighting with a stubborn disk from a broken raid0 array that prevents the system from booting another load or horsemanure! ___ 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: I hate to bitch but bitch I must
Steve Bertrand wrote: PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done If you feel that you've found a 'bug' within the manual/documentation of a piece of software or function, I highly recommend that you pass it by other users/developers ( as you've kind-of done here ), and then contact the person who is normally listed in the AUTHOR section of the man page after you get a consensus on whether the manual, the code or you have the bug :) If you believe the problem is an engish-linguistic one (and the man page is written in english), let the author know this. Provide the correct verbiage, and an explanation of what your words mean compared to theirs (remember, english may not be their first language). Also, take a look at RFC 2119 for the keyword 'SHOULD' and 'SHOULD NOT'. RFC 2119 is highly regarded as the authority for many keywords, and a quick reference of it may help when trying to explain to an author where you feel their documentation is incorrect (or lacking). Cheers, Steve It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. I speak english, french, italian, some spanish and german as well as latvian... but I would never attempt to translate into any language other than English... and then not without the help of the original language's originator. ;-) ___ 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: I hate to bitch but bitch I must
Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. fwiw, upon first reading, I got the exact same impression about the writing under its context as Bob did. Am I the only one annoyed by the monthly PJ soap-operas. It seems that we get a ridiculous installment from this guy who bites off more than he can chew and then complains that it's too big every full (or is it fool) moon (28 day cycle . . . sorry obvious,stupid joke). The patience he gets from folks on this list should be commended, but questioned. In what sense is the community benefited from the dramatic life-story of an ungrateful novice? This guy puts forth his problem(s) only to update the list at every small/backward step and then ultimately offer something offensive such that the devs can't speak English. He needs to work things out before blogging on freebsd-questi...@. IMHO ;-) Steve ___ 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 ___ 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: I hate to bitch but bitch I must
PJ wrote: Steve Bertrand wrote: PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done If you feel that you've found a 'bug' within the manual/documentation of a piece of software or function, I highly recommend that you pass it by other users/developers ( as you've kind-of done here ), and then contact the person who is normally listed in the AUTHOR section of the man page after you get a consensus on whether the manual, the code or you have the bug :) If you believe the problem is an engish-linguistic one (and the man page is written in english), let the author know this. Provide the correct verbiage, and an explanation of what your words mean compared to theirs (remember, english may not be their first language). Also, take a look at RFC 2119 for the keyword 'SHOULD' and 'SHOULD NOT'. RFC 2119 is highly regarded as the authority for many keywords, and a quick reference of it may help when trying to explain to an author where you feel their documentation is incorrect (or lacking). Cheers, Steve It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. I understand that I'm confused :) I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. That's an unfair thing to say. Are you saying that if someone with a French native tongue wrote software that would benefit everyone, and they wrote the manual in English to reach a broader audience, that the manual shouldn't be released unless proof-read and re-written by an English native? Vous faire ce travail, mon ami? Je n'aime pas d'accord avec votre utilisation du mot doit. ...the manual is available. I didn't mean to dis-respect you, I just meant that if one 'could' help, then the developer is the one to hit up. I speak english, french, italian, some spanish and german as well as latvian... but I would never attempt to translate into any language other than English... and then not without the help of the original language's originator. ;-) Nice... How 'bout Dutch ;) You will understand then: Ne dis pas que la documentation ne peuvent etre ecrites par un auteur si leur lange nest pas une espece indigen. Steve ___ 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: I hate to bitch but bitch I must
Neal Hogan wrote: Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. fwiw, upon first reading, I got the exact same impression about the writing under its context as Bob did. Am I the only one annoyed by the monthly PJ soap-operas. It seems that we get a ridiculous installment from this guy who bites off more than he can chew and then complains that it's too big every full (or is it fool) moon (28 day cycle . . . sorry obvious,stupid joke). Hadn't really paid attention. The patience he gets from folks on this list should be commended, but questioned. In what sense is the community benefited from the dramatic life-story of an ungrateful novice? This guy puts forth his problem(s) only to update the list at every small/backward step and then ultimately offer something offensive such that the devs can't speak English. The benefit(s)? If there are other long-term members who agree with what you are getting at, then I'd say that the benefits are that it shows to newcomers that no matter what, you'll always receive a respectable and educated response. It also shows that it doesn't matter what the poster's name is, or what language they speak in, that those who love FreeBSD for what it is will always bleed their souls to help them out, at any cost. What is learned from hard work is better passed on to someone else. Mia casa e tua casa, as my best friend's father always says. (my house is your house). Steve ___ 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: I hate to bitch but bitch I must
. He needs to work things out before blogging on freebsd-questi...@. IMHO ;-) Steve ___ 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 ___ 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 You are a pathetic example of the intolerant know-it all...not worthbothering with Yet you did . . . and we continue the saga. fBSD, oBSD, etc. is not the problem, as you claim. You, my friend, have a tendency to jump into things and then complain when they do not go your way. The latest of which is to complain about the language in which the man pages were written . . . and you expect to be taken seriously. I know English but it is sometimes difficult to understand. What?! Intolerance is something you can;t charge me of. I offerred my genuine help in the past. You chose to use that offer to bash an OS and come back to an OS that you (apparently) can't handle. You fail to see that it is your failings that let you down. %...@*#^#%$ . . . does that make more sense? ___ 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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 21:29:04 -0400, PJ af.gour...@videotron.ca wrote: It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. As English is not my native language, I *now* understand the meaning of it should; in this case, it seems to mean something like basically, it is supposed to, but in this case, it does not, regarding the desired action. I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. It's still possible that non-native speakers misunderstand. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: I hate to bitch but bitch I must
The benefit(s)? If there are other long-term members who agree with what you are getting at, then I'd say that the benefits are that it shows to newcomers that no matter what, you'll always receive a respectable and educated response. Does that really include taking seriously everything posted/asked/bitched about on the list? It also shows that it doesn't matter what the poster's name is, or what language they speak in, that those who love FreeBSD for what it is will always bleed their souls to help them out, at any cost. What is learned from hard work is better passed on to someone else. Yes . . . sure. . . but many, many houses have been built and it seems reasonable to help those attempting to build something unique or somewhat untested, than those who like to spend time complaining about things that have been built and which they have not spent much time thinking about, but just jotted down a command from google search and is disappointed when it fails to satisfy. Mia casa e tua casa, as my best friend's father always says. (my house is your house). Steve ___ 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: Unknown devices
On Thu, 15 Oct 2009 00:38:03 +0200 Polytropon free...@edvax.de wrote: On Wed, 14 Oct 2009 23:04:51 +0400, Arkady Tokaev tok...@hotmail.com wrote: While I was trying to update ports I have received message about absence disk space.It's impossible, I thought.But df command said: $ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 23G3.5G 18G16%/ devfs 1.0K1.0K 0B 100%/dev /dev/md0 9.4M2.8M6.5M30%/etc /dev/md131M 16M 13M55%/usr/local/etc /dev/md219M 18K 19M 0%/root /dev/md331M6.1M 24M20%/var $ What is the md devices?How I can remove them? See man md: The md devices refer to memory disks, RAM that emulates a hard disk. Sadly, I don't recognize a reason why your /etc, /usr/local/etc, /root and /var subtrees are mounted onto memory disks... seems that you're not running a default install, do you? I would imagine that they're vnode md devices that each have a file on the root filesystem as a backing store. I've never tried it myself but you could do this as an alternative to conventional partitioning. It's a little less efficient, but they can be resized. I'm not aware that sysinstall can install like this though - perhaps it's pc-bsd or something. There should lines like mdconfig_md0=... defining the devices in rc.conf ___ 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: small question about tape-based dumps
Replies inline On 10/16/09, Jerry McAllister jerr...@msu.edu wrote: On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / I understand that this creates a dumpfile on nsa0, and as I understand tapes (which may be wrong, which I ask for clarification here).. To mark a end-of-file to be able to fast-forward/rewind, why can't you use: mt -f /dev/nsa0 weof It's description in mt(1) says it writes the end-of-file mark at current position For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr So if we use weof, would the 2nd dump then be: dump 0af /dev/nsa0 /usr mt -f /dev/nsa0 weof thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var And 3rd: dump 0af /dev/nsa0 /var mt -f /dev/nsa0 weof etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline And I've never used offline, guess I'll start now. I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry With regards Stevan Tiefert Thanks for any input! --TJ ___ 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
zfs and vfs.numvnodes
Hi! I have a strange behavior on zfs filesystem. vfs.numvnodes tends to grow and when reach kern.maxvnodes no new files can be created or modified. System AMD64 8.0-RC1 FreeBSD 8.0-RC1 CVS from Oct 13 2009. I have increased kern.maxvnodes but vfs.numvnodes grows slowly. Any suggestions ? ___ 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: I hate to bitch but bitch I must
It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. I speak english, french, italian, some spanish and german as well as latvian... but I would never attempt to translate into any language other than English... and then not without the help of the original language's originator. ;-) since I'm in the mood PJ, you certainly sound like a scholar . . . you speak many languages and have a strict translation policy, yet (given those two points) it doesn't follow you have any idea how to use any of those languages. You prefer drama and at some point we're going to realize that there is no wolf? KISS! (google for translation). ___ 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 ___ 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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009, Bob Hall wrote: On Fri, Oct 16, 2009 at 07:27:42PM -0400, PJ wrote: BUGS This utility should work on active file systems. I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. I understand it, but see ambiguity in the word should. Easy enough to rewrite: BUGS This utility does not work on active file systems. Now here's my challenge to PJ: use send-pr(1) or the web PR interface at http://www.freebsd.org/send-pr.html to submit this as a doc bug report. That's how FreeBSD gets better, and how you help the next person in the same situation. -Warren Block * Rapid City, South Dakota USA ___ 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: I hate to bitch but bitch I must
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of PJ Sent: zaterdag 17 oktober 2009 3:50 To: Steve Bertrand Cc: Polytropon; freebsd-questions@freebsd.org Subject: Re: I hate to bitch but bitch I must but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed The meaning of 'should' is not nearly as narrow as you suggest. Often it also denotes reservation (as in the above example). To illustrate once more: Can I run dump on an active file system? It *should* run on an active file system, provided (enumerations of conditions which would need to be met; like preferably no disk-activity when making the backup). (Meaning: it can be done, but it's ill-advised, really.) And clearly it does not mean should be executed, done, carried out, performed. Another one: Will he run for President? Well, he should be able to get enough votes. (Meaning: if everything goes as planned, he might succeed, but it's by no means guaranteed he'll actually get enough votes). So, given the right intonation and context, This utility should work on active file systems. can certainly be understood to mean one could technically do so, but that it's not recommended. - Mark ___ 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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 20:59:18 -0600 (MDT), Warren Block wbl...@wonkity.com wrote: I understand it, but see ambiguity in the word should. Easy enough to rewrite: BUGS This utility does not work on active file systems. Now here's my challenge to PJ: use send-pr(1) or the web PR interface at http://www.freebsd.org/send-pr.html to submit this as a doc bug report. That's how FreeBSD gets better, and how you help the next person in the same situation. That's a good advice, because in this particular situation, the utility in question does NOT work on active file systems, it refuses to do so and throws the proper error message. There are cases where a program should work (under certain circumstances), but if a specified setting is not met, it works incorrectly (but still works), like using dump on a filesystem that's changing - usually producing a defective dump file that cannot be properly restored. For completeness: If a program does not work, the manual should not say it should work, but it does not work regarding a given situation. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: I hate to bitch but bitch I must
On Sat, Oct 17, 2009 at 02:34:40AM +, Mark wrote: Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Actually, what's happening here is dropping part of a sentence. It's common in English to shorten Yea, it should work, but it doesn't. to Yea, it should work. In order to catch the meaning, you have to be aware of context. Contrary to the OP's claim, this shows a pretty good grasp of English idiom. It's definitely not evidence that the man author is not a native speaker of English. On the other hand, it can be clarified so that the meaning is clear even without context. If the OP really believes that the present wording is a problem, other people have made suggestions on what to do about it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
using split, can i break up a huge txt file using a regex
Guys, I have the ASCII files of my novel, JOURNEY, in 66 textfiles. [Named 00 - 66]. I have my word-processor version is the (urp) DOC fmt to submit places and for me, when i play around with formatting and typefaces and so in, in open format, ODT. I would like to put back the huge text file into its 66 smaller files using split. Can I break this very large journeyTowardtheDawn.txt using the regex Chapter [:digit:]{1,2} ?? Or maybe just Chapter ? thanks for ideas, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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: sysinstall colours
On Fri, Oct 16, 2009 at 6:00 PM, Michiel Overtoom mot...@xs4all.nl wrote: On Friday 16 October 2009, Randi Harper wrote: Personally if I spent a lot of time on such a project, I'd be sure to have the is this going to make it into freebsd base? conversation first. I think there's no doubt about it that 'sysinstall' will feature in the next FreeBSD too. It will! Keep up the good work! It's worth it. Thank you for the kind words. :) The sysinstall manual page makes two apocalyptical remarks about itself: 1. This product is currently at the end of its life cycle and will eventually be replaced. 2. This utility is a prototype which lasted several years past its expiration date and is greatly in need of death. These doomsayings are wrong. To date no serious contenders have surfaced and up until that time sysinstall does its job, underappreciated perhaps, but it does it reasonably well, and adequately. Now that it is back in the focus, we can look to a bright, evolutionary future for sysinstall. As much as I want to agree with you, I can't quite do so. There are (to the best of my understanding) solid reasons why no other installer has made it into base. This doesn't necessarily mean that sysinstall is the final answer, though. Eventually, in my opinion, sysinstall needs to be replaced. It tries to do more than it should. For example, one of the things I'd like to see removed is the upgrade option - although I'm expecting quite a bit of backlash on that, so we'll see if that happens. I also don't think it should manage configuring rc.conf beyond network interfaces/hostname. The network services configuration is a mess. I don't think enabling the NFS server via sysinstall even works at this point. That aside, the code for sysinstall isn't really that bad, although it's been more of a history lesson than I initially expected. It was clearly written with the restrictions of older technology in mind. Bringing it completely up to date with current technology (devfs, gpt, zfs, whatever) is going to be such an extensive rewrite that it's true, one might as well write a new installer altogether. Then again, maybe I just like playing devil's advocate. :) -- randi ___ 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: I hate to bitch but bitch I must
PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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 ok, in short since i didn't see anyone answer this directly, your question of tunefs vs glabel: tunefs is for UFS: it labels a UFS filesystem, no matter the device, ie: ad or da. tunefs is part of the filesystem utilities for UFS. good example, can't tunefs -L SWAP /dev/ad0s1b if it is a swap. you can glabel it. glabel is for labeling a device itself. you can glabel an ntfs filesystem or ext2, whatever. ___ 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