Re: PXE boot jumpstarting
On 4/25/06, Vahan Yerkanian [EMAIL PROTECTED] wrote: While we are on the subject, is it possible to setup a FreeBSD PXE server that lets you netboot different OSes from iso images via a boot menu? I know it's possible with linux [1] [2]. Could be useful in labs where you use different OSes and want to minimize cd/dvd clutter. yes. in fact, most of the steps are exactly the same; the only difference is that you need to download syslinux itself, as I don't think it's in the ports tree. As a general rule, if the platform can install a dhcp server with the pxeboot options, and a basic tftp server, it can pxeboot anything you want it to. Now, this doesn't mean that what you pxeboot will be able to get auxillary files it needs off the server, but that's to be expected, and planned for (that's why the next server option is there, after all!). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GNOME help PLEASE
On 3/11/06, Wojciech Puchar [EMAIL PROTECTED] wrote: while i'm not regular user of gnome, i have to configure it for users. the problem is how to make configuration template default for every new user. i tried to copy whole or partial user directory to other users+chown but no success. always something crashes or doesn't work. only copying desktop icons ends in full success. /usr/share/skel/ is where default config files usually go, any file starting with . has to be renamed to dot. (so .fvwm2rc becomes dot.fvwm2rc). As far as I know, this only works with a normal adduser.conf and using the adduser command or pw. Also, (with X11 programs especially) you'll have to edit all absolute paths in the config files to point to either relative, of if the app supports it, $HOME or ~/, so the programs won't attempt to write or read from the user you copied the configs from. Example: IconPath /root/icons would become: IconPath $HOME/icons hope this helps :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GNOME help PLEASE
On 3/12/06, Wojciech Puchar [EMAIL PROTECTED] wrote: As far as I know, this only works with a normal adduser.conf and using the adduser command or pw. Also, (with X11 programs especially) you'll have to edit all absolute paths in the config files to point to either relative, of if the app supports it, $HOME or ~/, so the programs won't attempt to write or read from the user you copied the configs from. Example: IconPath /root/icons would become: IconPath $HOME/icons hope this helps :) thank you very much but it would not. i know this and use this. the problem is where to find documentation about what gnome file does what, and how to make these skeleton files. any attempt to create clean user, configure gnome in it, move files to skel etc. failed. gnome gets lots of bugs, panel crashes etc. this way. I just did a clean gnome2 install, in a new user, changed the configuration, copied the entirety to skel, and then adduser'd it. gnome seems to start fine using gnome-session, and the user accounts are independent, so it is indeed kept entirely under the user's home directory. The clean install created these directories: .gconf .gconfd .gnome .gnome2 .gnome2_private .gstreamer-0.8 .icons .metacity .nautilus .themes Desktop Most of the important elements are under .gnome2 and .gconf, but the others are gnome components, metacity is the windowmanager, nautilus is the file manager/desktop, etc. any attempt to create clean user, configure gnome in it, move files to skel etc. failed. gnome gets lots of bugs, panel crashes etc. this way. now i know how to move desktop icons themselves, but not configuration. no idea what files defines what. gnome is even worse than windows in it. From the looks of it, the only things you'd really need to worry about with a default config are in .gnome2/ and .gconf/ Most of the meat in .gconf/ is in the %gconf.xml files. Skeleton files are nothing special, just have to change the name a bit and some of the paths like I said. if you have some description about it - will be very helpful That's all I can think of, it seems pretty straightforward. I'd be careful to check all %gconf.xml files in gnome2 to make sure they are 'safe' to use in skel (ie, user is changed, paths to private areas in another's home, etc) This is gnome 2.10 under freebsd 6.0-rc1, but the version shouldn't matter that much unless it's 2.6 or less. If not any info on things that you have done with your install up till this point might help me to reproduce the problem, or at least understand it a bit better. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
getting virtual consoles to work reliably with X
I've admined a network of FreeBSD 5.4 desktops for a few months now, and I've noticed that when an X server crashes hard, it will no longer respond to the control-alt-fn sequences, and not pass them down to whatever handler is called to switch virtual consoles. When the crash isn't that bad, normally I'd just kill the wdm process and let init respawn the display manager. But some days I don't have the option to ssh in or use a serial console to kill the daemon, and am forced to use the ACPI events to let the kernel shutdown and then restart the machine. Not only that, but the other people responsible for these machines are used to using the normal virtual console keys to kill errant processes on one console that aren't responding to signals. So I'm wondering, is there a compile time option, patch for atkbd, or configuration setting that will allow that driver to trap the control-alt-fn sequences itself, before it gets passed up to X? Or am I misunderstanding how the keyboard is handled in this situation? I would appreciate any help on this matter. Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0-release remote x application failure to open display
I recently have performed a clean install of 6.0-release on this machine, on a new hard drive, and then copied over the data and some configuration files (ssh keys, etc.) from the old hard drive (it is a slow machine, so I didn't want to build current). Having done so, I then tried to login remotely to this machine and run xmms (it is mostly used as my music server), which failed with this error: ** CRITICAL **: Unable to open display I have tried with passing the -X flag, and with passing the -Y flag to ssh, but there is no change in behaviour. Is there something that I have forgotten to enable, or is this unexpected? first, always use the -X or -Y option for X11 forwarding. regardless of whether you think it needs to be specified, good habit in case the environment changes unexpectedly. next, check the environment after login (setenv in tcsh), make sure that the DISPLAY variable is being set. should be somwhere along the lines of localhost:10.0 or higher.. then, whereis xauth and make sure it's installed. ssh uses this to set up said X display, and isn't installed when X applications are compiled or installed from binaries (it's in xorg-clients iirc.) These are fairly general, but are a good start. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
