Re: How to Run WindowMaker and GWorkspace on OBSD 5.3
Hello again Sebastian, As you advised I was able to successfully install most if not all the apps that are to be included with the gnustep-desktop meta-package. One thing I observed is that the behavior is buggy. For example, in the GWorkspace menu, I selected the Info->Preferences menu, this will open up a Gworkspace Preferences window where there's a pulldown, I chose from the pulldown the Terminal option, clicked on the textbox with the label xterm hoping to replace it with the GNUstep-native Terminal.app. After clicking on that textbox, the cursor will change into an I-cursor, AND STAY SO thorughout the system until I restart X again by clicking on the GWorkspace Quit menu option. Is this an already reported bug? Being a DIY system, I patiently took time to edit the .xinitrc to only have 'wmaker' as entry, then from the xterm session, run the command to run the likes of Gorm, ProjectCenter and GNUMail, once they run, their icon will appear on the bottom left, I will drag them individually on the right to group them together, then on the WindowMaker Application menu, click on Session->Save Session, and click on Session->Exit, check the 'Save Workspace State' checkbox, then click on the 'Exit' button to ensure that the icons of the GNUstep-native apps remain on the desktop once I change my .xinitrc file to contain the changes I described from last email. Is there a way to simplify this for the common user? I really like the GNUstep and OpenBSD tandem, it's so cool, hope this would be one of the desktop options in OBSD. Thank you very much and look forward to help test and refine GNUstep on OBSD. On 5/19/13, Sebastian Reitenbach wrote: > > On Saturday, May 18, 2013 18:06 CEST, Tito Mari Francis Escaño > wrote: > >> Thanks for the pointers SEbastian :) >> I tried creating an xsession or .xsession file with those contents but >> they >> didn't work. Following your example, what I did instead was to create on >> the home dir the file .xinitrc with the following content: >> wmaker & >> /usr/local/bin/gpbs >> /usr/local/bin/gndc >> /usr/local/bin/make_services >> /usr/local/bin/GWorkspace >> >> This enabled me to run X with the WindowMaker and automatically starting >> GWorkspace, with the effect that exits X11 when I Quit GWorkspace. Thank >> you very much. Now my next task is to run the installed apps when I ran >> the >> command: >> pkg_add gnustep-desktop >> >> Maybe you can further advise me on this. I'm very grateful. Thank you >> very >> much. > > good that it works for you. > The gnustep-meta package installs a README file, with some pointers to > websites: > You should find it there: > /usr/local/share/doc/pkg-readmes/gnustep-desktop-VERSION > > Otherwise take a look at each softwares homepage, those you can find here: > http://readme.portsbug.me.uk/cat/x11/gnustep > > I know that at least GNUMail is a bit flaky and crashes here and there :(, > but the > others should at least "just work" T.M. > > If something doesn't work for you, or crashes on you, send me bug report so > that > I am hopefully be able to reproduce the problem in order to fix it. > Or even better, send patches ;) > > Besides maintaining the ports, I'm also working upstream on GNUstep and GAP > > so any feedback is appreciated. > > cheers, > Sebastian > > >> >> >> >> On Sat, May 18, 2013 at 11:15 PM, Sebastian Reitenbach < >> sebas...@l00-bugdead-prods.de> wrote: >> >> > Hi, >> > >> > On Saturday, May 18, 2013 16:32 CEST, Tito Mari Francis Escaño < >> > titomarifran...@gmail.com> wrote: >> > >> > > Good day, >> > > I tried to install OpenBSD 5.3 64-bit on VMware Workstation 9.x and >> > > so >> > far >> > > it's working like a charm. >> > > I next tried to install WindowMaker, to override the default twm, I >> > created >> > > an .xinitrc file on home directory with just one entry: wmaker. When >> > > I >> > > typed startx, as expected, the X window manager is WindowMaker. >> > > I then installed GWorkspace, and to run it, I have to type in the >> > > xterm >> > > window: GWorkspace. >> > > I read the man page on startx, I tried to follow the example of >> > > /etc/X11/init/xinitrc where it ran "fcwm || xterm" to run xterm after >> > > the >> > > default WM started, by creating an /.xinitrc with "wmaker >> > > || >> > > GWorkspace" but it doesn't seem to work. >> > > Can somebody please give me pointers how I can run GWorkspace >> > automatically >> > > when I start X with WindowMaker as WM? >> > > Thank you very much. >> > > >> > >> > just install the gnustep-desktop meta package: >> > sudo pkg_add -i gnustep-desktop >> > >> > then, I have this in my .xsession file in order to start windowmaker >> > and >> > GWorkspace: >> > >> > >> > if [ -f /usr/local/share/GNUstep/Makefiles/GNUstep.sh ];then >> > . /usr/local/share/GNUstep/Makefiles/GNUstep.sh >> > fi >> > >> > export GNUSTEP_STRING_ENCODING=NSUTF8StringEncoding >> > export LC_ALL='en_EN.UTF-8' >> > export LC_CTYPE='en_US.UTF-8' >> > if [ -x /usr/local/bin/gpbs ];then
Happy Birthday Theo...
Hey, It's Theo's Birthday today. Yeah, you could wish him via E-Mail, or maybe even call him up, or to be dramatic, you could send him a physical mail. But, how about donating a small amount to the OpenBSD project? (http://www.openbsd.org/donations.html) It would be a nice way of saying "Happy Birthday Dear Theo..." :-) ~Mayuresh
Re: Kernel Panic with Mon May 13 snapshot
Hi,
I built a kernel that include the fix in pf.c and everything is fine now.
Thanks,
Atanas Vladimirov
[ns]~$ uptime
5:37PM up 3 days, 3:44, 1 user, load averages: 1.23, 0.74, 0.64
[ns]~$ dmesg
OpenBSD 5.3-current (GENERIC) #0: Wed May 15 23:59:01 EEST 2013
vl...@ns.bsdbg.net:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(TM) XP1600+ ("AuthenticAMD" 686-class, 256KB L2 cache)
1.42 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,MMXX,3DNOW2,3DNOW
real mem = 804765696 (767MB)
avail mem = 780185600 (744MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 03/03/03, BIOS32 rev. 0 @ 0xf0d00,
SMBIOS rev. 2.3 @ 0xf2bc0 (46 entries)
bios0: vendor Award Software, Inc. version "ASUS A7V266-C ACPI BIOS Rev
1014" date 03/03/2003
bios0: ASUSTeK Computer INC. A7V266-C
apm0 at bios0: Power Management spec V1.2 (BIOS management disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0x1572
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf14b0/192 (10 entries)
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT82C586 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xcc000/0x1000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8366 PCI" rev 0x00
viaagp0 at pchb0: v2
agp0 at viaagp0: aperture at 0xfe80, size 0xe40
ppb0 at pci0 dev 1 function 0 "VIA VT8366 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci0 dev 12 function 0 "S3 ViRGE DX/GX" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
em0 at pci0 dev 13 function 0 "Intel PRO/1000MT (82540EM)" rev 0x02: irq
11, address 00:07:e9:10:32:a8
em1 at pci0 dev 15 function 0 "Intel PRO/1000MT (82540EM)" rev 0x02: irq
10, address 00:07:e9:10:2a:20
viapm0 at pci0 dev 17 function 0 "VIA VT8233A ISA" rev 0x00: SMI
iic0 at viapm0
lm1 at iic0 addr 0x2d: AS99127F
viapm0: 24-bit timer at 3579545Hz
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: ATA133,
channel 0 configured to compatibility, channel 1 confi
gured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 17 function 2 "VIA VT83C572 USB" rev 0x23: irq 12
uhci1 at pci0 dev 17 function 3 "VIA VT83C572 USB" rev 0x23: irq 12
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "VIA UHCI root hub" rev 1.00/1.00 addr 1
usb1 at uhci1: USB revision 1.0
uhub1 at usb1 "VIA UHCI root hub" rev 1.00/1.00 addr 1
isa0 at mainbus0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
mtrr: Pentium Pro MTRR support
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
scsibus1 at softraid0: 256 targets
root on wd0a (b198b672451a33ab.a) swap on wd0b dump on wd0b
WARNING: / was not properly unmounted
Re: How to Run WindowMaker and GWorkspace on OBSD 5.3
I apologize if my concerns turn out to be noise here. As I said in my previous mails, WindowMaker with GWorkspace works, following your advise, with modifications made on .xinitrc instead. Will email GNUstep-specific list to air my concerns there. Thanks again for the pointers and kudos for the work :) On 5/19/13, Sebastian Reitenbach wrote: > Hi, > > On Sunday, May 19, 2013 15:57 CEST, Tito Mari Francis Escaño > wrote: > >> Hello again Sebastian, >> As you advised I was able to successfully install most if not all the >> apps that are to be included with the gnustep-desktop meta-package. >> One thing I observed is that the behavior is buggy. For example, in >> the GWorkspace menu, I selected the Info->Preferences menu, this will >> open up a Gworkspace Preferences window where there's a pulldown, I >> chose from the pulldown the Terminal option, clicked on the textbox >> with the label xterm hoping to replace it with the GNUstep-native >> Terminal.app. After clicking on that textbox, the cursor will change >> into an I-cursor, AND STAY SO thorughout the system until I restart X >> again by clicking on the GWorkspace Quit menu option. Is this an >> already reported bug? > > This is a known bug in any GNUstep application, that the cursor doesn't > reset. > It not only happens on OpenBSD. With this, its probably best to mention > that it also happens for you on the GNUstep mailing list: > > http://www.gnustep.org/information/gethelp.html > discuss-gnus...@gnu.org > > If there are enough people being bugged by it, and crying out, hopefully > someone will eventually fix it. > >> Being a DIY system, I patiently took time to edit the .xinitrc to only >> have 'wmaker' as entry, then from the xterm session, run the command >> to run the likes of Gorm, ProjectCenter and GNUMail, once they run, >> their icon will appear on the bottom left, I will drag them >> individually on the right to group them together, then on the >> WindowMaker Application menu, click on Session->Save Session, and >> click on Session->Exit, check the 'Save Workspace State' checkbox, >> then click on the 'Exit' button to ensure that the icons of the >> GNUstep-native apps remain on the desktop once I change my .xinitrc >> file to contain the changes I described from last email. Is there a >> way to simplify this for the common user? > > So you only have WindowMaker running, but no GWorkspace? > I cannot really follow you. > > I usually run WindowMaker together with GWorkspace. > GWorkspace provides a desktop, where you can just drag n drop apps on > the desktop, or on the Dock on the right. > > For example, go with the File Viewer to /usr/local/libexec/GNUstep > From there you can CTRL-Drag apps to the desktop, and it will ask you > whether you'll link them there. Then you have them on your GWorkspace > desktop. Or you can just drag them to the Dock on the right. > >> I really like the GNUstep and OpenBSD tandem, it's so cool, hope this >> would be one of the desktop options in OBSD. Thank you very much and >> look forward to help test and refine GNUstep on OBSD. > > Those questions are not really OpenBSD specific, but more GNUstep related. > So I think its a bit off-topic for the misc@ mailing list. Better to either > keep it private, > or I think you are better off, asking such things on the > discuss-gnus...@gnu.org mailing list. > > cheers, > Sebastian > > >> >> On 5/19/13, Sebastian Reitenbach wrote: >> > >> > On Saturday, May 18, 2013 18:06 CEST, Tito Mari Francis Escaño >> > wrote: >> > >> >> Thanks for the pointers SEbastian :) >> >> I tried creating an xsession or .xsession file with those contents but >> >> they >> >> didn't work. Following your example, what I did instead was to create >> >> on >> >> the home dir the file .xinitrc with the following content: >> >> wmaker & >> >> /usr/local/bin/gpbs >> >> /usr/local/bin/gndc >> >> /usr/local/bin/make_services >> >> /usr/local/bin/GWorkspace >> >> >> >> This enabled me to run X with the WindowMaker and automatically >> >> starting >> >> GWorkspace, with the effect that exits X11 when I Quit GWorkspace. >> >> Thank >> >> you very much. Now my next task is to run the installed apps when I >> >> ran >> >> the >> >> command: >> >> pkg_add gnustep-desktop >> >> >> >> Maybe you can further advise me on this. I'm very grateful. Thank you >> >> very >> >> much. >> > >> > good that it works for you. >> > The gnustep-meta package installs a README file, with some pointers to >> > websites: >> > You should find it there: >> > /usr/local/share/doc/pkg-readmes/gnustep-desktop-VERSION >> > >> > Otherwise take a look at each softwares homepage, those you can find >> > here: >> > http://readme.portsbug.me.uk/cat/x11/gnustep >> > >> > I know that at least GNUMail is a bit flaky and crashes here and there >> > :(, >> > but the >> > others should at least "just work" T.M. >> > >> > If something doesn't work for you, or crashes on you, send me bug report >> > so >> > that >> > I am hopefully be abl
Re: openospfd vs bird vs quagga etc on OpenBSD for OSPF interoperating with IOS XE (v4 & v6)
Hi Stuart, Thanks for your great response, all makes perfect sense. I will start with OpenOSPFd and OpenBGPd and see how I get on. I was initially thinking of using BIRD for the previously mentioned reasons, but considering all the points discussed I will start testing, testing testing... Wish me luck and thank you everyone for all your comments! :) Andrew Lemin On Sat, 18 May 2013 22:33:21 +0100, Stuart Henderson wrote: > On 2013/05/18 18:10, andy wrote: >> Hi, >> Sorry for the slow reply, have just got back home from the RIPE 66 >> conference in Dublin. Which was great by the way :) >> Thank you very much for your comments and suggestions. When building >> something like this it is really important to me to hear the experience >> and >> thoughts of others. >> >> Ok, so I think Quagga is out the Window. >> This is what I have got it down too.. I have put question marks next to >> the items which I am not 100% sure on, and a score of 1 to 10 on how >> important it is. >> >> >> *BIRD; >> - Pro's >> Widely deployed - 7/10 >> Heavily tested - 10/10 >> Great interoperability with Cisco - 10/10 >> Fast development with many developers working on it - 5/10 >> >> - Con's >> All routes treated with same priority - 4/10 >> No CARP demote - (Not sure if this is important or not?) - ?/10 > > Important con here if you're talking about running it on OpenBSD is that > this is not a primary platform for them. I think it's safe to say that > far fewer people will be running BIRD on OpenBSD than will be running > OpenOSPFd on OpenBSD. (I mostly just imported it to ports in case it's > useful for interoperability testing rather than to actually use it..) > >> *OpenBGPd/OpenOSPFd; >> - Pro's >> Tightly integrated into OBSD code - 7/10 >> Routes support different priorities - 5/10 > > This is important when you're running with multiple routing daemons > but less important if everything is done in one process. > >> Supports CARP demote - (Not sure if this is important or not?) - ?/10 > > If you are using ospfd on a machine (firewall, etc) which is also > running carp, yes it's very important, otherwise a machine can become > carp master when ospf is down so it has no onward routes. > >> Better configuration interface compared to Bird(?) - 3/10 >> >> - Con's >> Not so widely deployed(?) - 7/10 > > I don't think it's really possible to say which is more widely deployed.. > I'm pretty sure Quagga is more deployed than either, still that wouldn't > make me want to use it unless it was the only option ;) > >> Not as well tested(?) - 10/10 > > see above; definitely better tested than BIRD on OpenBSD. > >> More likely to have interoperability issues with Cisco maybe(?) - 10/10 > > no known problems, and we do minimal dead time for sub-second failover. > >> I seem to remember seeing something when googling like OpenOSPFd once had >> assert fail problems when receiving packets from other routing daemons >> with >> unknown attributes, is this true or still the case? I can't remember >> where >> I heard that so not sure if thats even true. > > You're thinking of something else (possibly quagga's ospfd?) > OpenBSD's ospfd has never had asserts. > >> What is the level of integration with CARP for OpenBGPd and OpenOSPFd? >> I.e. Can I have both the Primary 'and' the Backup firewalls sending and >> receiving routes all the time, but referring to the CARP IPs in the route >> entires so the forwarding plane uses the CARP Masters etc, and the >> routing >> control plane always involves all firewalls etc? This would mean that a >> CARP fail-over would effectively be an instantaneous re-convergence? >> (this >> is very important). > > With OpenOSPFd normally both carp master *and* carp backup will advertise > the route, master with a low (more preferred) metric, backup with a high > metric. So when a failover occurs, the route will not drop out at all, > it will switch straight over. I think this is what you're looking for. > Other routing daemons do not do this. > >> The network I am building is as follows; >> I have 3 data centres (one primary, one DR/backup, one >> staging/development). >> I am building 2 brand new POPs at two new central locations using two >> Cisco ASR 1002 routers to join the data centres and firewalls I have >> inherited together, and bring all POPs/DCs under the same ASN and global >> IP >> prefixes etc. >> >> The DR/backup and staging/dev DCs just have single layer 2 back-haul >> links >> (one to one POP, and the other to the other POP). >> The primary data center has a fibre to the first POP, and a second >> diverse >> path fibre to the other POP, and the two POPs have a fibre between them. >> >> Transits&IXPs >> | >>---POP1DR_DC >> Primary_DC-| | >>---POP2-Dev_DC >> | >> Transits&IXPs >> >> The two Cisco ASRs are going to run eBGP to announce our ASN and full >> prefix globally
softraid: adding volumes, CPU requirements, RAID5
Hi, I'm building myself an openbsd-based fileserver, which will initially have three disks with softraid in RAID5 mode. I've three questions regarding softraid: 1) I intend on using a single-core 1.8Ghz Atom processor I have lying around. Would that limit my performance too much? I'll be using this fileserver mostly for media (movies/series/music) and some ocassional backups. Can anyone share what CPU they've used and their experience? (I'm clarifying my intended usage for the fileserver since I think it's quite relevant to say if the CPU is or isn't enough). 2) How do I add additional volumes to an already created softraid volume? I intend on adding additional disks as necessary. Is it possible? 3) The man pages report RAID5 as experimental. I'm curious, why is this so? Is it just not-very-thoroughly tested, or is there some missing feature? I read on a 2010 presentation that rebuild was not implemented yet, is this still so? Thanks, -- Hugo Osvaldo Barrera [demime 1.01d removed an attachment of type application/pgp-signature]
