Re: Patch into kernel sources

[Julian H. Stacey]

Venkat Duvvuru wrote:
> Does this procedure hold good for a device driver module's patch as well?

Yes

> On Thu, Sep 6, 2012 at 3:40 PM, Julian H. Stacey  wrote:
> 
> > Venkat Duvvuru wrote:
> > > Hi,
> > > Could somebody please point me to a procedure to apply a patch to the
> > > sources?
> > > I have a driver patch that I would like to commit.
> >
> > If you want to send from local mail client
> > man send-pr
> >
> > If you want to send via web
> > http://www.freebsd.org/support/bugreports.html
> > (pointed to from "Report a Bug" on front page)
> > http://www.freebsd.org/
> > (yup, easily missed on front page with new eyes, as Not a bug))
> >
> > Cheers,
> > Julian
> > --
> > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich
> > http://berklix.com
> >  Reply below not above, like a play script.  Indent old text with "> ".
> >  Send plain text. Not: HTML, multipart/alternative, base64,
> > quoted-printable.
> >
> 
> --e89a8fb1ef564d94e904c91ab01a
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> 
>  3px;background-color:rgb(255,255,255)">Does this procedure hold good for a =
> device driver module's patch as well?=A0 ail_quote">
> On Thu, Sep 6, 2012 at 3:40 PM, Julian H. Stacey < ref=3D"mailto:j...@berklix.com"; target=3D"_blank">j...@berklix.com> pan> wrote: ;border-left:1px #ccc solid;padding-left:1ex">
> Venkat Duvvuru wrote:
> > Hi,
> > Could somebody please point me to a procedure to apply a patch to the<=
> br>
> > sources?
> > I have a driver patch that I would like to commit.
> 
> If you want to send from local mail client
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 man send-pr
> 
> If you want to send via web
> =A0 =A0 =A0 =A0 http://www.freebsd.org/support/bugreports.html"; =
> target=3D"_blank">http://www.freebsd.org/support/bugreports.html
> (pointed to from "Report a Bug" on front page)
> =A0 =A0 =A0 =A0 http://www.freebsd.org/"; target=3D"_blank">http:=
> //www.freebsd.org/
> (yup, easily missed on front page with new eyes, as Not a bug))
> 
> Cheers,
> Julian
> --
> Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich  //berklix.com" target=3D"_blank">http://berklix.com
> =A0Reply below not above, like a play script. =A0Indent old text with "=
> ;> ".
> =A0Send plain text. Not: HTML, multipart/alternative, base64, quoted-printa=
> ble.
> 
> 
> --e89a8fb1ef564d94e904c91ab01a--
> 


Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
 Reply below not above, like a play script.  Indent old text with "> ".
 Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable.
___
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: Patch into kernel sources

[Venkat Duvvuru]

Does this procedure hold good for a device driver module's patch as well?

On Thu, Sep 6, 2012 at 3:40 PM, Julian H. Stacey  wrote:

> Venkat Duvvuru wrote:
> > Hi,
> > Could somebody please point me to a procedure to apply a patch to the
> > sources?
> > I have a driver patch that I would like to commit.
>
> If you want to send from local mail client
> man send-pr
>
> If you want to send via web
> http://www.freebsd.org/support/bugreports.html
> (pointed to from "Report a Bug" on front page)
> http://www.freebsd.org/
> (yup, easily missed on front page with new eyes, as Not a bug))
>
> Cheers,
> Julian
> --
> Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich
> http://berklix.com
>  Reply below not above, like a play script.  Indent old text with "> ".
>  Send plain text. Not: HTML, multipart/alternative, base64,
> quoted-printable.
>
___
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: Patch into kernel sources

[Julian H. Stacey]

Venkat Duvvuru wrote:
> Hi,
> Could somebody please point me to a procedure to apply a patch to the
> sources?
> I have a driver patch that I would like to commit.

If you want to send from local mail client
man send-pr

If you want to send via web
http://www.freebsd.org/support/bugreports.html
(pointed to from "Report a Bug" on front page)
http://www.freebsd.org/
(yup, easily missed on front page with new eyes, as Not a bug))

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
 Reply below not above, like a play script.  Indent old text with "> ".
 Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable.
___
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: Patch failed to apply cleanly [chromium-20.0.1132.57] FreeBSD 9.0-RELEASE

[Wayne Sierke]

On Thu, 2012-07-12 at 22:33 +0300, Alexander Kapshuk wrote:
> When attempting to upgrade chromium-19.0.1084.56_1 to 
> chromium-20.0.1132.57 on FreeBSD9.0 (FreeBSD box2 9.0-RELEASE FreeBSD 
> 9.0-RELEASE #0: Tue Jan  3 07:15:25 UTC 2012 
> r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386), one of 
> the patches failed to apply:
> --
> ===>  Applying extra patch /usr/ports/www/chromium/files/extra-patch-gcc
> ===>  Applying FreeBSD patches for chromium-20.0.1132.57
> patch:  malformed patch at line 15:  #if PLATFORM(CHROMIUM)
> => Patch patch-third_party__WebKit__Source__WebCore__config.h failed to 
> apply cleanly.
> --
> There seems to be a patch available that has been reported as having 
> worked on a 9.0-RELEASE/amd64:
> http://www.mail-archive.com/freebsd-chromium@freebsd.org/msg00340.html
> -
> www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h.orig 
> 
>  2012-07-12 09:19:26.0 +
> +++ www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h
> 2012-07-12 10:49:20.0 +
> @@ -1,6 +1,6 @@
>  third_party/WebKit/Source/WebCore/config.h.orig2012-05-30
> 10:05:35.0 +0300
> -+++ third_party/WebKit/Source/WebCore/config.h 2012-06-05 
> 22:32:48.0
> +0300
> -@@ -127,6 +127,11 @@
> +--- third_party/WebKit/Source/WebCore/config.h.orig2012-07-10
> 07:52:48.0 +
>  third_party/WebKit/Source/WebCore/config.h 2012-07-12 
> 10:48:15.0
> +
> +@@ -127,6 +127,14 @@
>#define WTF_USE_NEW_THEME 1
>#endif // PLATFORM(MAC)
> -
> Is there a patch available to an x86 based system?

The same patch will work for x86.

In lieu of the patch simply edit
www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h
and change the line:

@@ -127,6 +127,11 @@

to:

@@ -127,6 +127,14 @@


Wayne


___
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: Patch failed to apply cleanly [chromium-20.0.1132.57] FreeBSD 9.0-RELEASE

[Alexander Kapshuk]

When attempting to upgrade chromium-19.0.1084.56_1 to 
chromium-20.0.1132.57 on FreeBSD9.0 (FreeBSD box2 9.0-RELEASE FreeBSD 
9.0-RELEASE #0: Tue Jan  3 07:15:25 UTC 2012 
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386), one of 
the patches failed to apply:

--
===>  Applying extra patch /usr/ports/www/chromium/files/extra-patch-gcc
===>  Applying FreeBSD patches for chromium-20.0.1132.57
patch:  malformed patch at line 15:  #if PLATFORM(CHROMIUM)
=> Patch patch-third_party__WebKit__Source__WebCore__config.h failed to 
apply cleanly.

--
There seems to be a patch available that has been reported as having 
worked on a 9.0-RELEASE/amd64:

http://www.mail-archive.com/freebsd-chromium@freebsd.org/msg00340.html
-
www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h.orig 


2012-07-12 09:19:26.0 +
+++ www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h
2012-07-12 10:49:20.0 +
@@ -1,6 +1,6 @@
 third_party/WebKit/Source/WebCore/config.h.orig2012-05-30
10:05:35.0 +0300
-+++ third_party/WebKit/Source/WebCore/config.h 2012-06-05 
22:32:48.0

+0300
-@@ -127,6 +127,11 @@
+--- third_party/WebKit/Source/WebCore/config.h.orig2012-07-10
07:52:48.0 +
 third_party/WebKit/Source/WebCore/config.h 2012-07-12 
10:48:15.0

+
+@@ -127,6 +127,14 @@
  #define WTF_USE_NEW_THEME 1
  #endif // PLATFORM(MAC)
-
Is there a patch available to an x86 based system?

Thanks.

Alexander Kapshuk.

___
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: Patch Submission to a Port

[Charlie Kester]

On Mon 22 Mar 2010 at 15:08:43 PDT Charlie Kester wrote:

On Mon 22 Mar 2010 at 14:50:03 PDT Alejandro Imass wrote:

Hi,

I have finally tested and verified a patch for /usr/ports/graphics/sane-backends

To whon or where should I submit it?



http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-submitting.html



Sorry, wrong link.  That one's for submitting new ports.  Here's one for
the section of the handbook that describes how to submit a patch:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/port-upgrading.html

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Patch Submission to a Port

[Charlie Kester]

On Mon 22 Mar 2010 at 14:50:03 PDT Alejandro Imass wrote:

Hi,

I have finally tested and verified a patch for /usr/ports/graphics/sane-backends

To whon or where should I submit it?



http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-submitting.html

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Patch Submission to a Port

[Alberto Mijares]

> I have finally tested and verified a patch for 
> /usr/ports/graphics/sane-backends
>
> To whon or where should I submit it?
>


There's no specific maintainer for this port. Write to
po...@freebsd.org and submit the patch.

Regards


Alberto Mijares
___
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: Patch

[Michael Krafczyk]

I apologize for ignorance but I have freenas and not sure freebsd is the
same.  But the version of freenas I have is:

i386 07.1.4997

I am pretty sure I need the patch.  Whenever I reboot my system I get an
error that states the GPT is rejected.  If I unplug the power to the hard
drive and reboot and then plug in the power to the hard drive it works and I
do not get this error as per the instructions in the link above.

Mike

On Thu, Jan 28, 2010 at 4:01 PM, Chris Rees  wrote:

> On 28 January 2010 20:18, Michael Krafczyk  wrote:
> > Hi,
> >
> > I am new to FreeBSD and recently created a FreeNAS server.  I had a
> problem
> > with GEOM: GPT rejected.  I have Award Bios and found this fix
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=115406.  I, though, do not
> know
> > how to apply the patch.  I would appreciate any help.
> >
> > Thanks,
> >
> > Mike Krafczyk
>
> Are you certain that you need to? What version of FreeBSD are you using?
>
> Chris
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Patch

[Chris Rees]

On 28 January 2010 20:18, Michael Krafczyk  wrote:
> Hi,
>
> I am new to FreeBSD and recently created a FreeNAS server.  I had a problem
> with GEOM: GPT rejected.  I have Award Bios and found this fix
> http://www.freebsd.org/cgi/query-pr.cgi?pr=115406.  I, though, do not know
> how to apply the patch.  I would appreciate any help.
>
> Thanks,
>
> Mike Krafczyk

Are you certain that you need to? What version of FreeBSD are you using?

Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Patch Failures during Portupgrade

[Warren Liddell]

On Monday 23 June 2008 18:03:34 Odhiambo Washington wrote:
> On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell <[EMAIL PROTECTED]> wrote:
> > Below is the hunk of ports that continually fail to upgrade due to
> > problems with patching. i use the command portupgrade -aDkp -m BATCH=yes
> >
> > Any assistance with this greatly appreciated.
>
> Do you have the latest ports tree (via cvsup or csup)?


It appeard as though my entire ports structure was hosed, so i rm'd it and 
re-sup the entire lot and everything works fine now.  tnxs to all for 
suggestions and assitance.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch Failures during Portupgrade

[Robert Huff]

Warren Liddell writes:

>  > Do you have the latest ports tree (via cvsup or csup)?
>  
>  I csup'd my ports today and am re-doing it at present.  

Can't speak to the other ports, but the current version of ruby
is ruby-1.8.6.111_3,1 which built yesterday for me with zero
problems.


Robert Huff



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch Failures during Portupgrade

[Gonzalo Nemmi]

On Monday 23 June 2008 05:03:34 Odhiambo Washington wrote:
> On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell <[EMAIL PROTECTED]> wrote:
> > Below is the hunk of ports that continually fail to upgrade due to
> > problems with patching. i use the command portupgrade -aDkp -m BATCH=yes
> >
> > Any assistance with this greatly appreciated.
>
> Do you have the latest ports tree (via cvsup or csup)?

or 
portsnap fetch extract
portsnap update

portupgrade -arR

and since gettext got updated .. is gonna take a loot of time to update 
all of your ports ...

Actually .. from /usr/ports/UPDATING:

20080605:
  AFFECTS: users of devel/gettext (ie: YOU)
  AUTHOR: [EMAIL PROTECTED]

  As a result of the upgrade to gettext-0.17, the shared library version
  of libintl has changed, so you will need to rebuild all ports that
  depend on gettext:

  # portupgrade -rf gettext
  # portmaster -r gettext\*

  Given the scope and sheer number of dependent ports, it may be more
  advisable to simply blow away all existing install ports (after
  keeping any local configuration changes), and rebuilding from scratch.

Patience is a virtua ...
I guess :s

-- 
Blessings
Gonzalo Nemmi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch Failures during Portupgrade

[Warren Liddell]

On Monday 23 June 2008 18:03:34 Odhiambo Washington wrote:
> On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell <[EMAIL PROTECTED]> wrote:
> > Below is the hunk of ports that continually fail to upgrade due to
> > problems with patching. i use the command portupgrade -aDkp -m BATCH=yes
> >
> > Any assistance with this greatly appreciated.
>
> Do you have the latest ports tree (via cvsup or csup)?


I csup'd my ports today and am re-doing it at present.  src && kernel is all 
uptodate
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch Failures during Portupgrade

[Odhiambo Washington]

On Mon, Jun 23, 2008 at 8:32 AM, Warren Liddell <[EMAIL PROTECTED]> wrote:
> Below is the hunk of ports that continually fail to upgrade due to problems
> with patching. i use the command portupgrade -aDkp -m BATCH=yes
>
> Any assistance with this greatly appreciated.

Do you have the latest ports tree (via cvsup or csup)?

-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

"Oh My God! They killed init! You Bastards!"
 --from a /. post
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch for kern_clock.c

[RW]

On Thu, 10 Apr 2008 06:24:54 +0200 (CEST)
Wojciech Puchar <[EMAIL PROTECTED]> wrote:

> sent it as sent-pr, not to mailing list i think
> 

You can also do this from the website:

http://www.freebsd.org/send-pr.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch for kern_clock.c

[Wojciech Puchar]

sent it as sent-pr, not to mailing list i think


On Wed, 9 Apr 2008, Rudy wrote:




I have a machine with 6.3-STABLE in /usr/src.  The system is a 5.5 kernel 
(not sure if this matters).


Any how, buildkernel fails.  Ther error:
/usr/src/sys/kern/kern_clock.c: In function `sysctl_kern_cp_times': 
/usr/src/sys/kern/kern_clock.c:123: warning: unused variable `i'



The patch for kern_clock.c:


--- kern_clock.c.orig   Wed Apr  9 18:18:27 2008
+++ kern_clock.cWed Apr  9 18:18:07 2008
@@ -120,9 +120,10 @@
{
   struct pcpu *pcpu;
   int error;
-   int i, c;
+   int c;
   long *cp_time;
#ifdef SCTL_MASK32
+   int i;
   unsigned int cp_time32[CPUSTATES];
#endif
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH] Re: FreeBSD 6.0 on Sony Laptop

[Ruben de Groot]

On Thu, Nov 17, 2005 at 12:36:50PM -0800, Ted Mittelstaedt typed:
> Can you submit this via send-pr?

Done, thanks

http://www.freebsd.org/cgi/query-pr.cgi?pr=89227

Ruben

> Otherwise it's unlikely that it will get committed.
> 
> Ted
> 
> >-Original Message-
> >From: [EMAIL PROTECTED] 
> >[mailto:[EMAIL PROTECTED] Behalf Of Ruben de Groot
> >Sent: Wednesday, November 16, 2005 12:37 AM
> >To: Peter Clutton; Derek Tracy; freebsd-questions@freebsd.org
> >Subject: [PATCH] Re: FreeBSD 6.0 on Sony Laptop
> >
> >
> >
> >Following up on myself; the patch below (relative to 5.4-RELEASE) makes
> >my vaio VGN-S5M/S recognise the SATA controller for what it is.
> >
> >Before:
> >
> >atapci1:  port 
> >0x18a0-0x18af,0x1894-0x1897,0x18b0-0x18b7,0x18b8-0x18bb,0x18c0-0
> >x18c7 irq 18 at device 31.2 on pci0
> >ad4: 76319MB  [155061/16/63] at 
> >ata2-master UDMA33
> >
> >After:
> >
> >atapci1:  port 
> >0x18a0-0x18af,0x1894-0x1897,0x18b0-0x18b7,0x18b8-0x18bb,0x18c0-0
> >x18c7 irq 18 at device 31.2 on pci0
> >ad4: 76319MB  [155061/16/63] at 
> >ata2-master SATA150
> >
> >Patch:
> >
> >diff -u sys/dev/ata.orig/ata-chipset.c sys/dev/ata/ata-chipset.c
> >--- sys/dev/ata.orig/ata-chipset.c  Wed Mar 23 06:14:11 2005
> >+++ sys/dev/ata/ata-chipset.c   Tue Nov 15 21:39:17 2005
> >@@ -838,6 +838,7 @@
> >  { ATA_I82801FB,   0, 0, 0x00, ATA_UDMA5, "Intel ICH6" },
> >  { ATA_I82801FB_S1,0, 0, 0x00, ATA_SA150, "Intel ICH6" },
> >  { ATA_I82801FB_R1,0, 0, 0x00, ATA_SA150, "Intel ICH6" },
> >+ { ATA_I82801FBM,  0, 0, 0x00, ATA_SA150, "Intel ICH6-M" },
> >  { 0, 0, 0, 0, 0, 0}};
> > char buffer[64];
> >
> >diff -u sys/dev/ata.orig/ata-pci.h sys/dev/ata/ata-pci.h
> >--- sys/dev/ata.orig/ata-pci.h  Wed Mar 23 06:14:11 2005
> >+++ sys/dev/ata/ata-pci.h   Tue Nov 15 21:41:07 2005
> >@@ -127,6 +127,7 @@
> > #define ATA_I82801FB0x266f8086
> > #define ATA_I82801FB_S1 0x26518086
> > #define ATA_I82801FB_R1 0x26528086
> >+#define ATA_I82801FBM   0x26538086
> >
> > #define ATA_ITE_ID  0x1283
> > #define ATA_IT8212F 0x82121283
> >
> >___
> >freebsd-questions@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >To unsubscribe, send any mail to 
> >"[EMAIL PROTECTED]"
> >
> >-- 
> >No virus found in this incoming message.
> >Checked by AVG Free Edition.
> >Version: 7.1.362 / Virus Database: 267.13.3/173 - Release Date: 
> >11/16/2005
> >
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: [PATCH] Re: FreeBSD 6.0 on Sony Laptop

[Ted Mittelstaedt]

Can you submit this via send-pr?

Otherwise it's unlikely that it will get committed.

Ted

>-Original Message-
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED] Behalf Of Ruben de Groot
>Sent: Wednesday, November 16, 2005 12:37 AM
>To: Peter Clutton; Derek Tracy; freebsd-questions@freebsd.org
>Subject: [PATCH] Re: FreeBSD 6.0 on Sony Laptop
>
>
>
>Following up on myself; the patch below (relative to 5.4-RELEASE) makes
>my vaio VGN-S5M/S recognise the SATA controller for what it is.
>
>Before:
>
>atapci1:  port 
>0x18a0-0x18af,0x1894-0x1897,0x18b0-0x18b7,0x18b8-0x18bb,0x18c0-0
>x18c7 irq 18 at device 31.2 on pci0
>ad4: 76319MB  [155061/16/63] at 
>ata2-master UDMA33
>
>After:
>
>atapci1:  port 
>0x18a0-0x18af,0x1894-0x1897,0x18b0-0x18b7,0x18b8-0x18bb,0x18c0-0
>x18c7 irq 18 at device 31.2 on pci0
>ad4: 76319MB  [155061/16/63] at 
>ata2-master SATA150
>
>Patch:
>
>diff -u sys/dev/ata.orig/ata-chipset.c sys/dev/ata/ata-chipset.c
>--- sys/dev/ata.orig/ata-chipset.c  Wed Mar 23 06:14:11 2005
>+++ sys/dev/ata/ata-chipset.c   Tue Nov 15 21:39:17 2005
>@@ -838,6 +838,7 @@
>  { ATA_I82801FB,   0, 0, 0x00, ATA_UDMA5, "Intel ICH6" },
>  { ATA_I82801FB_S1,0, 0, 0x00, ATA_SA150, "Intel ICH6" },
>  { ATA_I82801FB_R1,0, 0, 0x00, ATA_SA150, "Intel ICH6" },
>+ { ATA_I82801FBM,  0, 0, 0x00, ATA_SA150, "Intel ICH6-M" },
>  { 0, 0, 0, 0, 0, 0}};
> char buffer[64];
>
>diff -u sys/dev/ata.orig/ata-pci.h sys/dev/ata/ata-pci.h
>--- sys/dev/ata.orig/ata-pci.h  Wed Mar 23 06:14:11 2005
>+++ sys/dev/ata/ata-pci.h   Tue Nov 15 21:41:07 2005
>@@ -127,6 +127,7 @@
> #define ATA_I82801FB  0x266f8086
> #define ATA_I82801FB_S1   0x26518086
> #define ATA_I82801FB_R1   0x26528086
>+#define ATA_I82801FBM 0x26538086
>
> #define ATA_ITE_ID0x1283
> #define ATA_IT8212F   0x82121283
>
>___
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to 
>"[EMAIL PROTECTED]"
>
>-- 
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.362 / Virus Database: 267.13.3/173 - Release Date: 
>11/16/2005
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[Andrew P.]

On 10/13/05, David Kirchner <[EMAIL PROTECTED]> wrote:
> On 10/13/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> > I don't see a single reason why I shouldn't ask
> > the BSD daemon to flame the hell out of you :-)
> >
> > Try again to verify. And again. Again then. And
> > if you think that 5 times are enough, you might
> > be right. But they are not enough for you.
>
> You're right. Damn, I must have done the wrong thing. I upgraded to
> RELENG_5 I guess. (It's hard to know, since the server panics when you
> run reboot or shutdown -r, and is not immediately in front of me). I
> screwed up.
>
> The reason I thought the way I did was that I saw something like
> 'bsnmpd' show up in mergemaster, but it looks like that only arrives
> when you upgrade to RELENG_5. Sorry Cody, sorry list.
>

No problem at all :-)

Maybe we can help you so that your server behaves
better. There are hundreds of techs subscribed to
this list, who eat headless servers for breakfast. If
you do have a problem, start a new thread, please.

Cheerz,
Andrew P.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[David Kirchner]

On 10/13/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> I don't see a single reason why I shouldn't ask
> the BSD daemon to flame the hell out of you :-)
>
> Try again to verify. And again. Again then. And
> if you think that 5 times are enough, you might
> be right. But they are not enough for you.

You're right. Damn, I must have done the wrong thing. I upgraded to
RELENG_5 I guess. (It's hard to know, since the server panics when you
run reboot or shutdown -r, and is not immediately in front of me). I
screwed up.

The reason I thought the way I did was that I saw something like
'bsnmpd' show up in mergemaster, but it looks like that only arrives
when you upgrade to RELENG_5. Sorry Cody, sorry list.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[Andrew P.]

On 10/13/05, David Kirchner <[EMAIL PROTECTED]> wrote:
> On 10/12/05, David Kirchner <[EMAIL PROTECTED]> wrote:
> > On 10/12/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> > > That's just not true. Cvsupping to something like
> > > RELENG_5_4 will do exactly the same thing as
> > > a patch, only it's the hassle-free way. You see
> > > a sec-advisory, you type "cvsup -g -L 2 mysup"
> > > recompile what's suggested in the advisory, or
> > > the whole world - and you're done.
> >
> > cvsupping to RELENG_5_4 will include all of those patches, not just
> > the one you just read about. So if you had to avoid installing a patch
> > for some reason (you had a local solution, or something, it happens
> > sometimes) then you need to avoid using the cvsup method.
>
> I just tried this again to verify. cvsuping to RELENG_5_4 gives you
> 5.4-STABLE, which includes _many_ things not found in the
> 5.4-RELEASE-p?? branch. I'm not saying people shouldn't upgrade to
> 5.4-STABLE (although I do think efforts should be directed towards
> including bugfixes in the 5.4-RELEASE-p?? branch) but that they should
> be aware that cvsup'ing to RELENG_5_4 will give them a very different
> result to patching the specific security advisory patches.
>

I don't see a single reason why I shouldn't ask
the BSD daemon to flame the hell out of you :-)

Try again to verify. And again. Again then. And
if you think that 5 times are enough, you might
be right. But they are not enough for you.

Currently:

RELENG_5_4 = 5.4-RELEASE-p*
RELENG_5 = 5.4-STABLE

What's so hard about remembering that? My
sense of humour is depleted, honestly.

Browse through the CVS if you don't believe
your eyes:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[David Kirchner]

On 10/12/05, David Kirchner <[EMAIL PROTECTED]> wrote:
> On 10/12/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> > That's just not true. Cvsupping to something like
> > RELENG_5_4 will do exactly the same thing as
> > a patch, only it's the hassle-free way. You see
> > a sec-advisory, you type "cvsup -g -L 2 mysup"
> > recompile what's suggested in the advisory, or
> > the whole world - and you're done.
>
> cvsupping to RELENG_5_4 will include all of those patches, not just
> the one you just read about. So if you had to avoid installing a patch
> for some reason (you had a local solution, or something, it happens
> sometimes) then you need to avoid using the cvsup method.

I just tried this again to verify. cvsuping to RELENG_5_4 gives you
5.4-STABLE, which includes _many_ things not found in the
5.4-RELEASE-p?? branch. I'm not saying people shouldn't upgrade to
5.4-STABLE (although I do think efforts should be directed towards
including bugfixes in the 5.4-RELEASE-p?? branch) but that they should
be aware that cvsup'ing to RELENG_5_4 will give them a very different
result to patching the specific security advisory patches.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[David Kirchner]

On 10/12/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> That's just not true. Cvsupping to something like
> RELENG_5_4 will do exactly the same thing as
> a patch, only it's the hassle-free way. You see
> a sec-advisory, you type "cvsup -g -L 2 mysup"
> recompile what's suggested in the advisory, or
> the whole world - and you're done.

cvsupping to RELENG_5_4 will include all of those patches, not just
the one you just read about. So if you had to avoid installing a patch
for some reason (you had a local solution, or something, it happens
sometimes) then you need to avoid using the cvsup method.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[Andrew P.]

On 10/12/05, David Kirchner <[EMAIL PROTECTED]> wrote:
> On 10/12/05, Cody Holland <[EMAIL PROTECTED]> wrote:
> > Thanks for the response.  I did  a terrible job of asking the correct
> > question to get the response I wanted.  I do know to cvsup the source
> > and build/make world.  I currently have 4 FreeBSD servers in production
> > serving various tasks.  The question I should have been asking is:
> > Is using the security patches provided by the FreeBSD maintainers as
> > good as actually updating the whole server?  What are the pros and cons
> > of using the security patches vs. full source upgrade via cvsup?
>
> If you cvsup, you're going to get more than just security patches.
> Basically, program functions could change in unexpected ways (unless
> you read /usr/src/UPDATING and it contains everything changed). When
> you do the specific security patch, you're reducing change, and thus
> reducing the chance of something else going "wrong" for you.
>
> It's probably safest to just do the security patch. However, if you
> ask questions about it on the mailing lists, your "uname -a" output
> won't be a complete picture of what has been patched. If you use the
> cvsup method, I believe your uname will show something like
> '5.4-RELEASE-p7'. Of course, most mailing list replies will be to
> upgrade to 6.0 or 7.0 but that's a side issue. :)
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

That's just not true. Cvsupping to something like
RELENG_5_4 will do exactly the same thing as
a patch, only it's the hassle-free way. You see
a sec-advisory, you type "cvsup -g -L 2 mysup"
recompile what's suggested in the advisory, or
the whole world - and you're done.

On the contrary to your latter statement, if you
start describing your problem with "I'm on
FreeBSD-Current", you'll be advised to downgrade
to Stable at least.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[David Kirchner]

On 10/12/05, Cody Holland <[EMAIL PROTECTED]> wrote:
> Thanks for the response.  I did  a terrible job of asking the correct
> question to get the response I wanted.  I do know to cvsup the source
> and build/make world.  I currently have 4 FreeBSD servers in production
> serving various tasks.  The question I should have been asking is:
> Is using the security patches provided by the FreeBSD maintainers as
> good as actually updating the whole server?  What are the pros and cons
> of using the security patches vs. full source upgrade via cvsup?

If you cvsup, you're going to get more than just security patches.
Basically, program functions could change in unexpected ways (unless
you read /usr/src/UPDATING and it contains everything changed). When
you do the specific security patch, you're reducing change, and thus
reducing the chance of something else going "wrong" for you.

It's probably safest to just do the security patch. However, if you
ask questions about it on the mailing lists, your "uname -a" output
won't be a complete picture of what has been patched. If you use the
cvsup method, I believe your uname will show something like
'5.4-RELEASE-p7'. Of course, most mailing list replies will be to
upgrade to 6.0 or 7.0 but that's a side issue. :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Patch vs. Upgrade

[Cody Holland]

On 10/12/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> > If things are not too tight on your hard drive, consider the cvsup 
> > way. It's very easy - and very clearly described in the handbook.
> 
> I've seen many people say this, but I suspect they haven't 
> tried looking for information on patching using cvsup in the 
> handbook. It's not easy to find. I think we're doing a 
> disservice to the community directing people there without 
> pointing them to a specific page (it is a 4MB document).
> 
> The notes on using cvsup to keep your system up to date are 
> under the section header "Cutting Edge". I dunno about you, 
> but when it comes to security patches, I'd like to see them 
> as easy as possible, not something as elite as that. Maybe 
> that's just a poor choice of a title, though.
> 
> The only specifically correct information -- using 'standard-supfile'
> -- appears under the header "Using FreeBSD-CURRENT", a 
> section most newbies certainly ought to avoid unless they 
> want to run bleeding-edge may-not-compile-at-all code.
> 
> In any case, a direct link to the information on how to keep 
> your system up to date is available here:
> 
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/curr
> ent-stable.html#AEN27683
> 
> You only need to read paragraph 2a -- the rest has to do with 
> -CURRENT and other crufty methods of getting source. Then you 
> can skip to:
> 
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sync
> hing.html
> 
> and read that and the next page. That should be enough to get 
> you going with the latest -RELEASE-pNN patch level.
> 

Thanks for the response.  I did  a terrible job of asking the correct
question to get the response I wanted.  I do know to cvsup the source
and build/make world.  I currently have 4 FreeBSD servers in production
serving various tasks.  The question I should have been asking is:
Is using the security patches provided by the FreeBSD maintainers as
good as actually updating the whole server?  What are the pros and cons
of using the security patches vs. full source upgrade via cvsup?

Thanks,
Cody
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[David Kirchner]

On 10/12/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> If things are not too tight on yout hard drive,
> consider the cvsup way. It's very easy - and
> very clearly described in the handbook.

I've seen many people say this, but I suspect they haven't tried
looking for information on patching using cvsup in the handbook. It's
not easy to find. I think we're doing a disservice to the community
directing people there without pointing them to a specific page (it is
a 4MB document).

The notes on using cvsup to keep your system up to date are under the
section header "Cutting Edge". I dunno about you, but when it comes to
security patchse, I'd like to see them as easy as possible, not
something as elite as that. Maybe that's just a poor choice of a
title, though.

The only specifically correct information -- using 'standard-supfile'
-- appears under the header "Using FreeBSD-CURRENT", a section most
newbies certainly ought to avoid unless they want to run bleeding-edge
may-not-compile-at-all code.

In any case, a direct link to the information on how to keep your
system up to date is available here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html#AEN27683

You only need to read paragraph 2a -- the rest has to do with -CURRENT
and other crufty methods of getting source. Then you can skip to:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html

and read that and the next page. That should be enough to get you
going with the latest -RELEASE-pNN patch level.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[David Kirchner]

On 10/12/05, Cody Holland <[EMAIL PROTECTED]> wrote:
> I'm still pretty new to the BSD world and wanted to throw out a question
> to see what kind of responses I get.  What is everyones take on what to
> do when security vulnerabities are discovered.  Do you upgrade your
> source (not always the easiest thing to do) or patch.  What are the pros
> and cons of patching?

We patch the source and rebuild the bare minimum of software.
Rebuilding world (ie: everything) is an extreme step which, logically,
should only be taken as a last resort. At least, in a production
environment. If this is just a toy computer, or a desktop, rebuilding
world is probably not so bad.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch vs. Upgrade

[Andrew P.]

On 10/12/05, Cody Holland <[EMAIL PROTECTED]> wrote:
> I'm still pretty new to the BSD world and wanted to throw out a question
> to see what kind of responses I get.  What is everyones take on what to
> do when security vulnerabities are discovered.  Do you upgrade your
> source (not always the easiest thing to do) or patch.  What are the pros
> and cons of patching?
>
> Thanks,
> Cody
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

We cvsup the source, rebuild the whole system
or just the part that's mentioned in a security
advisory (one always says what exactly needs
to be recompiled).

Patching pros:
doesn't require you to have the source at hand
doesn't require any development tools (like gcc)

Patching cons:
quite limited version availability
not so reliable as recompiling

If things are not too tight on yout hard drive,
consider the cvsup way. It's very easy - and
very clearly described in the handbook.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch errors

[Kris Kennaway]

On Mon, Jun 06, 2005 at 11:29:35AM +0900, FreeBSD MailingLists wrote:
> on all other servers I cvsup the src and ports tree, but for some
> reason the internet connection at the location of this particular
> server gets kicked when I start cvsup.  so I had to resort to this
> method.
> 
> I am not entirely convinced that it is a stale patch issue for 2 reasons.
> 1)  I have untar'd the same file on 2 different servers and only this
> one has issues updating the ports

Because you have stale files underneath.

> 2) I have tar'd up the /usr/ports dir from a different server that
> updates via cvsup.  The original server updates fine but when untar'd
> on this particular server the same exact patch errors appear.

Because you have stale files underneath.

> which leads me to believe the error is outside the ports tree itself.

Highly unlikely.

Kris


pgpOfKRDHuQbC.pgp
Description: PGP signature

Re: patch errors

[Alex Zbyslaw]

FreeBSD MailingLists wrote:


on all other servers I cvsup the src and ports tree, but for some
reason the internet connection at the location of this particular
server gets kicked when I start cvsup.  so I had to resort to this
method.

I am not entirely convinced that it is a stale patch issue for 2 reasons.
1)  I have untar'd the same file on 2 different servers and only this
one has issues updating the ports
2) I have tar'd up the /usr/ports dir from a different server that
updates via cvsup.  The original server updates fine but when untar'd
on this particular server the same exact patch errors appear.

which leads me to believe the error is outside the ports tree itself.
 

Did you delete the ports tree before untaring?  You don't mention that.  
(You could also investigate rsync or rdist to keep this machine's port 
tree up to date since that will do the deletions for you).


--Alex

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch errors

[FreeBSD MailingLists]

on all other servers I cvsup the src and ports tree, but for some
reason the internet connection at the location of this particular
server gets kicked when I start cvsup.  so I had to resort to this
method.

I am not entirely convinced that it is a stale patch issue for 2 reasons.
1)  I have untar'd the same file on 2 different servers and only this
one has issues updating the ports
2) I have tar'd up the /usr/ports dir from a different server that
updates via cvsup.  The original server updates fine but when untar'd
on this particular server the same exact patch errors appear.

which leads me to believe the error is outside the ports tree itself.

-tomoki



On 6/6/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 06, 2005 at 09:46:35AM +0900, FreeBSD MailingLists wrote:
> > Yes, Everyday I try this I grab the latest copy of ports.tar.gz from a
> > near by server.  The file is updated daily.  and using the same tar
> > file on other machine results in no errors.  I am thinking that my
> > patch program is messed up, since all the error s are patch errors,
> > either it can't find the file to patch or the file cannot be patched
> > correctly.
> 
> The problem is almost certainlythat you have stale patches in your
> tree.  Consider what will happen with your "upgrade" mechanism when a
> patch file is deleted from the ports tree.
> 
> There are much better ways to update your ports collection than this.
> 
> Kris
> 
> 
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch errors

[Kris Kennaway]

On Mon, Jun 06, 2005 at 09:46:35AM +0900, FreeBSD MailingLists wrote:
> Yes, Everyday I try this I grab the latest copy of ports.tar.gz from a
> near by server.  The file is updated daily.  and using the same tar
> file on other machine results in no errors.  I am thinking that my
> patch program is messed up, since all the error s are patch errors,
> either it can't find the file to patch or the file cannot be patched
> correctly.

The problem is almost certainlythat you have stale patches in your
tree.  Consider what will happen with your "upgrade" mechanism when a
patch file is deleted from the ports tree.

There are much better ways to update your ports collection than this.

Kris


pgpUICknHHwJS.pgp
Description: PGP signature

Re: patch errors

[FreeBSD MailingLists]

Yes, Everyday I try this I grab the latest copy of ports.tar.gz from a
near by server.  The file is updated daily.  and using the same tar
file on other machine results in no errors.  I am thinking that my
patch program is messed up, since all the error s are patch errors,
either it can't find the file to patch or the file cannot be patched
correctly.

is patch port of "world" or do I need to update a pkg? 



On 6/6/05, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> On 2005-06-06 00:24, FreeBSD MailingLists <[EMAIL PROTECTED]> wrote:
> > ===>  Applying FreeBSD patches for tiff-3.7.2
> > 4 out of 4 hunks failed--saving rejects to libtiff/Makefile.in.rej
> > => Patch patch-aa failed to apply cleanly.
> > => Patch(es) patch-Makefile.in applied cleanly.
> > *** Error code 1
> 
> Is your ports tree up to date?
> 
> gothmog:/usr/ports/graphics/tiff# make patch
> ===>  Extracting for tiff-3.7.2
> => Checksum OK for tiff-3.7.2.tar.gz.
> ===>  Patching for tiff-3.7.2
> ===>  Applying FreeBSD patches for tiff-3.7.2
> gothmog:/usr/ports/graphics/tiff#
> 
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch errors

[Giorgos Keramidas]

On 2005-06-06 00:24, FreeBSD MailingLists <[EMAIL PROTECTED]> wrote:
> ===>  Applying FreeBSD patches for tiff-3.7.2
> 4 out of 4 hunks failed--saving rejects to libtiff/Makefile.in.rej
> => Patch patch-aa failed to apply cleanly.
> => Patch(es) patch-Makefile.in applied cleanly.
> *** Error code 1

Is your ports tree up to date?

gothmog:/usr/ports/graphics/tiff# make patch
===>  Extracting for tiff-3.7.2
=> Checksum OK for tiff-3.7.2.tar.gz.
===>  Patching for tiff-3.7.2
===>  Applying FreeBSD patches for tiff-3.7.2
gothmog:/usr/ports/graphics/tiff#

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH] puc/ppc and amd64

[David Taylor]

On Thu, 07 Apr 2005, David Taylor wrote:

> Hi,
> 
> I've got an amd64 box with 1 built-in parallel port, which works fine.
> 
> I also bought an add-on parallel port adapter card (a MosChip
> SemiConductors Nm9805 chip).  After discovering puc, I enabled
> device puc and the card is now detected by puc, but doesn't
> appear to be picked up by the ppc driver.

I have now, finally, figured out what was going on.  After much
wasted time trying to debug ppc_puc.c, I realised it wasn't
even being compiled in the kernel.  After adding dev/ppc/ppc_puc.c
to files.amd64, everything worked a lot better.

A patch (against 5-STABLE) is attached, which adds ppc_puc.c to all
architectures with ppc.c listed (alpha, amd64, ia64 -- I can only test
amd64, however).

If this gets lost for ages, I'll add a PR...

-- 
David Taylor
--- sys/conf/files.alpha.oldWed Apr 13 12:20:57 2005
+++ sys/conf/files.alphaWed Apr 13 12:21:43 2005
@@ -183,6 +183,7 @@
 dev/kbd/kbd.c  optionalsc
 dev/kbd/kbd.c  optionalukbd
 dev/ppc/ppc.c  optionalppc
+dev/ppc/ppc_puc.c  optionalppc puc pci
 dev/sio/sio.c  optionalsio
 dev/sio/sio_isa.c  optionalsio isa
 dev/syscons/schistory.coptionalsc
--- sys/conf/files.amd64.oldWed Apr 13 12:21:15 2005
+++ sys/conf/files.amd64Wed Apr 13 12:21:53 2005
@@ -133,6 +133,7 @@
 dev/kbd/kbd.c  optionalukbd
 dev/mem/memutil.c  optionalmem
 dev/ppc/ppc.c  optionalppc
+dev/ppc/ppc_puc.c  optionalppc puc pci
 dev/sio/sio.c  optionalsio
 dev/sio/sio_isa.c  optionalsio isa
 dev/syscons/apm/apm_saver.coptionalapm_saver apm
--- sys/conf/files.ia64.old Wed Apr 13 12:21:05 2005
+++ sys/conf/files.ia64 Wed Apr 13 12:22:11 2005
@@ -59,6 +59,7 @@
 dev/kbd/kbd.c  optionalsc
 dev/kbd/kbd.c  optionalukbd
 dev/ppc/ppc.c  optionalppc isa
+dev/ppc/ppc_puc.c  optionalppc puc pci
 dev/syscons/schistory.coptionalsc
 dev/syscons/scmouse.c  optionalsc
 dev/syscons/scterm-dumb.c  optionalsc
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Jay O'Brien]

Michal Mertl wrote:
> Jay O'Brien píše v po 11. 04. 2005 v 00:43 -0700: 
>>
>>Michal,
>>
>>The md5 results for vidcontrol.diff.20050215 are the same as yours. The other 
>>files, however, are different. I first did 
>>fetch 
>>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c
>>fetch 
>>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1
>>to get the files. I now see this doesn't get the correct files. Rather, it 
>>gets 
>>files marked up for the web. Obviously that was a big problem. 
>>
>>Then, using WinXP Pro and Mozilla, I downloaded the files again from 
>>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/
>>and I moved them to the FreeBSD machine using WS_FTP Pro. 
>>Different md5 results again. 
>>
>>I found that now the first hunk of the patch on vidcontrol.1 failed. 
>>
>>After much file comparing, I found the differences in the files. The 
>>"$FreeBSD" 
>>line near the beginning of each file had  "/repoman/r/ncvs/" in front of 
>>src/user.sbin/... and when I edited those characters out, the md5 results 
>>were 
>>the same as yours, and the patch completed without errors. I found that the 
>>vidcontrol.c file would patch ok without editing out those characters, but 
>>the 
>>vidcontrol.1 file would error in hunk #1 if "/repoman/r/ncvs/" was present.
> 
> 
> I see. Sorry about that. I didn't actually retrieve my files from
> cvsweb, I have a local copy of the repository.
> 
> 
>>I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got 
>>16 lines of "vidcontrol:  showing the mouse:  Invalid argument" which I see 
>>from a google search is a common problem.
> 
> 
> Yes. I didn't look into it.

Do you see this problem on your system?

> 
> 
>>Whenever I select a mode with more than 80 characters the screen goes black. 
> 
> 
> I'm afraid I've never seen this.
> 
> 
>>I loaded cp837-8x8 font, but no change.
> 
> 
> I suppose you mean 437. It shouldn't be important. 
> 

Yes, 437. My typo. sorry.

> 
>>I have the following in /etc/rc.conf, to set up 80x50, could it be the 
>>problem?
>>font8x8="iso08-8x8"
>>font8x14="iso08-8x14"
>>font8x16="iso08-8x16"
>>scrnmap="iso-8859-1_to_cp437"
>>allscreens_flags="-m on 80x50 white black" 
> 
> 
> I didn't try it lately. I just used vidcontrol manually.
> 
> 
>>Or perhaps this that I have now in /etc/ttys?
>>ttyv0 "/usr/libexec/getty Pc" cons50  on  secure
>># Virtual terminals
>>ttyv1 "/usr/libexec/getty Pc" cons50  on  secure
>>ttyv2 "/usr/libexec/getty Pc" cons50  on  secure
>>ttyv3 "/usr/libexec/getty Pc" cons50  on  secure
>>ttyv4 "/usr/libexec/getty Pc" cons50  on  secure
>>ttyv5 "/usr/libexec/getty Pc" cons50  on  secure
>>ttyv6 "/usr/libexec/getty Pc" cons50  on  secure
>>
>>At least now I can see what MAY be possible; vidcontrol -i mode returns a 
>>screenful of fonts to try. Tomorrow I'll identify which ones work and 
>>which ones don't.
> 
> 
> This is a part of my 'vidcontrol -i mode' command output:
> 

Where is this display explained? flags, type, window, linear buffer? It isn't 
in MAN VIDCONTROL

> mode# flags type size font window linear
> --
>   
> 24 (0x018) 0x0001 T 80x25 8x16 0xb8000
> 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000
> 32 (0x020) 0x0001 T 80x30 8x16 0xb8000
> 34 (0x022) 0x0001 T 80x60 8x8 0xb8000

My modes 24,30,32 and 34 are identical to yours.

> 259 (0x103) 0x000f G 800x600x8 1 8x14
> 275 (0x113) 0x000f G 800x600x15 1 8x14
> 276 (0x114) 0x000f G 800x600x16 1 8x14
> 277 (0x115) 0x000f G 800x600x24 1 8x14

My modes 259,275,276,277 all show 0x000b and 8x16; otherwise the same.

> 290 (0x122) 0x000f G 800x600x32 1 8x14

I don't have mode 290.

> To set the desired mode use vidcontrol MODE_mode#. From the modes listed
> here mode 259 can't be used (it's 8bpp mode which isn't supported).
> 

Yes, that works fine.

> To be able to use a mode you must have the appropriate font loaded.
> 
> Command 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x14.fnt' may be
> used to use some 8x14 font. You should have loaded all for resolutions'
> fonts though because they're listed at rc.conf.
> 
> I really don't see what you've done wrong this time, sorry. From my
> experience vidcontrol allows you to switch to a desired mode only if
> it's possble - the appopriate font is loaded and in case you ask for
> graphics mode SC_PIXEL_MODE is defined and the mode has supported color
> depth.
> 
> I tested it all again and it works for me flawlessly.
> 
> Michal
> 

Here's my observations now.  Does this suggest any actions to try?

I note that consoles ttyv1-7 are now 80x25, not 80x50 as I had 
them set up before. I can go to each, type vidcontrol MODE_30 
to put that virtual console into 80x50 mode. ttyv0, however, 
starts up in 80x50 as before. 

I have 45 modes in my vidcontrol -i mode display. 21 work fine,

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Jay O'Brien]

Michal Mertl wrote:

> Jay O'Brien wrote:
> 
>>Michal Mertl wrote:
>>
>>>
What? I don't know how the patching of vidcontrol ended but you'd
better redo it with fresh files from current. Go download vidcontrol.c
v 1.48 and vidcontrol.1 from
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/

Then run the patch on it again and recompile/reinstall vidcontrol
binary.
>>>
>>I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. 
>>Now all hunks failed. The results are below. 
> 
> 
> I don't know. The text before the line starting with "Patching" is taken
> from the patch file. The patch program doesn't retrieve any files. So I
> think you either used bad files to patch or bad patchfile.
> 
> You need to have the original files. To check they're correct you can
> use md5 utility.
> 
> md5 vidcontrol.c
> MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1
> md5 vidcontrol.1
> MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406
> md5 vidcontrol.diff.20050215 
> MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021
> 
> You need to see the same strings.
> 
> Then command 'patch < /path/to/vidcontro.diff.20050215' must work.
> 
> Michal
> 

Michal,

The md5 results for vidcontrol.diff.20050215 are the same as yours. The other 
files, however, are different. I first did 
fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c
fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1
to get the files. I now see this doesn't get the correct files. Rather, it gets 
files marked up for the web. Obviously that was a big problem. 

Then, using WinXP Pro and Mozilla, I downloaded the files again from 
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/
and I moved them to the FreeBSD machine using WS_FTP Pro. 
Different md5 results again. 

I found that now the first hunk of the patch on vidcontrol.1 failed. 

After much file comparing, I found the differences in the files. The "$FreeBSD" 
line near the beginning of each file had  "/repoman/r/ncvs/" in front of 
src/user.sbin/... and when I edited those characters out, the md5 results were 
the same as yours, and the patch completed without errors. I found that the 
vidcontrol.c file would patch ok without editing out those characters, but the 
vidcontrol.1 file would error in hunk #1 if "/repoman/r/ncvs/" was present.

I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got 
16 lines of "vidcontrol:  showing the mouse:  Invalid argument" which I see 
from a google search is a common problem. 

Whenever I select a mode with more than 80 characters the screen goes black. 
I loaded cp837-8x8 font, but no change.

I have the following in /etc/rc.conf, to set up 80x50, could it be the problem?
font8x8="iso08-8x8"
font8x14="iso08-8x14"
font8x16="iso08-8x16"
scrnmap="iso-8859-1_to_cp437"
allscreens_flags="-m on 80x50 white black" 

Or perhaps this that I have now in /etc/ttys?
ttyv0   "/usr/libexec/getty Pc" cons50  on  secure
# Virtual terminals
ttyv1   "/usr/libexec/getty Pc" cons50  on  secure
ttyv2   "/usr/libexec/getty Pc" cons50  on  secure
ttyv3   "/usr/libexec/getty Pc" cons50  on  secure
ttyv4   "/usr/libexec/getty Pc" cons50  on  secure
ttyv5   "/usr/libexec/getty Pc" cons50  on  secure
ttyv6   "/usr/libexec/getty Pc" cons50  on  secure

At least now I can see what MAY be possible; vidcontrol -i mode returns a 
screenful of fonts to try. Tomorrow I'll identify which ones work and 
which ones don't.

What next?

Jay O'Brien
Rio Linda, California, USA










___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Jay O'Brien wrote:
> Michal Mertl wrote:
> > 
> > You haven't read the thread in the archives carefully enough, have you?
> 
> Yes, but unfortunately I didn't comprehend. 
> 
> > Here is what I wrote (privately to the original poster but I explained
> > the error to the mailing list too):
> > 
> > 
> >>What? I don't know how the patching of vidcontrol ended but you'd
> >>better redo it with fresh files from current. Go download vidcontrol.c
> >>v 1.48 and vidcontrol.1 from
> >>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/
> >>
> >>Then run the patch on it again and recompile/reinstall vidcontrol
> >>binary.
> > 
> 
> I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. 
> Now all hunks failed. The results are below. 

I don't know. The text before the line starting with "Patching" is taken
from the patch file. The patch program doesn't retrieve any files. So I
think you either used bad files to patch or bad patchfile.

You need to have the original files. To check they're correct you can
use md5 utility.

md5 vidcontrol.c
MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1
md5 vidcontrol.1
MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406
md5 vidcontrol.diff.20050215 
MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021

You need to see the same strings.

Then command 'patch < /path/to/vidcontro.diff.20050215' must work.

Michal

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Jay O'Brien]

Michal Mertl wrote:
> 
> You haven't read the thread in the archives carefully enough, have you?

Yes, but unfortunately I didn't comprehend. 

> Here is what I wrote (privately to the original poster but I explained
> the error to the mailing list too):
> 
> 
>>What? I don't know how the patching of vidcontrol ended but you'd
>>better redo it with fresh files from current. Go download vidcontrol.c
>>v 1.48 and vidcontrol.1 from
>>http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/
>>
>>Then run the patch on it again and recompile/reinstall vidcontrol
>>binary.
> 

I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. 
Now all hunks failed. The results are below. 

What did I screw up this time?

Jay 


|Index: vidcontrol.1
|===
|RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v
|retrieving revision 1.55
|diff -u -r1.55 vidcontrol.1
|--- vidcontrol.1   2 Mar 2003 21:04:21 -   1.55
|+++ vidcontrol.1   17 Jan 2005 05:27:25 -
--
Patching file vidcontrol.1 using Plan A...
Hunk #1 failed at 11.
Hunk #2 failed at 88.
Hunk #3 failed at 297.
Hunk #4 failed at 532.
4 out of 4 hunks failed--saving rejects to vidcontrol.1.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|Index: vidcontrol.c
|===
|RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v
|retrieving revision 1.48
|diff -u -r1.48 vidcontrol.c
|--- vidcontrol.c   13 Jan 2005 03:59:44 -  1.48
|+++ vidcontrol.c   17 Jan 2005 05:27:25 -
--
Patching file vidcontrol.c using Plan A...
Hunk #1 failed at 24.
Hunk #2 failed at 48.
Hunk #3 failed at 66.
Hunk #4 failed at 187.
Hunk #5 failed at 223.
Hunk #6 failed at 239.
Hunk #7 failed at 257.
Hunk #8 failed at 297.
Hunk #9 failed at 332.
Hunk #10 failed at 348.
Hunk #11 failed at 377.
Hunk #12 failed at 419.
Hunk #13 failed at 507.
Hunk #14 failed at 572.
Hunk #15 failed at 669.
Hunk #16 failed at 722.
Hunk #17 failed at 743.
Hunk #18 failed at 806.
Hunk #19 failed at 891.
Hunk #20 failed at 900.
Hunk #21 failed at 933.
Hunk #22 failed at 950.
Hunk #23 failed at 962.
Hunk #24 failed at 985.
Hunk #25 failed at 1035.
Hunk #26 failed at 1050.
Hunk #27 failed at 1148.
Hunk #28 failed at 1173.
Hunk #29 failed at 1217.
Hunk #30 failed at 1234.
30 out of 30 hunks failed--saving rejects to vidcontrol.c.rej
done
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Jay O'Brien píše v ne 10. 04. 2005 v 15:21 -0700:
> Michal Mertl wrote:
> > There's no standard VGA 132 character text mode. It's either provided by
> > VESA or emulated using some graphics mode. Newer graphics hardware
> > stopped supporting extended text modes. If you want such modes you need
> > to emulate them (render the characters using lots of small dots instead
> > of just writing characters to the adapter which renders them for you).
> > Support for this functionality is included in syscons/vga driver when
> > you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar
> > graphics mode 800x600 dots with 4 bits (16) of color information per
> > pixel which can be run on old plain VGA with 256KB of memory.
> > 
> > The patches we are talking about add support for rendering the
> > characters in any graphics mode your card supports (through VESA) with
> > >= 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions
> > of colours) for a text mode console. You can't use any graphics there
> > but the textual resolution will be bigger. There also isn't support for
> > using simultaneously more than 16 (or is it 15?) different colors for
> > characters even when milions are technically possible.
> > 
> 
> Thanks for the explanation, it is appreciated. I tried the process and 
> encountered errors. Here's what happened: 
> 
> patch  patch  
> 
> 
> # patch  me...
> The text leading up to this was:
> --
> |Index: vidcontrol.1
> |===
> |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v
> |retrieving revision 1.55
> |diff -u -r1.55 vidcontrol.1
> |--- vidcontrol.1 2 Mar 2003 21:04:21 -   1.55
> |+++ vidcontrol.1 17 Jan 2005 05:27:25 -
> --
> Patching file vidcontrol.1 using Plan A...
> Hunk #1 succeeded at 11.
> Hunk #2 succeeded at 88.
> Hunk #3 succeeded at 297.
> Hunk #4 succeeded at 532.
> Hmm...  The next patch looks like a unified diff to me...
> The text leading up to this was:
> --
> |Index: vidcontrol.c
> |===
> |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v
> |retrieving revision 1.48
> |diff -u -r1.48 vidcontrol.c
> |--- vidcontrol.c 13 Jan 2005 03:59:44 -  1.48
> |+++ vidcontrol.c 17 Jan 2005 05:27:25 -
> --
> Patching file vidcontrol.c using Plan A...
> Hunk #1 succeeded at 24.
> Hunk #2 succeeded at 48.
> Hunk #3 succeeded at 66 with fuzz 1.
> Hunk #4 failed at 187.
> Hunk #5 succeeded at 223.
> Hunk #6 failed at 239.
> Hunk #7 failed at 257.
> Hunk #8 failed at 297.
> Hunk #9 failed at 332.
> Hunk #10 succeeded at 348 with fuzz 2.
> Hunk #11 failed at 377.
> Hunk #12 failed at 419.
> Hunk #13 failed at 507.
> Hunk #14 failed at 572.
> Hunk #15 failed at 669.
> Hunk #16 failed at 722.
> Hunk #17 failed at 743.
> Hunk #18 failed at 806.
> Hunk #19 succeeded at 891.
> Hunk #20 failed at 900.
> Hunk #21 failed at 933.
> Hunk #22 succeeded at 950 with fuzz 2.
> Hunk #23 failed at 962.
> Hunk #24 failed at 985.
> Hunk #25 failed at 1035.
> Hunk #26 failed at 1050.
> Hunk #27 succeeded at 1148.
> Hunk #28 succeeded at 1173.
> Hunk #29 succeeded at 1217.
> Hunk #30 succeeded at 1234.
> 19 out of 30 hunks failed--saving rejects to vidcontrol.c.rej
> done
> 
> 
> 
> Not being a c programmer, I can't understand what the 
> vidcontrol.c.rej file is trying to tell me. It is a 29K file.
> 
> As I recalled a previous email telling someone to go ahead 
> anyway, I went ahead with make clean and that went ok. Then I 
> did make all and here's the results:

You haven't read the thread in the archives carefully enough, have you?

Here is what I wrote (privately to the original poster but I explained
the error to the mailing list too):

> What? I don't know how the patching of vidcontrol ended but you'd
> better redo it with fresh files from current. Go download vidcontrol.c
> v 1.48 and vidcontrol.1 from
> http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/
>
> Then run the patch on it again and recompile/reinstall vidcontrol
> binary.



Michal

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Jay O'Brien]

Michal Mertl wrote:
> There's no standard VGA 132 character text mode. It's either provided by
> VESA or emulated using some graphics mode. Newer graphics hardware
> stopped supporting extended text modes. If you want such modes you need
> to emulate them (render the characters using lots of small dots instead
> of just writing characters to the adapter which renders them for you).
> Support for this functionality is included in syscons/vga driver when
> you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar
> graphics mode 800x600 dots with 4 bits (16) of color information per
> pixel which can be run on old plain VGA with 256KB of memory.
> 
> The patches we are talking about add support for rendering the
> characters in any graphics mode your card supports (through VESA) with
> >= 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions
> of colours) for a text mode console. You can't use any graphics there
> but the textual resolution will be bigger. There also isn't support for
> using simultaneously more than 16 (or is it 15?) different colors for
> characters even when milions are technically possible.
> 

Thanks for the explanation, it is appreciated. I tried the process and 
encountered errors. Here's what happened: 

patch http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Jay O'Brien wrote:
> Michal Mertl wrote:

> >>
> >>I feel like I am missing a lot here. I want to display 132 characters per 
> >>line on my console. I am not running X Windows and it is not a notebook.
> > 
> > 
> > It doesn't matter. I only saw the most complaints from notebook owners
> > who didn't have text mode console covering all LCD surface.
> > 
> > 
> >>I am running 5.3-RELEASE-p5 #0.
> >>
> >>What is this SC_PIXEL_MODE and where may I find documentation on it? I 
> >>don't find it in /usr/src/sys/i386/conf/NOTES. 
> > 
> > 
> > man syscons(4). It's also mentioned in NOTES although not the NOTES you
> > were looking at. Don't forget that on 5.x there are two conf directories
> > - one platform independent in /sys/conf and other in /sys/$ARCH/conf.
> > Common (platform independent) options like this one are
> > in /sys/conf/NOTES.
> > 
> 
> 
> Thanks! Now that I see that it is perhaps not required for my system, that 
> is not a laptop, is it possible that I don't need this at all? Is it 
> definitely needed to support 132 character terminal mode, or is just 
> needed for laptops? 

There's no standard VGA 132 character text mode. It's either provided by
VESA or emulated using some graphics mode. Newer graphics hardware
stopped supporting extended text modes. If you want such modes you need
to emulate them (render the characters using lots of small dots instead
of just writing characters to the adapter which renders them for you).
Support for this functionality is included in syscons/vga driver when
you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar
graphics mode 800x600 dots with 4 bits (16) of color information per
pixel which can be run on old plain VGA with 256KB of memory.

The patches we are talking about add support for rendering the
characters in any graphics mode your card supports (through VESA) with
>= 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions
of colours) for a text mode console. You can't use any graphics there
but the textual resolution will be bigger. There also isn't support for
using simultaneously more than 16 (or is it 15?) different colors for
characters even when milions are technically possible.

> It is wonderful to be a part of a caring community that spans the 
> world, without concern for international borders. Fortunately for 
> me, everyone uses english; I'm stuck with only one language (plus 
> international morse code, but that's another story).

Yes, it really is great. Not the English though. I'd prefer Czech but
I'm afraid it's a lost battle :-).

Michal

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Jay O'Brien]

Michal Mertl wrote:

> Jay O'Brien wrote:
> 
>>Michal Mertl wrote:
>>
>>
>>>Didier Wiroth wrote:
>>>
>>>
>>>
Hi,

I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati
mobility radeon 9600.
Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does
not work, 90x60 is the highest resolution I can get for now.
It looks like I'm not the only one having this problem with ati
chipsets:
http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w
ww/db/text/2005/freebsd-questions/20050123.freebsd-questions


I saw this posting:
http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht
ml

Unfortunately I'm not a programmer and have no ... to very poor patching
skills.
It looks to me, that in this posting(s) a "few" patches are grouped
together to enable vesa 1024x768.

1) Has someone applied this patches?
2) As the patch(es) is/are on the entire page, I don't know how to
separate them. Would someone mail me as an attachment the different
patches and tell me how I should apply them:
for example, mail me patch1, patch2, patch3
and the explanation how to patch them:
cd /usr/src
patch < ~/patch1
patch < ~/patch2 ...etc
>>>
>>>
>>>I think the newest and probably best (?) patch was prepared by Xin Li
>>>([EMAIL PROTECTED]) who is also committer. I sent this email to him
>>>(or she? - sorry about that) in case he has some comments. Beware that
>>>he said he experienced some problems with previous version of the patch.
>>>
>>>I haven't tested this version of the patch myself but it at least
>>>compiles.
>>>
>>>It's available at http://people.freebsd.org/~delphij/vesa/
>>>in files syscons.diff.20050215 and vidcontrol.diff.20050215
>>>
>>>You would apply them with:
>>>
>>>cd /usr/src/sys/dev/syscons
>>>patch < /path/syscons.diff.20050215
>>>cd /usr/src/usr.sbin/vidcontrol
>>>patch >>make clean
>>>make all
>>>make install
>>>
>>>You need also to rebuild and reinstall the kernel. You must have
>>>'options SC_PIXEL_MODE' in your kernel config. You also need to have
>>>VESA available - you can load it with kldload vesa or include it in the
>>>kernel with 'options VESA'.
>>>
>>>After reboot with the new kernel you should be able to get list of all
>>>VESA and standard modes your card support with 'vidcontrol -i mode'. To
>>>be able to use them as your console mode you need to have the
>>>appropriate font loaded. The font resolution is seen in vidcontrol
>>>output in the 'font' column. To load the font 8x8 you can use
>>>'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To
>>>set the mode use 'vidcontrol MODE_$num' where $num is the mode number
>>>(first column in 'vidcontrol -i mode' output).
>>>
>>>HTH
>>>
>>>Michal
>>>
>>>
>>
>>
>>I feel like I am missing a lot here. I want to display 132 characters per 
>>line on my console. I am not running X Windows and it is not a notebook.
> 
> 
> It doesn't matter. I only saw the most complaints from notebook owners
> who didn't have text mode console covering all LCD surface.
> 
> 
>>I am running 5.3-RELEASE-p5 #0.
>>
>>What is this SC_PIXEL_MODE and where may I find documentation on it? I 
>>don't find it in /usr/src/sys/i386/conf/NOTES. 
> 
> 
> man syscons(4). It's also mentioned in NOTES although not the NOTES you
> were looking at. Don't forget that on 5.x there are two conf directories
> - one platform independent in /sys/conf and other in /sys/$ARCH/conf.
> Common (platform independent) options like this one are
> in /sys/conf/NOTES.
> 


Thanks! Now that I see that it is perhaps not required for my system, that 
is not a laptop, is it possible that I don't need this at all? Is it 
definitely needed to support 132 character terminal mode, or is just 
needed for laptops? 


> 
>>To "rebuild and reinstall the kernel", after editing my 
>>/usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 
>>'make buildkernel' and then 'make installkernel' or is there something 
>>else I'm missing?  
> 
> 
> No, that's the way to do it.
> 
> 
>>I note that some of the messages are posted to multiple mailing lists, 
>>and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing 
>>the entire story.
> 
> 
> I'm afraid that's quite possible. Please go search the archives.
> 
> 
>>Jay O'Brien 
>>Rio Linda, California USA
> 
> 
> Michal Mertl
> 
> Prague, Bohemia, Czech Republic :-)
> 

It is wonderful to be a part of a caring community that spans the 
world, without concern for international borders. Fortunately for 
me, everyone uses english; I'm stuck with only one language (plus 
international morse code, but that's another story).

Jay O'Brien
Rio Linda, California, USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Jay O'Brien wrote:
> Michal Mertl wrote:
> 
> > Didier Wiroth wrote:
> > 
> > 
> >>Hi,
> >>
> >>I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati
> >>mobility radeon 9600.
> >>Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does
> >>not work, 90x60 is the highest resolution I can get for now.
> >>It looks like I'm not the only one having this problem with ati
> >>chipsets:
> >>http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w
> >>ww/db/text/2005/freebsd-questions/20050123.freebsd-questions
> >>
> >>
> >>I saw this posting:
> >>http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht
> >>ml
> >>
> >>Unfortunately I'm not a programmer and have no ... to very poor patching
> >>skills.
> >>It looks to me, that in this posting(s) a "few" patches are grouped
> >>together to enable vesa 1024x768.
> >>
> >>1) Has someone applied this patches?
> >>2) As the patch(es) is/are on the entire page, I don't know how to
> >>separate them. Would someone mail me as an attachment the different
> >>patches and tell me how I should apply them:
> >>for example, mail me patch1, patch2, patch3
> >>and the explanation how to patch them:
> >>cd /usr/src
> >>patch < ~/patch1
> >>patch < ~/patch2 ...etc
> > 
> > 
> > I think the newest and probably best (?) patch was prepared by Xin Li
> > ([EMAIL PROTECTED]) who is also committer. I sent this email to him
> > (or she? - sorry about that) in case he has some comments. Beware that
> > he said he experienced some problems with previous version of the patch.
> > 
> > I haven't tested this version of the patch myself but it at least
> > compiles.
> > 
> > It's available at http://people.freebsd.org/~delphij/vesa/
> > in files syscons.diff.20050215 and vidcontrol.diff.20050215
> > 
> > You would apply them with:
> > 
> > cd /usr/src/sys/dev/syscons
> > patch < /path/syscons.diff.20050215
> > cd /usr/src/usr.sbin/vidcontrol
> > patch  > make clean
> > make all
> > make install
> > 
> > You need also to rebuild and reinstall the kernel. You must have
> > 'options SC_PIXEL_MODE' in your kernel config. You also need to have
> > VESA available - you can load it with kldload vesa or include it in the
> > kernel with 'options VESA'.
> > 
> > After reboot with the new kernel you should be able to get list of all
> > VESA and standard modes your card support with 'vidcontrol -i mode'. To
> > be able to use them as your console mode you need to have the
> > appropriate font loaded. The font resolution is seen in vidcontrol
> > output in the 'font' column. To load the font 8x8 you can use
> > 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To
> > set the mode use 'vidcontrol MODE_$num' where $num is the mode number
> > (first column in 'vidcontrol -i mode' output).
> > 
> > HTH
> > 
> > Michal
> > 
> > 
> 
> 
> I feel like I am missing a lot here. I want to display 132 characters per 
> line on my console. I am not running X Windows and it is not a notebook.

It doesn't matter. I only saw the most complaints from notebook owners
who didn't have text mode console covering all LCD surface.

> I am running 5.3-RELEASE-p5 #0.
> 
> What is this SC_PIXEL_MODE and where may I find documentation on it? I 
> don't find it in /usr/src/sys/i386/conf/NOTES. 

man syscons(4). It's also mentioned in NOTES although not the NOTES you
were looking at. Don't forget that on 5.x there are two conf directories
- one platform independent in /sys/conf and other in /sys/$ARCH/conf.
Common (platform independent) options like this one are
in /sys/conf/NOTES.

> To "rebuild and reinstall the kernel", after editing my 
> /usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 
> 'make buildkernel' and then 'make installkernel' or is there something 
> else I'm missing?  

No, that's the way to do it.

> I note that some of the messages are posted to multiple mailing lists, 
> and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing 
> the entire story.

I'm afraid that's quite possible. Please go search the archives.

> Jay O'Brien 
> Rio Linda, California USA

Michal Mertl

Prague, Bohemia, Czech Republic :-)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Jay O'Brien]

Michal Mertl wrote:

> Didier Wiroth wrote:
> 
> 
>>Hi,
>>
>>I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati
>>mobility radeon 9600.
>>Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does
>>not work, 90x60 is the highest resolution I can get for now.
>>It looks like I'm not the only one having this problem with ati
>>chipsets:
>>http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w
>>ww/db/text/2005/freebsd-questions/20050123.freebsd-questions
>>
>>
>>I saw this posting:
>>http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht
>>ml
>>
>>Unfortunately I'm not a programmer and have no ... to very poor patching
>>skills.
>>It looks to me, that in this posting(s) a "few" patches are grouped
>>together to enable vesa 1024x768.
>>
>>1) Has someone applied this patches?
>>2) As the patch(es) is/are on the entire page, I don't know how to
>>separate them. Would someone mail me as an attachment the different
>>patches and tell me how I should apply them:
>>for example, mail me patch1, patch2, patch3
>>and the explanation how to patch them:
>>cd /usr/src
>>patch < ~/patch1
>>patch < ~/patch2 ...etc
> 
> 
> I think the newest and probably best (?) patch was prepared by Xin Li
> ([EMAIL PROTECTED]) who is also committer. I sent this email to him
> (or she? - sorry about that) in case he has some comments. Beware that
> he said he experienced some problems with previous version of the patch.
> 
> I haven't tested this version of the patch myself but it at least
> compiles.
> 
> It's available at http://people.freebsd.org/~delphij/vesa/
> in files syscons.diff.20050215 and vidcontrol.diff.20050215
> 
> You would apply them with:
> 
> cd /usr/src/sys/dev/syscons
> patch < /path/syscons.diff.20050215
> cd /usr/src/usr.sbin/vidcontrol
> patch  make clean
> make all
> make install
> 
> You need also to rebuild and reinstall the kernel. You must have
> 'options SC_PIXEL_MODE' in your kernel config. You also need to have
> VESA available - you can load it with kldload vesa or include it in the
> kernel with 'options VESA'.
> 
> After reboot with the new kernel you should be able to get list of all
> VESA and standard modes your card support with 'vidcontrol -i mode'. To
> be able to use them as your console mode you need to have the
> appropriate font loaded. The font resolution is seen in vidcontrol
> output in the 'font' column. To load the font 8x8 you can use
> 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To
> set the mode use 'vidcontrol MODE_$num' where $num is the mode number
> (first column in 'vidcontrol -i mode' output).
> 
> HTH
> 
> Michal
> 
> 


I feel like I am missing a lot here. I want to display 132 characters per 
line on my console. I am not running X Windows and it is not a notebook.
I am running 5.3-RELEASE-p5 #0.

What is this SC_PIXEL_MODE and where may I find documentation on it? I 
don't find it in /usr/src/sys/i386/conf/NOTES. 

To "rebuild and reinstall the kernel", after editing my 
/usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 
'make buildkernel' and then 'make installkernel' or is there something 
else I'm missing?  

I note that some of the messages are posted to multiple mailing lists, 
and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing 
the entire story.

Jay O'Brien 
Rio Linda, California USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Didier Wiroth]

Ok, sorry!
I rebooted now to be sure and... the touchpad work and the "usb mouse"
does work too!
But still error messages.
Didier

-Original Message-
From: Didier Wiroth [mailto:[EMAIL PROTECTED]
Sent: Friday, April 08, 2005 11:00
To: 'Xin LI'
Cc: 'freebsd-questions@freebsd.org'; 'freebsd-current@freebsd.org';
'[EMAIL PROTECTED]'
Subject: RE: [PATCH TO TEST] VESA [1024x768] mode support for
FreeBSD-CURRENT

Hello,
Thx for the patch, I tried it and here is my feedback.

To clear out things I'm not using CURRENT, I used:
a) FreeBSD5.4-prerelease (as I'm using RELENG_5), running on a HP NC6000
laptop, connected to a docking station with a Microsoft USB mouse
b) I downloaded the current rc.d/moused version 1.9 and patched the file
with your patch
c) copied the current-patched file

1) Unfortunately the problem still exists, error messages still appear.
2) The touchpad worked but my usb mouse didn't work at all

>I don't have a patch that is good enough to warrant a commit at
present.
>You may want to try the patch attached, but I can not promise that it
will work for every case.
>Thanks for your testing!



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Didier Wiroth]

Hello,
Thx for the patch, I tried it and here is my feedback.

To clear out things I'm not using CURRENT, I used:
a) FreeBSD5.4-prerelease (as I'm using RELENG_5), running on a HP NC6000
laptop, connected to a docking station with a Microsoft USB mouse
b) I downloaded the current rc.d/moused version 1.9 and patched the file
with your patch
c) copied the current-patched file

1) Unfortunately the problem still exists, error messages still appear.
2) The touchpad worked but my usb mouse didn't work at all

>I don't have a patch that is good enough to warrant a commit at
present.
>You may want to try the patch attached, but I can not promise that it
will work for every case.
>Thanks for your testing!



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Xin LI]

Hi, Michal,

å 2005-04-05äç 22:07 +0200ïMichal Mertlåéï
> Didier Wiroth wrote:
> > Hello,
> > Thank you very much for replying.
> > 
> > > cd /usr/src/usr.sbin/vidcontrol
> > > patch  > 
> > I'm using the RELENG_5 sources from today.
> 
> > The syscons.diff.20050215 works but the vidcontrol.diff.20050215 gives
> > some errors.
> 
> The diff is against the sources from -CURRENT where it applies and
> compiles cleanly. You should be ok using the current vidcontrol sources
> on -STABLE. The only difference is just some code purity fixes by Xin Li
> - probably in preparation for integrating the changes we speak about.

I went into some problem when using the patch on my own laptop, which
indicates that USB based mouse can play something nasty with the
patchset :-(  It does not affect the functionality seriously, but is
really annoying.  I would appreciate if someone can fix the issue.

Cheers,
-- 
Xin LI   http://www.delphij.net/


signature.asc
Description: This is a digitally signed message part

RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Xin LI]

Hi, Didier,

å 2005-04-06äç 13:39 +0200ïDidier Wirothåéï
> Is there a patch available for the rc.d mouse script?

I don't have a patch that is good enough to warrant a commit at present.
You may want to try the patch attached, but I can not promise that it
will work for every case.

Thanks for your testing!

Cheers,
-- 
Xin LI   http://www.delphij.net/
Index: jail
===
RCS file: /home/ncvs/src/etc/rc.d/jail,v
retrieving revision 1.21
diff -u -r1.21 jail
--- jail	16 Jan 2005 03:12:03 -	1.21
+++ jail	1 Feb 2005 07:21:57 -
@@ -59,6 +59,14 @@
 	eval jail_procfs=\"\$jail_${_j}_procfs_enable\"
 	[ -z "${jail_procfs}" ] && jail_procfs="NO"
 
+	# Default settings for skel jail
+	eval jail_skel_enable=\"\$jail_${_j}_skel_enable\"
+	[ -z "${jail_skel_enable}" ] && jail_skel_enable="NO"
+	eval jail_skel_root=\"\$jail_${_j}_skel_root\"
+	[ -z "${jail_skel_root}" ] && jail_skel_root="/"
+	eval jail_skel_romounts=\"\$jail_${_j}_skel_romounts\"
+	[ -z "${jail_skel_romounts}" ] && jail_skel_romounts="bin sbin lib libexec usr/bin usr/sbin usr/include usr/lib usr/libdata usr/libexec usr/sbin usr/share"
+
 	eval jail_mount=\"\$jail_${_j}_mount_enable\"
 	[ -z "${jail_mount}" ] && jail_mount="NO"
 	# "/etc/fstab.${_j}" will be used for {,u}mount(8) if none is specified.
@@ -81,6 +89,9 @@
 	debug "$_j fstab: $jail_fstab"
 	debug "$_j exec start: $jail_exec_start"
 	debug "$_j exec stop: $jail_exec_stop"
+	debug "$_j skel enable: $jail_skel_enable"
+	debug "$_j skel mount-readonly: $jail_skel_romounts"
+	debug "$_j skel mount-readonly from: $jail_skel_root"
 }
 
 # set_sysctl rc_knob mib msg
@@ -136,6 +147,14 @@
 		[ -f "${jail_fstab}" ] || warn "${jail_fstab} does not exist"
 		umount -a -F "${jail_fstab}" >/dev/null 2>&1
 	fi
+	if checkyesno jail_skel_enable; then
+		for _mntpt in $jail_skel_romounts
+		do
+			if [ -d "${jail_rootdir}/${_mntpt}" ] ; then
+umount -f ${jail_rootdir}/${_mntpt} > /dev/null 2>&1
+			fi
+		done
+	fi
 }
 
 jail_start()
@@ -155,6 +174,13 @@
 	for _jail in ${jail_list}
 	do
 		init_variables $_jail
+		if checkyesno jail_skel_enable; then
+			info "Mounting skeleton for jail ${_jail} from ${jail_skel_root}"
+			for _mntpt in $jail_skel_romounts
+			do
+mount_nullfs -ordonly ${jail_skel_root}/${_mntpt} ${jail_rootdir}/${_mntpt} > /dev/null 2>&1
+			done
+		fi
 		if checkyesno jail_mount; then
 			info "Mounting fstab for jail ${_jail} (${jail_fstab})"
 			if [ ! -f "${jail_fstab}" ]; then
Index: moused
===
RCS file: /home/ncvs/src/etc/rc.d/moused,v
retrieving revision 1.9
diff -u -r1.9 moused
--- moused	16 Jan 2005 03:12:03 -	1.9
+++ moused	7 Apr 2005 13:41:45 -
@@ -10,10 +10,16 @@
 
 . /etc/rc.subr
 
+# stdin must be redirected because it might be a serial console
+#
+ttyv=/dev/ttyv0
+
 name=moused
 rcvar=`set_rcvar`
 command="/usr/sbin/${name}"
+required_files="${ttyv}"
 start_cmd="moused_start"
+stop_postcmd="moused_postcmd"
 _pidprefix="/var/run/moused"
 pidfile="${_pidprefix}.pid"
 _pidarg=
@@ -66,10 +72,13 @@
 		;;
 	esac
 
-	for ttyv in /dev/ttyv* ; do
-		vidcontrol < ${ttyv} ${_mousechar_arg} -m on
-	done
+	vidcontrol < ${ttyv} ${_mousechar_arg} -m on
 	echo '.'
 }
 
+moused_postcmd()
+{
+	vidcontrol < ${ttyv} -m off
+}
+
 run_rc_command $*


signature.asc
Description: This is a digitally signed message part

RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Didier Wiroth]

Hi,
I've updated the vidcontrol sources to those in the current cvs and was
able to compile and install the patch on stable.
High resolution console is fantastic have 1400x1050 (MODE_322) on my
laptop now.
I get an "pfctl -sa", on one screen ... amazing :-))

It does make freebsd so much better ... I would be great to integrate
these patches in future releases, please!

The mouse actually works without problem in the console but I've a small
mouse bug after a reboot. I assume the /etc/rc.d/mouse script needs a
tiny patch. After a reboot and while launching the different
services/daemon, there are about 10 lines of vidcontrol errors. Here a
sample output:
vidcontrol: showing the mouse: invalid argument

Is there a patch available for the rc.d mouse script?

Thank you
Didier

>I believe Didier used broken vidcontrol.c file. The patch was for
current and needs to be applied to clean vidcontrol.c >ver 1.48.
>It works for me (on CURRENT anyways).
>Michal




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Didier Wiroth wrote:

> Unfortunately with patch applied it does not compile on stable:
> 
> Warning: Object directory not changed from original 
> /usr/src/usr.sbin/vidcontrol
> cc -O -pipe   -c vidcontrol.c
> vidcontrol.c: In function `video_mode':
> vidcontrol.c:500: error: `_VESA_800x600_DFL_COLS' undeclared (first use in 
> this 
> function)
> vidcontrol.c:500: error: (Each undeclared identifier is reported only once
> vidcontrol.c:500: error: for each function it appears in.)
> vidcontrol.c:505: error: `_VESA_800x600_DFL_FNSZ' undeclared (first use in 
> this 
> function)
> vidcontrol.c:509: error: `_VESA_800x600_DFL_ROWS' undeclared (first use in 
> this 
> function)
> *** Error code 1


I believe Didier used broken vidcontrol.c file. The patch was for
current and needs to be applied to clean vidcontrol.c ver 1.48.

It works for me (on CURRENT anyways).

Michal


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re : Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Didier Wiroth]

Unfortunately with patch applied it does not compile on stable:

Warning: Object directory not changed from original /usr/src/usr.sbin/vidcontrol
cc -O -pipe   -c vidcontrol.c
vidcontrol.c: In function `video_mode':
vidcontrol.c:500: error: `_VESA_800x600_DFL_COLS' undeclared (first use in this 
function)
vidcontrol.c:500: error: (Each undeclared identifier is reported only once
vidcontrol.c:500: error: for each function it appears in.)
vidcontrol.c:505: error: `_VESA_800x600_DFL_FNSZ' undeclared (first use in this 
function)
vidcontrol.c:509: error: `_VESA_800x600_DFL_ROWS' undeclared (first use in this 
function)
*** Error code 1


- Message d'origine -
De: Michal Mertl <[EMAIL PROTECTED]>
Date: Mardi, Avril 5, 2005 10:07 pm
Objet: Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for 
FreeBSD-CURRENT

> Didier Wiroth wrote:
> > Hello,
> > Thank you very much for replying.
> > 
> > > cd /usr/src/usr.sbin/vidcontrol
> > > patch  > 
> > I'm using the RELENG_5 sources from today.
> 
> > The syscons.diff.20050215 works but the vidcontrol.diff.20050215 
> gives> some errors.
> 
> The diff is against the sources from -CURRENT where it applies and
> compiles cleanly. You should be ok using the current vidcontrol 
> sourceson -STABLE. The only difference is just some code purity 
> fixes by Xin Li
> - probably in preparation for integrating the changes we speak about.
> 
> Michal
> 
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Didier Wiroth wrote:
> Hello,
> Thank you very much for replying.
> 
> > cd /usr/src/usr.sbin/vidcontrol
> > patch  
> I'm using the RELENG_5 sources from today.

> The syscons.diff.20050215 works but the vidcontrol.diff.20050215 gives
> some errors.

The diff is against the sources from -CURRENT where it applies and
compiles cleanly. You should be ok using the current vidcontrol sources
on -STABLE. The only difference is just some code purity fixes by Xin Li
- probably in preparation for integrating the changes we speak about.

Michal

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Didier Wiroth]

Hello,
Thank you very much for replying.

> cd /usr/src/usr.sbin/vidcontrol
> patch http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

[Michal Mertl]

Didier Wiroth wrote:

> Hi,
> 
> I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati
> mobility radeon 9600.
> Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does
> not work, 90x60 is the highest resolution I can get for now.
> It looks like I'm not the only one having this problem with ati
> chipsets:
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w
> ww/db/text/2005/freebsd-questions/20050123.freebsd-questions
> 
> 
> I saw this posting:
> http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht
> ml
> 
> Unfortunately I'm not a programmer and have no ... to very poor patching
> skills.
> It looks to me, that in this posting(s) a "few" patches are grouped
> together to enable vesa 1024x768.
> 
> 1) Has someone applied this patches?
> 2) As the patch(es) is/are on the entire page, I don't know how to
> separate them. Would someone mail me as an attachment the different
> patches and tell me how I should apply them:
> for example, mail me patch1, patch2, patch3
> and the explanation how to patch them:
> cd /usr/src
> patch < ~/patch1
> patch < ~/patch2 ...etc

I think the newest and probably best (?) patch was prepared by Xin Li
([EMAIL PROTECTED]) who is also committer. I sent this email to him
(or she? - sorry about that) in case he has some comments. Beware that
he said he experienced some problems with previous version of the patch.

I haven't tested this version of the patch myself but it at least
compiles.

It's available at http://people.freebsd.org/~delphij/vesa/
in files syscons.diff.20050215 and vidcontrol.diff.20050215

You would apply them with:

cd /usr/src/sys/dev/syscons
patch < /path/syscons.diff.20050215
cd /usr/src/usr.sbin/vidcontrol
patch http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: >> Patch patch-ac failed to apply cleanly.

[Ilker Ozupak]

I should have cc'ed this to here but after 12 hours sitting
in front of a PC, I sent to current..

forwarded to list so it would be archived.
sorry for the noise...
 IO
--  Forwarded Message  --

Subject: Re: >> Patch patch-ac failed to apply cleanly.
Date: Thursday 19 August 2004 19:15
From: Ilker Ozupak <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]

On Thursday 19 August 2004 18:18, Tyler Parrott wrote:
> Thanks, that took care of my problem with m4.
>
> I now have a similar problem with openldap.  After installing m4, I
> ran pkgdb -F again, and I downloaded the latest makefile from
> freebsd.org.   The following is the error I get:
>
> A332195# make install clean
> ===>  Patching for openldap-client-2.2.15
> ===>  Applying FreeBSD patches for openldap-client-2.2.15
> Ignoring previously applied (or reversed) patch.
> 3 out of 3 hunks ignored--saving rejects to build/ltmain.sh.rej
>
> >> Patch patch-build::ltmain.sh failed to apply cleanly.
>
> *** Error code 1
>
> Any ideas on this one?

again i would suggest you to use the web page
http://www.freebsd.org/cgi/cvsweb.cgi/ports//
or update your ports tree

Q: did you untar ports.tar.gz over existing ports tree??
if you did still have the tarball remove everything from ports and
untar it again.

- --
IO
- --
gpg public key @ http://cmpe.emu.edu.tr/ilker/ilker.asc
pub Â1024D/A4F41BD0 2003-07-16 Ilker Ozupak <[EMAIL PROTECTED]>
Primary key fingerprint: E509 17B6 C8E2 ADB7 32A7 Â4746 BF14 814A A4F4 1BD0
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: >> Patch patch-ac failed to apply cleanly.

[Lowell Gilbert]

Tyler Parrott <[EMAIL PROTECTED]> writes:

> I now have a similar problem with openldap.  After installing m4, I
> ran pkgdb -F again, and I downloaded the latest makefile from
> freebsd.org.

Sounds like you updated the makefile without updating the patches in
the port.  You need to update the *entire* port directory tree for
openldap if you're going to update any part of it.  [It is quite
common to use cvsup and do the entire ports tree in one shot...]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: >> Patch patch-ac failed to apply cleanly.

[Tyler Parrott]

Thanks, that took care of my problem with m4.

I now have a similar problem with openldap.  After installing m4, I
ran pkgdb -F again, and I downloaded the latest makefile from
freebsd.org.   The following is the error I get:

A332195# make install clean
===>  Patching for openldap-client-2.2.15
===>  Applying FreeBSD patches for openldap-client-2.2.15
Ignoring previously applied (or reversed) patch.
3 out of 3 hunks ignored--saving rejects to build/ltmain.sh.rej
>> Patch patch-build::ltmain.sh failed to apply cleanly.
*** Error code 1

Any ideas on this one?

On Thu, 19 Aug 2004 17:57:33 +0300, Ilker Ozupak <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> 
> On Thursday 19 August 2004 16:34, Tyler Parrott wrote:
> > Hey guys,
> >
> > I'm currently trying to build evolution (for the sole purpose of using
> > ximian-connector) and the install is choking on m4-1.4.1.
> >
> > The following is what I get when I try to install m4 separately:
> >
> > Chernak# make install
> > ===>  Vulnerability check disabled
> >
> > >> m4-1.4.1.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
> > >> Attempting to fetch from http://ftp.gnu.org/gnu/m4/.
> >
> > m4-1.4.1.tar.gz   100% of  335 kB  477 kBps
> > ===>  Extracting for m4-1.4.1
> >
> > >> Checksum OK for m4-1.4.1.tar.gz.
> >
> > ===>  Patching for m4-1.4.1
> > ===>  Applying FreeBSD patches for m4-1.4.1
> > Ignoring previously applied (or reversed) patch.
> > 2 out of 2 hunks ignored--saving rejects to src/m4.c.rej
> >
> > >> Patch patch-ac failed to apply cleanly.
> > >> Patch(es) patch-aa patch-ab applied cleanly.
> >
> > *** Error code 1
> >
> > Stop in /usr/ports/devel/m4.
> >
> > After getting this error, I did the following:
> >
> > Downloaded the latest ports.tar.gz from freebsd.org (don't have cvsup
> > configured yet), un tarred it into /usr/ports.  I then ran pkgdb -F
> > followed by portupgrade -aRr.
> >
> > Any ideas as to what else I can try?
> i checked my local ports collection and also looked at the cvs throught
> cvsweb cgi ( http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/m4/files )
> it seemed to me that patch-ac has been removed.
> give it a try after deleting patch-ac
> or
> download it from the web
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/m4/m4.tar.gz?tarball=1
> use this to built your port:
> cp m4.tar.gz /usr/ports/devel && untar it there (delete m4 folder first might
> be good)
> 
> >
> > Thanks
> > TP
> - --
> IO
> - --
> gpg public key @ http://cmpe.emu.edu.tr/ilker/ilker.asc
> pub  1024D/A4F41BD0 2003-07-16 Ilker Ozupak <[EMAIL PROTECTED]>
> Primary key fingerprint: E509 17B6 C8E2 ADB7 32A7  4746 BF14 814A A4F4 1BD0
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.4 (FreeBSD)
> 
> iD8DBQFBJL/rvxSBSqT0G9ARArNSAJwIrE4a9tsliZTdicD77k+V24sJ3wCfWnYK
> bCDeGMkY4IUVIabNXmSn5zA=
> =EhCS
> -END PGP SIGNATURE-
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: >> Patch patch-ac failed to apply cleanly.

[Ilker Ozupak]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 19 August 2004 16:34, Tyler Parrott wrote:
> Hey guys,
>
> I'm currently trying to build evolution (for the sole purpose of using
> ximian-connector) and the install is choking on m4-1.4.1.
>
> The following is what I get when I try to install m4 separately:
>
> Chernak# make install
> ===>  Vulnerability check disabled
>
> >> m4-1.4.1.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
> >> Attempting to fetch from http://ftp.gnu.org/gnu/m4/.
>
> m4-1.4.1.tar.gz   100% of  335 kB  477 kBps
> ===>  Extracting for m4-1.4.1
>
> >> Checksum OK for m4-1.4.1.tar.gz.
>
> ===>  Patching for m4-1.4.1
> ===>  Applying FreeBSD patches for m4-1.4.1
> Ignoring previously applied (or reversed) patch.
> 2 out of 2 hunks ignored--saving rejects to src/m4.c.rej
>
> >> Patch patch-ac failed to apply cleanly.
> >> Patch(es) patch-aa patch-ab applied cleanly.
>
> *** Error code 1
>
> Stop in /usr/ports/devel/m4.
>
> After getting this error, I did the following:
>
> Downloaded the latest ports.tar.gz from freebsd.org (don't have cvsup
> configured yet), un tarred it into /usr/ports.  I then ran pkgdb -F
> followed by portupgrade -aRr.
>
> Any ideas as to what else I can try?
i checked my local ports collection and also looked at the cvs throught
cvsweb cgi ( http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/m4/files )
it seemed to me that patch-ac has been removed.
give it a try after deleting patch-ac
or
download it from the web 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/m4/m4.tar.gz?tarball=1
use this to built your port:
cp m4.tar.gz /usr/ports/devel && untar it there (delete m4 folder first might 
be good)


>
> Thanks
> TP
- -- 
IO
- --
gpg public key @ http://cmpe.emu.edu.tr/ilker/ilker.asc
pub  1024D/A4F41BD0 2003-07-16 Ilker Ozupak <[EMAIL PROTECTED]>
Primary key fingerprint: E509 17B6 C8E2 ADB7 32A7  4746 BF14 814A A4F4 1BD0
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBJL/rvxSBSqT0G9ARArNSAJwIrE4a9tsliZTdicD77k+V24sJ3wCfWnYK
bCDeGMkY4IUVIabNXmSn5zA=
=EhCS
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch

[Chuck Swiger]

[EMAIL PROTECTED] wrote:
I have a source ( in fact it's many sources) divided in many directories;
and I have to patch it with a diff file. But when I perform the patch command,
the computers wants to know which file I want to patch; but there are a lot of
sources, and many of them have to be patched. So is there any option which can
specify that all sources must be modified ?
If you create the diff recursively (the -r option), it will record the 
directory structure so that patch knows how to find each of the changed files. 
 Create the diff from the same relative position as the patch command will 
run and you should be fine, otherwise consider the -d and -p options to patch...

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch level - info

[Jeremy Faulkner]

Joel Gudknecht wrote:
Does the freebsd website explain what has changed with every RELEASE
patch level?
I.E. 4.9-RELEASE-p1

What is p1 exactly, what has changed since?

TIA
/usr/src/UPDATING documents what has changed.

http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING?only_with_tag=RELENG_4_9
--
Jeremy Faulkner http://www.gldis.ca
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch SSH Not Work?

[Sean Hafeez]

the patch does not change the version string. there is an earlier email 
about this. look back a few days.

On Sunday, September 21, 2003, at 01:45 PM, Dustin Puryear wrote:

At 08:27 AM 9/19/2003 -0400, Ben Dover wrote:

I patched my SSHD on FreeBSD ver 5.1 (base system, not ports) and 
after stopping the SSHD server and restarting I checked the version 
and received the following:

schizoid# /usr/sbin/sshd -\?
sshd version OpenSSH_3.6.1p1 FreeBSD-20030423
Why did I not receive the September date?  Did the patch fail?
Show us exactly how you patched and then restarted sshd.

---
Dustin Puryear <[EMAIL PROTECTED]>
Puryear Information Technology, LLC 
Providing expertise in the management, integration, and
security of Windows and UNIX systems, networks, and applications.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch SSH Not Work?

[Brent Bailey]

I ran into the same thing...i ran the patch as per the directions on FBSD
website
ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc

but i still get the following:
sshd version OpenSSH_3.5p1 FreeBSD-20030201

when i do a ls -al on the /usr/sbin/sshd   it has the date as follows:

-r-xr-xr-x  1 root  wheel  151016 Sep 21 23:08 /usr/sbin/sshd*

that was the time i ran the patch...so i can only assume that the thing
was patched

is this the case or did i miss something ...when i did
# cd /usr/src
# patch < /path/to/sshd.patch
# cd /usr/src/secure/lib/libssh
# make depend && make all install
# cd /usr/src/secure/usr.sbin/sshd
# make depend && make all install
# cd /usr/src/secure/usr.bin/ssh
# make depend && make all install

everything seemed to go ok ... no errors...so did this work or not ?

thank you for all your help :-)
-- 
Brent Bailey CCNA
Bmyster LLC
Computer Networking and Webhosting
Network Engineer, Webmaster, President
http://www.bmyster.com
[EMAIL PROTECTED]
207-247-8330


> At 08:27 AM 9/19/2003 -0400, Ben Dover wrote:
>
>>I patched my SSHD on FreeBSD ver 5.1 (base system, not ports) and after
>>stopping the SSHD server and restarting I checked the version and
>> received
>>the following:
>>
>>schizoid# /usr/sbin/sshd -\?
>>sshd version OpenSSH_3.6.1p1 FreeBSD-20030423
>>
>>Why did I not receive the September date?  Did the patch fail?
>
> Show us exactly how you patched and then restarted sshd.
>
>
> ---
> Dustin Puryear <[EMAIL PROTECTED]>
> Puryear Information Technology, LLC 
> Providing expertise in the management, integration, and
> security of Windows and UNIX systems, networks, and applications.
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch for SSHD help !?!?!

[Gary]

Hi Brent,

--On Sunday, September 21, 2003 10:11:47 PM -0400 Brent Bailey 
<[EMAIL PROTECTED]> wrote:

patch < ~brent/PATCHES/buffer46.patch

it then asks me
File To Patch:< what do i do here ??..what file ??
First you have to look at the patch, to see what/where it goes into. Then 
do a locate for that file, or dir..  In this case, it is in

/usr/src/crypto/openssh

Put the patch in there... type patch < buffer46.patch


Ive never used this procedure before. Is there a howto on this procedure
that someone might be able to point me to ??
any help is great appreciated
That's it, then follow the instructions after patching . ...

See man patch to learn about patching.

--
Gary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: patch for SSHD help !?!?!

[Brent Bailey]

i tried leaving the deamon running...
i also followed the directions on the how to you sent..which is also the
same write up off of the main page

ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-03:12.openssh.asc

anywho ...when i do this i still get it askig me :

File to Patch:

im not sure what to enter here ??? anyone run into this ?

again im running FBSD 4.8rc1 w/ OpenSSH 3.5p1


any help is greatly appreciated
thanx
-- 
Brent Bailey CCNA
Bmyster LLC
Computer Networking and Webhosting
Network Engineer, Webmaster, President
http://www.bmyster.com
[EMAIL PROTECTED]
207-247-8330


> Brent Bailey on Sun, Sep 21, 2003 at 10:11:47PM -0400 wrote:
>> Hello,
>> Im running FBSD 4.8rc1 and im trying to patch the sshd using the
>> directions on the freebsd site. Im also using the out of the box version
>> of Openssh ...it think OpenSSH 3.5p1
>>
>> anywho im killing the sshd deamon and doing the following:
>
> don't kill the deamon till after your done with the patch.
>
>>
>> patch < ~brent/PATCHES/buffer46.patch
>>
>> it then asks me
>> File To Patch:< what do i do here ??..what file ??
>>
>> Ive never used this procedure before. Is there a howto on this procedure
>> that someone might be able to point me to ??
>
> step by step instructions:
>  http://www.freebsdforums.org/forums/showthread.php?threadid=14213
>
>
>> any help is great appreciated
>>
>> thank you
>> --
>> Brent Bailey CCNA
>> Bmyster LLC
>> Computer Networking and Webhosting
>> Network Engineer, Webmaster, President
>> http://www.bmyster.com
>> [EMAIL PROTECTED]
>> 207-247-8330
>>
>>
>>
>> ___
>> [EMAIL PROTECTED] mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "[EMAIL PROTECTED]"
>
> --
> Mark L Ogden
> [EMAIL PROTECTED]
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Patch SSH Not Work?

[Dustin Puryear]

At 08:27 AM 9/19/2003 -0400, Ben Dover wrote:

I patched my SSHD on FreeBSD ver 5.1 (base system, not ports) and after 
stopping the SSHD server and restarting I checked the version and received 
the following:

schizoid# /usr/sbin/sshd -\?
sshd version OpenSSH_3.6.1p1 FreeBSD-20030423
Why did I not receive the September date?  Did the patch fail?
Show us exactly how you patched and then restarted sshd.

---
Dustin Puryear <[EMAIL PROTECTED]>
Puryear Information Technology, LLC 
Providing expertise in the management, integration, and
security of Windows and UNIX systems, networks, and applications.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [PATCH] PPP in -direct mode does not execute any chat scripts

[Terry Lambert]

Maksim Yevmenkin wrote:
> Please find attached patch that adds new option to the PPP.
> 
> run-scripts-in-direct-mode
> Default: Disabled. This allows to run chat scripts in
> direct mode.
> 
> did i miss anything? objections? comments? reviews?

First comment: run it past Brian Somers <[EMAIL PROTECTED]>; it's
his baby, and he's the active maintainer.

Rest of comments:

Actually, why doesn't "-direct" allow a chat script by default?
The man page doesn't document that as a side-effect of "-direct",
only of "-dedicated", but it's been there since the import.

Should this really be a "negotiate" section command, rather than
just a command or a "set" command?

Also, there are only two other commands even have a "-" in them,
and both of them only have one (just seems a little long, compared
to, say, "rsid" or "direct-with-script", or even "force-script").

Personal preference: don't make it conditional on "-direct", let
it also work with "-dedicated", and call it "force-script" or
something, instead.

The man page should be updated -- including the undocumented
side-effect of "-direct" disabling scripts).

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: [PATCH] PPP in -direct mode does not execute any chat scripts

[M. Warner Losh]

In message: <[EMAIL PROTECTED]>
Maksim Yevmenkin <[EMAIL PROTECTED]> writes:
: Dear Hackers,
: 
: Please find attached patch that adds new option to the PPP.
: 
: 
: run-scripts-in-direct-mode
:   Default: Disabled. This allows to run chat scripts in
:   direct mode.
: 
: did i miss anything? objections? comments? reviews?

Maybe it would be better to call this "force-scripts" or something
more general purpose so that one could force the use of scripts
anywhere.  Making direct mode have a special case override seems a
little too restrictive.  The heart of the patch would become:

-  if (dl->physical->type & (PHYS_DIRECT|PHYS_DEDICATED))
+  if (!Enabled(dl->bundle, OPT_FORCE_SCRIPTS) &&
+  (dl->physical->type & (PHYS_DIRECT|PHYS_DEDICATED))
 /* Ignore scripts */
 runscripts = 0;

with corresponding changes to the docs, defines, etc.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message