The only furniture available for me to customize is the Basic Large Table, Basic Chair and the Basic Wardrobe. Anyone else have this problem?
I will be making a model of an event location to test out setups for work. I suggested building it in Planet Zoo when someone mentioned ‘it be nice to have a model’ and they loved the idea. Now I’m kind of doubting between sims and planet zoo cause I will need to put lots of furniture as well and sims is better for that. Now I’m wondering if anyone has any good links to some nice furniture from the Planet Zoo workshop? I’m gonna need a bunch of couches, chairs, high tables, etc.
So I have this friend who I have a lot of history with that I guess is pertinent here so sorry if this is long. I’m getting married a year from now and I’m on the fence of what to do regarding STD/invites for her. Backstory:
I was best friends with this girl for about 14 years. We were so close we used to call each other sisters; we would talk every day and call each other often etc. We had a falling out a few years in; she had run off and gotten married and came back 6 months later with like a “surprise I’m married now!” And expected me to be ok with it. I was lowkey offended that she never even told me she was getting married but I didn’t bring that up at all because I was more so concerned about her life path because she was so young like right out of high school. I kept it real with her and gently asked what she planned to do, what about her plans for college, how are they going to support themselves, etc. She did not take it well and we didn’t talk for a few years after that.
About 3 years later I saw she had moved back to town and I missed her so I messaged her if we could get together and catch up. This rekindled our friendship and we became close again. She also apologized for what happened between us and promised she would never do that again (disappearing, etc). Things were back to normal for several years.
I met my fiancé and was dating him for about a year when she called me and told me she was getting a divorce. I was actually on my first real vacation with my fiancé (boyfriend at the time) and I talked to her on the phone for like an hour consoling her. I spent the next year supporting her through a very contentious divorce, giving her lots of advice, helping her with strategy and how to shield her kids from everything that was happening.
About a year and a half ago we had another falling out. Although it wasn’t really a fight or anything, but I was annoyed so I didn’t message her back and we didn’t talk for about 5-6 months. My boyfriend wanted to try to repair our relationship and texted her but she said she hadn’t heard from me and wanted the two of us to work it out without him getting involved. Eventually I did reach out, just to check in and say we should catch up etc just like we had the first time we had fixed our friendship. She did respond but things were just never the same. I reached out probably 5 times after that. She would respond but never texted me first, agreed that we should catch up but never followed through, etc.
Then my birthday passed and she knew about it, but never reached out to greet me. Then I got engaged and she saw it on social media, but never congratulated me. Since I was getting messages from people I hadn’t talked to in 10-15 years I felt like she was really making a statement.
Despite all this I was still planning on inviting her. I figured we had been important to each other for so long, that I still wanted to make sure she knew that even if we were having issues. We had always said we were like sisters for life despite anything that happened between us etc. We had even talked about before that she would be my MOH if I were to get married, her kids would be in the bridal party etc. Obviously this was no longer on the table considering the state of our relationship and the timing because I needed someone I could actually work with now since the wedding is a year away. I figured I would send her a STD (which would ask people to input their addresses for invites) and this would hopefully open the door for reconciliation.
That is until all of a sudden she posted that she got married. For the second time I was not only not invited, I was not even informed it was happening. I didn’t know she had gotten engaged.
So now idk what to do. My fiancé thinks I can still send her a STD as an olive branch, and if she doesn’t respond with her address then it is what it is and she won’t get an invite. But my other friend said the etiquette is that anyone who gets a STD should get an invite. Literally everyone else has told me to not invite her because she no longer deserves one. And that she didn’t consider me therefore I should give her the same treatment.
I also know at this point it seems like she wouldn’t come anyway so really it’s probably moot. But should I send a STD and see if she inputs her address or not? Or should I wait until next year and gauge where the relationship is and just send an invite if warranted at that time? Should I send an invite anyway knowing she will just decline or not respond (but what if she just decides to show up)? I wouldn’t want to have to chase her down for an RSVP in that case bc I feel like it would be super awkward.
I have a VC1S type VPS instance since 2016. Scaleway has deprecated the "bootscript" booting method which was initially used by default some years ago, unfortunately without providing a method to perform in-place migration for current "local boot" method for this type of instance.
The
official migration documentation provides the steps to convert only newer types of instances which were initially configured for UEFI booting, and tells us to export all the data, recreate the disk and attach it to a new instance otherwise, which is the case with VC1-x, X64-x, Start1-x types.
My VC1S type of machine is a legacy one and not offered anymore, but more importantly, it's much cheaper than the current instance families. that's why I'd like to keep it instead of creating new type of instance with the old data.
The major inconvenience is that VC1-x, X64-x, Start1-x come with no partition table and partitions on local disk: the ext4 file system is created directly on the disk, without the bootloader or even kernel (it is provided by the bootscript/hypervisor). This kind of partitioning could not be used for regular UEFI booting. We'll move the data partition, make the partition table and create the EFI partition for it to boot.
BEFORE YOU BEGIN
Create a snapshot of your disk using Scaleway interface, just in case something goes wrong. Wait until it finishes creating.
The steps we'll take to convert the data:
- Install the kernel and grub packages to the OS
- Shrink the filesystem size
- Move the filesystem data in-place further to the disk
- Create GPT partition table, EFI and data partitions
- Install the bootloader (GRUB) in UEFI mode
- Fill in fstab
All is based on Debian 10.
1. Install the packages
You'll need at least the kernel and the bootloader. I've also installed "ifupdown", as for some reason it was missing in my installation and no network was configured after all the steps (the console access worked though).
# apt install linux-image-amd64 grub-efi-amd64 ifupdown
Make sure that /boot has the vmlinuz and initrd files
# ls /boot config-4.19.0-24-cloud-amd64 initrd.img-4.19.0-24-cloud-amd64 System.map-4.19.0-24-cloud-amd64 vmlinuz-4.19.0-24-cloud-amd64
Make sure grub-install command is present (you don't need to install the bootloader yet)
# grub-install --version grub-install (GRUB) 2.06-3~deb10u3
2. Shrink the filesystem size
Now reboot to the rescue image of Scaleway. poweroff from the console, go to Advanced Settings, select "Use rescue image", boot the machine.
Once it's booted, login to the machine over SSH, you'll be in a rescue mode. It boots a special image from another disk, allowing unrestricted manipulations with your local disk.
Ensure you have your local disk with the filesystem
# cat /dev/vda file - /dev/stdin: Linux rev 1.0 ext4 filesystem data, UUID=1865917f-d4e9-4bcf-b624-de9dc97d0f20 (extents) (large files) (huge files)
Perform the filesystem check:
# fsck.ext4 -f /dev/vda e2fsck 1.46.5 (30-Dec-2021) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/vda: 178933/3055616 files (1.1% non-contiguous), 2852413/12207031 blocks
Check the filesystem size:
# dumpe2fs /dev/vda grep -F 'Block count' dumpe2fs 1.46.5 (30-Dec-2021) Block count: 12207031
This is 12207031
blocks × 4096 block size = 49999998976
bytes (50 GB)
Now shrink the partition size to the minimal amount, to ease its moving:
-M Shrink the file system to minimize its size as much as possible, given the files stored in the file system. # resize2fs -M /dev/vda resize2fs 1.46.5 (30-Dec-2021) Resizing the filesystem on /dev/vda to 3045809 (4k) blocks. The filesystem on /dev/vda is now 3045809 (4k) blocks long.
This took about 7 minutes and shrunk the filesystem from 50 GB down to 12.4 GB, without any free space inside the filesystem.
Now the filesystem is
3045809 blocks in size.
3. Move the filesystem data in-place further to the disk
This is the most important step which could and will irreversibly corrupt your filesystem if done incorrectly.
In order to create the partition table and additional EFI partition, we need to move the existing filesystem, which begins right from the very first sector of the local drive, somewhere further away, down the disk. I recommend moving it for 128MiB (134217728 byte) to the right. This is more than enough for the partition table and EFI partition, where the bootloader would be stored.
We'll need to install GNU ddrescue to the rescue environment:
# apt install gddrescue
GNU ddrescue allows to copy the data
backwards (in reverse, starting from the last block) which is very important in our case, as we're copying the data "from the left to the right" of the disk. Otherwise the data would be irrecoverably corrupted.
The syntax as follows:
ddrescue --reverse --size= --input-position=0 --output-position= --sector-size=512 --cluster-size=256 --same-file --force --ask /dev/vda /dev/vda
The filesystem size could be calculated as shown in the example above (multiply filesystem block count by 4096, the block size). I'm going to move the filesystem 134217728 bytes to the right. The command in my case is:
# ddrescue --reverse --size=12475633664 --input-position=0 --output-position=134217728 --sector-size=512 --cluster-size=256 --same-file --force --ask /dev/vda /dev/vda GNU ddrescue 1.23 About to copy 12475 MBytes from '/dev/vda' [UNKNOWN] (50000000000) to '/dev/vda' [UNKNOWN] (50000000000) Proceed (y/N)? y Press Ctrl-C to interrupt ipos: 8131 MB, non-trimmed: 0 B, current rate: 210 MB/s opos: 8265 MB, non-scraped: 0 B, average rate: 160 MB/s non-tried: 8131 MB, bad-sector: 0 B, error rate: 0 B/s rescued: 4343 MB, bad areas: 0, run time: 27s pct rescued: 34.81%, read errors: 0, remaining time: 51s time since last successful read: 0s Copying non-tried blocks... Pass 1 (backwards)
This took about 2 minutes.
Check that everything is fine by issuing:
# dd if=/dev/vda iflag=skip_bytes skip=134217728 file - /dev/stdin: Linux rev 1.0 ext4 filesystem data, UUID=1865917f-d4e9-4bcf-b624-de9dc97d0f20 (extents) (large files) (huge files)
4. Create GPT partition table, EFI and data partitions
Now we need to create the partition table and two partitions: one for EFI booting, another is for our moved filesystem.
Use cfdisk for that:
# cfdisk /dev/vda
Create GPT partition table, then 1 new partition of "260096s" size (260096 sectors) and set the type of it to "EFI system", then create another partition for the remaining of the disk.
You should see something like this:
Disk: /dev/vda Size: 46.6 GiB, 50000000000 bytes, 97656250 sectors Label: gpt, identifier: B6341233-F14A-334D-A2F7-74BE5649F848 Device Start End Sectors Size Type >> /dev/vda1 2048 262143 260096 127M EFI System /dev/vda2 262144 97656216 97394073 46.5G Linux filesystem
Make sure that start sector of /dev/vda2 is the same value as the amount you've moved your partition for. The sector size is 512 bytes in this case (and the block size of the filesystem is 4096).
262144 × 512 = 134217728
Press "write" to save your data on disk.
Now we'll mount our filesystem as partition, to make sure that everything was done correctly:
# mkdir m # mount /dev/vda2 m # ls m bin dev home initrd.img.old lib64 media opt root sbin sys usr vmlinuz boot etc initrd.img lib lost+found mnt proc run srv tmp var vmlinuz.old # umount m
Now you can enlarge your filesystem again:
# resize2fs /dev/vda2
It's time to create the EFI file system. It should be FAT32 (vfat):
# mkfs.vfat /dev/vda1 mkfs.fat 4.2 (2021-01-31)
5. Install the bootloader (GRUB) in UEFI mode
Installing the bootloader from the other system is always a bit tricky. For maximum compatibility, we'll install the original bootloader from Debian in chroot environment. First we need to mount /proc, /sys and /dev mount points from the host (rescue system) to our filesystem, and then chroot to it.
# mount /dev/vda2 ./m # mount --bind /proc ./m/proc # mount --bind /sys ./m/sys # mount --bind /dev ./m/dev # mkdir ./m/boot/efi # mount /dev/vda1 ./m/boot/efi # chroot m
In the chroot environment, execute the following:
# grub-install --removable --target=x86_64-efi # grub-install --target=x86_64-efi
Next we need to generate GRUB configuration file. This require some modifications for the Scaleway. Open /etc/default/grub and change GRUB_CMDLINE_LINUX_DEFAULT line to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet console=tty1 console=ttyS0"
Execute configuration file generation:
# update-grub
This will copy all the needed files to our EFI partition and generate grub.cfg bootloader configuration file. Don't be scared of the "warning: Discarding improperly nested partition" messages, they are safe to skip. For non-Debian and non-Ubuntu OS you'll need to generate configuration file using grub-mkconfig, something like:
# grub-mkconfig -o /boot/grub/grub.cfg
6. Fill in fstab
Add the following lines in ./m/etc/fstab file, otherwise your root mount point would be read-only on the next boot:
/dev/vda2 / ext4 defaults 0 1 /dev/vda1 /boot/efi vfat defaults 0 2
And that's it! All is left is to exit the chroot and unmount the partitions:
# exit # exit from chroot # umount ./m/boot/efi # umount ./m/proc # umount ./m/sys # umount ./m/dev
Power off the machine
# poweroff
Go to Advanced Settings in the Scaleway panel, select "Local Boot" method, boot the machine.
If everything is done correctly, the machine should boot and be reachable from the network. If you can't reach it over SSH, open the console in the panel and debug it from there.
It boots, gets an IP but no data on the dashboard
I reset to factory, here is my log, if anyone can help it would be supremely appreciated:
--
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b3c040, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu
u/cddf0000 s19916 r8192 d21044 u49152
pcpu-alloc: s19916 r8192 d21044 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 209340K/245760K available (6317K kernel code, 243K rwdata, 1932K rodata, 1024K init, 232K bss, 20036K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090e410 (9242 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b3cda0 ( 244 kB)
.bss : 0xc0b3cda0 - 0xc0b77024 ( 233 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32. RCU restricting CPUs from NR\_CPUS=4 to nr\_cpu\_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[
[email protected]](mailto:
[email protected])>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 6964K (cd42d000 - cdafa000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 159, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
cdns-i2c e0005000.ps7_i2c: 100 kHz mmio e0005000 irq 154
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: disable subpage write
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: NAND_ECC_HW
nand: NAND_ECC_HW_SYNDROME
mtd->writesize = 2048
ecc->strength = 1
ecc->size = 2048
mtd->writesize = 2048
chip->ecc_strength_ds = 4
chip->ecc_step_ds = 512
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000000140000
8 ofpart partitions found on MTD device pl35x-nand
Creating 8 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-dts-marker-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000005200000 : "sig"
0x000005200000-0x000006000000 : "reserve1"
0x000006000000-0x000007000000 : "upgrade-ramfs"
0x000007000000-0x00000a800000 : "upgrade-file"
0x00000a800000-0x000010000000 : "reserve2"
nf_conntrack version 0.5.0 (3635 buckets, 14540 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs warning (device ram0): ext4_update_dynamic_rev:746: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,errors=remount-ro
devpts: called with bogus options
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 11/4, WL threshold: 4096, image sequence number: 262741923
ubi0: available PEBs: 36, total reserved PEBs: 28, PEBs reserved for bad PEB handling: 4
ubi0: background thread "ubi_bgt0d" started, PID 729
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 733
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, small LPT model
ubi2: attaching mtd4
ubi2: scanning is finished
ubi2: empty MTD device detected
ubi2: attached mtd4 (name "reserve1", size 14 MiB)
ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi2: good PEBs: 112, bad PEBs: 0, corrupted PEBs: 0
ubi2: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi2: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 2067240595
ubi2: available PEBs: 104, total reserved PEBs: 8, PEBs reserved for bad PEB handling: 4
ubi2: background thread "ubi_bgt2d" started, PID 739
UBIFS (ubi2:0): default file-system created
UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 745
UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "misc"
UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi2:0): FS size: 11935744 bytes (11 MiB, 94 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
UBIFS (ubi2:0): reserved for root: 563754 bytes (550 KiB)
UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID EEB062CF-C448-4C2D-B662-A49819A4078C, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
random: id2mac urandom read with 1 bits of entropy available
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfbe4000
*base_vir_addr = 0xb051
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
===========================================Miner log===========================================
time="1970-01-01 00:00:10" level=error pid=886 msg="invalid URL -- ''"
time="1970-01-01 00:00:10" level=error pid=886 msg="invalid URL -- ''"
time="1970-01-01 00:00:10" level=error pid=886 msg="invalid URL -- ''"
time="1970-01-01 00:00:10" level=info pid=886 msg="release version"
time="1970-01-01 00:00:10" level=info pid=886 msg="asic mode"
time="1970-01-01 00:00:10" level=error pid=886 msg="No valid pools, please configure them first!"
time="1970-01-01 00:00:10" level=notice pid=886 msg="algo ltc fan_control_mode 2"
time="1970-01-01 00:00:10" level=notice pid=886 msg=platform_init
time="1970-01-01 00:00:10" level=info pid=886 msg="mmap fpga_mem_addr_hal = 0xb5cd9000
"
time="1970-01-01 00:00:10" level=info pid=886 msg="HARDWARE_VERSION = 0x2000b051
"
time="1970-01-01 00:00:10" level=notice pid=886 msg="chain_offset 0, chain 1"
time="1970-01-01 00:00:12" level=notice pid=886 msg="chain_offset 0, chain 1, pic firmware verion = 0x89"
time="1970-01-01 00:00:12" level=notice pid=886 msg="chain_offset 1, chain 2"
time="1970-01-01 00:00:15" level=notice pid=886 msg="chain_offset 1, chain 2, pic firmware verion = 0x89"
time="1970-01-01 00:00:15" level=notice pid=886 msg="chain_offset 2, chain 3"
time="1970-01-01 00:00:18" level=notice pid=886 msg="chain_offset 2, chain 3, pic firmware verion = 0x89"
time="1970-01-01 00:00:18" level=notice pid=886 msg="reset fpga"
time="1970-01-01 00:00:18" level=notice pid=886 msg="Begain check_fan_valiad"
time="2023-06-07 17:06:00" level=notice pid=886 msg="check_fan_valiad, check_fan_speed ok, fan_num = 4"
time="2023-06-07 17:06:00" level=notice pid=886 msg="Miner compile time: Mon Jan 24 16:01:20 CST 2022 type: Antminer L7"
time="2023-06-07 17:06:00" level=info pid=886 msg="godminer Version = 0xB051 1.0.0_release_dirty_master_4c4db04fc8fb8ce1a21da1db2301f261664943c2_Jan 24 2022 16:18:48"
time="2023-06-07 17:06:00" level=notice pid=886 msg="miner thread with 3 backend runtime created pid 886"
time="2023-06-07 17:06:00" level=notice pid=886 msg="opt_algo 6, ltc"
time="2023-06-07 17:06:02" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:02" level=error pid=886 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:04" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:04" level=error pid=886 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:07" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:07" level=error pid=886 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:07" level=error pid=886 msg="Data load fail for chain 1.
"
time="2023-06-07 17:06:09" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:09" level=error pid=886 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:11" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:11" level=error pid=886 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:14" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:14" level=error pid=886 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:14" level=error pid=886 msg="Data load fail for chain 2.
"
time="2023-06-07 17:06:16" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:16" level=error pid=886 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:18" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:18" level=error pid=886 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:21" level=error pid=886 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:21" level=error pid=886 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:21" level=error pid=886 msg="Data load fail for chain 3.
"
time="2023-06-07 17:06:21" level=error pid=886 msg="Chain1 load EEPROM error."
time="2023-06-07 17:06:21" level=notice pid=886 msg="Error! Chain [1] EEPROM data corrupted"
time="2023-06-07 17:06:29" level=error pid=1167 msg="invalid URL -- ''"
time="2023-06-07 17:06:29" level=error pid=1167 msg="invalid URL -- ''"
time="2023-06-07 17:06:29" level=error pid=1167 msg="invalid URL -- ''"
time="2023-06-07 17:06:29" level=info pid=1167 msg="release version"
time="2023-06-07 17:06:29" level=info pid=1167 msg="asic mode"
time="2023-06-07 17:06:29" level=error pid=1167 msg="No valid pools, please configure them first!"
time="2023-06-07 17:06:29" level=notice pid=1167 msg="algo ltc fan_control_mode 2"
time="2023-06-07 17:06:29" level=notice pid=1167 msg=platform_init
time="2023-06-07 17:06:29" level=info pid=1167 msg="mmap fpga_mem_addr_hal = 0xb5cd6000
"
time="2023-06-07 17:06:29" level=info pid=1167 msg="HARDWARE_VERSION = 0x2000b051
"
time="2023-06-07 17:06:29" level=notice pid=1167 msg="chain_offset 0, chain 1"
time="2023-06-07 17:06:32" level=notice pid=1167 msg="chain_offset 0, chain 1, pic firmware verion = 0x89"
time="2023-06-07 17:06:32" level=notice pid=1167 msg="chain_offset 1, chain 2"
time="2023-06-07 17:06:35" level=notice pid=1167 msg="chain_offset 1, chain 2, pic firmware verion = 0x89"
time="2023-06-07 17:06:35" level=notice pid=1167 msg="chain_offset 2, chain 3"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="chain_offset 2, chain 3, pic firmware verion = 0x89"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="reset fpga"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="Begain check_fan_valiad"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="check_fan_valiad, check_fan_speed ok, fan_num = 4"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="Miner compile time: Mon Jan 24 16:01:20 CST 2022 type: Antminer L7"
time="2023-06-07 17:06:38" level=info pid=1167 msg="godminer Version = 0xB051 1.0.0_release_dirty_master_4c4db04fc8fb8ce1a21da1db2301f261664943c2_Jan 24 2022 16:18:48"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="miner thread with 3 backend runtime created pid 1167"
time="2023-06-07 17:06:38" level=notice pid=1167 msg="opt_algo 6, ltc"
time="2023-06-07 17:06:40" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:40" level=error pid=1167 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:42" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:42" level=error pid=1167 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:45" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:45" level=error pid=1167 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:06:45" level=error pid=1167 msg="Data load fail for chain 1.
"
time="2023-06-07 17:06:47" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:47" level=error pid=1167 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:49" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:49" level=error pid=1167 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:52" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:52" level=error pid=1167 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:06:52" level=error pid=1167 msg="Data load fail for chain 2.
"
time="2023-06-07 17:06:54" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:54" level=error pid=1167 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:56" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:56" level=error pid=1167 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:59" level=error pid=1167 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:06:59" level=error pid=1167 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:06:59" level=error pid=1167 msg="Data load fail for chain 3.
"
time="2023-06-07 17:06:59" level=error pid=1167 msg="Chain1 load EEPROM error."
time="2023-06-07 17:06:59" level=notice pid=1167 msg="Error! Chain [1] EEPROM data corrupted"
time="2023-06-07 17:07:14" level=error pid=1485 msg="invalid URL -- ''"
time="2023-06-07 17:07:14" level=error pid=1485 msg="invalid URL -- ''"
time="2023-06-07 17:07:14" level=info pid=1485 msg="release version"
time="2023-06-07 17:07:14" level=info pid=1485 msg="asic mode"
time="2023-06-07 17:07:14" level=notice pid=1485 msg="algo ltc fan_control_mode 2"
time="2023-06-07 17:07:14" level=notice pid=1485 msg=platform_init
time="2023-06-07 17:07:14" level=info pid=1485 msg="mmap fpga_mem_addr_hal = 0xb5d0a000
"
time="2023-06-07 17:07:14" level=info pid=1485 msg="HARDWARE_VERSION = 0x2000b051
"
time="2023-06-07 17:07:14" level=notice pid=1485 msg="chain_offset 0, chain 1"
time="2023-06-07 17:07:17" level=notice pid=1485 msg="chain_offset 0, chain 1, pic firmware verion = 0x89"
time="2023-06-07 17:07:17" level=notice pid=1485 msg="chain_offset 1, chain 2"
time="2023-06-07 17:07:20" level=notice pid=1485 msg="chain_offset 1, chain 2, pic firmware verion = 0x89"
time="2023-06-07 17:07:20" level=notice pid=1485 msg="chain_offset 2, chain 3"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="chain_offset 2, chain 3, pic firmware verion = 0x89"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="reset fpga"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="Begain check_fan_valiad"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="check_fan_valiad, check_fan_speed ok, fan_num = 4"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="Miner compile time: Mon Jan 24 16:01:20 CST 2022 type: Antminer L7"
time="2023-06-07 17:07:23" level=info pid=1485 msg="godminer Version = 0xB051 1.0.0_release_dirty_master_4c4db04fc8fb8ce1a21da1db2301f261664943c2_Jan 24 2022 16:18:48"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="miner thread with 3 backend runtime created pid 1485"
time="2023-06-07 17:07:23" level=notice pid=1485 msg="opt_algo 6, ltc"
time="2023-06-07 17:07:25" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:25" level=error pid=1485 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:07:28" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:28" level=error pid=1485 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:07:30" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:30" level=error pid=1485 msg="Data decode fail for chain 1.
"
time="2023-06-07 17:07:30" level=error pid=1485 msg="Data load fail for chain 1.
"
time="2023-06-07 17:07:32" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:32" level=error pid=1485 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:07:34" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:34" level=error pid=1485 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:07:37" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:37" level=error pid=1485 msg="Data decode fail for chain 2.
"
time="2023-06-07 17:07:37" level=error pid=1485 msg="Data load fail for chain 2.
"
time="2023-06-07 17:07:39" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:39" level=error pid=1485 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:07:41" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:41" level=error pid=1485 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:07:44" level=error pid=1485 msg="EEPROM eeprom_key_version or eeprom_encryption_algorithm error! eeprom_key_version:4, eeprom_encryption_algorithm:0"
time="2023-06-07 17:07:44" level=error pid=1485 msg="Data decode fail for chain 3.
"
time="2023-06-07 17:07:44" level=error pid=1485 msg="Data load fail for chain 3.
"
time="2023-06-07 17:07:44" level=error pid=1485 msg="Chain1 load EEPROM error."
time="2023-06-07 17:07:44" level=notice pid=1485 msg="Error! Chain [1] EEPROM data corrupted"
In England. Hi there, I’m at a bit of a loss as to what to do. I’m autistic and I hate confrontation. The mere thought of it makes me want to shrivel up and hide but I’m in a situation where it’s unavoidable.
I’m going to try and explain this situation as well as I can but I’m really angry and upset so I apologise if anything is unclear. Apologies, this post is going to be quite long.
Basically, I live in a houseshare with two other people. Our tenancy ends on 19th July. One of my housemates moved out today because she decided to go travelling for at least 3 months, meaning she won’t be here for the end of the tenancy. She has had this planned for at least 6 months.
I began to worry a few weeks ago when I noticed that she hadn’t started organising or packing for her move at all. Baring in mind, she has 2 full rooms in this house with loads of stuff that belongs to her. She didn’t start packing until 1 week ago and even then, she only did 2 half days worth and has spent the rest of the time working, getting drunk and going to festivals.
Today she moved out and she has left A LOT of stuff. Like, big pieces of furniture like tables and armchairs etc. She also left everything absolutely filthy. Like, actual dirt everywhere including used cat litter from HER cats. Just describing it doesn’t justify just how awful it is!!
We asked her via messenger what she planned on doing regarding the rest of her stuff and cleaning and she got angry with us and said “I’m not even out of the country yet, you need to pipe down”. No apology for leaving it the way she has. My other housemate and I both have chronic anxiety and we worry about not getting our deposits back for the house and now she has made it 10x harder for us.
Talking to friends and family, I think we need to give her the ultimatum of “sort this out or we’ll throw your stuff away” but I am so so scared of her reaction.
Others have suggested giving her a time period and if she doesn’t send anyone to remove her stuff, we will throw it away. Is this legal? Also, should we let the landlord know about this? She’s on the tenancy.
I don’t know what to do. I’m so angry and upset 😞
I’m having a hard time wrapping my head around everything that has happened since April 25th, the day you left me.
I’ve been on several business trips and I still anticipate coming home to your wagging tail, it’s so hard.
We replaced furniture you used to lay on all day. The house doesn’t feel the same between you not laying on the couch and it not looking the same.
Your bowls are dry. I just want to see you eating from your bowl and to see your smile after you ate, it made me so happy seeing you do that. I used to hate the water dripping from your face after you drank from your bowl, but now, I miss it so.
I want to run over to your bed and say good morning to you. You used to be a grumpy man in the morning, I am too.
I want to take naps with you on the couch, running around all day makes me tired too.
I want to take you for long walks around the neighborhood. You can see all of the bunnies and squirrels and chase after them. You can also pee on every tree that you see and mark them as your own, you own the world.
I want to go into the back yard and take pictures of you and show them off to my friends and family, you hated getting your picture taken though.
I want you to come running over when I open the refrigerator, you loved sniffing our food. When we used to cook and drop something from the stove, we said “hot hot hot hot hot” and you knew that you have to wait a few seconds to eat it.
I want to see you laying in the sun rays at the front door. You loved the warmth of the sun but the cold days of the winter.
When the rained, you used to step in every puddle in sight. I miss cleaning and drying your paws after a rain storm.
I want to take you for another haircut, you had quite the grumpy personality coming home from them.
You loved apples. You loved going apple picking, you loved going with the family to pick and eat fresh apples.
Having people at the house isn’t the same anymore. There’s no dog going to our guests begging for table scraps. No dog to tell us someone is at the door. Do dog barking to say goodbye.
Goodbye. I love you bud. Until we meet again.
A WOMAN SHOULD HAVE....
Enough money within her control to move out... And rent a place of her own even if she never wants to or needs to... Something perfect to wear if the employer or date of her dreams wants to See Her in an hour...
A WOMAN SHOULD HAVE... A youth she's content to leave behind.... A past juicy enough that she's looking forward to retelling it in her Old Age....
A WOMAN SHOULD HAVE... A set of screwdrivers, a cordless drill, and a black lace bra... One friend who always makes her laugh... And one Who lets her cry...
A WOMAN SHOULD HAVE.... A good piece of furniture not previously owned by anyone else in her Family... Eight matching plates, wine glasses with stems, And a recipe for a meal that will make her guests feel Honored... A feeling of control over her destiny...
EVERY WOMAN SHOULD KNOW... How to fall in love without losing herself.. HOW TO QUIT A JOB, BREAK UP WITH A LOVER, AND CONFRONT A FRIEND WITHOUT RUINING THE FRIENDSHIP... When to try harder... And WHEN TO WALK AWAY...
EVERY WOMAN SHOULD KNOW... That she can't change the length of her calves, The width of her hips, or the nature of her parents.. That her childhood may not have been perfect... But it's over...
EVERY WOMAN SHOULD KNOW... What she would and wouldn't do for love or more... How to live alone... Even if she doesn't like it...
EVERY WOMAN SHOULD KNOW... Whom she can trust, Whom she can't, And why she shouldn't take it personally...
EVERY WOMAN SHOULD KNOW... Where to go... Be it to her best friend's kitchen table... Or a charming inn in the woods... When her soul needs soothing...
EVERY WOMAN SHOULD KNOW... What she can and can't accomplish in a day... A month... And a year... ॐ
Written By: Pamela Redmond Satran