alphaOS [closed]
You really didn't have a reason to say my name. You created one. My name doesn't fit in that spot in your post. You made it fit. Like a square in a circle, it just don't fit right. Unless you KICK it in.
I think you owe me an apology. for accusing me of doing something i didn't do.
I wasn't rude to Puppy Linux or any of it's Developers.
I made a rude comment regarding someone's 'character' not their developing skills.
Furthermore...i decided to delete the rude post.
I guess because of the explosion in the last thread....I'm guilty of doing something. when i haven't done anything, except asked Barry a question.
I think you owe me an apology sc0ttman....
I think you owe me an apology. for accusing me of doing something i didn't do.
I wasn't rude to Puppy Linux or any of it's Developers.
I made a rude comment regarding someone's 'character' not their developing skills.
Furthermore...i decided to delete the rude post.
I guess because of the explosion in the last thread....I'm guilty of doing something. when i haven't done anything, except asked Barry a question.
I think you owe me an apology sc0ttman....
-
- Posts: 102
- Joined: Mon 23 May 2011, 13:10
Neither do I.sc0ttman wrote:I dont see the problem with AlphaOS and simargls works etc...
Sorry to say but I am not exactly sure about this paragraph.sc0ttman wrote:As long as it is made clear that despite using *some* of the Puppy Linux boot stuff, AlphaOS is NOT a proper puppy linux, and that it is a fork of puppy linux cos it is built using a different method, has a different setup etc, then i dont see the problem..
Please, don't take my words wrong but what exactly is Puppy? Where is it's official definition? Is it this one?
http://puppylinux.org/main/Overview%20a ... tarted.htm
Because if it is, there is not much on that list that AlphaOS isn't right now.
I mean, usually official Puppies do bring some stuff that is not in AlphaOS but we're talking about some CLI tools that now have GTKDialog GUIs.
It shouldn't take an enormous amount of space to include them in an additional SFS should we need them.
But I do get your point: AlphaOS looks different, is setup different and is organized different than most Puppies so I guess it should have it's own murga thread so that questions about it don't go clogging the rest of the forum where discussion is usually about official puppies.
Yes, there have been some very negative remarks and comments, some even in this thread by the form of link to youtube videos.sc0ttman wrote:I do of course see why many long time users have been upset by some of the rude comments...
I am not saying that people should be silenced and I don't want to reignite anything but we should always voice ourselves in polite manners.
If simargl, scooby or myself for that matter had ever referred to BarryK or Puppy in those manners we would have been immediately kicked out of here.
Never mind, hope it's all in the past now.
Cheers
Version 2.0.0 available
see screenshot in first post, and change log here http://alphaos.freeforums.org/version-2-0-0-t16.html
see screenshot in first post, and change log here http://alphaos.freeforums.org/version-2-0-0-t16.html
Yes , you are right http://murga-linux.com/puppy/viewtopic.php?t=75588, but that has only 3 gtk3 applications included,ally wrote:just waiting for the iso to become available
out of interest there is another puppy with gtk3 from jan 2012
214X-GTK3-alpha10.1.iso
here everything except firefox uses Gtk3 - so I will leave title as is.
iso is now available!
Edit and off-topic: I's sorry, but this forum starts to look kinda boring
Great! If you mean resolution is now OK, and other problems from hereally wrote:booting from lenovo t61
correctly configured display, sound and ethernet
startup music nice
would be useful to have a gui for locale, keyboard mapping though
http://www.murga-linux.com/puppy/viewto ... 252#693252 are now solved?
xf86-input-synaptic package is new, probably that package missing caused problems before.
What am I doing wrong? Should I press a key during boot to get the proper X display ?
This is my set-up (from inxi):
Thanks in advance.
musher0
This is my set-up (from inxi):
Is it compatible with alphaOS? I had the same problem with alphaOS v. 1.0.Machine: System: ASUS product: A7V400-MX version: 1.03 serial: 123456789000
Mobo: ASUSTek model: A7V400-MX version: 1.03 serial: 123456789000
Bios: Phoenix version: ASUS A7V400-MX 1009 date: 12/21/2004
CPU: Single core (AMD Athlon XP 2600+,1908.926,512 KB,fpu vme de pse tsc msr pae mce cx8
apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
up,3819.92,amd) (-UP-) cache: unknown flags: (-) clocked at MHz
Graphics: Card: Advanced Micro Devices [AMD] nee ATI R250 If [Radeon 9000]
X.org: 1.12.4 driver: radeon tty size: 129x72 Advanced Data: N/A for root
Audio: Card: VIA VT8233/A/8235/8237 AC97
Audio Controller driver: snd_via82xx
Sound: ALSA ver: 1.0.25
Network: Card: VIA VT6102 [Rhine-II] driver: via-rhine
Drives: HDD Total Size: (1120.2GB,14.2% used) ()
1: id: /dev/sda model: ST31000528AS size: 1000.2GB
2: id: /dev/sdb model: WDC_WD1200AB size: 120.0GB
Thanks in advance.
musher0
- Attachments
-
- alphaOS-2-what-shows-after-boot!.jpg
- (56.94 KiB) Downloaded 292 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
musher0, you're not the only one; same screen on my Rage 128
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
Hex musher0, I don't think you're doing anything wrong
This is issue probably caused by missing xf86-video-ati package - assumed that error appears before Xorg should start, not right on startup
following xorg video drivers are included:
xf86-video-fbdev-0.4.3-3.spkg
xf86-video-intel-2.21.3-1.spkg
xf86-video-nv-2.1.20-3.spkg
xf86-video-vesa-2.3.2-2.spkg
I thought this generic vesa driver would work for everyone...
This is issue probably caused by missing xf86-video-ati package - assumed that error appears before Xorg should start, not right on startup
following xorg video drivers are included:
xf86-video-fbdev-0.4.3-3.spkg
xf86-video-intel-2.21.3-1.spkg
xf86-video-nv-2.1.20-3.spkg
xf86-video-vesa-2.3.2-2.spkg
I thought this generic vesa driver would work for everyone...
Thanks, simagil, for reassuring me (and thanks also to "session"). I'll have to wait for the next version, I guess!simargl wrote:Hex musher0, I don't think you're doing anything wrong
This is issue probably caused by missing xf86-video-ati package - assumed that error appears before Xorg should start, not right on startup
following xorg video drivers are included:
xf86-video-fbdev-0.4.3-3.spkg
xf86-video-intel-2.21.3-1.spkg
xf86-video-nv-2.1.20-3.spkg
xf86-video-vesa-2.3.2-2.spkg
I thought this generic vesa driver would work for everyone...
Anyway, keep up the good work!
BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Re: alphaOS
It's not possible to include pacman because it would be broken, and I believe that every OSrameshiyer wrote:Dear Simargl.
My humble request is to include Pacman also in alphaos. This is very easy to use and a versatile package handler. Moreover, powerful also. I like it very much. Others also having same opinion.
should have just one package manager. Just try spkg -a pkgname, and it will convert PKGBUILD
from Arch repository or from AUR, to def script; compiling new package is so easy that way.
Re: alphaOS
It would be nice to have a little example walk thru on how to take a 'pacman' package and make it an alpha-package.simargl wrote:It's not possible to include pacman because it would be broken, and I believe that every OSrameshiyer wrote:Dear Simargl.
My humble request is to include Pacman also in alphaos. This is very easy to use and a versatile package handler. Moreover, powerful also. I like it very much. Others also having same opinion.
should have just one package manager. Just try spkg -a pkgname, and it will convert PKGBUILD
from Arch repository or from AUR, to def script; compiling new package is so easy that way.
When Alpha loads additional SFSs does it update the list of packages installed?
Qt4 package is compiling, and expect it soon to appear in the repository
darkcity,
How to install Arch package in Alpha OS?
- script called paka used for making ArchPup is still here in Alpha, so you can install
any Arch package from any date. package is first converted to spkg format and then installed:
1) (optional) open /usr/bin/paka and change date if you want (default date="2013/03/18")
2) type: paka -Syu. This will make packages list
3) Search for package: paka -Ss pkgname
4) Convert and install package: paka -S fullpackagename
5) Convert but do not install package:paka -Sd fullpackagename
Important: Script does not resolve dependencies, and 2nd argument must be full package name
This is for directly installing Arch packages, I prefer to convert PKGBUILD to def and then compile package in Alpha OS,
although sometimes it only make sense to use Arch packages. For example gparted in Alpha is just converted Arch package
as compiling whole gtkmm, glibmm, cairomm.... for just one program would be ridiculous.
How to convert PKGBUILD from Arch to compatible def script?
spkg -a pkgname
Conversion is very good but not perfect; for example package function may require editing and package category is always set to development.
This works for ALL Arch packages, for those in official repositories and also for AUR https://aur.archlinux.org/
darkcity,
How to install Arch package in Alpha OS?
- script called paka used for making ArchPup is still here in Alpha, so you can install
any Arch package from any date. package is first converted to spkg format and then installed:
1) (optional) open /usr/bin/paka and change date if you want (default date="2013/03/18")
2) type: paka -Syu. This will make packages list
3) Search for package: paka -Ss pkgname
4) Convert and install package: paka -S fullpackagename
5) Convert but do not install package:paka -Sd fullpackagename
Important: Script does not resolve dependencies, and 2nd argument must be full package name
This is for directly installing Arch packages, I prefer to convert PKGBUILD to def and then compile package in Alpha OS,
although sometimes it only make sense to use Arch packages. For example gparted in Alpha is just converted Arch package
as compiling whole gtkmm, glibmm, cairomm.... for just one program would be ridiculous.
How to convert PKGBUILD from Arch to compatible def script?
spkg -a pkgname
Conversion is very good but not perfect; for example package function may require editing and package category is always set to development.
This works for ALL Arch packages, for those in official repositories and also for AUR https://aur.archlinux.org/