This could be related to the bug mentioned in However, having made the break from the restrictive organisation of murga forum to its own WeeDogLinux forum it seems appropriate to complete that break.I try to summarize the results of my experience:ġ) there is no difference in results using Unebootin and fat32 file system or TazUsb Installer and ext3 file system: in both cases writefs doesn't work and doesn't save current configuration to usb running writefs produce a rootfs.gz on root directory in ram and this file is not copied anyway to boot directory in usb: in order to do it, you have to manually copy file from / to /media/diskĢ) in order to save configuration automatically, you have to run writefs as root user, not as tux ordinary user: in this case rootfs.gz is created correctly in usb and also a backup copy is generated on the same drive ģ) the problem is that creating rootfs.gz apparently delete Tux user configuration: in fact, after creating it, it is impossible to login as tux (it is only possible to log in as root). Up until now I was happy to announce new WeeDogLinux releases since some murga forum members have in the past expressed interest during the early development days of FirstRib WeeDog last year. Some of these non-puppy-derived distros have had their main feedback threads on this murga forum for six or seven years or more - perhaps that should never have happened, but people tend to develop what they wish. That WeeDogLinux initrd/init was created entirely from scratch, and from first principles (originally for my own further education) without any thought or attempt to mirror the approach of any other frugally installable distribution.įurthermore, I have made it very clear for a long time that I was unhappy with the organisation of the Murga forum, particulaly in it, in my view, not being willing to provide proportional space/exposure to the now many alternative distros being developed by murga-forum members. The WeeDogLinux build systems use no Puppy Linux code and relies on its own, unique, and entirely independent initrd/init overlayfs related code to provide its functionality, which includes what was its unique designed in ability to load either sfs files or uncompressed directories into the filesystem layers (via overlayfs). None of the current or planned WeeDogLinux variants are in any way derivatives of Puppy Linux. I cannot guarantee the currency of any downloads of build scripts or isos retrieved from any other source, particularly since WeeDogLinux variants are under regular active development. As you know WeeDogLinux has its own forum and, to avoid user confusion, all downloads should be retrieved from the official downloads there. Wiak wrote: The above announcement regarding WeeDogLinux SliTaz flavour will be the final announcement regarding new WeeDogLinux releases on this murga-forum. Sensors: None detected - is lm-sensors installed and configured? RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present IF: eth0 state: down mac: 00:1a:4b:82:66:40Ĭard-2: Intel PRO/Wireless 4965 AG or AGN Network Connection driver: iwl4965 Network: Card-1: Broadcom NetLink BCM5787M Gigabit Ethernet PCI Express driver: tg3 X.org: 1.15.1 drivers: intel (unloaded: vesa) tty size: 80x24 Advanced Data: N/A for rootĪudio: Card: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA ver: k3.14.56 Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) F.0B date: ĬPU: Dual core Intel Core2 Duo CPU T7500 (-MCP-) cache: 4096 KB flags: (lm nx pae sse sse2 sse3 ssse3 vmx)Ĭlock Speeds: 1: 1200.00 MHz 2: 800.00 MHz Mobo: Hewlett-Packard model: 30C0 version: KBC Version 71.2Aīios: Hewlett-Packard version: 68DDU Ver. Machine: System: Hewlett-Packard (portable) product: N/A version: F.0B System: Host: dellbot Kernel: 3.14.56 i686 (32 bit) Desktop: JWM git-976 Distro: tahrpup 6.0.5 I did a frugal install of weedog slitaz on ext3 partition, but the boot process hangs as seen in the attached pic.
0 Comments
Leave a Reply. |