search for: 4.2bsd

Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under

I sent this to freebsd-questions earlier via the newsgroup, but I just found out today that the list-to-news gateway has been down for half a month now. Any idea when it's going back up? Who was hosting that service anyway? And now for the question.. I have a test server that is being used to test a 4.4-REL to 4.8-STABLE upgrade, and I've found the system will no longer boot unless I

Hi there. OS version: FreeBSD 4.7-Stable FreeBSD #3 I just added a disk to my box and after playing with fdisk and disklabel with this configuration: fdisk: **************************************************************** g c16383 h16 s63 p 1 165 0 39102336 **************************************************************** disklabel

As others have noted, Tor's patch appears to be a total solution to the recent instability the PAE patch introduced. So, if you're experiencing panics with a recent kernel, or are in a position to stress a machine, please cvsup and give it a test! Thanks, Mike "Silby" Silbersack ---------- Forwarded message ---------- Date: Sat, 30 Aug 2003 08:39:08 -0700 (PDT) From: Tor Egge

Hello there! Here's my story, hopefully some of you won't follow my steps and avoid some troubles :) Yesterday I've decided that's about time to test zfs functionality on my home server PC (i386 FreeBSD 7.1-pre) . A couple of weeks ago I bought new desktop PC (with SATA), so I had a bunch of PATA disks from old one to use in server. Lucky me - there was 3 HDD at size 40GB -

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > A recent discussion in the issue tracker brought up the idea to allow the > `LISTEN` keyword to also accept a single "host:port" token (e.g. if there > is only one argument, with at least one colon, and the last colon is > followed only by numbers, split it into host and port) : >

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > A recent discussion in the issue tracker brought up the idea to allow the > `LISTEN` keyword to also accept a single "host:port" token (e.g. if there > is only one argument, with at least one colon, and the last colon is > followed only by numbers, split it into host and port) : >

On Nov 19, 2015, at 3:49 PM, Devin Reade <gdr at gno.org> wrote: > > size of the disk was never the original motivation for > keeping / separate, at least within my memory Prior to SysV, the location of user home directories was not standardized, and AT&T recommended that you put them in /usr.[1] Also, in the PDP days, you had things like the RL and RK series drives, which

Hello list, I observed a problem with interactive bash script executed by ssh: when I pressed <Ctrl+C>, ssh was killed on client side, but script remained active in remote machine and didn't receive signal INT. Using option -t gives no problem like that, but should it be perceived as a normal behaviour in case without -t? Please send a reply to my address too...

Hey, So, I would be looking at type A. Forgive me if my understanding of how OpenSSH operates is not reflective of reality. I am assuming that, the file transfer is happening somewhat logically, with a name being known, content written, blah blah. >From reading scp.c, it appears that, the client end at least knows the file name so I must assume the server end must be given it. I am hoping to

https://bugzilla.mindrot.org/show_bug.cgi?id=2626 Bug ID: 2626 Summary: ssh 172.10 resolves to ssh 172.0.0.10 Product: Portable OpenSSH Version: 7.3p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: normal Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at

Cheers all, A recent discussion in the issue tracker brought up the idea to allow the `LISTEN` keyword to also accept a single "host:port" token (e.g. if there is only one argument, with at least one colon, and the last colon is followed only by numbers, split it into host and port) : https://github.com/networkupstools/nut/issues/2424 I see certain pros to the idea (may be more

Cheers all, A recent discussion in the issue tracker brought up the idea to allow the `LISTEN` keyword to also accept a single "host:port" token (e.g. if there is only one argument, with at least one colon, and the last colon is followed only by numbers, split it into host and port) : https://github.com/networkupstools/nut/issues/2424 I see certain pros to the idea (may be more

I'm sure most people here know about Dash in Debian. Have there been discussions about providing a more efficient shell in Centos for use with heavily invoked non-interactive scripts? With sh being a link to bash in Centos I don't know if it would explode if the link was changed to something else, but at least the scripts we made on our own that run certain services could be changed and

Use /etc/hosts instead of /etc/fstab to detect whether a partition represents the root of a Linux installation; the latter might not exist in smaller/special installations like Docker images. Put an empty /etc/hosts in all the phony Linux guests to keep them detected as we want. --- src/inspect-fs.c | 2 +- test-data/phony-guests/make-archlinux-img.sh | 1 +

On Nov 18, 2015, at 9:49 PM, Devin Reade <gdr at gno.org> wrote: > > The one thing I would point out regarding the above link is that despite > conventional UNIX wisdom, *don't* put /usr on a separate filesystem > in CentOS 7. <sarcasm>Thank you RedHat</sarcasm> > > Flames to /dev/null. Sorry, you don?t get to throw that grenade and then run away. The

Thanks for sharing your take on this. (Sorry about likely mixing historic standards, was not in position to cross-check while posting) Just to clarify: using a different port *is* possible since forever, with `LISTEN host port` (as two arguments to the directive); the question was if having a way to spell it as one argument as `LISTEN host:port` would solve some shortcomings/ease adoption more

Thanks for sharing your take on this. (Sorry about likely mixing historic standards, was not in position to cross-check while posting) Just to clarify: using a different port *is* possible since forever, with `LISTEN host port` (as two arguments to the directive); the question was if having a way to spell it as one argument as `LISTEN host:port` would solve some shortcomings/ease adoption more

https://bugzilla.mindrot.org/show_bug.cgi?id=1386 Summary: OpenSSH 4.7p1 compile error in atomicio.c under Tru64 4.0f Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Alpha OS/Version: Tru64 Status: NEW Severity: major Priority: P2 Component: Build