Re: Reinstall without reformat
On Mon, 14 Oct 2013 07:51:15 -0600 (MDT), Warren Block wrote: It is possible to mount filesystems manually from the shell and have bsdinstall continue with the install without formatting them. It's been a while since I tried that, and I don't recall the exact details. bsdinstall(8) suggests it may be as easy as just having the existing filesystems mounted at /mnt. Still, not something to try without a backup. So if I understand everything correctly, the decision logic is -- when partitions do already exist -- as follows: a) existing partitions not mounted: run newfs mount partitions copy files b) existing partitions mounted: do not run newfs copy files The installer itself doesn't seem to give a hint about this logic, even though the manual _might_ suggest it. I haven't examined the source code to fully verify this logic, even though it would be a reasonable approach. -- 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: Reinstall without reformat
On Sun, 13 Oct 2013 13:24:30 -0400, Kenta Suzumoto wrote: Hi all. Is it possible to install FreeBSD without formatting the disk? Yes. The installer supports not formatting existing partitions. The file system characteristica will be kept, possible content will overwritten. Note that superfluous content will also be kept, except of course you previously remove everything. I have one directory of data that I want to keep. You should still make a backup, because I want to keep does imply exactly that in regards of an OS installation. :-) I can boot from the installer and rm every directory except that (/bin /boot etc), but how could I install the OS from there? You simply re-enter the installer, assign the (existing, but now empty) partitions to the desired mountpoint, make sure _not_ to newfs them, and then commit to the installation as usual. An alternative would be, after preparing the partitions, mount them as desired and extract the installation datasets from the installation media manually (via shell commands). Still you might miss other steps the installer performs. I've done ZFS on root installs with the shell and mounting the zpool to /mnt, would that work here too? Probably yes (never tried that myself). -- 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: Reinstall without reformat
On Sun, 13 Oct 2013 23:01:02 -0600 (MDT), Warren Block wrote: On Mon, 14 Oct 2013, Polytropon wrote: On Sun, 13 Oct 2013 13:24:30 -0400, Kenta Suzumoto wrote: Hi all. Is it possible to install FreeBSD without formatting the disk? Yes. The installer supports not formatting existing partitions. The file system characteristica will be kept, possible content will overwritten. Note that superfluous content will also be kept, except of course you previously remove everything. sysinstall supported that, but AFAIK bsdinstall does not. Oh, seems you're right. I've checked The FreeBSD Handbook for the relevant instructions for using bsdinstall at http://www.freebsd.org/doc/handbook/bsdinstall-partitioning.html and http://www.freebsd.org/doc/handbook/bsdinstall-final-warning.html and I didn't find an option to _not_ initialize existing partitions, even though it seems you can assign existing partitions without any problem. The remaining question: Will they be initialized again? I know that sysinstall had the option newfs toggle so you could skip the newfs step after you had assigned the existing partitions to the desired mountpoints. It can be seen at http://www.freebsd.org/doc/handbook/install-steps.html in Fig. 3.19 and 3.24. I have to admit that I didn't assume such a significant loss of functionality (that sysinstall provided!) in the new installer... :-( That's why maybe manually extracting the distribution files from the installation media, using the CLI tools, would probably the easiest thing: Manually mount existing partitions as desired, then extract the installation datasets, and apply any further modifications as needed. -- 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: what kind of freeBSD to download for my pc?
On Sat, 12 Oct 2013 16:44:09 -0700 (PDT), cikitaluzza wrote: what kind of freeBSD to download for my pc?amd athlon(tm) 64 x2 dual core processor 4000+ 2.11 GHz 960 MB RAM Try 9.2 for AMD64. The i386 version should also work (as you are low on RAM if that might matter, depending on what non-OS software you're going to run on that machine). -- 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: what kind of freeBSD to download for my pc?
On Sat, 12 Oct 2013 16:50:32 -0700 (PDT), cikitaluzza wrote: can i run exe files on freeBSD? Depends. VMX EXE files may work via the SimH emulator. For DOS EXE and Windows EXE files, there are dosbox and wine. Those compatibility packs can be easily installed. They are not part of the OS. it spoils fast or not?this question comes from fastest ever spoil OS windows which always spoil in a week seven times i think with things like errors or dll and many things from blue screen.do you have any problems within freeBSD or no problems?i dont like blue screen error or driver things and no matter what . Definitely no bluescreens in FreeBSD. The system will behave exactly as intended and won't change its mind a few days after installation. :-) how much total ram and bit is my pc of amd athlon(tm) 64 x2 dual core processor 4000+ 2.11 GHz 960 MB RAM? That's a 64 bit CPU, if I remember correctly. The AMD64 version should run fine. But as you are a little bit low on RAM, you might consider using the i386 version (32 bit version) if you don't _need_ to run any 64 bit application. Especially as you've mentioned to run EXE files, this might be the better solution. From what I've heared, wine (the Windows compatibility pack) runs better on i386 than on amd64. (I'm running it myself on the i386 OS on a 64 bit system without any problems.) im always in internet watching live camers,what do you suggest me to use os type? Is this via web? In this case, only the web browser matters. The typical candidates Firefox and Chrome should be fine. The OS does not matter here. If you need a proprietary program to watch the live cameras, often available only for an outdated Windows version, running it with (the mentioned) wine should work. (I've successfully tried something like that with a program to watch CCTV cameras via Internet.) i like to save pictures and videos and never lost them,if you think your os is gonna spoil and lost my all files then i dont need it. Definitely no problem. But keep in mind: _You_ are responsible for creating backups! FreeBSD offers excellent tools to do so, no matter if you want to backup to disks, DVDs, the Cloud, or even to old-fashioned tape. Saving pictures from videos is no problem. There is mplayer and mencoder. It plays, records and converts _everything_. i want stable os and never to reinstall or update That approach is unreasonable, I think. You _should_ update when security updates become available. It's in _your_ interest to do so, because effciency, security and usability improves from version to version. Luckily, FreeBSD has an easy way of updating the OS. It's _independent_ (!) from your installed applications and of course from your data. You can also decide to update your programs independently. However, a install once, then keep using scenario is easily possible with FreeBSD. (My home system has been installed in summer 2011 and worked _flawlessly_ since that point, never touch a running system.) I suggest you make yourself familiar with FreeBSD by using the resources from http://www.freebsd.org/ and you _might_ also want to check out PC-BSD (might be perfect for what you want) and VirtualBSD (easy way to try it out without installing 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: Do I really have to install 80 packages?
On Sat, 12 Oct 2013 23:28:40 +0100, gct7photogra...@gmail.com wrote: I don't know what others think, but what *I* really want is that the free software versions of Flash (gnash and klash, etc) work at least as well as versions of Adobe Flash do, or if versions of Adobe Flash are to be used, that it will be free and covered by the GPL. First of all, keep in mind you're walking corporate territory here. No company will give you anything for free, and even if it looks free, there's a catch somewhere. Flash as a technology is dying. It didn't make the transition to the growing mobile markets. That's why Adobe does not continue its Linux line of product - a completely reasoname business decision. People who use, or to be correct, _abuse_ Flash as a replace- ment for markup and content are not interested in bringing their product to your attention and reception. What I'd like to see would be a Flash plugin integrated in the web browser, with the option of being switched off. I'd consider it a 1st class citizen by demanding that is has the same status as embedded media, centered text, a PNG image or a hyperlink, being a functional module of the web browser like the renderer, the CSS interpreter, the JS interpreter or something like that. Could you imagine to install a pro- prietary plugin to be able to see a JPG image? To see text centered? To click on a hyperlink? And all the time keep in mind that it is backdoored? Hmmm... Its unlikely to happen unless we start a campaign among the Free Software users of the world to make Flash free software. That won't happen. Flash is the property of a corporation. The only alternative I see is that this corporation would donate the product, releasing all the sources and abandoning all involved lawyer-crap. But that won't happen. I think most companies better close away the stuff they won't develop anymore instead of handing it over to a community. Yes, I know HTML 5 is just around the corner, but we've seen a concerted effort already (in the European Parliament at least) to introduce DRM into HTML 5 and though it may make using Flash marginally easier, it would be a retrograde step if DRM is to be introduced. As far as I know, DRM will be covered by the upcoming standard. This means it will be _possible_ to implement DRM solutions in HTML. _Using_ them - that's a totally different field. Keep in mind an important thing: Alternatives for Flash have been around for a decade at least. Video, audio, interaction - all possible without it. It's not just about the browser plugin (the player), it's also about the creative tools that people use to produce the stuff. Those tools are offered usually in expensive commercially distributed suites. As soon as developers and creators get aware of alternatives that they can learn and use for free, they _might_ change, but only if the mindset changes. It's not just about those tools, it's also about file formats. What I'm talking about is media codecs. Some of them offer DRM capabilites, others don't. Some of them are highly infected with patents and other lawyer-crap. There are reasons why some systems and environments can play various formats out of the box, and others can't. Which formats are efficient for use with the Internet? Which offer scaling and streaming capabilities, important for mobile users who demand lower quality, less data transfer, and tolerance to higher latency? Which codecs can make use of a decoder made in hardware? _This_ problem also has to be solved! Now put this back into relation with my initial idea of making that kind of content decoder part of the web browser. The same way you see a JPG image on a web page and click on a hyperlink... It should be easy, but sadly it isn't. HTML5 tries to solve those problems. Its markup will be better suited for handling media content, plus CSS and JS will be important players on the interaction field. There are already projects that utilize those tools, and _developer tools_ as well as _creator tools_ will be present. Maybe they will even be present for free. YouTube can do fine without Flash already. Online games in HTML5 are appearing. On the other hand, Flash is a no-go on mobile, and mobile is becoming more and more important to consumers. Additionally, more and more people become aware of the danger of proprietary software (in regards of privacy and corporate control, as well as an improving understanding of what DRM does to their freedom). It will take some time to show significant effect. Let's hope people are going to get smarter than I assume. :-) So what are we left with? Free software to replicate what Flash does (at least) that does not have the taint of proprietary software? Is that not an achievable goal? It is a _desired_ goal. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http
Re: what kind of freeBSD to download for my pc?
Typo warning! On Sun, 13 Oct 2013 03:26:45 +0200, Polytropon wrote: On Sat, 12 Oct 2013 16:50:32 -0700 (PDT), cikitaluzza wrote: can i run exe files on freeBSD? Depends. VMX EXE files may work via the SimH emulator. For ^^^ DOS EXE and Windows EXE files, there are dosbox and wine. Those compatibility packs can be easily installed. They are not part of the OS. Of course I meant _VMS_ executables. ^ Also I don't know if there would be a way to run OS/2 EXE files. This is probably only possible with a VM running the appropriate OS/2 version. This approach might also apply for running Novell NetWare EXE files. There are several VM systems available for FreeBSD, for example VMWare and VirtualBox. I hope I have covered all typical possibilities of what exe file could mean. :-) -- 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: Do I really have to install 80 packages?
On Fri, 11 Oct 2013 17:54:24 -0400, Glenn Sieb wrote: On 10/11/13 5:38 PM, Walter Hurry wrote: FreeBSD 9.1 I want ONE shared lib; i.e. rsvg.so, which is provided by x11-toolkits/py-gnome-desktop. Unfortunately, it seems that going the normal route I shall have to install 80! ports to get it. Is there an easier way? Actually I think you want x11-toolkits/gtk20..? Would pkg_add work for you? Maybe graphics/librsvg2 is better suited (even though it's version 2 of the library). The problem initially mentions will remain: lots of installation dependencies. Sadly, that seems to be normal today as modern software tends to rely on layers of libraries of abstraction of tools of utilities of stuff of layers of layers of other abstractions. :-) As you see: gnome-desktop and gtk20. That should bring your warning lights up: lots of dependencies ahead! When you try to install a simple desktop environment, you'll be confronted with hundreds of packages to be installed, some of them you've probably never had thought of in regards of what you need to install a desktop, such as two or more different databases, LaTeX, translators, and other surprising stuff. This will probably apply to most complex components and parts of desktop environments or X11 toolkits (as mentioned above). As I mentioned, the librsvg2 port will install lib/librsvg-2.so. It might require you to re-install your target application to link against that library. A library libsvg.so (without version number) doesn't seem to be in the ports tree by that name. My lazy man's method of searching what port might contain the library: Midnight Commander, go to /usr/ports, Meta-?, seach in pkg-plist, search for text librsvg and examine the results with PF3. This method relies on approaches that might be wrong... :-) Note that my (locally installed) ports tree is not up to date anymore so you should consider performing a search on a recent tree to make sure I didn't miss anything. -- 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: Why no ls on DVD or livefs.iso?
On Thu, 10 Oct 2013 21:45:58 -0500, W. D. wrote: Thanks, Polytropon. I couldn't get FrieSBIE to work. It's a rather old project, and as far as I know, it isn't being continued anymore. It should still support at least the CLI mode for most computers... (I have to admit that I'm still using it, but usually on _older_ computers where it often works flawlessly.) Hung up. Used mfsBSD instead. Good choice. :-) Had to use 8.X because 9.X hangs. I think it has something to do with my PS2 mouse and keyboard. Can't imagine _that_ as a cause of OS hangs, but it might still be a hardware compatibility or configuration problem. If v8 works for you - no problem, it's still supported. -- 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: mounting a .iso image? ... missing man page
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote: Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Of course. :-) It is possible by using a virtual node connected to the ISO file. Without having tested, according to your example: # mdconfig -u 0 -t vnode -f /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso # mount -o ro -t cd9660 /dev/md0 /mnt/tmp ... do stuff ... # umount /mnt/tmp # mdconfig -u 0 -d An alternative would be to use tar to extract the files from the image, change whatever you want, and use mkisofs afterwards to rebuild the (new) image, in case you want to modify its content. -- 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: mounting a .iso image? ... missing man page
On Wed, 09 Oct 2013 22:18:41 -0600, Gary Aitken wrote: for the record, that's: mdconfig -a -t vnode -u 0 -f file Correct, I noticed too late that -a was missing. But man mdconfig mentions all parts that are needed. :-) # mount -o ro -t cd9660 /dev/md0 /mnt/tmp ... do stuff ... # umount /mnt/tmp # mdconfig -u 0 -d and that one is mdconfig -d -u 0 order appears to be important The manpage doesn't seem to explicitely mention this, but if I remember correctly, it actually matters, as you said. By the way, the manpage mentions mount -t cd9660 /dev/`mdconfig -f cdimage.iso` /mnt as an interesting construction in the EXAMPLES section. :-) -- 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: 9.1 - 9.2 upgrade
On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: I tried downloading the src with: svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src I didn't get Release 9.2. The first entry in UPDATING is: 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. There is an entry earlier for Release 9.1. but no entry for Release 9.2. You could try downloading and extracting the src distribution: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz -- 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: How do I ring a bell?
On Mon, 07 Oct 2013 12:37:35 +0100, Frank Leonhardt wrote:
In the good'ol days I could make UNIX ring a bell (literally) by sending
\a to the console TTY (an ASR33 in my case).
Ah, the famous ^G control character... :-)
Now there's an electronic
synthesised ting or beep from an terminal emulator IF it's got a sound
card and so on, and an IBM-PC had a beep routine in the BIOS.
The terminal beep routine will primarily address the system's
speaker (located at or connected to the mainboard). A side
effect on the sound card is possible (the Logitech SoundMan
did have that feature), but it's not really in relation.
Is there any way to make a noise through the built in bell speaker
found on an IBM PC compatible server box? Writing 007 to the BIOS cout
routine might do it, but I've realised I haven't got a clue how to do that.
Making it audible is part of the local terminal emulator,
either the TTY (text mode) driver or via xterm (or the
preferred alternative terminal emulator in X).
A simple
printf \a
from the shell prompt should be sufficient. Note that if
you're running this in X, you have to make sure the bell
is not disabled. For example, put
xset b 100 1000 15
in your ~/.xinitrc (or ~/.xsession respectively).
A more sophisticated interface is provided as soon as your
kernel has
device speaker
compiled in (or speaker.ko has been loaded). Now you can
play wonderful music through the speaker. :-)
See man 4 speaker for details.
See the following shell script as an example of what you
can do:
#!/bin/sh
read -p CW === TEXT
echo ${TEXT} | morse | awk '{
if(length($0) == 0)
printf(P4\n);
else {
gsub( dit, P32L32E, $0);
gsub( di, P32L32E, $0);
gsub( dah, P32L8E, $0);
printf(%sP16\n, $0);
}
}' | dd bs=256 of=/dev/speaker /dev/null 21
Feel free to add support for reading from stdin so you can
listen to your console messages piped into the script. :-)
Always make sure that the system actually _has_ got an
internal speaker! I assume that modern PC hardware could
have it removed along with floppy drive connector, parallel
port or power switch.
P.S. cdcontrol -f /dev/mycdrom eject is the best I've come up with so
far for getting attention.
That's a really clever idea, never heared of that. It has
the advantage of being permanent because the drive will
stay open when the sound of its motor has finished. :-)
--
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: How do I ring a bell?
On Mon, 07 Oct 2013 21:09:44 +0100, Frank Leonhardt wrote: On 07/10/2013 13:36, Polytropon wrote: Is there any way to make a noise through the built in bell speaker found on an IBM PC compatible server box? Writing 007 to the BIOS cout routine might do it, but I've realised I haven't got a clue how to do that. Making it audible is part of the local terminal emulator, either the TTY (text mode) driver or via xterm (or the preferred alternative terminal emulator in X). Yers, but I'm not running X. Or a character terminal come to that :-) In that case, something line printf \a /dev/console should work - I've just tried it. You can do that from a shell script or maybe even via fprintf() from your own code. See the following shell script as an example of what you can do: snip Overkill. I have proper work to do rather than working out how to play appropriate bit silly little tunes for every eventuality. Actually spkr.c has some useful comments in it - apparently it works the same as IBM PC BASIC. Now how do I make it polyphonic... By adding more computers. This is the established solution to _every_ IT-related problem. :-) The code in /usr/src/sys/dev/speaker/spkr.c provides a more streamlined interface to sound generation. It's even more bare metal than what I remember from Borland Turbo-C: sound(1000); delay(2500); nosound(); It was important not to miss the 3rd line or the fun would never end. :-) Always make sure that the system actually _has_ got an internal speaker! I assume that modern PC hardware could have it removed along with floppy drive connector, parallel port or power switch. Remains to be seen, but most still seem to have one so the BIOS ROM can make beep diagnostic codes if it can't do anything else. This proves that it is present, even if it's not an attached speaker anymore. Many mainboards contain a little piezo speaker directly mounted (my ultracheap home PC does, for example). P.S. cdcontrol -f /dev/mycdrom eject is the best I've come up with so far for getting attention. That's a really clever idea, never heared of that. It has the advantage of being permanent because the drive will stay open when the sound of its motor has finished. :-) I use it all the time, especially when directing a tech to the appropriate server in a rack. It's the one I just popped the CD drive on. These days servers have the spring-loaded notebook drives instead of the motorised trays, which is a pity. You could keep winding the motorised ones in and out until someone spotted it. This seems to be better than those slot-in drives I had in one server: no moving parts to the outside. I suppose if you did it energetically enough it might catch fire and set off the smoke alarm (audible). This procedure has been part of an independent quality test of CD recorders, performed by a PC maganzine many years ago. Interesting result: the cheapest drive would last longer than the most expensive one in which the gears automatically had disassembled. :-) Or leave it wound out with a tin can balanced on it; to make a noise wind it back in and hear it clatter to the floor. Interesting use for the 4X cup holder. :-) -- 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: Why no ls on DVD or livefs.iso?
On Sun, 06 Oct 2013 01:29:19 -0500, W. D. wrote: Booted with both. Alt-F4 to get to command line. Very limited commands: ls: not found. Try /rescue/ls explicitely instead. Why? What good are these disks if they don't have the most basic of commands? Only live systems offer more than the holographic shell when booted properly. FreeSBIE has been a very good live system in the past, but the current installers also allow you to drop into a working shell environment at a very early stage (from within bsdinstall). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall/bsdinstall-choose-mode.png This dialog should bring you into a working shell. I've been using it myself for disk initialization with a FreeBSD 9.1 CD. Trying to clone a hard disk that has an number of bad sectors. Trying to save most of my data. A good approach. If possible, try to obtain a 1:1 copy of the disk (or partition) and work with that. Check the mailing list archives for further inspiration. -- 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: Problem completing a 9.1 release to 9.2 release upgrade
On Sun, 06 Oct 2013 08:08:42 +0100, Matthew Seaman wrote: On 05/10/2013 21:41, Polytropon wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. That is true. But if I understand the question (as quoted above) correctly, installing world from source has been involved, that's why my suggestion of following the instructions (or a subset of them, as it applies). While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. I've copied the the instructions from the comment header of /usr/src/Makefile (at least on my outdated system at home they're there). Of course if the _only_ problem of the initial question is to install a custom kernel, with an otherwise updated system using freebsd-update (with world, kernel and sources in sync), just installing a custom kernel from within multi-user mode is fully supported by the system. This implies that only a small subset of the quoted instructions would apply here (steps 1 and 3 - 5), after freebsd-update has been finished successfully. -- 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: Failure to build FreeBSD 9.2
On Sat, 5 Oct 2013 09:40:31 +0300, Juris Kaminskis wrote: i recompiled my kernel with more verbose output and I see following errors before it stops: procfs registered panic: No usable event timer found! cpuid=0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x1d8/frame initclocks() mi_startup() btext() ... KDB: enter: panic [thread pid 0 tid 10] Stopped at kdb_enter+0x3b: moxq can someone help me to explain what this means and what to do next? In many cases, this indicates a problem introduced by the computer's BIOS settings or ACPI. Make sure ACPI is enabled and the BIOS is configured properly (e. g. no timer settings modified or features deactivated). You could also check if a newer version of the BIOS is available. In addition, there's the suggestion to add the line debug.acpi.disabled=hostres to /boot/loader.conf and reboot. Source: http://www.freebsd.org/releases/9.0R/errata.html -- 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: Problem completing a 9.1 release to 9.2 release upgrade
On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- 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: gptid's in fstab while installing FreeBSD using ISO
On Fri, 4 Oct 2013 20:04:09 +0530, varanasi sainath wrote: Hi All, How do I get gptid's as default in fstab while installing using FreeBSD iso file (Virtual,machine installation) ? Is this possible currently? As far as I know, the installer bsdinstall currently does not have this option included, but it already offers labeling the partitions as desired, so you could change the content of /etc/fstab manually to use labels instead of those device names. You could do this as a post-installation task while leaving the installer for the command shell and using an editor to do this. if not how do I achieve this? I use guided partitioning while installing - If I were to tweak in to the source code which files or drivers I should be focusing on? I haven't looked into the source yet, but I assume you should concentrate on the component doing the partitioning tasks as explained here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-partitioning.html which drivers write the contents of fstab? The corresponding installer's component itself which creates the file according to the partitioning layout at installation time. I assume the required data will actually be written when the installer performs the _real_ installation steps (committing to the installation). PS: any reason why we use device names in the place of gptid's as default in fstab. Because it's not always wanted or intended. Next to GPT partitioning with GPT labels, UFS partitioning is possible (both MBR and dedicated style), which _may_ have cases where it needs to be applied. Maybe this can happen when you have a very strange combination of striping, mirroring, encryption and other things that require metadata here and there... The different methods have different capabilities regarding labels (UFS labels, UFSIDs to be mentioned). You can find out more about them here: http://www.freebsd.org/doc/handbook/geom-glabel.html And read about the different methods of partitioning itself: http://www.wonkity.com/~wblock/docs/html/disksetup.html Even hardcoded device names could also be required, though I can't imagine such a situation at the moment. :-) It highly depends on the toolset you're using (the bsdinstall program, gpart, fdisk disklabel, newfs only). PS. I've trimmed the CC list to the freebsd-questions@ list for my reply, hope that's okay. -- 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: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? Step 2: make buildworld Step 3: make build_kernel KERNCONF=LAFN Step 4: make install_kernel KERNCONF=LAFN I assume the correct targets buildkernel and installkernel have been used. ;-) Step 5: reboot Attention: Into single-user mode. Step 6: mergemaster -p Step 7: make installworld Step 8: mergemaster -i Step 9: make delete-old Step 10: reboot Into multi-user mode again. oops, something went wrong.. After step 5, uname -a still showed 9.2 but now it listed the kernel I built rather than generic. Again, verify your configuration. Compare your steps with the comment header of /usr/src/Makefile which illustrates the exact procedure; from a (dated) 8-STABLE installation: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. 4. can be combined by using the kernel target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster'(you may wish to use -i, along with -U or -F). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) -- 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: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way... -- 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: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: On 4 October 2013, at 20:03, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon free...@edvax.de wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that src is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its enclosure, software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? We have serious communications issues - they want to use back slashes and have no idea what a slash is. Maybe that is the result of many years of administration on Windows PCs. :-) Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. Uh... knowing better would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. The disk should be in the mail to me now. I will be able to work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean SSH only or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the normal way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the beastie menu (or whatever it is called today) enabled to go to SUM to perform the make installworld step? Anyway, if you can install everything is required with the disk at home, and then send it back to that datacenter (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. -- 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: cause of reboot
On Mon, 30 Sep 2013 20:32:39 -0400, Michael Powell wrote: kpn...@pobox.com wrote: [snip] While we're throwing ideas onto the table let me mention power supplies. Power supplies and hard drives are in a race to see which one will fail first. It may be that the power supply is marginal and added load from the drives being hit hard may send it over the edge. How heavily loaded is the machine in question? Absolute and total agreement with this. The idea of a hardware problem looks more and more obvious here. A software configuration problem could be located by diff'ing the currently used files against stock files, or by checking the logs of a versioning system (if you use one to track your local configuration file changes, for example in a CVS reposi- tory). It could be a matter of power (by more than usual drain when the machine is heavily loaded), but also a file system inconsis- tency is possible. In case the machine is using a background fsck that silently fails to deal with a specific damage, using background_fsck=NO in /etc/rc.conf to _definitely_ bring the file systems up _clean_ prior to multi-user mode booting would probably be a good idea. Using smartctl to check the hard disks SMART data would make sure the disk is not dying (and the reboot is an effect of that). Monitoring the server when (or while) it reboots would surely be interesting. Maybe open some sessions to have a close look at programs like top, systat -v and mbmon (to check for temperatures and voltages) - and when run at 1 second intervals, it should be possible to obtain a good system status diagram of the last state before reboot, when the connection drops. I once had a box where the RAM chips would sing with a high-pitched whistle only during the 0300 periodic run. It sounded just like the horizontal output on a television right before destruction. :-) I have heared something comparable from a graphics card when developing some OpenGL demo stuff. :-) -- 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: minor vi/vim qstn
On Wed, 25 Sep 2013 19:47:08 -0700, Gary Kline wrote:
dunno how you know im using the zsh, but yup.
This is because of my magical allknowinglyness. :-)
You wrote:
pts/14 17:11 tao [5011] vi!
zsh: command not found: vi!
^^^
This gave me the impression you're using the Z shell.
The C shell says:
% vi!
vi!: Command not found.
And bash says:
$ vi!
bash: vi!: command not found
So the shell that says zsh should be the Z shell, or a different
shell that's just lying. :-)
with the bang stuff
if you do a
% !-3
you go back three vi cmds. !-N, N cmds.
Yes, this also works in C shell. You can use the h (or history)
builtin command to get an impression of content of the last commands
submitted to the shell.
At least in csh,
% !-1
equals
% !!
and repeats the last command.
You could use the following command to print the last 20 commands
with the relative number (-1, -2, -3 and so on) printed infront of
them:
% history 20 | awk 'BEGIN {cmds=20} { printf(\t%2d\t%s\n, -(cmds-i),
$0); i++ }'
It's probably a good idea to define an alias for that, like h20
(history of last 20 commands).
You could also use the zsh's equivalent of the precmd alias: It
is a command that will be executed prior to displaying the shell
prompt, so after you're done with a command, the last commands
(maybe shortened to 10, just substitute the two appearances of
the 20 to 10) will be displayed before the prompt appears;
this will make it easier (and save keystrokes) to check the last
commands and maybe repeat one.
Downside: The command pollutes the list of commands with itself,
so it should probably be grepped away.
% history 20 | awk 'BEGIN {cmds=20} { printf(\t%2d\t%s\n, -(cmds-i),
$0); i++ }' | grep -v history
It might be good to define a better exclusion pattern than just
history because that might lead to false-positives. I'd suggest
to rename the variables in the awk script to something unique and
then grep for those instead...
thankfully there are shortcuts!
And shell aliases. :-)
ps: zsh is sort of a ksh clone; I remember porting the zsh onto
my 286 in 1989. got a lot of csh-isms :)
The Z shell combines nice interactive features of the C shell
(to be correct: the tcsh) and the scripting features of sh and
bash. It's considered one of the most powerful shells. So it's
a wise move to use it, because it combines the _good_ things of
both worlds (and not the bad things, as the csh is a terrible
scripting shell, just as plain sh is an awful dialog shell).
--
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: Voice Mail required QuickTime
On Thu, 26 Sep 2013 13:54:34 -0400, Carmel wrote: I have a voice mail account with Time Warner Cable. I can access the account from my home telephone, Windows PC, etcetera, but not from my FreeBSD machine. This error message pops up when I try to play the recording on the web site: To play audio online, you must have QuickTime Player installed. How can I make this work from my FreeBSD machine? Without any experience with the service you've mentioned, I'd suggest using mplayer, because mplayer plays everything. As far as I know, there's also an mplayer plugin for web browsers (probably Firefox) that can be used to play QT content embedded in web pages. Note that this might involve recompiling mplayer with the proper options set, as QT is probably not part of the defaults. (By the way, it's strange that QT is used for this purpose, I would have assumed that the codec of choice would still be MP3...) There's also the libquicktime and openquicktime libraries in ports which _maybe_ allow a better in-browser experience to handle that proprietary format. If the web page to access the service is really that backward oriented that it _requires_ the actual QT player, then I'd say that Time Warner Cable needs a friendly reminder to make the transition to _standard_ HTML-compatible formats that have less restrictions in your rights to use _your_ voice mail - even if it's just a stupid MP3 download or something comparable. Everyone else on the planet can already play audio data via web pages without QT for decades. :-) -- 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: minor vi/vim qstn
On Thu, 26 Sep 2013 12:51:32 -0700, Gary Kline wrote:
my zsh does a default to 10 or so history with just
% h
I was trying to remember how to set it to ,, say, 100.
Depending on _typical_ terminal heights (100 lines?), this
seems to be a bit high. But I assume zsh handles the h
alias similarly to the csh, where an alias is defined
(system-wide in /etc/csh.cshrc or per user in ~/.cshrc).
Look for ~/.zshrc (if I remember correctly):
alias h 'history 25'
and change it accordingly. An interactive change is also
possible (but will only be kept for the current session).
I also assume the zsh has some settings on how many commands
should be kept in history. The system's /etc/csh.cshrc provides
the csh's equivalent:
set history = 100
set savehist = 100
Probably zsh has something similar.
(for as many centuries as ive been using vi [nvi], there are
*still* things I never had need to learn. so it turns out that
a lot of theses clever sh scripts are over my head it
takes mins - hours to figure out.
You notice that you're saying that to a programmer whose
shell scripts are usually overcomplicated, dull, and could
use lots of optimization? ;-)
% history 20 | awk 'BEGIN {cmds=20} { printf(\t%2d\t%s\n, -(cmds-i),
$0); i++ }' | grep -v history
It might be good to define a better exclusion pattern than just
history because that might lead to false-positives. I'd suggest
to rename the variables in the awk script to something unique and
then grep for those instead...
I have grep -v aliased to grv.
If you're using that alias inside another alias, zsh (if it
acts like csh) will expand it properly. Using such an alias
in a one-time entry (as I'd consider an addition to a
configuration file) still doesn't sound optimal regarding
readability and maintainability. As if we would ever maintain
our naturally grown (over centuries) configuration files... ;-)
Still I think turning the example into a shell alias (h20) or
assigning it (with 20 - 10) to the precmd alias could not
be trivial, at least regarding the C shell, because lots of
quoting and escaping would be needed; maybe zsh does not behave
like a madman in this regards (unmatched this, unmatched that,
sytax error, cannot expand, missing argument, blah ...). :-)
--
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: minor vi/vim qstn
On Thu, 26 Sep 2013 13:58:19 -0700, Gary Kline wrote:
Organization: Thought Unlimited. Public service Unix since 1986.
Of_Interest: With 27 years of service to the Unix community.
On Thu, Sep 26, 2013 at 10:05:06PM +0200, Polytropon wrote:
I also assume the zsh has some settings on how many commands
should be kept in history. The system's /etc/csh.cshrc provides
the csh's equivalent:
set history = 100
set savehist = 100
I'remember seeing this a long time ago. in my ~/.zshrc I've got
iit in all CAPS.
HISTFILE=~/.zhistory
SAVEHIST='5000'
HISTSIZE=1000
got to google this; been tooo long since I glanced at the code!
That's probably correct, it reflects the sh-like aspects
of code (as I said, csh is a terrible scripting shell, and
this is also true regarding its configuration files). So
those entries look correct.
I'm not a zsh user, so I can't say this for sure. I'm heavily
infected with csh already. ;-)
On Thu, 26 Sep 2013 14:15:17 -0700, Gary Kline wrote:
FWIW, I just tried:
alias -- h='history 50'
works as it ought; last time I tried, the history quit
after ~10. [?]
The reason might be that the history, at this point in time,
did only contain 10 entries. I don't know how the content
of ~/.zhistory behaves if more than one shell is running
for a given user...
The Z shell is very customizable and can automate routine
tasks (regarding the shell dialog) in a pleasant manner.
If you want the last 10 commands to be displayed before the
shell prompt appears, try something like this in ~/.zshrc:
function precmd {
history 10 | awk 'BEGIN {histcmds=10} { printf(\t%2d\t%s\n,
-(histcmds-i), $0); i++ }' | grep -v histcmds
}
Not tested, but it seems to be much easier as zsh simply
defines a function precmd and doesn't require the user
to fight with quotes, doublequotes and escaping as csh
successfully does. :-)
--
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: minor vi/vim qstn
On Wed, 25 Sep 2013 14:27:41 -0700, Gary Kline wrote: am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. To repeat the last command, . can be used. The vi editor (and probably vim and gvim) supports according to man vi: [Vi]i[sual][!] [+cmd] [file] Vi mode only. Edit a new file. Is this what you're searching for? Or do you refer to command lines where @: would repeat the last command (started with :)? -- 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: minor vi/vim qstn
On Wed, 25 Sep 2013 17:21:04 -0700, Gary Kline wrote: Organization: Thought Unlimited. Public service Unix since 1986. Of_Interest: With 27 years of service to the Unix community. On Thu, Sep 26, 2013 at 12:23:27AM +0200, Polytropon wrote: On Wed, 25 Sep 2013 14:27:41 -0700, Gary Kline wrote: am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. To repeat the last command, . can be used. The vi editor (and probably vim and gvim) supports according to man vi: [Vi]i[sual][!] [+cmd] [file] Vi mode only. Edit a new file. Is this what you're searching for? I THOGoHT it was !, but lookit: pts/14 17:11 tao [5010] vi sent pts/14 17:11 tao [5011] vi! zsh: command not found: vi! pts/14 17:12 tao [5012] ... this is vi == vim. AHA:: found it. it's [bang]commant pts/14 17:17 tao [5016] vi sent pts/14 17:17 tao [5017] !v I'll tell ya, if vi disappeared , I'd end it all! Ah, I see - you've been refering to repeating a _shell_ command (so the question was regarding the shell, which in your case is Z shell). You can probably use (like in the C shell) the arrow keys to browse the command history. Similarly, you can use the !number command refering to the command number obtained by the history command. There's a handy alias defined globally for the C shell: h which means history 25 (lists the last 25 commands), handy in regards of saving keystrokes. :-) I assume the zsh is also capable of filtered history: For example, you enter vi s and use the up and down arrow keys to browse all commands that have been entered starting with vi s (for example vi sent, vi stuff and so on). If the system's csh can do this, zsh should also provide this useful feature. And as your prompt pts/14 17:12 tao [5012] suggests, the command number is being shown. If this information is the same as the command number in the history, entering !5010 would execute the 2nd from last command. To repeat the last command, whatever it has been, !! can be used. Again, this works in csh, so I can't predict if it will work in zsh too, but I _assume_ it does. -- 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: dangerously dedicated physical disks.
On Sun, 22 Sep 2013 08:25:24 -0600 (MDT), Warren Block wrote: It's dangerous because that partitioning format is rare outside of BSD-based systems. Disk utilities may not recognize it, and could damage it. I think this is a good characterization of the term currently used. In historical context this layout would deserve the name traditional, as non-PC BSD installations did not _require_ a MBR enclosing to be present - this is a concept introduced by the PC world. Most PCs still work with dedicated perfectly well if desired (even though there is no real reason to use that layout approach). I try to avoid the part dangerously because the danger is only significant in non-BSD land, like some obscure systems that could try to repair something and cause data loss, which is well known and feared... :-) Most of the rest of the world used MBR partitioning, which allowed up to four MBR partitions (called slices by FreeBSD) per disk. Those are, precisely called DOS primary partitions (in difference to DOS extended partitions which somehow behave like slices in BSD terminology). :-) Yes, one partition format inside another. It only seems complicated because it is. Which makes it useful and flexible. :-) With GPT, there is no reason to use BSD disklabels at all. And most modern computers do not have any problem booting it. The old MBR approach (as well as dedicated) will probably only be needed in niche applications and exceptions. You can have all the advantages of being easy stuff known from dedicated layout by using the GPT tools, plus you gain more compatibility if this matters. -- 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: history
On Thu, 19 Sep 2013 19:36:43 +, william benton wrote: when I log into free bsd I am in the sh shell. i type history at the command line and the machine says history not found. If I type h at the command line it works like i expect the history command to work. That is strange. The sh shell (system scripting shell and emergency dialog shell in SUM) does not have a history function. % sh $ h h: not found $ history history: not found $ _ In the csh or tcsh shells history works as well as h. This is correct. A system-wide alias is defined for those shells: alias h 'history 25' It can be found in /etc/csh.cshrc. why does entering history at the command line work in the csh and tcsh shells but not in the sh shell. The sh shell (Bourne-like shell, actually a derivate of ash) does not have this functionality. Bash, the Bourne-again shell, supports the history function internally, and a h alias can be defined for this shell. % bash $ history [...] 501 history $ _ Considering that all three shells seem to have the same .cshrc file? They don't. The csh and tcsh (system default dialog shell) use the cshrc mechanism (/etc/csh.cshrc for global settings, .cshrc for user settings, and .login and .logout for interactive shells), while sh uses /etc/profile and .profile and .shrc similarly. Bash uses .profile as well as .bash_profile and .bash_login in a comparable manner. -- 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: FreeBSD stuck during the boot process.
On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote: When I try to boot FreeBSD from a USB stick, it stuck during the boot process. But if I boot it in safe mode, it succeeds to boot. How can I figure out what's wrong with the standard boot process? I can't even log the boot messages since the computer stuck and not respond. You could try a verbose boot (equivalent: boot -v) and see _when_ the system stops resonding. It would help to post the error message (last lines of console output) to the list to get a better impression about what's happening. If I remember correctly, safe mode refers to the mode with ACPI disabled, right? In this case, it _could_ be an ACPI problem (a really wild guess, as you have provided no information about the system you are trying to boot FreeBSD on). -- 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: test if script called by cron
On Mon, 16 Sep 2013 12:26:59 +0100, Paul Macdonald wrote: Is there a simple way of testing whether a given script was called via cron, I'd rather find a solution that would work from within the script rather than setting an environment variable in the crontab. I'd suggest the script creates a file (lock file or, much easier, just a simple normal file) at its beginning: #!/bin/sh /usr/bin/touch /tmp/scriptrun # ... your script content here ... You could also output the date command to that file to see when the script has been called: #!/bin/sh /bin/date +%Y-%m-%d %H:%M:%S /tmp/scriptrun # ... your script content here ... Of course you would have to manually remove that file after you have verified its existence and content. -- 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: persistence in freeBSD
On Mon, 16 Sep 2013 20:32:43 -, atar wrote: What does the '-u' option do? I've not find in the 'mount' man page any explanation on this option. That's strange. I'm currently looking at man mount on a FreeBSD 8.2 system and the following paragraph is readable: -u The -u flag indicates that the status of an already mounted file system should be changed. Any of the options discussed above (the -o option) may be changed; also a file system can be changed from read-only to read-write or vice versa. An attempt to change from read-write to read-only will fail if any files on the file system are currently open for writing unless the -f flag is also specified. The set of options is determined by applying the options specified in the argument to -o and finally applying the -r or -w option. The -u flag is referenced in other sections of the manpage. -- 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: Migration TeX/LaTeX: from teTeX -- TeXlive
On Mon, 16 Sep 2013 20:33:15 +0200, Roland Smith wrote: On Mon, Sep 16, 2013 at 01:57:51AM +0200, Polytropon wrote: On Sun, 15 Sep 2013 21:00:22 +0200, Roland Smith wrote: Personally I don't think TeX is a good fit for the ports tree (because of duplication of effort). I have to add that I think that the chosen strategy (provide a full port and a minimal port) is a good balance between functionality and maintenance workload. This is a good approach for all cases where no custom configuration (being done by tlmgr) has been done, and it should work for most scenarios, I assume. In conclusion, that could be said about many other software that brings its own package management. More or less. Not all of those work equally well as tlmgr or the ports tree. Of course; think about pip, npm, and the like. The preferred goal of using tlmgr from the TeXLive distribution instead of installing it with the ports tree (or pkg) would be that it somehow at least records the existence of the TeXLive installation on the system. This causes ports depending on it _not_ to attempt any futile additional installation. Of course, LaTeX is a big and complex beast that TeXLive manages well (instead of the system-provided tools for managing the ports tree). In my opinion, a good _integration with_ the ports tree is important, so dependencies will be resolved properly (and you won't end up havong both TeXLive _and_ teTeX on your system for no particular need). The problem is that if you hand over the management of the TeXLive install to tlmgr, the ports tree doesn't know and cannot know what is provided and what is depended on... Correct. As I said, I'd suggest tlmgr could honor that case if it is run on FreeBSD and update the system records accordingly, so port management and pkg can work with that foreign installation as if it would have been a valid installation done with the system's default means. On the other hand, this might introduce demands of other software compilations to move their management out of the system's range, so we end up micro-managing many different sets of software in their own specific way, abandoning the centralized means of maintaining our software... There is indeed no silver bullet. True. However, a good integration with keeping an eye on the most obvious and important side effects could help. For example, the TEX_DEFAULT setting in /etc/make.conf is already a good beginning to select between teTeX and TeXLive. Maybe something similar could be added by tlmgr to satisfy port and package management tools with the illusion that everything went fine? :-) Since TeXLive is very complete and self-contained, I don't have other ports that depend on TeX. It's the port maintainers' task to take care of the proper declaration of dependencies, and for system tools to handle them. I don't think it is a big problem to make this consistent with how TeXLive handles things. It is not that simple. After every tlmgr run, you'd have to generate a new plist for the port. Since TeXLive is contained in one directory tree (/usr/local/texlive/year) that part is relatively simple. But tlmgr can also install scripts or binaries. So after every tlmgr run, the list of binaries that the port provides and the list of libraries or interpreters (ports) that it requires would have to be updated. This is not trivial. I recognize that complicated task, but I would like to say that solving that problem (or at least possible annoyance) would really benefit both worlds - TeXLive can be managed with tlmgr _and_ the system software records will keep working properly. -- 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: test if script called by cron
On Mon, 16 Sep 2013 23:28:17 -0400, kpn...@pobox.com wrote: On Mon, Sep 16, 2013 at 02:05:04PM +0200, Polytropon wrote: On Mon, 16 Sep 2013 12:26:59 +0100, Paul Macdonald wrote: Is there a simple way of testing whether a given script was called via cron, I'd rather find a solution that would work from within the script rather than setting an environment variable in the crontab. I'd suggest the script creates a file (lock file or, much easier, just a simple normal file) at its beginning: #!/bin/sh /usr/bin/touch /tmp/scriptrun # ... your script content here ... Wouldn't the lockf command be better than touch? That way you get the condition code telling you whether or not the script is already running. Yes, it would probably be better in this case. This, in combination with the suggestion of test-t 0 to check if the script has been interactively called or not, looks like a better solution. However, the intial question does not make fully sure (at least to me as a non-native speaker) if the intention is (a) to check _if_ the script has been run via cron, or (b) to check if the script has been run via _cron_. :-) Of course you would have to manually remove that file after you have verified its existence and content. If you use lockf as a drop-in replacement for touch then, yes, you'll need to keep the lock file until removing it at the end of the script. Depends. Let's say the script is scheduled at 3:00 and will finish in about half an hour. The evidence file will only be visible from 3:00 to ca. 3:30, so removing the evidence file after the script has finished could lead to a false-negative result (has not been run). This is also true for the more simple solution using the touch command (no rm call at the end of the script). -- 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: howto kill x if x is running?
On Sat, 14 Sep 2013 23:20:46 -0700, Gary Kline wrote:
say that I have a utility xxx running sometimes. xxx is
soaking up a chunk of my load. I have to use top to find if
xxx is running, then kill -9 to kill xxx and have a steady load of,
say, between 0.10 and 0.15. what's the script that can do this?
Quick and dirty, needs adjustments. Repeat the following
(endless loop, depending on the shell you're using):
top -n | awk '/%/ { load=$11; sub(%, , load); sub(\\., , load);
if(load 1000 load 1500) print $1 }' | xargs kill -9
The margin is coded in the conditional: 1000 means 10.00% WCPU
(load 0.10), 1500 means 15.00% WCPU (load 0.15). You will have
to set the valid load accordingly.
Done some minor testing, killed my media player (as expected).
I'm sure someone will present a much better, less dirtier
approach to accomplish the requested task. :-)
--
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: Migration TeX/LaTeX: from teTeX -- TeXlive
On Sun, 15 Sep 2013 21:00:22 +0200, Roland Smith wrote: Personally I don't think TeX is a good fit for the ports tree (because of duplication of effort). In conclusion, that could be said about many other software that brings its own package management. Of course, LaTeX is a big and complex beast that TeXLive manages well (instead of the system-provided tools for managing the ports tree). In my opinion, a good _integration with_ the ports tree is important, so dependencies will be resolved properly (and you won't end up havong both TeXLive _and_ teTeX on your system for no particular need). On the other hand, this might introduce demands of other software compilations to move their management out of the system's range, so we end up micro-managing many different sets of software in their own specific way, abandoning the centralized means of maintaining our software... I installed TeXLive using its own installer long before it was present in the ports tree. It should maybe be possible (and encouraged?) to use a concept like using the ports tree for invoking the TeXLive custom installer, so you don't have to manually download and extract stuff, a simple make install from the ports tree would do that for you. However, the TeXLive installer co-operates well with FreeBSD, so it's not a big problem to get TeXLive installed and running. Since TeXLive is very complete and self-contained, I don't have other ports that depend on TeX. It's the port maintainers' task to take care of the proper declaration of dependencies, and for system tools to handle them. I don't think it is a big problem to make this consistent with how TeXLive handles things. I am certain that TeXLive has pre-built binaries for FreeBSD 9, but I don't know about CURRENT. It would be even more greaterer to have pkg add texlive working, performing the download, and installing the FreeBSD binaries and libraries as needed, while keeping the system records intact. :-) To see which ports require (parts of) teTeX, use `pkg_info -Rx tetex` Plus `pkg_info -Rx teTeX` because of the way it is spelled. :-) -- 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: cant mount CD
On Thu, 12 Sep 2013 10:13:28 +0200, Matthias Apitz wrote: # mount -t cd9660 -o -e /dev/acd0 /mnt mount_cd9660: /dev/acd0: Invalid argument Try cd instead of acd. The acd interface has been deprecated in favour of SCSI over ATA for optical devices (including ATAPI CD and DVD drives). # mount_cd9660 -e /dev/cd0 /mnt In case the extended attributes cause problems, try first without using them in the normal way: # mount -t cd9660 -o ro /dev/cd0 /mnt Permission problems should not count here. Also make sure it's really an ISO-9660 file system: % file -s /dev/acd0 /dev/acd0: ISO 9660 CD-ROM filesystem data '0110241307 This example from a 8.2 system where the acd subsystem is still being used. :-) the 'cdrecord -minfo' command gives lines in /var/log/messages as: Sep 12 10:09:36 vm-9Current kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 Sep 12 10:09:36 vm-9Current kernel: acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 Sep 12 10:09:36 vm-9Current kernel: acd0: FAILURE - START_STOP ILLEGAL REQUEST asc=0x24 ascq=0x00 Sep 12 10:09:36 vm-9Current kernel: acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 Proper cabling? Drive and media not covered with dust? ;-) -- 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: initialize msdosfs on memory stick?
On Thu, 12 Sep 2013 16:13:11 -0600, Gary Aitken wrote: On 09/12/13 15:51, Polytropon wrote: On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: I can't seem to find how to do this in the handbook or man pages. I need to initialize a usb memory stick with an msdos file system. Is it possible, or do I have to find a windoze system? It is possible. The OS provides the newfs_msdos tool. There is no need to deal with Windows for this task. Great, thanks. I checked the newfs manpage but didn't look too carefully when the summary line said construct a new UFS1/UFS2 file system That's correct: newfs refers to newfs_ufs (which obviously initializes a UFS file system), but there are other newfs_* just as there are corresponding (and more) mount_* commands. See man newfs_msdos for more details. -- 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: initialize msdosfs on memory stick?
On Thu, 12 Sep 2013 15:39:26 -0600, Gary Aitken wrote: I can't seem to find how to do this in the handbook or man pages. I need to initialize a usb memory stick with an msdos file system. Is it possible, or do I have to find a windoze system? It is possible. The OS provides the newfs_msdos tool. There is no need to deal with Windows for this task. -- 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: mount: /dev/ada0p1: Device busy Busy with what?
On Fri, 13 Sep 2013 00:54:01 +0200, Per olof Ljungmark wrote: I have apart from the boot drives a SATA disk for storage. Usually I would mount it with mount /dev/ada0p1 /archive but as my last reboot into FreeBSD 9.1-STABLE #0 r252369 I cannot mount the disk, I get mount: /dev/ada0p1: Device busy Well, busy with what? fuser -m /dev/ada0p1 /dev/ada0p1: I REALLY need to acces trhis UFS formatted drive, how can I convice it that everything is ok and it's not really busy with anything? Could anyone please help to sort this please? Maybe a fsck is running on the disk device? Also check mount -v if the disk is really unmounted. Make sure any running fsck has been finished and try again. In worst case, manually initiate a file system check. Then try mounting the disk again. -- 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: question
On Wed, 11 Sep 2013 09:41:31 +0200, Pawel Sulewski wrote: How to recognize kernel panic and dump memory state onto USB device using C language? The kernel has its own crash handling and will initiate the writing of the proper image automatically. It will be stored on the partition designated by the /etc/rc.conf setting dumpdev=device, usually a swap partition, and at next boot time that image will be written to a file in /var/crash, if nothing else has been defined with dumpdir=directory (same file; see man rc.conf and /etc/defaults/rc.conf for details). If you want to coredump to a USB device, you need to configure this accordingly. You can find more information about this topic in the following manual pages: man 2 sigaction, man 8 crash, and man 5 core. -- 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: Proper way to share ZFS via NFS
On Tue, 10 Sep 2013 12:10:13 +0100, krad wrote: which is why you shouldnt use /etc/exports for zfs datasets. Just because you can do something doesn't mean you should eg dancing down the motorway at night in dark clothing is never a good idea, no matter how confident you are in your skills. ZFS _encourages_ the use of its own toolset instead of those known from UFS. This includes the file system handling as well as backup/restore processes, mounting and exporting. ZFS has its own equivalents for those things. It's probably the best choice to use the _right_ tools here. :-) -- 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: ufs recovery
On Tue, 10 Sep 2013 22:38:46 +0200, Laszlo Danielisz wrote: Dear All, It looks like I'm able to recover all of the deleted files. I'm using UFS Explorer Professional Recovery, I'm working on it for more than 30 hours, its a long time but it works! If recovery works, time does not matter. Success does. :-) -- 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: lpd(8) sending email to the wrong address
On Tue, 10 Sep 2013 11:44:09 +0700, Olivier Nicole wrote: When a print job is failing, lpr will try to send a warning email to user@client but that e,ail address does not exist; is there a way to send email at user@default.domain instead? Depending on your sendmail setup, you could probably use an alias for those specific cases (via /var/mail/aliases). Because sendmail and lpr should match archaic-wise... :-) -- 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: ufs recovery
On Sun, 8 Sep 2013 11:39:08 +0200, Laszlo Danielisz wrote: Hi Frank, Thank you very much for the information! Meanwhile I've found this software: http://www.ufsexplorer.com/, I'm going to give a try. That program was on my famous list of recovery tools for futile attempts. :-) I may say that I have the same problem (of unclear origin). Files have been removed, but the assumption that the data could still be somewhere is alive. In such situations, you would usually have two choices: 1. money Get as much money as you can. You'll need it. Several 1000 euro / dollar / local currency will buy you service at a company specialized in recovery. There is no guarantee they will be successful. 2. time You invest time in learning how UFS works. There are many excellent articles (especially the authoritative one by M. K. McKusick). You try out different tools (with different scope). If you are lucky, you get your data back. (I was lucky once, got my data back!) There are _many_ good tools around. Most of them are free, so you don't need to invest massive amounts of money in a repeating trial error process. Allow me to repeat my list (which gets a little bit modified each time I post it to this list): OS tools: fetch -rR device recoverdisk Ports collection: ddrescue dd_rescue - use this to create images to work with magicrescue testdisk- restores content recoverjpeg foremost photorec ffs2recov scan_ffs tsk - The Sleuth Kit fls dls ils autopsy There are some commercial tools worth mentioning: UFS Explorer can be run in wine. It probably won't restore your data, but it can be used to determine if there is something to restore. Also consider R-Studio and R-Studio Emergency (live CD). Those offer free versions that can be used for testing. Finally, I'd like to mention The Sleuth Kit. It's one of the most powerful toolsets, also used in forensics and investigation. As I said, I ran into a similar problem (files deleted). Maybe you can find this discussion thread in the archives and gain some more inspiration from it. A massive data loss (meanwhile cured!) brought me to this list, so I continue to spread my experience about recovery when needed. :-) Good luck! -- 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: Question about those special (countdown numbers) at shutdown / sync
On Thu, 5 Sep 2013 21:30:29 +0800 (SGT), Patrick Dung wrote: I am curious about the special (count down numbers) at shutdown / sync. Those nubmers is like 8 8 8 8 2 1 2 1 0 0 0 0. Actually what do those numbers mean? Those numbers show you how many buffers have to be synced until the system is ready to finally shut down and power off. This makes sure no pending hard disk operations will be left and forgotten in memory. The important text displayed prior to the numbers is: Syncing disks, buffers remaining... You can find it here: /usr/src/sys/kern/kern_shutdown.c around line 330 (8-STABLE/i386 here). -- 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: Setup HP Laserjet 1120m over network with LPD
On Tue, 20 Aug 2013 07:31:09 -0600 (MDT), Warren Block wrote: I would get the filter working alone before involving the extra complication of lpd. The documentation at the foo2xqx home page may help: http://foo2xqx.rkkda.com/ That is a good advice. I'd suggest to use a PS test page as input, let it run through the filter, and send its output directly to the printer (with netcat if networked, with to /dev/lpt or /dev/ulpt if local). If _that_ part is working, integrate it with the LPD subsystem or CUPS. -- 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: undelete files in msdosfs
On Sun, 18 Aug 2013 19:00:39 +0200, Matthias Apitz wrote: After a nice day in the fields, my wife deleted accidently the pictures in her cam; the microSD mounts fine in FreeBSD as -t msdosfs; do we have some FreeBSD 10-CUR tool to undelete the files, as there are some for M$? We have plenty of them. From my unbelievable list of tools for data recovery and regarding that you are trying to recover files from a camera: photorec. It's in the ports collection. In the same context, magicrescue is worth mentioning. If they all fail, consider using TSK. Note: Do _not_ do ANY writes to the card! Mount it -o ro if needed. Make an 1:1 copy (using dd_rescue from ports), work with that copy. Everything that slips through fat fingers could reduce the chance of a successful recovery session. I know 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: undelete files in msdosfs
On Sun, 18 Aug 2013 20:28:53 +0100, Frank Leonhardt wrote: I wrote something to do this a long time back, but I doubt I can find the source quickly. The easiest way would be to download a forensic live-CD like DEFT, which includes Undelete 360. Possibly over-kill but it's handy to have one around. Most of these forensic tools use a GUI. Or UBCD, if I remember correctly. It also offers some of those tools, usually the text-mode variants (not CLI, but dialog-driven) which allow you to perform the tasks quickly and safely. There is a program called fatback in the ports collection but I haven't tried it. The tools on these forensic live-CDs are likely to be more powerful by a long way. Most of the programs can be used from within FreeBSD. As I said, there are many of those available for free. Some of them require the user to _know_ what he does. The more complex the recovery task is, the more knowledge is involved. GUIs are good to hide this fact, and in worst case, you lose your data. Of course there is no problem delegating the recovery task to a service center for $$$. And sometimes, if you look close enough, you can see that those are using the free tools. :-) -- 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: undelete files in msdosfs
On Sun, 18 Aug 2013 15:01:37 -0500, iamatt wrote: Its called backups. Not trying to be a dick but it's 2013. Not 1983. But it doesn't help when Johnny Fatfingers presses the wrong buttons on the camera _prior_ to archiving the photos. :-) Plenty of online backup/archive options. And local options, because you have to trust your online backup provider (except it's _yourself_ who provides and maintains the systems). As always. Test restores periodically. A backup that cannot be restored is _not_ a backup. :-) -- 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: undelete files in msdosfs
On Sun, 18 Aug 2013 22:09:57 +0200, CeDeROM wrote: On Sun, Aug 18, 2013 at 7:00 PM, Matthias Apitz g...@unixarea.de wrote: After a nice day in the fields, my wife deleted accidently the pictures in her cam; the microSD mounts fine in FreeBSD as -t msdosfs; do we have some FreeBSD 10-CUR tool to undelete the files, as there are some for M$? /usr/ports/sysutils/testdisk http://www.cgsecurity.org/wiki/TestDisk That one is also on my famous list, and if I remember correctly, also part of the UBCD for OS-less use. :-) -- 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: freebsd 9.2 via svn
On Mon, 19 Aug 2013 02:28:25 +0100, John wrote: Is it safe to start using 9.2 in the svn repos? I have a line like this in a daily crontab: svn co svn://svn.us-east.freebsd.org/base/releng/9.1 /usr/src Can I change that 9.1 to 9.2 now, or should I wait? I aim to follow 9.2-R with security updates. 9.2-RELEASE hasn't been released yet. :-) http://www.freebsd.org/releases/9.2R/schedule.html If you don't use a custom kernel, why not use freebsd-update and follow the 9.2-RELEASE path with the security updates? -- 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: freebsd 9.2 via svn
On Mon, 19 Aug 2013 04:22:15 +0100, John wrote: If you don't use a custom kernel, why not use freebsd-update and follow the 9.2-RELEASE path with the security updates? Not sure if this is logic or religon, but freebsd-update makes me nervous. I'm allergic to automatic anything unless I've written it. The only times I've run generic is when installing a new system, to see what I need and what I don't. Maybe I'm just old. You demonstrated a valid argument for building from source. Using freebsd-update, a binary method is used for updating the _default_ system and the GENERIC kernel. If you have custom settings and therefore _intend_ to build from source, changing the version in your svn co command to the new -RELEASE-pX branch (security update branch) is safe. I've been using a similar approach with CVS to follow the -STABLE branch with a custom kernel and custom settings for building the system. If this makes me old, I should deserve several birthday parties per year. ;-) -- 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: Mouse Trails?
On Sat, 17 Aug 2013 09:07:20 + (UTC), Walter Hurry wrote: My sight is deteriorating. I can still see and read the screen, but sometimes locating the mouse pointer (LXDE here) is difficult. If LXDE uses an ugly white mouse cursor, try changing it to black (the normal color for mouse cursors on all serious GUI systems). The classical way of solving the where is the mouse cursor problem is to install xeyes. :-) Is there a port which will give me mouse trails when the rodent is moved? This is usually done by the means of the desktop environment's mouse configuration, but if I remember correctly, LXDE does not offer this. Additional software like Compiz could help you here: There seems to be a plugin that adds a mouse trail. -- 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: Mouse Trails?
On Sun, 18 Aug 2013 03:08:16 +0200, cpghost wrote: On 08/17/13 18:14, Walter Hurry wrote: On Sat, 17 Aug 2013 17:31:26 +0200, Polytropon wrote: If LXDE uses an ugly white mouse cursor, try changing it to black (the normal color for mouse cursors on all serious GUI systems). The classical way of solving the where is the mouse cursor problem is to install xeyes. :-) I am reluctant to install Compiz, but xeyes looks to be just the ticket! Good ole Xeyes... ;-) Old but still useful in specific cases. But beware, xeyes crashes X server right now! Using xeyes-1.1.1 xorg-server-1.7.7_8,1 on FreeBSD 9.2-PRERELEASE #0 r253323 Sat Jul 13 21:00:32 CEST 2013 amd64 WHAT?! Unbelievable... that such a simple program could crash the whole X server... Does this happen in similar programs (speyes, wmeyes, xeyes+) too? @Polytropon: what version of xeyes/xorg-server are you using? Currently none. My system is too old, I currently can't install any new software without reinstalling the whole system. Still on 8.2 at home, because I never touch a running system. :-) -- 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: Laptop Fn key causes X (Gnome 2) to sleep immediately
On Fri, 16 Aug 2013 13:25:41 +0200, Matthias Petermann wrote: Hi Adrian, Zitat von Adrian Chadd adr...@freebsd.org: Hi! I'm glad someone else is seeing this! I have the same behaviour with KDE4 on my T60 and T400. If I go to run amiwm (because hey, Workbench is awesome!) it doesn't happen. .. and bah, I wish the resume worked for you. It works fine for me on T42i, T60, T400. Thanks for your response. The fact it happens also in KDE appears interesting... so the root cause might exist in a component on top of pure X which is shared by Gnome and KDE. I have tested a Lenovo R61i running Xfce, and I don't experience the strange behaviour desribed. However, using the xev event tester, the keycode for the Fn key is being displayed as 227, and the KeyPress event is held (!) until the key is released, which means KeyPress and KeyRelease happen immediately after each other. Because my IBM T60p is still in the ICU, I can't test this, but I would assume to get a similar result. Hopefully some time suspend/resume will also work on the newer Lenovo models (I would be curious if the wakeup problem is Intel/KMS only or if also the NVidia models e.g. T430 NVS are affected). It would also be nice if as much as possible would work on the older models (including the docking stations), because Thinkpads seem to live much longer (and therefore will probably many more years in productive use), compared to their crappy competitors on the laptop market. :-) -- 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: Laptop Fn key causes X (Gnome 2) to sleep immediately
On Fri, 16 Aug 2013 11:24:51 -0700, Adrian Chadd wrote: ... xf86sleep as a keypress id? Yes, there are many of XF86... key symbols that can be associated to key codes. Probably this is some setting in Gnome or KDE (but not in other environments). You can use xev to check which symbol is associated to which key (or key combination, if this creates a new unique key event). -- 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: Laptop Fn key causes X (Gnome 2) to sleep immediately
On Fri, 16 Aug 2013 18:07:25 -0700, Adrian Chadd wrote: What keyboard / laptop has the key code '150' map to 'go to sleep' ? My Sun Type 7 USB keyboard has the Copy key at code 150... :-) -- 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: 9.2-RC1: Problem with Kernel
On Mon, 12 Aug 2013 21:01:14 + (UTC), Walter Hurry wrote: Sorry again. Anyway, I have it nailed down now. For anyone who is interested, the missing entry was: options ATA_CAM Correct. Line 84 and 264 have it commented out. This is the new method of talking to disk devices, similarly as the acd interface for optical media has been trans- formed into SCSI over ATA (ex device atapicam). So the disk drive has not been recognized by the kernel, therefore: No soup for you (i. e., no boot device). :-) -- 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: New to Free-BSD with questions.
On Sat, 10 Aug 2013 09:58:07 GMT, r_oliva...@juno.com wrote: New to Free-BSD. Downloaded a current ISO image and burned it to a DVD. System boots from DVD to command line mode. It should boot into a text mode installer. After installation, FreeBSD usually boots into a text mode (depending on what has been installed and configured already). Questions are: A.) Is Xwindows, (X11) included on the DVD copy? If I remember correctly, the required packages are part of the DVD #1. If you are already connected to the Internet, you can use that medium as installation source. Just a side note: PC-BSD, a system derived from FreeBSD, offers a graphical installer and a more tight integration with GUI-centric concepts (installs X automatically and even brings a desktop environment preinstalled). B.) If included, what command is used to start it? It depends. If you want to start X from a regular login shell, startx is used. But a display manager which maintains a GUI login (like xdm) can also be used. See the handbook for more details: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-install.html And don't miss the excellent FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ C.) What shell is installed as the standard shell in command line mode? FreeBSD's default dialog shell is the C Shell (more precisely, the tcsh). The command shell in single user mode (maintenance mode) is a plain Bourne-alike shell (sh), which is also the systems default scripting shell. You can install shells like ksh, zsh and bash if you like. D.) Is there a site that I can download a complete copy of the documentation for Free-BSD, as one file and not a series/set of separate files? Not that I know of, because the documentation on the web is primarily for use with a web browser, that's why it's hierarchically designed and separated. However, the documentation is part of the FreeBSD installation, and you can generate PS and PDF book, as _one_ (voluminous) file, from them (even though I've never tried that). You can use a tool like wget to download a copy of the web documentation for offline use (keeping the mentioned separation). The web pages contain a Split HTML and Single HTML option, so you could maybe simply save this web page http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html for the FAQ, and http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html for The FreeBSD Handbook, but it might be unhandy for printing. -- 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: 9.2-RC1: Problem with Kernel
On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote: This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the source from releng/9.2 and rebuilding kernel and world). The kernel compiles and runs fine using the supplied GENERIC, but when I try to use my custom kenel config file, on reboot I get this: Mounting from ufs:/dev/ada0p2 failed with error 19 What module(s) have I missed? Diff against the GENERIC kernel. Maybe device xhci? What bootable media is listed when you type ? at the mountroot prompt? If GENERIC boots and your kernel doesn't, there should be a significant difference regarding the config file's content. :-) -- 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: .sh script code to determine IPv4 or IPv6
On Tue, 06 Aug 2013 10:20:05 -0600, markham breitbach wrote: On 13-08-03 8:04 AM, Teske, Devin wrote: Actually, there's /usr/share/bsdconfig/media/tcpip.subr I don't seem to have that (FreeBSD 8.3-RELEASE). Where would I get that from? Maybe from sysutils/bsdconfig in the ports collection? I have not checked if this specific subroutine file is part of the port... -- 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: .sh script code to determine IPv4 or IPv6
On Tue, 6 Aug 2013 16:50:37 +, Teske, Devin wrote: And yes... to clarify... the port is a mirror of what's in 9.x base. (however, see my recent notes in a separate reply; TL;DR: port is 9.x only; proceed only if you know you don't care about the dialog(1) aspects of the library code). I think it should be relatively unproblematic to fetch the port and only use the subroutines as is, even if it's just for educational purposes. :-) -- 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: Setup HP Laserjet 1120m over network with LPD
On Tue, 6 Aug 2013 22:57:27 -0600 (MDT), Warren Block wrote: On Wed, 7 Aug 2013, Juris Kaminskis wrote: 2013. gada 6. aug. 23:17 Warren Block wbl...@wonkity.com rakst?ja: On Tue, 6 Aug 2013, Juris Kaminskis wrote: after several trials and errors and reading through FreeBSD handbook I am at dead end on how to proceed further, hope someone can guide me. Are you sure about that model number? I can't find specs for a Laserjet 1120M. There is a Laserjet M1120. It's a Winprinter. The file entries are confusing and use some non-base programs. You may be mixing the base system's lpr/lpd with the CUPS versions of the same names from ports. For plain lpr/lpd, I have this article: http://www.wonkity.com/~wblock/docs/html/lpdprinting.html Model number: HP LaserJet M1120n MFP I try your how-to in few days as it seems I need to redo whole config. I will post my results, thanks The Laserjet M1120 is a winprinter, which means it does not understand plain text or common PDLs like PCL or PostScript. There is print/foo2zjs in ports, but it's meant to be used with CUPS. I have not tested it. It seems that a HPLIP interface is available for this printer, so it should probably work with CUPS and _maybe_ with the normal means of printing (FreeBSD printer spooler plus a printer filter that turns PS, the _default_ output language for printing, into the specific non-standard language that printer wants to be spoken to in). http://hplipopensource.com/hplip-web/models/laserjet/hp_laserjet_m1120_mfp.html http://foo2xqx.rkkda.com/ I'm using a similar approach for a terrible Samsung color laserprinter (foo2qpdl-wrapper in my specific case) which I could easily integrate with the already mentioned CUPS, as well as the normal system's printer subsystem. However, I also have not tested if it works for the M1120, because I prefer to use printers that work, that's why I don't own such a thing. :-) -- 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: Assign program call to a key
On Sat, 3 Aug 2013 14:43:14 + (UTC), jb wrote: Polytropon freebsd at edvax.de writes: Is there a way to assign a predefined program call to a key in X, _independently_ from the window manager or desktop environment in use? ... https://wiki.archlinux.org/index.php/Extra_Keyboard_Keys_in_Xorg It may give you some hints. The last entries on the page look interesting, but keytouch and actkbd are not available, only xbindkeys is in the ports collection. From the description Allows you to launch shell commands under X with your keyboard it seems to be exactly what I'm looking for. Thanks for the *pointer! ;-) -- 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: hardware monitor
On Sun, 04 Aug 2013 14:48:56 -0600, Gary Aitken wrote: Can anyone suggest a hardware monitor app in the ports tree? I've got an amd64 which may have a temperature issue, but I can't see it to tell... If it's primarily about temperature... amdtemp (kernel module), healthd (system service), mbmon and xmbmon (in the ports collection). -- 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
Assign program call to a key
Is there a way to assign a predefined program call to a key in X, _independently_ from the window manager or desktop environment in use? Currently I'm using the following approach: In ~/.xmodmap, I define a symbol according to the keycode I found out by using the xev program: keycode 140 = F27 This file is activated by the xmodmap ~/.xmodmaprc command in ~/xinitrc (called via ~/xsession, cascaded). In WindowMaker's menu, I define a submenu Functions where I put the program calls I want to assign to keys, then use the Capture function and press the desired key. Now the association is made. Of course, this approach is _specific_ to WindowMaker! I'm searching for a way to do this among different environments in X without having to configure each one of them (or even being disappointed because this feature is not implemented). My goal is to make the volume keys of various laptops change the volume via the mixer command. Those keys are nothing special, they just send key codes. Similarly I want to use this with my Sun Type 7 USB keyboard. But I'd also like to make use of additional and multimedia keys on laptops that simply send key codes that can be assigned key names. -- 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: xcdroast cannot locate cdda2wav
On Tue, 30 Jul 2013 08:29:47 -0400, Jerry wrote: The xcdroast application use to work, but lately it has started to throw an error message. First, it would not let me start it unless I was root. I had long ago done the reacquired preliminary start-up as root. If you set device permissions properly, you should not have to do this (potentially dangerous) elevation of privileges. Now, when I attempt to start it as root, it emits this error message: ~ # xcdroast ** (xcdroast:96970): WARNING **: Invalid cdda2wav version -unknown- found. Expecting at least version 2.01 Start xcdroast with the -n option to override (not recommended!) ~ # cd /usr/ports/sysutils/xcdroast I have tried deleting the port and rebuilding it, but the same problem exists. That's a logical consequence, as cdda2wav is not part of this port, even though cdrtools is both defined as a build time and a runtime dependency... I have not been able to locate cdda2wav on the system or in a port. The cdda2wav program is part of the cdrtools port. Try updating that one. -- 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: xcdroast cannot locate cdda2wav
On Tue, 30 Jul 2013 10:36:37 -0400, Jerry wrote:
On Tue, 30 Jul 2013 14:37:38 +0200
Polytropon articulated:
The cdda2wav program is part of the cdrtools port.
Try updating that one.
Been there, done that, doesn't work. I am considering doing a forced
update of the xcdroast port and its dependencies via portupgrade.
That seems to be the best choice at the moment. The port's
Makefile contains --with-cdrtools-prefix=${LOCALBASE} which
suggests that the integration of cdrtools / cdda2wav might
already be important at compile time.
Also look at the option Use xcdroast w/o being root which
should enable you to use the program without being root (which
is not good in terms of security).
I
really hate wasting time like this, but I need the port to work.
This is a typical symptom of install once, then keep using,
and never touch it again. :-)
Interestingly enough, this is the output from cdda2wav:
# cdda2wav -version
cdda2wav 3.00 (amd64-unknown-freebsd8.3) Copyright (C) 1993-2004 Heiko
Ei�feldt (C) 2004-2010 J�rg Schilling
Defaults: stereo, 16 bit, 44100.00 Hz, track 1, no offset, one track,
type: wav filename: 'audio', don't wait for signal, not quiet,
use: 'generic_scsi', device:
'yourSCSI_Bus,yourSCSI_ID,yourSCSI_LUN', aux: ''
Obviously, it is installed.
Version 3.00 is better than 2.01 (required), so it should work.
But maybe xcdroast isn't just checking binary versions, but
also expects some kind of specific library version? At least
that kind of requirement should be resolved when you recompile
xcdroast _and_ its dependencies.
The xcdroast application suddenly cannot
locate it though or is not able to properly determine the version
number. I am thinking of filing a PR against it.
If an upgrade of all involved parts doesn't help, this seems
to be a good thing to do.
--
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: FreeBSD slices and the Boot Manager
On Mon, 29 Jul 2013 13:34:10 +0930, Shane Ambler wrote: On 29/07/2013 08:23, Polytropon wrote: On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote: In this case, sade is (or was) a direct by-product of the death of sysinstall(8). It only exists in 9 or higher. % which sade /usr/sbin/sade System is FreeBSD 8.2-STABLE of August 2011. I think sade has been introduced in a v8 version of FreeBSD. Or earlier. On 9.1 man sade says -- HISTORY This version of sade first appeared in FreeBSD 6.3. The code is extracted from the sysinstall(8) utility. Really _that_ old? I have to admit that I never really _knew_ about sade, and that is has been mentioned to me when I was already using FreeBSD 8.x, so my memory can be distorted in this regards. Out of lazyness, I've been using the corresponding functionality of sysinstall - formerly also known as /stand/sysinstall :-) - to access what sade can also do. -- 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: Unusual file: /bin/[
On Mon, 29 Jul 2013 14:25:08 +0100, Paul Macdonald wrote:
Hi, I spotted what i'd call an unusual file in the basejail on a jail
install, and have since seen this on other non jailed boxes.
-r-xr-xr-x 2 root wheel 11488 Jun 10 12:19 [
man [ reveals
test, [ -- condition evaluation utility
just checking thats all ok, and i've not been rooted!
The [ program is the same as the test program. It's
a valid file name and it's often used in shell scripts
instead of test.
% ll /bin/test /bin/\[
-r-xr-xr-x 2 root wheel 8336 2011-08-21 20:23:20 /bin/[*
-r-xr-xr-x 2 root wheel 8336 2011-08-21 20:23:20 /bin/test*
Consider shell scripts. When you have a script with something like
if [ -f bla.txt ]; then
... some stuff ...
fi
it is the same as
if test -f bla.txt; then
... some stuff ...
fi
It's also often being used like
[ -x blah.sh ] do_something
which is identical to calling test and acting upon the value
of the return code.
Nothing to worry here.
YOu can _always_ counter-check by building /usr/src/bin/test
from source and compare the resulting binary. Both /bin/[
and /bin/test are usually installed as hardlinks (two file
names for one / for _the same_ file), as seen in the
corresponding Makefile:
LINKS= ${BINDIR}/test ${BINDIR}/[
So it's not _that_ unusual. ;-)
--
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: FreeBSD slices and the Boot Manager
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote: Hi, I have a workstation with two factory installed hard disks. The first disk, ada0, is occupied by a Windows 7 Pro OS (mainly kept for the three year warranty of the workstation as Dell techs mostly speak the Microsoft language). It's just a series of pictures, not a language. ;-) Instead I have configured the BIOS to boot from the MBR on the second disk as I most of the time (99%) use FreeBSD. The MBR on ada1 was installed with sysinstall's option Install the FreeBSD Boot Manager, when I installed the FreeBSD 8.3-RELEASE. (The latest BIOS version 2.4.0 for Dell T1500 does not support UEFI/GPT/GUID.) The second disk ada1, now has three FreeBSD slices: 1) ada1s1 with FreeBSD 8.1-RELEASE 2) ada1s2 with FreeBSD 8.2-RELEASE 3) ada1s3 with FreeBSD 8.3-RELEASE I want to install the new FreeBSD 8.4-RELEASE on ada1s1 by overwriting the now existing two first slices. This means that ada1s3, must become ada1s2 instead. Is this possible to do? Why do you want to do this? If you keep the s1 slice, you can easily install FreeBSD 8.4 into that slice, leading to this result: 1) ada1s1 with FreeBSD 8.4-RELEASE 2) ada1s2 with FreeBSD 8.2-RELEASE 3) ada1s3 with FreeBSD 8.3-RELEASE Or is the numbering order important to you? You could even keep the partitioning inside s1, but there is no problem re-partitioning inside s1. A very important question is if sysinstall's option Install the FreeBSD Boot Manager detects that I have a FreeBSD 8.3 and detect it as slice 2 on disk 1? I'm not sure I'm following you correctly. The sysinstall program is considered obsolete, the new system installer is bsdinstall. So it becomes a boot option when I am rebooting? (Maybe the slice may come up as ad6s2, because AHCI in FreeBSD 8.4 isn't enabled at the time of the install.) That is a _good_ consideration! To make sure things work independently from boot-time recognition, use labels for the file system and then mount them by using the labels. Encode the OS version number in the labels, so it's even easier to deal with them. Use newfs -L on un-mounted partitions (you can do that from the install media). From the install media, you can easily go to the CLI and use the bsdlabel program to re-write the boot blocks and boot manager if needed. Can I mount ada1s2a (FreeBSD 8.3) from the newly installed FreeBSD 8.4 and edit my FreeBSD's 8.3-R /etc/fstab according to the new disk layout, and occasionally run FreeBSD 8.3 without problems? Or do I have to do more to get it to work? Yes, that should be possible. I don't see any problem because this is a UFS partition. As I mentioned earlier, if you apply labels to the partitions on the slices, it's even easier to determine _which_ 'a' partition (root partition) you are currently dealing with. And if you continue your installation scheme in further versions, you will be freed from remembering what OS version resides on what slice. You then simply do mount /dev/ufs/root83 /mnt; vi /mnt/etc/fstab and you _immediately_ know which installation you're currently dealing with. -- 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: FreeBSD slices and the Boot Manager
On Sun, 28 Jul 2013 08:18:39 -0600 (MDT), Warren Block wrote: On Sun, 28 Jul 2013, Polytropon wrote: On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote: A very important question is if sysinstall's option Install the FreeBSD Boot Manager detects that I have a FreeBSD 8.3 and detect it as slice 2 on disk 1? I'm not sure I'm following you correctly. The sysinstall program is considered obsolete, the new system installer is bsdinstall. AFAIK, sysinstall is still used in FreeBSD 8.X, and bsdinstall does not have a boot manager option anyway. Sometimes I'm confusing them, because I usually don't use the installer and usually use fdisk (if needed), bsdlabel and newfs. :-) So it becomes a boot option when I am rebooting? (Maybe the slice may come up as ad6s2, because AHCI in FreeBSD 8.4 isn't enabled at the time of the install.) Sorry, I don't understand this at all. AHCI should not be involved with identifying slices. Maybe the required device driver is not part of the 8.x GENERIC kernel? So for example a drive could come up either as /dev/ada0 or as /dev/ad6, depending on how the recognition order and PATA / SATA thing is handled by the system and its BIOS. Labels will work independently from wheather the device will be recognized as ATA disk (for example /dev/ad6s1a being the root disk) or SATA disk (where /dev/ada6s1 would be the root disk). -- 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: FreeBSD slices and the Boot Manager
On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote: In this case, sade is (or was) a direct by-product of the death of sysinstall(8). It only exists in 9 or higher. % which sade /usr/sbin/sade System is FreeBSD 8.2-STABLE of August 2011. I think sade has been introduced in a v8 version of FreeBSD. -- 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: Delete a directory, crash the system
On Sat, 27 Jul 2013 13:57:31 -0500, David Noel wrote: So the system panics in ufs_rmdir(). Maybe the filesystem is corrupt? Have you tried to fsck(8) it manually? fsck worked, though I had to boot from a USB image because I couldn't get into single user.. for some odd reason. From your initial description, a _severe_ file system defect seems to be a reasonable assumption. Make sure fsck is run in foreground prior to bringing up the system. The option background_fsck=NO in /etc/rc.conf will make sure you won't encounter this problem again (_if_ it was related to the file system). Always make sure you're booting into a fsck'ed environment. You could also use a S.M.A.R.T. analysis tool such as smartmon (from ports) to make sure the OS didn't panic because of a hard disk defect. I'm just mentioning this because I have sufficient exoerience in this field. :-) Even if the filesystem is corrupt, ufs_rmdir() shouldn't panic(), IMHO, but fail gracefully. Hmmm... Yeah, I was pretty surprised. I think I tried it like 3 times to be sure... and yeah, each time... kaboom! It's really surprising that a (comparable) high-level function could fail in that drastic way, but on the other hand, one would assume that there is a _reason_ for this behaviour. -- 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: Delete a directory, crash the system
And here, kids, you can see the strength of open source
operating system: You can see _why_ something happens. :-)
On Sat, 27 Jul 2013 20:35:09 +0100, Frank Leonhardt wrote:
On 27/07/2013 19:57, David Noel wrote:
So the system panics in ufs_rmdir(). Maybe the filesystem is
corrupt? Have you tried to fsck(8) it manually?
fsck worked, though I had to boot from a USB image because I couldn't
get into single user.. for some odd reason.
Even if the filesystem is corrupt, ufs_rmdir() shouldn't
panic(), IMHO, but fail gracefully. Hmmm...
Yeah, I was pretty surprised. I think I tried it like 3 times to be
sure... and yeah, each time... kaboom! Who'd have thought. Do I just
post this to the mailing list and hope some benevolent developer
stumbles upon it and takes it upon him/herself to fix this, or where
do I find the FreeBSD Suggestion Box? I guess I should file a Problem
Report and see what happens from there.
I was going to raise an issue when the discussion had died down to a
concensus. I also don't think it's reasonable for the kernel to bomb
when it encounters corruption on a disk.
If you want to patch it yourself, edit sys/ufs/ufs/ufs_vnops.c at around
line 2791 change:
if (dp-i_effnlink 3)
panic(ufs_dirrem: Bad link count %d on parent,
dp-i_effnlink);
To
if (dp-i_effnlink 3) {
error = EINVAL;
goto out;
}
The ufs_link() call has a similar issue.
I can't see why my mod will break anything, but there's always
unintended consequences.
One of the core policies usually is to stop _any_ action that
had failed due to a reason that cannot be and make sure it
won't get worse. This can be seen for example in fsck's behaviour:
If there is a massive file system error that cannot be repaired
without further intervention that _could_ destroy data or make
its retrieval harder or impossible, the operator will be requested
to make the decision. There are options to automate this process,
but on the other hand, always assume 'yes' can then be a risk,
as it could prevent recovery. My assumtion is that the developers
chose a similar approach here: We found a situation that should
not be possible, so we stop the system for messing up the file
system even more. This carries the attitude of not hiding a
problem for the sake of convenience by being silent and going
back to the usual work. Of course it is debatable if this is the
right decision in _this_ particular case.
By returning invalid argument, any code above
it should already be handling that condition although the user will be
scratching their head wondering what's wrong with it.
By determining the inode number and using the fsdb tool internal
data about inodes can be examined. Will it also show something
that's basically impossible? :-)
Returning ENOENT
or EACCES or ENOTDIR may be better (No such directory, Access denied
or Not a valid directory).
Depends on the applying definition of those errors.
The trouble is that it's tricky to test properly without finding a good
way to corrupt the link count :-)
There is a _simple_ way to do this, and I have even mentioned it.
Use the fsdb program and manipulate the inode manually. Make
sure that you actually understand that _what_ you are doing there
is creating severe file system inconsistency errors. :-)
--
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: Delete a directory, crash the system
On Sat, 27 Jul 2013 14:57:07 -0700, Adrian Chadd wrote: Yes. It'd be nice if UFS/FFS would just downgrade things to read-only and not panic. That would be possible, but it would confuse programs and users. It's not that you could walk up to the disk drive and flip the write protect switch back... ;-) -- 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: Creating freebsd usb boot
On Thu, 25 Jul 2013 12:01:10 +0300, Erhan Gulsen wrote: Hi, I am Erhan,i have a problem,i read your all definition but i can not create usb boot FreeBSD,i have a ubuntu 12.04 operating system.I want to create it with FreeBSD-9.1-RELEASE-amd64-disc1.iso but when i try this,it shows ''boot error''.Can you help me? The .iso file is designed to be used for optical media (CD and DVD). For USB sticks, use the .img (memstick) file from the download section. ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ FreeBSD-9.1-RELEASE-amd64-memstick.img will be the correct file which you can easily dd onto the USB stick. But maybe this will help you will the file you already have: http://forums.freebsd.org/showthread.php?t=30136 -- 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: Theft in the Clouds
On Thu, 25 Jul 2013 16:15:09 -0400, Jerry wrote: Not really a FreeBSD issue, but I did find this article rather fascinating. http://www.technologyreview.com/news/506976/how-to-steal-data-from-your-neighbor-in-the-cloud/ Some details for the interested ones (I think this is what the article refers to): http://eprint.iacr.org/2013/448.pdf Source: http://eprint.iacr.org/2013/448 -- 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: Fresh installation 9.1
On Fri, 19 Jul 2013 18:13:07 +0530, hrkesh sahu wrote: Hi All, after using freebsd for 10 to 20 mins, Key board is getting locked. Is that inside X? Before this problem , i have enabled ftpd and provided root login for ftp server access. That is something you should _not_ do, especially not within a network you don't trust (see also: The Internet). Usually FTP access can't be trusted (too much plaintext), and especially for root this is a threat to security. Better use scp (SSH) for transfering files in an FTP-like way. after that I am facing this problem . but i revert back this root access. and i stopped the ftpd service. That is a good step regarding security. Still make sure your system hasn't been compromized. Also be sure to change your root password, because you _never_ know. :-) mouse is working properly. but key board is not responding properly. When this happens inside X, it sounds a bit familiar. Does the keyboard start working again when you move the mouse? I'm not sure if _this_ is still an issue: http://www.wonkity.com/~wblock/docs/html/aei.html Make sure the keyboard is working as expected, for example by testing it in a non-X session (text mode terminal). -- 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: hey some questions
On Sat, 20 Jul 2013 01:02:07 +0300, mt2 magic wrote: hey bro bro can you help me to enable remote access to mysql server i am using FreeBSD 9.0 Yo bro, L33T help ahead. :-) http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html http://forums.freebsd.org/showthread.php?t=19940 Does this provide some help for you? If not, you might need to be less un-bro-like and instead more specific in regards of your problem description. ;-) -- 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: LC_CTYPE=fr_FR.ISO8859-1 with xterm - still French accented characters are corrupted
On Wed, 17 Jul 2013 15:38:53 +0200, Elimar Riesebieter wrote: * Anton Shterenlikht me...@bris.ac.uk [2013-07-17 13:14 +0100]: I tried, in tcsh: % setenv |grep FR XTERM_LOCALE=fr_FR.ISO8859-1 LC_CTYPE=fr_FR.ISO8859-1 but the accented French characters are corrupted, e.g. in /usr/ports/french/aster/pkg-descr. I built xterm with % make -C /usr/ports/x11/xterm showconfig === The following configuration options are available for xterm-296: 256COLOR=on: Enable 256-color support DABBREV=off: Enable support for dabbrev-expand DECTERM=off: Enable DECterm Locator support GNOME=off: GNOME desktop environment support LUIT=on: Use LUIT for locale convertion from/to UTF-8 PCRE=on: Use Perl Compatible Regular Expressions SIXEL=on: Enable Sixel graphics support WCHAR=on: Enable wide-character support === Use 'make config' to modify these settings I usually can read russian with either ru_RU.KOI8-R or en_US.UTF-8 in xterm, so I think the xterm is set up correctly to view 8-bit characters. Doesn't fr_FR.UTF8 work? That probably won't matter. The characters in that file are normal 1-byte characters (ISO), not 2-byte ones (UTF-8). I have built xterm with no special options and can see them properly. For comparison: % echo $XTERM_LOCALE en_US.ISO8859-1 % echo $LC_CTYPE de_DE.ISO8859-1 % make -C /usr/ports/x11/xterm showconfig === The following configuration options are available for xterm-282: DABBREV=off: Enable support for dabbrev-expand DECTERM=off: Enable DECterm Locator support GNOME=off: GNOME desktop environment support LUIT=on: Use LUIT for locale convertion from/to UTF-8 PCRE=off: Use Perl Compatible Regular Expressions WCHAR=on: Enable wide-character support === Use 'make config' to modify these settings I assume you have all neccessary _fonts_ installed? -- 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: Help to secure my FreeBSD/Apache installation
On Wed, 17 Jul 2013 23:11:27 +0200, Andy Wodfer wrote: Hi everybody! I'm running a server on FreeBSD 8.1 STABLE (apache 2.2.16, mysql 5.1.50, php 5.3.3) and I server some websites from it, most of them using Joomla or Wordpress CMS. Those are typical (and known) attack vectors. Make sure you're always up to date regarding fixes! I recently had a security breach where someone used a hole in an older Joomla version and was able to install a php script called webadmin.php. From that the person was able to browse all folders and view all files - and change them... not nice! This implies you cannot know in how far your system has been compromized. I'd suggest a new installation. Make backups of user files and configurations. Make sure you audit them (so you won't re-install a possible backdoor after a clean install). I need some help and pointers to what I can do to strengthen security and to atleast prevent someone from writing to the filesystem and browse all directories and files. (allthough joomla needs some folders to be chmod 777) I'm thinking about installing apache2-mpm-itk or similare to jail each site into its own directory and run each virtualhost as its own user. Is this a good idea? At least it is a _working_ idea. If it is actually a good idea depends on many different factors. Jails are a good means of separation. Sometimes, using simple user accounts is sufficient, but especially regarding complex web content (such as CMS, stuff that involves PHP and whatnot) the more security you can add, the better it is. Also install portaudit to check for security fixes that have been made available for the software you're running. Apply restrictions as hard as possible. If programs want write access to specific directories, try to make then writable per uer accounts, not within the global tree structure (or even within system directories). The nobody user can also be helpful (regarding on what you are running). If you can separate the different CMSs and sites, a possible security breach will be restricted to that only instance. It can be taken down without affecting the other sites. But also: Educate your users. In order to do that, use money. Make them pay. ;-) PS. Allow me a short addition, I know people will beat me with a pointed stick for mentioning it, but: There are no folders. This term is wrong. What you mean are called directories. A folder is the name of one visual representation (among others) of a directory in a graphical user interface. It _is_ not a directory and it is not similar to one. It's comparable to the relation of the handbrake light in your car's dashboard vs. the real handbrake. Don't claim your handbrake light isn't working when in fact your handbrake is broken. :-) Bottom line: Directory correct, folder plain wrong. You don't call files sheets of paper either. :-) -- 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: rsyslog
On Tue, 16 Jul 2013 22:04:05 +0200, Pol Hallen wrote: Where I found a standard rsyslog.conf config file to put it to /usr/local/etc? I think you can find a rsyslog-example.conf file in the directory for examples, probably /usr/local/share/examples or in a rsyslog/ or rsyslog7/ subdirectory thereof. -- 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: UEFI Secure Boot
On Mon, 8 Jul 2013 16:21:28 + (UTC), jb wrote: I hope FreeBSD (and other OSs) luminaries, devs and users will find a way not to harm themselves. A massive problem I (personally) have is that with Restricted Boot (this is what Secure Boot basically is) you are no longer able to _ignore_ MICROS~1 and their products. A restrictive boot loader mechanism that requires signed and confirmed keys, handled by a major offender of free decisions and a healthy market - no thanks. What prevents MICROS~1 from revoking keys of a possible competitor? Or from messing with the specs just that things start breaking? Don't get me wrong: I don't even argument that a mechanism where a competitor requires you to pay money to run _your_ software instead of _their_ software sounds horribly wrong. This approach will introduce a philosophical or even legal context to the technical problem. I see interesting chances in UEFI per se. It can be called a kind of micro-OS which can be rich on features that could also be useful. But history has shown that if such an infrastructure is provided, it will lead to bloated, insecure and incompatible implementations quickly, and the worst, it will happen at a very low level. This is simly dangerous. Regarding UEFI + Restricted Boot: To obtain MICROS~1's sticker of approval for hardware, vendors need to implement those features. Even worse, on _specific_ platforms, they are not allowed to make it possible to _remove_ those features, so on by default is required - if I remember correctly (Intel vs. ARM architectures). As you see, I try to ignore this whole topic as I am not interested in using it. In the past, this has been possible. When building a new system, buying a blank disk and _no_ Windows was particularly easy. For systems that already came with some Windows preinstalled, simply deleting the partition was a solution; install FreeBSD boot mechanism, initialize disk, and be done. No more dealing with what MICROS~1 seems to insist is normal. When _their_ product decisions make _me_ invest time to find a way to remove and ignore them, I feel offended. I would like to see a way UEFI hardware, with or without Restricted Boot, can be used with FreeBSD _without_ involving the good will of MICROS~1. But as they have already gotten their fingers everywhere, this doesn't seem to happen all too soon... :-( -- 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: install on external hdd
Your research is correct so far. On Sun, 07 Jul 2013 00:18:11 +0400, Nazar Kazakov wrote: I found on Google about bsdinstall segfault without disks. Then I reboot computer, disconnected the hdd and connected it immediately after starting bsdinstall, that's what I brought: usb_alloc_device: set address 2 failed (USB_ERR_STALLED, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_STALLED usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_STALLED, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_STALLED usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_STALLED, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_STALLED ugen1.2: Unknown at usbus1 (disconnected) uhub_reattach_port: could not allocate new device It should not matter when the disk is attached; bsdinstall will operate on any disk recognized by the system, no matter if detected at program runtime or system boot. As I understand it, my external hdd is not mounted. The disk is not _recognized_. Only a file system can be mounted (which requires the disk to be recognized). For a USB disk, from the /dev/ugenX.Y device a /dev/daX device will be generated, corresponding to the disk. The process you've shown above does not even reach that step. If you go to the shell, you can enter dmesg to see the last messages that will be the same. You can also check the content of /dev regarding daX devices (ls /dev/da*) or use camcontrol devlist to check if they are present. Maybe it's because I have a hdd with usb 3.0, but my computer does not have usb 3.0. Yes, this looks like a typical cannot connect error. Normally, a USB 3 disk would switch down to USB 2. But USB 3 has a different current requirement, so it could be possible that the power drain from the USB port is insufficient for the disk to work properly. Can you try to attach a separate power supply to the disk? For USB 3, _all_ involved parts (disk, cable, ports, controller, OS) need to be in USB 3 mode, else it probably won't work. -- 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: install on external hdd
On Sun, 07 Jul 2013 01:15:48 +0400, Nazar Kazakov wrote: In dmesg repeats the old conclusion that I wrote, but in dmesg I found information about five usbus and all except the last one (it has 2.0) written usb 1.0. I tried to connect the hdd to last, but failed. Looks like a current issue. From WP: A unit load is defined as 100 mA in USB 2.0, and 150 mA in USB 3.0. A device may draw a maximum of 5 unit loads (500 mA) from a port in USB 2.0; 6 (900 mA) in USB 3.0. If the disk needs more than 500 mA to spin up and start properly, it won't work on a USB 2.0 port unless you use the external power supply. Also about usbus written that they are 2-port hub (probably built into the motherboard). In the first four usbus is intel UHCI root HUB, at the last - intel EHCI root HUB That kind of combination can often be found. My older home PC also had this kind of configuration (Intel EHCI, VIA UHCI). ls / dev / da * finds nothing camcontrol devlist outputs only DVD RW This shows that the disk isn't recognized by the OS, therefore not usable in any disk-related operation. My hdd has an input for an external power supply, and it is already connected to a second usb port. Also check the USB cable. Sometimes a partially defective cable causes this kind of trouble. -- 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: gvim GUI cannot be used
On Fri, 5 Jul 2013 13:51:08 +0200, Fernando Apesteguía wrote: El 05/07/2013 13:20, Jens Jahnke jan0...@gmx.net escribió: Hi, On Fri, 5 Jul 2013 12:56:32 +0200 CeDeROM cede...@tlen.pl wrote: C Hey Raphael :-) Go to /usr/ports/editors/vim and make deinstall C reinstall it, that works for me, and it helps with dialogs in texmode C as well :-) for me this does not work. Unless I hack the Makefile and force it to enable gui mode it just isn't compiled in. Try a make rmconfig first and then make install. And make sure /etc/make.conf does not contain any offending settings that might suggest you do not have or want X11. -- 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: X client without X server
On Wed, 3 Jul 2013 11:47:16 +0100 (BST), Anton Shterenlikht wrote: $ pkg info -xd xterm xterm-293: xproto-7.0.24 xextproto-7.2.1 renderproto-0.11.1 printproto-1.0.5 libxcb-1.9.1 libXrender-0.9.8 libXpm-3.5.10 libXp-1.0.2,1 libXext-1.3.2,1 libXdmcp-1.1.1 libXau-1.0.8 libX11-1.6.0,1 libSM-1.2.1,1 libICE-1.0.8,1 kbproto-1.0.6 libXt-1.1.4,1 libXmu-1.1.1,1 libXaw-1.0.11,2 libXft-2.3.1 fontconfig-2.9.0,1 expat-2.0.1_2 freetype2-2.4.12_1 pkgconf-0.9.2_1 pcre-8.33 libpthread-stubs-0.3_3 Obviously xterm does not depend on xorg-server. But one of its dependencies might. -- 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: X client without X server
On Wed, 3 Jul 2013 18:07:11 +0700, Olivier Nicole wrote: On Wed, Jul 3, 2013 at 6:03 PM, Polytropon free...@edvax.de wrote: On Wed, 3 Jul 2013 11:47:16 +0100 (BST), Anton Shterenlikht wrote: [...] Obviously xterm does not depend on xorg-server. But one of its dependencies might. That make no sense, xterm may (and certainly does) depend on the same libraries as the X server, but there is no way xterm depends on X server itself. That's what I would imagine too. But who knows what's going on in the strange realm of build dependencies and run dependencies... :-) I can manually remove X server and the fonts and xclac... and the system is still running very well (and updating without trying to reinstall X server...) That should even work without a warning (as the libs for xterm would be kept, and those required by the X server _only_ could safely be removed). In case such a procedure is needed more often, a local patch could be added to the respective port that would remove the unneeded parts in the post-install phase. -- 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: any way to stop boot2 from waiting for keypress at system startup
On Tue, 2 Jul 2013 11:05:22 +0430, takCoder wrote: Hi Everyone, i wanna stop boot2 from getting a input string to change default boot point.. is there any way around, other than changing boot2.c source code to disable this feature?? As you may know, on system-startup, if you press any key, you will see the following prompt, waiting for you to enter related string: FreeBSD/x86 boot Default: 0:ad(0,a) boot: I checked it and found out that i can change boot2.c file to disable this section.. but I'd rather find another way.. Would you please let me know whether there are any other ways to do so? Without having checked it, but is this what you are searching for? In /boot/loader.conf: autoboot_delay=-1 From /boot/defaults/loader.conf: Delay in seconds before autobooting, set to -1 if you don't want user to be allowed to interrupt autoboot process and escape to the loader prompt, set to NO to disable autobooting I'm using autoboot_delay=1 to limit the time which the system is waiting before continuing the boot process. -- 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: any way to stop boot2 from waiting for keypress at system startup
On Tue, 2 Jul 2013 15:18:04 +0430, takCoder wrote: i found the answer! if i add a -n parameter to /boot.config file, the mentioned feature will be disabled.. Sorry for my confusion. The option you've successfully found is documented in man 8 boot (which also provides a short description of the stages performed at system boot). That's why it's good to know how the different components of the boot process are named so it becomes more logical where to search. :-) From the manual page: -nignore key press to interrupt boot before loader(8) is invoked. Explained: However, it is possible to dispense with the third stage altogether, either by specifying a kernel name in the boot block parameter file, /boot.config, or, unless option -n is set, by hitting a key during a brief pause (while one of the characters -, \, |, or / is displayed) before loader(8) is invoked. Booting will also be attempted at stage two, if the third stage cannot be loaded. It's always good to know where thine documentation is. ;-) -- 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: question, following error Shared object libc.so.6 not found, required by fortune
On Sat, 29 Jun 2013 10:48:38 -0400, Rev Herbert Miller wrote: I was trying to use the content management system for our website. I needed to restart on terminal but I keep coming up with the following error: I don't know programing at all, so don't know if this is something I can fix. In worst case, notify your system administrator. Shared object libc.so.6 not found, required by fortune This kind of error often indicates an incomplete system update were libraries are out of date or missing. What way of system update has been performed? root@psumc:/usr/local/tomcat5.5 # bin/startup.sh Neither the JAVA_HOME nor the JRE_HOME environment variable is defined At least one of these environment variable is needed to run this program That can be a side effect, maybe some accidentally overwritten configuration file or a program that's unable to run due to a missing dependency? What happens if you manually define those variables to the proper valies and try again, e. g. # setenv JAVA_HOME=/usr/local/where your JAVA stuff is # setenv JRE_HOME=/usr/local/where your runtime lives # bin/startup,sh Does this produce a different result? root@psumc:/usr/local/tomcat5.5 # su -c 'killall -9 java' That command doesn't make sense. The prompt indicates that you are already root. The -c parameter for the su command is missing an argument, the class. See man su for details, no programming knowledge required. ;-) -- 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: ALT key problem with Virtual Box?
On 29 Jun 2013 16:24:57 -, Scott Ballantyne wrote: Hi, I'm running Windows 7 under VirtualBox 4.2.6_OSE, and it seems the ALT key doesn't work. I need to use Photoshop, and there are a few operations that require a combination of holding down the ALT key and using a left-mouse-button click. I've googled and found reports on Linux from 2011 of this problem, but none of the solutions I've tried have fixed the problem. I'm using Gnome as my window manager, if that has any bearing on the issue. Maybe this is the reason. Several window managers are using Alt + left mouse key for a windowing operation (usually moving the window without requiring dragging it by the title bar). Check if you can unconfigure this setting in Gnome's window management preferences. -- 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: A very 'trivial' question about /root
On Fri, 28 Jun 2013 15:25:44 +0200, Julian H. Stacey wrote: Before we might ask (via send-pr) for it to be commited, we should various of us run chmod 750 /root;chown root:wheel /root give it a couple of months to see if problems. Done years ago: drwxr-x--- 7 root wheel 512 2013-04-05 21:42:34 /root/ System has been installed in August 2011. No problems so far. :-) ( I'd guess OpenBSD might go for a tighter /root though, as they're supposedly keen on security. ) Currently I've got no OpenBSD installation at hand to verify, but I _assume_ they still have the same defaults as FreeBSD regarding permissions of /root. if it leads to programs and daemons that would otherwise run as nobody having to run with root priviledges. Good point, we should be cautious, best if lots of us try chmod 750 /root for a couple of months see if any burnt fingers. What programs or daemons should attention be paid at, especially? -- 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: Retrieving a FreeBSD installation
On Thu, 27 Jun 2013 07:28:49 +, KK CHN wrote: List, I accidentally installed a Linux variant(mint OS) on my Harddisk where FreeBSD is installed( which contains my data). Is there a possibility to retrieve that FreeBSD Installation which is overwritten by Linux installation. In most cases: What has been overwritten is lost. But: What has only been disallocated (data still on disk) can _sometimes_ be recovered. So it depends on _what_ is still left. Anyway, do not do anything with the disk. Do not try any recovery on the disk itself. Make an image of the disk and use that image file for any further action. In case you damage it, make a new copy. Only work with copies. One wrong step can massively decrease your chances of recovery. Any hints welcome! It will be a very hard thing. You will probably have a lot of trial error experience, and you will surely learn a lot, for example about file systems. I've written about this topic on this list already, and I will again re-use some details from a previous post to make a list for what you can try. Boot from a live CD or USB stick or a different disk. Then make a copy of the disk using # dd if=/dev/ad0 of=disk.dd where /dev/ad0 is the disk you have accidentally overwritten your OS installation. In case the disk makes any trouble, use dd_rescue or ddrescue (from ports). You can also try this: # fetch -rR /dev/ad0 Also recoverdisk could be useful. Maybe there's enough information left to re-instantiate the file systems? Also try testdisk. When no file system can be re-instantiated, but you're sure your data is still somewhere, you can use photorec for recovery. It is able to recover a lot more than just photos. The ports collection contains further programs that might be worth investigating; just in case they haven't been mentioned yet: ddrescue dd_rescue - use this to make an image of the disk! magicrescue testdisk- restores content recoverjpeg foremost photorec Then also ffs2recov scan_ffs should be mentioned. And finally, the cure to everything is found in The Sleuth Kit (in ports: tsk): fls dls ils autopsy Keep in mind: Read the manpages before using the programs. It's very important to do so. You need to _know_ what you're dealing with, or you'll probably fail. There is no magical tetroplyrodon to click ^Z and get everything back. :-) Proprietary (and expensive) tools like R-Studio or UFS Explorer can still be considered worth a try. Their trial versions are for free. UFS Explorer even works using wine (I've tried it). If you can remember significant content of your data, you can even use # grep pattern disk.dd to see if it's still in there. With magicrescue, you can try something like this: # magicrescue -r /usr/local/share/magicrescue/recipes -d out disk.dd where out/ is the directory where your results will be written to. Keep in mind that _this_ approach will _not_ recover file _names_! I know how bad it feels for such a simple mistake and I won't make fun on you, pointing you to use your backups. Of course you always have the option to send your disk to a professional recovery company. This substitutes learning and trying yourself by impressive amounts of money. ;-) Good luck! -- 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: A very 'trivial' question about /root
On Wed, 26 Jun 2013 23:34:41 +0200, ASV wrote: There's any reason (and should be a fairly good one) why the /root directory permissions by default are set to 755 (for sure on releases 8.0/8.1/9.0/9.1) This is the default permission for user directories, as root is considered a user in this (special) case, and /root is its home directory. The installer does not put anything secret in there, but _you_ might, so there should be no issue changing it to a more restricted access permission. Hint: When a directory is r-x for other, then it will be indexed by the locate periodic job, so users could use the locate command (and also find) to look what's in there. If this is not desired, change to rwx/---/---, or rwx/r-x/--- if you want to allow (trusted) users of the wheel group to read and execute stuff from that directory (maybe homemade admin scripts in /root/bin that should not be public). There are few things that touch /root content. System updating might be one of them, but as it is typically run as root (and even in SUM), restrictive permissions above the default are no problem. To summarize the answer for your question: It's just the default. :-) -- 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: logging during loader
On Wed, 26 Jun 2013 23:40:07 -0400, Robert Huff wrote: Polytropon writes: During the processing of loader.conf, something gets printed that suggests all is not right. However, this is a sufficiently modern machine it goes by too fast to read exactly what. It is my understanding that file gets read before the system logging facilities are operational, and possibly before things like ^S/^Q work on the terminal. Is there a way to store the results of that phase of boot-up? Being on the 1st virtual terminal in text mode (ttyv0) which also acts as the console device, press the Scroll Lock key and use the vertical arrow keys and page scrolling keys to get to the top of the log. This does not work for me. Specifically, pushing [Scroll Lock] causes the appropriate light to go on, but output continues to flow. This doesn't look normal. Maybe kernel messages have precedence and can appear while regular output is halted? The cursor block should disappear (and the LED should light up). When the console TTY (ttyv0) does not show any more action, is scrolling back possible then? I've tried it on my home 8.2 system. Normal output is halted. I seem to remember that kernel messages unlock Scroll Lock... -- 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
