On 4 March 2014 12:59, sven falempin wrote:
> I did it again with another disk:
>
> Which disk is the root disk? ('?' for details) [sd0]
> Use DUIDs rather than device names in fstab? [yes]
> Disk: sd0 geometry: 500/8/32 [312581808 Sectors]
> Offset: 0 Signature: 0xAA55
>
I recently set up npppd on a 5.4 system to provide l2tp VPN service. This
system is the border router, and also runs ospfd to communicate routes to
the internal network, some subnets of which use vlans on the OpenBSD system
itself to avail of pf, while others are routed on a layer 3 Cisco switch.
This new bug report is also incomplete.
You are done.
If this is a real and serious problem, I am certain someone else
will submit a complete and correct bug report.
> Using the current available amd64 snapshot (install.iso)
> the using whole disk install function do unexpected result.
> This h
Using the current available amd64 snapshot (install.iso)
the using whole disk install function do unexpected result.
This has been tested in 5.4, it is a regression.
It has been reproduced with a different disk, it gave the following
information,
Before installation i have the current data :
I'm sorry, this time against -current.
Regards
André
Index: newsyslog.c
===
RCS file: /cvs/src/usr.bin/newsyslog/newsyslog.c,v
retrieving revision 1.92
diff -u -r1.92 newsyslog.c
--- newsyslog.c 26 Nov 2013 13:19:07 - 1.92
Hi,
it seems there is a bug in newsyslog when using the monitor flag in
conjunction with a time specification. Files are only monitored if
they're about to getting rotated (time's up).
Given the following line in newsyslog.conf:
# Rotate every week on Monday at 00:00 hr
/var/log/
Sven,
You really need to write a single comprehensive bug report that has no
inconsistancies. THEN SEND IT IN ONE EMAIL. If after the initial
mail, you find that you have to send an addendum... then it means you
are being rude and inconsiderate of the developers.
If you think people are going t
I did it again with another disk:
Which disk is the root disk? ('?' for details) [sd0]
Use DUIDs rather than device names in fstab? [yes]
Disk: sd0 geometry: 500/8/32 [312581808 Sectors]
Offset: 0 Signature: 0xAA55
StartingEnding LBA Info:
#: id
On Tue, Mar 4, 2014 at 9:39 AM, sven falempin wrote:
>
>
>
> On Tue, Mar 4, 2014 at 8:46 AM, Kenneth Westerback
> wrote:
>
>> On 4 March 2014 08:41, sven falempin wrote:
>> > Installing the snapshot on external HD,
>> > when using W for all disk the installer created only a very small
>> > Parti
On Tue, Mar 4, 2014 at 8:46 AM, Kenneth Westerback wrote:
> On 4 March 2014 08:41, sven falempin wrote:
> > Installing the snapshot on external HD,
> > when using W for all disk the installer created only a very small
> > Partition (Disk was clean, all 4 base empty.
> >
> > Not present in 5.4 (i
Works ok for me. Tested on a Lenovo M58, and could go into installation.
For those with Mac OSC: to be able to create the USB stick on Macintosh
(MBPro), I used these commands (in a Terminal window):
bash-3.2$ diskutil list
/dev/disk0
#: TYPE NAMESIZE
On 4 March 2014 08:41, sven falempin wrote:
> Installing the snapshot on external HD,
> when using W for all disk the installer created only a very small
> Partition (Disk was clean, all 4 base empty.
>
> Not present in 5.4 (i tried, it creates the layout, then i use the snapshot
> 5.5 and use
>
Installing the snapshot on external HD,
when using W for all disk the installer created only a very small
Partition (Disk was clean, all 4 base empty.
Not present in 5.4 (i tried, it creates the layout, then i use the snapshot
5.5 and use
O [OpenBSD].
( Will use this disk on a machine with a non
I could not find this commited or further discussed.
Therefore: ping?
Bye, Marcus
ccut...@csail.mit.edu (Cody Cutler), 2013.11.29 (Fri) 20:32 (CET):
> j...@sing.id.au (Joel Sing) - Thu, Nov 28, 2013 at 03:16:20AM +1100
> > From a quick glance, you should be able to use opendev(3) to open the dis
Sorry if I missed a follow up discussion but to me this seems an
undeclined, untested and unapplied diff.
Flimsy excuse from me: no such hardware.
Bye, Marcus
b...@comstyle.com (Brad Smith), 2013.12.02 (Mon) 02:21 (CET):
> Here is a diff for the sf(4) Starfire driver to clean up and update the
>
Apologies if I missed something but to me it looks like this was neither
commited nor declined.
This is about
src/sys/dev/isa/soekris.c (nonexistent)
and not
src/sys/arch/amd64/amd64/bios.c Revision 1.23
Fake 'SMBIOS detection' for the Soekris boxes, by Matt Dainty
References:
http://marc.info/
16 matches
Mail list logo